DNS in AD

[Kenneth]

I am having a big problem at one of my clients sites. He
has a SBS 2000 setup already as a workgroup.
I ran dcpromo on the SBS2000 and it ran through like
normal. Then I installed a windows 2003 server, I ran the
adprep tools and everything runs fine, no errors, well
till i run dcpromo on the 2003 server, I then get a error
that it can not resolve the domain name in DNS.
So I looked at the DNS on the SBS2000 server and I
noticed that there is one forward look up zone, and three
records with in it. I then remembered there is supposed
to be more records ones like _tcp, _msdc, and a few more,
nut they are missing. I fould a artical to run the
netdiag /fix, and I followed that and it did not work, so
out of desperation I removed AD from the SBS server,
restarted, removed DNS completly from the system and
restarted again, and ran dcpromo, it asked to setup DNS
and went through with out a problem, but the records that
are need, so I resorted to dropping it back to a
workgroup just to get them back running tonight.

I am so frustrated, Please I need help!!!!!!!!

Thanks
Ken

 

[Nathan]

I am having a big problem at one of my clients sites. He

has a SBS 2000 setup already as a workgroup.

Can you set up the new 2003 server and make it the first
DC and DNS server for the new AD domain?

 

[Lanwench [MVP - Exchange]]

I am having a big problem at one of my clients sites. He
has a SBS 2000 setup already as a workgroup.

SBS can't run in a workgroup - it needs to be a DC in its own domain and has
to hold all the FSMO roles for it. When you install SBS, it creates a domain
by default - don't know how you got it to be in a workgroup unless you
demoted it, which will cause all kinds of problems.

I ran dcpromo on the SBS2000 and it ran through like
normal. Then I installed a windows 2003 server, I ran the
adprep tools and everything runs fine, no errors, well
till i run dcpromo on the 2003 server, I then get a error
that it can not resolve the domain name in DNS.
So I looked at the DNS on the SBS2000 server and I
noticed that there is one forward look up zone, and three
records with in it. I then remembered there is supposed
to be more records ones like _tcp, _msdc, and a few more,
nut they are missing. I fould a artical to run the
netdiag /fix, and I followed that and it did not work, so
out of desperation I removed AD from the SBS server,
restarted, removed DNS completly from the system and
restarted again, and ran dcpromo, it asked to setup DNS
and went through with out a problem, but the records that
are need, so I resorted to dropping it back to a
workgroup just to get them back running tonight.

I don't know that you can do this as you're trying to upgrade an SBS2000
domain to a W2003 domain.

Really not a DNS issue as far as I can see - SBS is limited in what it can
do, although it's a fine product - best to post in an SBS group. I hope you
have good backups. Your SBS server is likely hosed and will need a
reinstall. You can run W2003 as a member server in an SBS2000 domain, but
don't try to promote the W2003 server to a DC.

 

[Kenneth]

-----Original Message-----

Can you set up the new 2003 server and make it the first
DC and DNS server for the new AD domain?
.
I tryed that, figure that would have been easy, but SBS

must be the primary domain controller, so you have to set
SBS as the first controller in the domain.

Ken

 

[Lanwench [MVP - Exchange]]

Thats what I thought as well, that SBS2000 must run a
domain, but the client already had the server up and
running when I got here and he had is as a workgroup, so
he must have demoted it after install.

Then he was likely having a ton of problems.

I was also told the
SBS will only allow one AD Domain controller per domain,
have you heard of this, I know you can only have one SMS
server, but I thought you were able to have another server
joined to AD.

In SBS4x this was true - in SBS2000/2003 you can have other DCs. But the SBS
server still has to be the big kahuna - hold all the FSMO roles, etc.

In my opinion it's time to scratch this whole install (back up their data,
exmerge their mailboxes, presuming Exchange is even functional, which I
doubt) and start over clean.

 

[Ace Fekay [MVP]]

In Lanwench [MVP - Exchange]

Then he was likely having a ton of problems.

<snip>

Hi Lanwench,

Just want to point out about DNS that if he did promote the SBS2000 box, and
its still not registering the SRV properly, he may have chosen a single
label domain name for AD, which of course we all know it won't work
properly.

Cheers!


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[Lanwench [MVP - Exchange]]

In Lanwench [MVP - Exchange]

Then he was likely having a ton of problems.

<snip>

Hi Lanwench,

Just want to point out about DNS that if he did promote the SBS2000
box, and its still not registering the SRV properly, he may have
chosen a single label domain name for AD, which of course we all know
it won't work properly.

Yes indeedy - but I think with SBS if you try to dcpromo down to a member
server in a hence-nonexistent domain it will keep rebooting itself or
something similar (read this in a post recently; have never tried it). So
there are larger problems afoot in that case!!

;-)
LW

 

[Ace Fekay [MVP]]

In Lanwench [MVP - Exchange]

Yes indeedy - but I think with SBS if you try to dcpromo down to a
member server in a hence-nonexistent domain it will keep rebooting
itself or something similar (read this in a post recently; have never
tried it). So there are larger problems afoot in that case!!

Ouch! Double Ouch!!


Ace