Re: Problem establishing SSL connection in code-behind

The logon audit may not necessarily be a failure when the 401 happens. It
could still be a success. It is, however, possible that you are
accidentally authenticating the anonymous user or a different user than you
think you are and then that user in turn does not have read access on the
file specified. That is why the details of the audit events are important.
You want to know what is different between the working case with wfetch and
the non-working case with the code, as that will help explain why the system
is behaving differently.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--

I am also interested in checking out if there is some significant
discrepancy between my VB and C# code. I will test it out today.

Also, sorry I did not make clear that the 540 log which you saw was
not from production. It is from a testing machine to whose AD we do
have access.

I haven't see any failed logon from my web application in the event
viewer. It seems even if when I was getting the 401 error, the event
audit still says Success.


.

Relevant Pages