In
Cabal10 said:
Our network has 4 locations, but the main location is the only one
that has AD, the others have NT4. In our main site we have 3 DC's.
The forest root DC is in the nj1.com domain, but its fully qualified
domain name is server.nj1. There is no .com. This server is also
our FSMO role holder. The other two server are servername.nj1.com. I
am trying to move the FSMO roles and demote it, but when I tried to
transfer the roles I get errors. When I run dcdiag I get DNS guid
errors. I am not sure how fix this server so that it's fully
qualified name is server.nj1.com? Any ideas?
Thanks in advance.
Well, this depends. YOu didn't provide any detail about the configuration
other than mentioning a couple of different names, I'll do my best to
explain your options.
I assume you upgraded your PDC to a Windows 2000, or is it a 2003 domain
controller? That would be the only way the BDCs are part of this domain.
If the AD DNS domain name is actually a single label name as you stated,
then to fix it you have a number of options:
1. Rebuild the AD domain from scratch. But this isn't so easy because you
will lose the NT4 BDCs as part of the domain. You can always promote one of
them to the PDC of the domain, and create a two way trust between that
domain and the new one. But I'm sure you don't want to do that.
2. If Windows 2003, you can possibly use the domain rename tool choosing the
correct name. Preserves the current domain. However if you have Exchange
2000, 2003 or 2007, it will complicate matters and require additional steps.
3. Since you only have the one DC, you can also simply unplug the DC,
promote one of the other NT4 BDCs to the PDC, then reinstall NT4 on the
machine as a BDC, then promote it to the PDC, then upgrade it to Windows
2003 this time choosing the correct name. Long out and drawn, but it
preserves the current domain.
However if the Primary DNS suffix is incorrect on the DC, and/or the FQDN in
the computername properties is incorrect, BUT the AD DNS domain name is not
single label, this is alot easier. This is called a disjointed namespace.
Eg. If Windows 2000, you can use a script to correct it. If 2003, you can
simply change it in Computer Properties, Computer Name tab.
So to better assist:
What is the actual Active Directory DNS domain name? This name shows up
under ADUC.
In addition, please provide the following information.
1. Unedited "ipconfig /all" of the AD domain controller
2. Same for one of your Windows 2000 and/or XP Pro machines that is joined
to the domain
3. Any errors in the event logs on the AD DC (post the EventID# and Source
name)
4. The name of the AD DNS zone name in DNS and if the SRV records exist
5. Re-run dcdiag with switches: 'dcdiag /v /fix' and post the whole result.
--
Regards,
Ace
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 MVP - Directory Services
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.
Infinite Diversities in Infinite Combinations