IIS Server Behind NAT Troubles

[gnault]

I have just set up Windows 2000 Server behind a Nat Router which is also a DHCP Server. The only reason I want to use Windows 2000 Server is to be able to host multiple web sites.

The existing NAT router is working fine for all the clients and the Windows 2000 Server box. The gateway is set properly, I can browse the internet from all clients and the Windows 2000 Server box.

My public IP address is 208.252.253.184 and is mapped to the Windows Server through the NAT and all clients can ping the public IP address just fine.

Now the weird part. After I built the web sites, the Windows 2000 Server machine can browse the public IP address just fine. (naultfamily.net 208.252.253.184) However, even though the clients can ping naultfamily.net, they can not browse naultfamily.net. The browser returns can not find page error.

Any ideas??

 

[dankelt]

It worked just fine for me. I browsed to naultfamily.net and got your default page.
I'm gussing your clients are within your LAN, and will need to browse to the IP address of your web server, not the IP of the NAT box.

Dan

 

[JWFdev]

Are you using two NICs???

I found this older white paper but cannot find anything that says that it has been fixed. It seems that windows servers have problems with browsing their own networks if they do if from a maching that has two network adapters.

This could be why it works for some and not others.

Here's an URL to read about it...

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

All you've got to do if your server is not a DC is to set the computer browser service to "manual" instead of automatic.

Please let me know if this is still and issue as I'm thinking it might be what's causing me problems as I'm busy trying to do the same thing.

John Ford

 

[gdvissch]

Are you using NAT to the Webserver or simply forwarding port 80?

When you ping the public address, it is probably your router that answers. You should check that when the origin is an internal address forwarding is done properly.
Try to telnet to you webserver on port 80
(telnet <address> 80) you should get a connection