I've got a single intranet server running IIS5, with the production site on port 80 and the development site on port 81. I'm generally the only one using the dev site, so assigning a different port number seemed like a simple way to implement a separate development site. Both sites depend heavily on ntlm authentication.
This setup has worked fine for a year, but today I just got a laptop with winXP preloaded, and i'd like to keep using xp. On the xp machine, i can access the production (port 80) site with no problem--authentication works great. However, when I try getting to the port 81 site, authentication fails.
I've tried setting the development site to listen on other ports like 8080, to no avail. XP's built-in firewall is disabled. Authentication on the development site still works fine on my win2k client. Does anyone know of anything in xp that would be preventing ntlm authentication from working if you're not on port 80? I've been searching the KB and google for hours--any help would be GREATLY appreciated...
This setup has worked fine for a year, but today I just got a laptop with winXP preloaded, and i'd like to keep using xp. On the xp machine, i can access the production (port 80) site with no problem--authentication works great. However, when I try getting to the port 81 site, authentication fails.
I've tried setting the development site to listen on other ports like 8080, to no avail. XP's built-in firewall is disabled. Authentication on the development site still works fine on my win2k client. Does anyone know of anything in xp that would be preventing ntlm authentication from working if you're not on port 80? I've been searching the KB and google for hours--any help would be GREATLY appreciated...