Replacing DC problem

[Hong]

I want to replace the DC with a better performance one
Here's my steps
1. dcpromo the new DC
2. take over 5 roles from the old DC
3. plug out the old DC to test the functions of new DC (i haven't demote the
old DC yet.)

I find that the client machine cannot access other PCs from the network..

It prompts me this error

<<Computer>> is not accessible
There are currently no logon servers available to service the logon request.
..

I have promoted 2 new DCs and got the same results..
Should I demote the old DC first? but I am afraid it won't work even I demot
e the old DC..

I plug in my old DC back and the network works fine again.

 

[Cary Shultz [A.D. MVP]]

Hong,

You might want to check to make sure that you have a Global Catalog Server
available on the network. So, the 'new' DC should also be a CG. Also, is
DNS running on the new DC? If not, that would create problems.
Additionally, make sure that you make the appropriate changes in DHCP so
that the clients are aware of the new information.

Please look at the following MSKB Article on how to make a Domain Controller
also a Global Catalog Server:

http://support.microsoft.com/?id=313994

HTH,

Cary

 

[Achari Nandipati]

Follow these steps. These may help
1. Run DCPROMO on the new machine as a DC allow it to
replicate with current FSMO DC.
2. Take out the Old FSMO from the network (Make it offline)
3. Force the new machine to be as FSMO ( hardway) to grab
all the five FSMO roles from old one ( it might need a
reboot)

Then the new machine will be the new FSMO DC.

Hope this works . let me know
Achari Nandipati
(e-mail address removed)

 

[Santhosh Srinivasan]

An additional thing to look at are your Wins and DNS entries for the domain.
Have the entries been updated after the FSMO role transfer.

When the PDC emulator role is tranferred over to another DC, the Domain
Master Browser entry requires to be updated in Wins and the FSMO role
entries in DNS also require to be updated. If your newly promoted dc is a
DNS and Wins server ensure that it is pointing back to itself and then do a
NBTSTAT -RR and a ipconfig /registerdns to update the Wins and DNS
respectively.

This should resolve your issues. Your process seems to be correct other than
the GC setup that you are missing.

-Santhosh.

 

[Cary Shultz [A.D. MVP]]

Good point!

Cary

An additional thing to look at are your Wins and DNS entries for the domain.
Have the entries been updated after the FSMO role transfer.

When the PDC emulator role is tranferred over to another DC, the Domain
Master Browser entry requires to be updated in Wins and the FSMO role
entries in DNS also require to be updated. If your newly promoted dc is a
DNS and Wins server ensure that it is pointing back to itself and then do a
NBTSTAT -RR and a ipconfig /registerdns to update the Wins and DNS
respectively.

This should resolve your issues. Your process seems to be correct other than
the GC setup that you are missing.

-Santhosh.