HELP!! Server can't access internet router.

[J741]

We have a small network. Internet conenction is broadband through a small internet router/gateway. The Windows 2000 server serves our web page and Exchange mail services.

All was functioning perfectly until...

I disabled the DHCP functions on the standalone internet router/gateway. I installed and enabled DHCP functions on the Windows 2000 server. Configured the DHCP assigned DNS server address to 192.168.0.1 (the address of the W2K server). Configured the Default Gateway to 192.168.0.254 (the address of the standalone internet router/gateway).

Now, all of the workstations can access our website (via the LAN), as well as any internet site. However, the server can not access any internet site, and no one on the internet can access our web site.

Ping 192.168.0.254 from any workstation works fine, but the server returns "request timed out".

NETDIAG reports that the gateway can not be reached.

This is very strange, as the W2K server is physically attached to the standalone internet gateway/router, which has an integrated 10/100MBps HUB for our LAN. This PING test worked fine before I installed DHCP on the server.

Also, by rights, the workstations should not be able to resolve internet names (but they do), as the DNS server is the W2K server which can't access the internet (and as such has no route to the known root DNS servers).

If anyone can tell my why the W2K server will not ping the gateway now that DHCP services are installed, I would be grateful.

 

[J741]

More Info: Some other things I also changed before I noticed this problem:

I changed the server's IP address form 192.168.0.2 to 192.168.0.1, and reflected these changes in the DNS records.

I installed and enables Remote Installation Services.

I don't see how these could affect the isue listed above, but I thought it worth mentioning, just in case.

 

[J741]

Well, no one has replied yet, so I tried to back-up out of what I had done. The first reverse step I did was to un-install Remote Installation Services. Now I can ping the gateway at 192.168.0.254, but can not ping anything on the internet (by name or IP address) from our server. Neither can I use the web browser to access the router's configuration at 192.168.0.254. These functions still work fine from the workstations, but not from the server.

 

[J741]

2 days an no replies exept my own? Does nobody have any ideas about this?

 

[J741]

Well, I gave up on this. I un-authorised the DHCP service on the W2K server, re-enabled the DHCP service on the standalone router, and changed the TCP/IP settings on the W2K server to "assigned by DHCP". Now the server can ping and browse the router, and access the internet. And people on the internet can access our web site and send us e-mail.

Why would this not work with the W2K server handling DHCP services !?

The only things I could see different in the 'IPCCONFIG -ALL" results was that with the router handling DHCP, there is a second DNS suffix which is appropriate for our ISP. Also, 'IP routing' says 'no' but when the IP is static on the W2K server, 'IP routing' says 'yes'. I don't thing a second DNS suffix would cause the issue, but 'IP routing' may. SO when I set up the IP address on the W2K server with static settings, how do I disable 'IP routing' ?

 

[GlenJohnson]

2 days an no replies exept my own? Sorry, but I don't use this on weekends, way to much stuff to do. Why did you want to change it in the first place? The first thing I would have said was ipconfig /all. Sorry for the delay. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com


"How many things, too, are looked upon as quite impossible until they have been actually effected?."
Pliny the Elder, Caius Plinius Secundus(c.23-79 A.D.); Roman writer.

 

[imatthec]

Did you have your server's primary DNS server pointing to itself?

 

[J741]

Glen, I want to do this so that we can use Remote Installation Services. As I understand it, this requires that the W2K server handle the DHCP services. Am I wrong?

Imatthec, yes, the server's primary DNS is pointing to itself (by it's address, not by 127.0.0.1).

 

[GlenJohnson]

I've not used or even checked into RIS, so I can't say. Check this site out.

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q298750&

Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com


"How many things, too, are looked upon as quite impossible until they have been actually effected?."
Pliny the Elder, Caius Plinius Secundus(c.23-79 A.D.); Roman writer.

 

[J741]

I figured out that it was "Routing and Remote Access" that was causing the problem. With this disabled, 'IPCONFIG -ALL' now reports 'IP Routing = no', and everything works as desired.

Now I need to figure out specifically what portion of the "Routing and Remote Access" configuration is causing the issue, because we do want remote access.