Re: Windows Auth Problem

Hi Walter,

Thank you for the reply. I had already tested a very simple page using
User.Identity.Name. I changed it to do exactly as you've indicated and I get
the same behavior. IE is also set as indicated. I also get the same
behavior with Firefox. I've tried this on three different machines--one XP
and two Server 2003--browsing locally (localhost) as well as remotely and
get the same result.

Here's a funny twist: I just tested this code on a Virtual PC session that
is not on the domain; it's in a workgroup. It worked as expected and
properly recognized me and displayed my local machine username. So I'm
wondering if there's some Active Directory setting that is incorrect. Is
that possible?


"Walter Wang [MSFT]" <wawang@xxxxxxxxxxxxxxxxxxxx> wrote in message
Hi John,

If you're using IE and IE's security setting is set correctly (IE Options:
Advanced/Security: (check) Enable Integrated Windows Authentication), this
should work out-of-box.

I've just tested it on my side using a simple web application:


<allow users="*"/>
<identity impersonate="true"/>


protected void Page_Load(object sender, EventArgs e)

It should print out current user's logon name when viewed in IE.

If your settings are correct, would you please create a simple web site
like above and test it? Thanks.


#Integrated Windows Authentication - Wikipedia, the free encyclopedia

#Integrated Windows Authentication (IIS 6.0)
* Integrated Windows authentication is supported by only Internet Explorer
2 and later.
* Integrated Windows authentication does not work over HTTP proxy

Walter Wang (wawang@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support

Get notification to my posts through email? Please refer to
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at

This posting is provided "AS IS" with no warranties, and confers no