I have inherited the following problem, and appreciate at least a direction as to isolate what the cause could be. The server in question is NT4 SP 6 with IIS4 and Site Server 3.0
1. The DNS has defined the FQDN host.domain.com. If I were to pingfrom a remote site, it resolves.
2. If I try to access from intranet http://host.domain.com/test.htm, I can see on my browser gets redirected to http://host/test.htm, and the page appears.
3. If I access from internet http://host.domain.com/test.htm, I can see at the bottom of the browser it is Finding: host, and then page not found, the message would say something like DNS error, server not found.
4. In that server, Site Server is installed. So if I access from both intranet or internet http://host.domain.com/SiteServer/, the page would appear as http://host.domain.com/SiteServer/, no redirection. SiteServer is a virtual directory under the default web site.
5. There are other virtual directories under the same default website. But if I try to access http://host.domain.com/
6. The website is configured to ip unassigned, no host header defined. But I don’t think that is the problem. If so, by right /SiteServer/ should be having problem too. I did try putting in host header, the result is no page could be seen. Since it’s a production system I had to quickly unwind it to what it used to be.
7. The site is a proprietary document management application. Since we inherited it, the code and site server settings are very much a black box to us right now.
Appreciate clue as to where the binding to hostname could have occured.The more specific the better. We need to internet-enable it.
Thank you