I am trying to replace an old Win2003 DC server with a new one.  I have installed Server 2003 on the new machine, connected it to the network, and I can see it fine.  I've copied all data from the old server to the new one as well.  I've also installed and configured DNS on the new server, exactly like it was configured on the old one.  I have run ntdsutil to transfer all FSMO roles to the new server, and I ran DCPROMO on the old server to make it a member server (however, that process got interrupted...it timed out at one point).

My problem is that when I remove the old server from the network, I lose my internet connectivity from all desktops.  I can still access the internet from the new server, but I can't access the internet from any desktops.  I'm assuming that DNS is messed up somehow.  What am I missing?????
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dwd4243Author Commented:
Ok, when I run IPCONFIG /ALL from a desktop, the DNS servers show up as being the OLD server's IP addresses.  How can I correct that, and make it so that the new server's IP addresses show up as the DNS servers???
where is it (subnetting/routing)?
Does it have exact same IP and name (for replacement -consistency)
This should leave only the MACs.
Routing tables sometimes take awhile to settle down.
Active directory also takes its time in propagating.
I do not have answer (yet)
But I think you should also indicate that you waited an amount of time for everytning to find everything again.
Perhaps 15 minutes to two hours.
You should ensure browsers services and proxies and Wins are in order, and try to make it where there is no more than one application per server (easier IMO as HW gets retired, keep it around, just doing less)
Erik BjersPrincipal Systems AdministratorCommented:
If your new DNS server has a different IP from the old either change the IP, or change your DHCP options to reflect the new IP for the DNS server.  Make sure you configured forwarders in the new DNS server to point to your ISP DNS servers, otherwise it will try to resolve names and not beable to and they will have no where to go.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CompTIA Security+

Learn the essential functions of CompTIA Security+, which establishes the core knowledge required of any cybersecurity role and leads professionals into intermediate-level cybersecurity jobs.

Hardcoded, fix it on desktop.
DHCP, fix it at dhcp server.
You should not have changed IP address.
You can tell dhcp server to hand out the address of new DNS servers each time the desktops request a renewal of their license.
Note, this will not work for anyone needing dns that has hardcoded IP address, for them you must go to each machine. That should only be servers (not printers)
Ok, when I run IPCONFIG /ALL from

               I run IPCONFIG /ReNew

IPConfig /?
shows option to flushdns. I am unfamiliar with that, it sounds good but should not be required unless something else crops up
Kevin CrossChief Technology OfficerCommented:
Windows XP caches name resolutions, so if you have instances where computers are still pulling up IP addresses for a name that have been changed since moving to new DNS server, then you would use IPCONIG /FLUSHDNS.

It is correct that what probably occurred is either that the primary/secondary DNS server IP addresses conigured or the machines are no longer valid because they changed or that you don't have the proper root hints or forwarders in DNS configuration on Windows server.  Should be anything outside your domain forwards to your ISP DNS servers.

You can verify this, but trying to access a website by its IP address and you will probably see you can access sites like google.com and other Internet sites fine by IP address, but you seem to have no Internet Access because all the pages will come up as not found since can't resolve IP.
If the old server is decomissioned and the DNS entries are statically set on all of the workstations, sometimes what is easier than going around re-assigning the DNS settings on each of the machines would be to just add a second IP to the server's network adapter by going into TCP/IP properties, clicking advanced, and adding a second IP address.
Kevin CrossChief Technology OfficerCommented:
Thing that is what ebjers was trying to suggest as well.  That is my recommendation as well.  Or simplier change IP address to old one totally if new address is not used anywhere yet.
It is only slightly different, I would advise AGAINST just outright changing the IP as this could lead to several other problems relating to DNS and Active Directory, but yes, it is quite similar.
Kevin CrossChief Technology OfficerCommented:
Erik BjersPrincipal Systems AdministratorCommented:
Bill_Fleury's right, changing the IP of a DNS server can cause problems.  I've had to do it before and it worked fine once and caused all sorts of problems the second time I did it (on a different domain)  I should have attached this warning to my comment earlier.

If you do change the IP of the DC you may need to have all the clients rejoin the domain to get them to function correctly again... not fun

OK the best solution in detail...
Your computers are looking in the wrong place for DNS name resolution so...

1) Change the IP if your DNS server in your DHCP (this is either on your router or on one of your servers) if you are not using DHCP change the DNS servers on each of your workstations.
    a) If you have 2 DC you should use primary and secondary DNS entries for your DCs
    b) If you only have one DC you should use your DC IP for the Primary and one of your ISPs for the secondary (or use as the secondary, this is my fav DNS server in the world, it always works)

2) MAKE SURE TO CONFIGURE forwerding in DNS settings on your DC otherwise it will not know how to redirect DNS requests that it can not handle

3) One each WS either run IPconfig /release then ipconfig /renew to get the new IP settings, or reboot each WS (rebooting can be done from one location using the shutdown /i command from the run prompt.  Just add the computers to the list and select restart)

Good luck
A BTW, I think that any swapping of equipment should ALWAYS keep the names and addresses exactly the same from the get go.

One that I do not push, but my company does, is to also keep the serial numbers exactly the same (and have them match the Host's name, or vice versa). This can be worked out where one is fortunate enough to have the newer bios, and has a greater need to track equipment that may get moved on the network (or off).
I agree with Ebjers except for the part about changing the IP of the DNS server.  It would be much better just to add a second IP to the NIC so you don't damage anything else.
There's one way to add DNS records to DHCP Server in order to let DHCP to spreed the setting to client.

You need to configure the DHCP at your new DomainServer.
1. Configure DHCP scope option.
2. add record 006 DNS Servers (pls configure the IPAddress)
3. ipconfig/renew

Try this. Thk.
was that a ditto?
dwd4243Author Commented:
I realized shortly after my post that the reason I was having the problem was because I was unable to gain access into our PIX firewall (which also served as our DHCP server) and tell it the new IP Addresses of our new DNS server.  Thanks
Erik BjersPrincipal Systems AdministratorCommented:
Thanks for the points
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.