Re: Problem establishing SSL connection in code-behind

Well, that is some progress I guess. Assuming that you are using the same
credentials in wfetch that you use in your NetworkCredential object, the
next thing to look at would be the different in the logon event audits
generated by wfetch and your code. There might be some clue as to what is
different between the two of them.

I also assume you are running wfetch from the server that is executing the
..NET HttpWebRequest and not from a different machine, right? You really
want to make sure you are doing an apples to apples comparison. You also
want to be sure you use the same hostname in wfetch that you use in the .NET
code.

If nothing else comes of it, hopefully you will have learned some useful
info about HTTP authentication and some of the various tools and techniques
available for troubleshooting this stuff. :)

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
--

OK, I tried testing it again with wfetch using Negotiate, and it
works! No more unauthorized error message, and the requested hola
amigo page displays nicely as an html text.

But in my web application, I am still getting the 401 Unauthorized
error.


.

Quantcast