Discussion Locked

Win2k Server setup and Net connectivity

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I recently setup a Win2k Server, DNS, DHCP, Active Directory. It has a static IP Address and is connected to a small router (static ip address). In the server setup, I entered the router's IP address as the default gateway. When I restart the server, all the computers connected to it see the LAN, and the server sees the computers, but the connection to the Internet is not available. I can ping the router from the server, I see traffic in the router from the server but the connection to the Net cannot be established. Now, when I turn the server off, and give the router DHCP rights (it has that option) all the computers suddenly have access to the Net (the router uses NAT). I have checked the server setup and cannot figure out what is causing it not to connect to the internet. I would really appreciate your help.

11 replies

by technews

It sounds like you are having a conflict between the router DHCP and the W2K DHCP configuration. If you disable DHCP on the W2K server and keep the DHCP on the router active do you get the desired result?
Also, are your DNS settings pointing to theDNS servers on the ISP side? Not really an answer I know, but I am trying to get a feel for the situation.

by mckaytech

It sounds like your server's static IP is not within the range of addresses that are forwarded to the Internet. It's hard to say for sure without knowing the make and model of the router, but there are routers out there that only support (for example) only 32 addresses out of the 254 available in a Class C subnet.

It's probably time to dig out the router docs and make sure your static server IP is within the specified range.

paul

by tony.colgrove

You may have an issue with your DNS configuration. From your server can you resolve FQDN's? Try pinging www.techrepublic.com from the server. If DNS is resolving properly you should get an address response of 208.50.157.239 (at least as of 9:36 CST on 3/19/01).
If you don't then it's DNS. If you have "." domain in your forward lookup zone, delete it. Then stop and start the DNS service.
Try resolving again.
You can also add your ISP's DNS servers to the forwarders tab in DNS. This willpass all name resolution on to their DNS, when it can't resolve a name.
Hope that helps.

by tony.colgrove

Don't worry if your pings don't get a response. TechRepublic blocks ping, the goal is getting a name resolution to the IP address.

by choad

I would definitely say that you are having a problem with DHCP configurations, and maybe DNS settings as well. Make sure that the static IP addresss given to the Win2k server is NOT one that is administered by the router's DHCP service, yet IS routed to the net via NAT. You should be able to make a manual entry to the router's route table if necessary.

Make sure you DO NOT have both the Win2k server's DHCP service AND the router's DHCP service running at the same time. Pick one or the other, it doesn't matter which.

The last item you need to check is to make sure that your DNS references on the properties of TCPIP on the Win2k server are pointing to legitimate DNS servers.

With all these in place, you should be set to go.
Regards,

Pete Floyd

This discussion is closed to new replies.