Discussion Locked

Configuring IIS 4.0

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have DSL through an ISP. Our router is using NAT. Our ISP takes care of our DNS. We use WINS and DHCP. Our Proxy Server has been given the IP 192.168.0.2 (this is what the outside world sees). This is not a real IP. Our "real" IP is 64.182.38.114 but is not bound to the NIC of the Proxy Server.
Here's my question: I created a web site on IIS 4.0 which is on NT 4.0. The rest of the world can see my site but we cannot see it from inside the network. "page cannot be found" is what we get. My ISP is no help and I'm an IIS novice. Can anyone please help? Thanks,

5 replies

by Former member

Well, can your users bring up
http:\\64.182.38.114 ?
or what about http:\\192.168.0.2 ?

One or both?

If both then routing is ok. If one then routing is not OK.

This is a little confusing. Is the IIS server and proxy server the same machine? And what is the IIS server's IP address? Is this a DSL router you use? What kind?

The best thing for you to do is some troubleshooting as described above. Do some pinging then some http-ing. You can then eliminate some factors such as routingand narrow it down to a DNS resolution problem. Let me know by posting a comment...

by burcjo

Most likely your router doing the nat can't forward correctly. Most likely you will need to have an internal DNS that has your internal (192.168.0.2) address, OR add an entry to the hosts file that has that internal 192.168.0.2 address, OR as suggested above, you could access the web server by the actual address.

If you have lots of machines, I would suggest installing Microsoft DNS. If you only have a couple of machines, then you could do hosts files.

Write if you need more info on configuring either.

This discussion is closed to new replies.