Your answer was exactly what I needed. I understand and have impletmented the change.
Thank you.
Main Topics
Browse All TopicsBackground: School Environment, 60+ client computers
Server: windows 2000. Server manages DHCP and DNS. So client computers either had DNS set to automatically find DNS or was set to server address of 192.168.0.2.
Network: Cable modem >> old Net gear Router >> To Switch which distributes to balance of building, one of which is the server.
Issue:
Road Runner (Time Warner Cable) made a change to their DNS addresses. Everything worked before change, no internet access after change. They had a window appear saying we needed to change the DNS settings to the new addresses. They provided the new primary and secondary addresses.
I spoke with Time Warner tech support about what to do. Not as helpful as I had hoped. Basically told me I had to go to all computers and manually enter the new addresses. I did that and we now have access to internet.
Multi part question. Any help will be appreciated.
1. I do not understand how this change from TW killed our internet access? There were TW DNS servers before and all worked fine. Why would the change make a difference?
2. Is manually changing everything to the TW DNS servers the right way to go? It solved the immediate problem, but it seems like there should be a better way.
3. I am thinking of replacing the router with a new one. AND allow it to manage the DHCP and DNS for the network. Assuming I need to turn off DHCP and DNS on my windows 2000 server, what do I need to consider in order to make the switch? OR is that a bad idea?
Thank you.
Jerlo
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: tigermattPosted on 2008-04-23 at 08:44:24ID: 21421961
Hopefully the answers to your questions below will solve the problem...:
1. I guess you already know what DNS (Domain Name System) is, but essentially it is a directory which maps logical website address (such as experts-exchange.com), which us, as humans, like to use and find easy to remember, to IP addresses, whether IPv4 or IPv6, which computers like to communicate with. If your ISP change the configuration on their DNS servers so they were at a new bank of IP addresses, your network is going to be unable to resolve the domain name of websites to the IP address (since it cannot contact the Internet name servers) and therefore Internet access would be lost. I suspect if you went to the IP address of a website, things would have worked first time, since you have cut out DNS.
2. As for fixing the problem, the last thing you should be doing in a network supporting the client-server model is going and making changes on every PC - the whole point of a server is so things are done centrally, and Time Warner tech support obviously aren't aware of that. If the server is dealing with DNS and DHCP, then you should have the DNS service running on the server, as well as DHCP, correct? In this case, your DHCP scope should be configured with the IP of the server as the ONLY DNS server listed, don't include external DNS servers at this stage. If you open the DNS console, you can then go to the root of the server and view the Properties of the "Forwarders" object - in here will be TW's DNS servers, you need to remove the old IPs and enter the IPs of the new DNS servers at TW. Then, make sure you go and reset the configuration on all workstations to ensure they are getting DNS information automatically from the DHCP server.
3. There should be no reason to do this once you've made the changes in DNS on your server.
-tigermatt