I recently added a new Win2008 DC that has the global catalog and is the only computer that will be the fileserver. However, I have an older computer running Win2003 that used to be the DC but still runs AD. The users network cards all point to the new Win2008 DC and its IP address. However, when I run nslookup, the user computers all show the IP of the old Win2003 computer. I tried manually to set the server to the new one on the command line on the user computer, but when I reboot the user computer, it always defaults to the old DC and its IP address. What I am doing wrong?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to point to new domain controller
- Thread starter gattabria
- Start date
- Thread starter
- #3
All of the users on the network with AD seem to point to the old DC even the new DC with Windows2008 server is running DNS. When I remove the old DC, the users cannot even get on the internet. The new DC with Windows 2008 server runs DNS and GC. However, if you run configip - server on a user machine, it always states that the old DC is the server. I am sorry if I did not explain the problem correctly the first time.
- Thread starter
- #4
All of the users on the network with AD seem to point to the old DC even the new DC with Windows2008 server is running DNS. When I remove the old DC, the users cannot even get on the internet. The new DC with Windows 2008 server runs DNS and GC. However, if you run nslookup - server on a user machine, it always states that the old DC is the server. I am sorry if I did not explain the problem correctly the first time.
Well, you're not using the correct terms, which is complicating the problem.
What DNS server are the client machines configured for? Sounds like your DHCP server is still sending out the old DC as the preferred DNS server.
Is the new DC configured in the correct site in Sites & Services?
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
What DNS server are the client machines configured for? Sounds like your DHCP server is still sending out the old DC as the preferred DNS server.
Is the new DC configured in the correct site in Sites & Services?
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
- Thread starter
- #6
That would likely be in your DHCP configuration.
The correct configuration would be that the new DC is listed in the correct site, and is a GC.
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
The correct configuration would be that the new DC is listed in the correct site, and is a GC.
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
- Status
Similar threads
- Locked
- Question