General discussion

Locked

Shared DSL Access

By hlopezj ·
I have a Cayman 3220-H DSL Router, a Windows 2000 server, and 7 clients running a mix of Windows 95/98, Windows ME, and Windows NT. Originally, the DSL router was set up with default network settings, i.e. the DSL router acted as the DHCP server and everything else, including the server, as a DHCP client. I believe DNS was also handled by the router because when I disabled DHCP on the router without enabling it on the server, clients were no longer able to find the server by its name, only byits IP address. Unfortunately, this caused severe network problems whenever the DSL connection was lost for any length of time. In response, I turned DHCP off at the router and enabled it on the Windows 2000 server. The internal network now runs beautifully, but (almost) nobody can access the Internet through DSL anymore. Even the server itself which is plugged directly into the DSL router cannot get out to the Internet. Oddly enough, a Windows ME computer also plugged directly into the DSL router has no problems connecting to the Internet. I suspect the problem is with Internet DNS name resolution on the Windows 2000 server itself. Except for the one client connected directly to the DSL router, all the other clients would have to go through this server before they can get out to the Internet. How do I restore Internet access to all the clients?

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Shared DSL Access

by ins413 In reply to Shared DSL Access

I had a similar problem with my dlink router and my cable connection. The dlink supplies the dhcp and gateway address to all clients. I let the router handle the dhcp and the server handle dns. You have to add the domain suffix of your provider in the lan settings of all the clients including the server. Make sure that your server uses a static IP address for name resolution on the private side of the network and that the loopback address is specified on the preffered dns setting of the server and then add your isp dns server addresses in the advanced settings. Another work around would be to disable the dhcp service on your router and create a similar scope on the server that can hand out all appropriate IP adresses to clients. It worked like a charm for me after playing around with the settings.

Collapse -

Shared DSL Access

by Shanghai Sam In reply to Shared DSL Access

Disabling DHCP from the router and creating a similar scope on the server did not fix the problem. In fact, this is part of what caused my problem in the first place. Also, I did not have to add the domain suffix or the DNS server addresses from our ISP to any of the clients or the server to fix this problem. I point this out simply to indicate why this response wasn't directly helpful. I did appreciate the response, but it did not readily solve my problem.

This was the solution.
1.) Disable DHCP on the router and create a similar scope on the server. Make sure that the "use DNS settings from the DHCP server" option is checked.
2.) Specify the Default Gateway (i.e. "Router" in Windows 2000) and specify the static IP address of the server as the "DNS Server" in the optional DNS settings on the server itself. These DNS settings will then be pushed out to all the DHCP clients.
3.) Enable DNS Forwarding on the Windows 2000 server and specify the local IP address (private side of the network) of the router in the DNS Forwarder address settings.
4.) Run winipcfg (Windows 95/98/ME) or ipconfig (Windows NT) to release the DHCP lease on each client and renew the IP address (and the appropriate DNS settings) from the Windows 2000 server.

After these 4 steps, everything worked beautifully.

Collapse -

Shared DSL Access

by hlopezj In reply to Shared DSL Access

This question was closed by the author

Back to Windows Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums