New Domain Controller and DNS server problems

5 pts.
Tags:
Active Directory
DHCP
DNS configuration
DNS server
Domain Controller
Domain Controller Migration
Microsoft Windows Server 2003
SonicWALL
Windows 2000 Server migration
I'm trying to get rid of an old w2k server that is the DC and DNS server. I added DC and DNS to an existing w2k3 server and it looks like it replicated all the AD data ( I see users and machines listed ) but when I unplug the old server and login to the network at a workstation I don't get access to the internet trying to use the new server as the DNS server or to local network stuff. DHCP is being handled by a SonicWall. I don't want to remove the old server from AD because I need to be able to fall back on it so people can still work. I think I may have both DC and DNS server configuration problems. Thanks in advance Mike
Asked: Last updated:
Related Questions
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi, did you transfer the DNS already? Remember that you need to transfer the DNS zones to the new server in order to let the users resolve addresses correctly.
Please refer to this article that explains the process

Also reconfigure your DHCP settings. You need to update the DNS server IP address in your DHCP server.

You also need to make the new server a global catalog, and probably transfer some of the FSMO roles to it as it is more powerful hardware.

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: