Discussion Locked

can see IIS4.0 web site in Intranet but

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

I have a NT4 server with proxy, IIS and exchange. I built a web site in IIS and I can see the web in my Intranet. However, I cant browse it via internet. Nevertheless, I can surf the internet via the proxy and the router in my Intranet.
So where should I start to troubleshoot? or anyone has any idea of such problem?

9 replies

by mano

In web proxy, You need to enable web publishing.

In MMC, get the property of web proxy and goto publish tab. Enable Web publishing option

by morgan_donohue

You require to have a DNS delegation authority for your domain on your ISP. ie their name server needs to know about your web server. Usually a www alias entry for the servers IP.

by Member 34256391

There are several possible problems/options here. Usually when you can see a site on an intranet but not the internet it is because the website is assigned an internal/private IP number, or it is because of a proxy server/firewall that allows for outgoing internet requests only and doesn't have the appropriate ports open for incoming requests to the webserver.
Is the IP number of the website - you can check that through the properties of the website in the IIS manager - a public one you have been allocated by your ISP or a private one used on the internal network? If it is a private one - for example in the 192.168.x.x range - you will need to obtain a public IP number you can allocate for the website. You say you have a proxy and router - is this a firmware proxy built into the same box as the router, or a software proxy running on one of your machines?
Are you accessing the site by domain name, server name or by IP number? If you are using a domain name, are you running your own dns server or using t

by corky132

You've got to use reverse publishing to put your intranet server out to the internet. Just be careful that your DNS server doesnt get in the way.. the proxy must point to an internal dns without messing up the outside dns servers.. it's best to publish the intranet site using the server name, instead of www.inside.com or something like that..

This discussion is closed to new replies.