Discussion Locked

Unable to connect to Internet with DSL

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Using a Windows 2000 Server (SP2), I am unable to connect to the Internet using a DSL connection. All client computers can connect using the DSL connection. The topology is a Windows 2000 Server domain. Client computers connect through a DSL Router/10-100 switch and then through the DSL modem (pacbell). Browser is IE 6. The server is running AD and DNS. The router acts as the DHCP server, but the server has a static IP address. Any help?

8 replies

by timwalsh

Are your clients by chance Win9x boxes? If my hunch is correct, you would be having even more problems if they were running Win2K or WinXP.

Here are the probable issues:
By running DHCP on the router, your clients are getting DNS info relating to your ISP, not your domain. They are bypassing your DNS server completely.
Your server is probably pointing to itself for DNS information (your DNS server is listed as Primary) and you possibly have your ISP's DNS server listed as Alternate. If this is the case, your DNS queries related to the Internet are not being resolved. This is because an Alternate DNS server is only queried if the Primary is not available, not because the Primary can't resolve a query. To fix this, you need to add the ISP DNS server's IP address to the forwarders list. I would also suggest that you disable the DHCP capability of the router and setup DHCP on your server. That way your clients will receive DNS info related to your domain, not the ISP.

by di

The clients are both Win98 & Win2K. I believe that the forwarders list is the solution. In fact, you have confirmed what I suspected, and what I was headed toward. I do have the ISP's DNS server listed as an alternate and the DNS server is the primary. I don't believe the clients are bypassing the server altogether because the DSL was configured long after the DNS server was up and running. I agree, that I should disable DHCP in the router and use the server for DHCP, and I will make the change as suggested. Thanks for your help. I appreciate your input and will address the forwarders list issue.

by reference

Also check that your server has a gateway address pointing to the DSL router. Are you able to ping a public IP (64.58.79.230 - currently yahoo.com's IP) If you can ping the IP address, but not the name(www.yahoo.com) then this would indicate a DNS problem. If you cannot ping either the address or the name, then this would indicate a gateway problem.
Hope it helps

by reference

Also a GOOD idea to apply SP3 for your server, especially if it will be accessing and/or be accessed from the internet.

by di

Point well taken regarding SP3. I am in the process of applying this service pack to both Win2000 Pro and Win2000 Server. Thanks for you help.

by mcse rabbi

Basic troubleshooting:

1) Can you ping external addresses by IP address? (Try google.com = 216.239.53.101

2) Can you ping an external address by domain name (www.google.com)?

If neither of these works, you either have a problem with your DSL modem or some sort of physical connection problem. But this is not likely if everything works internally.

If you can ping by IP address, but not by domain name, you have a name resolution (DNS) problem. My bet is you have a DNS problem.

Your Win2k server probably has it's own IP address as DNS, but the clients get their information from the DSL router via DHCP (they probably have the 2k server AND the DSL router's IP address). Try adding the DSL router's internal IP address as a secondary DNS entry in the network connection properties on your 2k server.

by di

Thanks for your help. I have not yet tryed the idea of adding the router's IP address as a secondary DNS entry for the server. I agree that this is not a hardware or connection issue.

This discussion is closed to new replies.