AD problems(FSMO, GC) 2

[BTSsupport]

Hi,

I got myself into kind of a mess. I have a windows 2000 server that is the domain controller. I was planning on setting up a new windows 2000 server to act as the domain controller so I could take down the first one and do some maintenence on the machine. Well i joined the second one to the domain and then ran dcpromo. Everything seemed alright, the users were brought over to the new server and they were running fine. A login attempt with the old server shut off failed. So I turned the old one back on, users can login no problem. The problem is when i try to open AD on the second server I get a error saying the server is not operational. When i run dcdiag.exe this is what i get:

"C:\>dcdiag.exe

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\VITFS002
Starting test: Connectivity
VITFS002's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(709f64c8-ded8-46be-aaa4-e26480251370._msdcs.VITAMED.local) could
be resolved, the server name (vitfs002.VITAMED.local) resolved to
IP address (192.168.61.3) and was pingable. Check that the IP ad
is registered correctly with the DNS server.
......................... VITFS002 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\VITFS002
Skipping all tests, because server VITFS002 is
not responding to directory service requests

Running enterprise tests on : VITAMED.local
Starting test: Intersite
......................... VITAMED.local passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
......................... VITAMED.local failed test FsmoCheck"

Please help if you can, if you need more info just let me know,
Thank You

C

 

[mlichstein]

DNS?

How is DNS set up? Is the new DC pointing to the old DC for DNS?

 

[markdmac]

I agree with mlichstein,

Did you setup DNS on the new server? How about DHCP so your clients can still get IP addresses when you take down the old server? Did you make the new server a GC?

How long are you taking the other server down for? A few hours or forever? Don't transfer FSMO roles if it will just be for a short time, but if it will be an extended time you may need to.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[BTSsupport]

Thanks for the responses,

Stupid question, How do you make the new server a GC?

Sorry I am new at AD,

Thanks

 

[markdmac]

In AD Sites and Sevices. Under NTDS Settings for your server. Right click and put a check in the Globabl Catalog box.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[Digitalcandy]

I had to do the same scenario you described a few weeks ago, and here are some things you need to consider:

- Move all five FSMO roles to new server, (move manually follwing MS KB article)
- Make new server a Global Catalog
- Install DHCP on new server, be sure to adjust scope entries
- Install DNS on new server
- Install WINS if you need it


These things should take care of your problems. After all is complete, turn off original DC computer, restart all other servers and a few clients if you can. Check Event Logs.