Hi, I did not think I was spamming you at all. You were the person responsible for NTLM code, right? If you do not have a clue, ok, but there is still a problem. Let's concentrate on fixing our codes...
The account can be authenticated well from web server directly. One clue could be the account is on another domain: login name: domain\username where the domain is different than web server and reverse proxy's. One last thing: since I use gmail for fastream.com, I cannot see if mails sent to list are delivered. So that's why I simply ping. I sent to all your inboxes because I was not sure which one you were reading. Since you seem to get all of them, from now on I will use one of them. Best Regards, SZ On 3/14/08, Arno Garrels <[EMAIL PROTECTED]> wrote: > > SZ, > > Yes, I read your post, however I have no glue what's wrong, > otherwise I would have answered. That's no reason for spamming me! > There are many possible reasons why authorization can fail, the NTLM > handshake you posted seems ok. Why do you think I should know? > Tell us more about the environment and your implementation details, > may be the user simply is not found (local account on the IIS box)? > > -- > Arno Garrels [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
