up vote 0 down vote favorite
share [g+] share [fb]

We have an IIS6.0 Server running on a Windows 2003 Server. Last weekend it went though maintenance, and updated a quite a few Windows updates, it is now brought up to current updates (as of March 29th). Previous to these updates we could connect to the Web page via the hostname or via a alias (there is a DNS and a WINS alias (the alias is the same name in both) that are both pointing to the system).

Now since the updates it asks for credentials to access the page, when trying to access the page via IP, or by name. If you use the alias it will go right into the page. I had added a new alias in DNS and tried to access it via this name with the same effect. So it appears that the WINS alias allows the page to show up properly.

I have seen this KB but http://support.microsoft.com/kb/871179 though not sure if it really is relevant to this issue. As it does refer to the 3 strikes rules to display the 401.1 error.

The IIS Application pool is running under a domain account. Teh default page is allowing Anonymous login under a local account.

Any thoughts? Thanks

Adam

link|improve this question
33% accept rate
It may well be a coincidence about the MS updates but wanted to add that in not rule it out as a possible cause. – Adam M. Apr 1 '10 at 15:05
how are your bindings setup for the site in IIS? – MattB Apr 2 '10 at 14:48
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.