I have access to 2 web servers on 2 completely different and unrelated
domains. The first is our own domain (the development domain) and the second
is a customer domain (the live environment). Both servers are running W2K3
server SP1 with IIS 6.0 and the IIS 6.0 Resource Kit Tools. I create a simple
virtual server in IIS containing a single HTML page (test.htm) on both
servers and then apply the CustomAuth ISAPI to each virtual server using the
instructions outlined in the ini file / guides on the web.
I apply the process stringently on both servers so all settings and
permissions are set identically, including denying access to test.htm for the
IIS anonymous account. On our own development server the built-in login form
of CustomAuth is shown when I try and access the test page as expected. On
the customer live server I never get presented with the login form - the
browser seems to cycle endlessly.
I can't understand what could possibly be causing the 2 apparently identical
setups to behave differently. I did not setup the customer live W2K3 server,
so there is potential for something to have been configured differently that
would stop CustomAuth from working, but I am at a loss to what it could be.
The only difference I have noted so far is that on the live customer server
(which does not work), when I first choose Permissions on the new virtual
server web site, the IIS anonymous account (IUSR_ComputerName) is not shown
as set with any permissions on the web site. I have to add the user to the
virtual web site and then deny it permission to the web site.
Any thoughts / help would be gratefully received,
Thanks,
Paul.