Integrated Windows Authentication is suitable for Intranet use.
Since it is a connection-based protocol, it is easily disrupted by proxies
when used on the Internet. So, you may be able to make it work, but your
clients may be on AOL that causes it to fail -- and since you can't control
any of that, it is completely hit-or-miss.
Another way to disrupt Integrated Windows Authentication is if you disabled
KeepAlives on your server (frequently people do this when using the
Professional SKU).
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"adrian" <anonymous DeleteThis @discussions.microsoft.com> wrote in message
news:0B55F9D3-57BD-49A6-A83B-7AD99291845F@microsoft.com...
yes im using Integrated Windows Authentication. so what if he is using IE.
could there be anything else?
----- David Wang [Msft] wrote: -----
401.2 means that the server was configured to require an authentication
protocol that the client cannot fulfill. So, what authentication type
did
you configure on the virtual directory?
If you configure Integrated Windows Authentication and the client
browsers
are not IE, it will result in 401.2.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no
rights.
//
"Adrian" <anonymous DeleteThis @discussions.microsoft.com> wrote in message
news:B2F76114-420F-4CF7-AF9B-48565DB22E1C@microsoft.com...
internally and externally i can access this virtual directory, i have
two
clients that cannot access it they get
access is denied. the authentication , user name and password will not
come
up to prompt him either. just the error will come up
Help please
>> Stay informed about: access is denied / 401.2 error