Replacing domain controller - what did i miss? 3

[SimonDavis]

Hi folks.

I'm trying to remove our old domain controller from the network, and have tried to configure a new server to take over its role.

The problem I have is that when I take the old server down, it kills the network. Nobody can browse anything - it asks for a user/password (which doesn't work). When I fire up the old server, it all works OK.

I did the following (both servers are win2k server, sp4);

- Installed AD on the new server.
- Installed DNS on the new server.
- Seized all FSMO roles to the new server.
- Installed DHCP on the new server
- Checked the new server as a global catalog server.

This was all done 24 hours ago, so i'd assume everything that is going to be updated has been updated.

This is on a single domain, nothing complicated.

Anything obvious I have missed? Do I need to do something special wIth the old server to persuade it to let go of something?

Thanks

 

[SimonDavis]

That's not a bad idea. Certainly nothing to lose - all I'm doing is letting Windows do what I have been trying to do manually.

I reckon Windows is probably better at it than I am!

Will give that a try. Thanks again.

 

[GrimR]

If you have no naming conventions or policies restricting you from renaming the server, I would do as Davetoo suggests only when you dcpromo it back in do it under a different name and IP e.g exch02