0

On Windows Server 2003 I am using a web browser (http://servername/site) to get to a web site on itself (servername) referencing an entry in the hosts.txt file - required for the use of the software. I am receiving the user authentication box ('connect to') box. Verified that the integrated windows authentication is unchecked in the IIS properties.

I can access this web site (http://servername/site) successfully from another Windows Server 2003 and Windows XP with the hosts.txt entry. I can also access a web site (http://servername1/site1) from servername with the servername1 entry in the hosts.txt file.

From this I can see that servername is utilizing the hosts.txt file. For the IP address I tried both the actual address and the loopback (127.0.0.1) address.

user49352
  • 123
  • 2
  • 4
  • 12

2 Answers2

0

Are you expecting automatic login to the site? If you have unchecked integrated Windows auth, what have you anabled? Is anonymous access allowed?

uSlackr
  • 6,337
  • 21
  • 36
  • Yes, anonymous access is enabled. – user49352 Jan 24 '11 at 16:30
  • This server is internal to the organization and any browser should be able to access it, including itself. The problem is not the other server(s) getting to the website on 'servername' but for it to get to itself. It works if I use http://servernameIP/site. – user49352 Jan 24 '11 at 18:36
0

I found inconsistencies in IIS security at the site (anonymous) and virtual directory (integrated Windows) levels. Evidently, something triggered finding these when the web site was accessed with a host name from the same server but not found when an IP address (or requested from another machine - when the host was already converted to IP) was used.

When I changed them both to Integrated Windows security it worked fine.

user49352
  • 123
  • 2
  • 4
  • 12