I've noticed a similar loop with my NTLM attempts. All my recent attempts have failed which might be because of newer IIS/NTLM versions.
FWIW you might want to look at the responses and linked comments in the thread NTLM - Not Telling Linux Much | [reply] |
Hi aufflick,
Thanks for looking into post. Yah, I've already seen the link that you posted, but it doesn't seem to tell me much. FYI, most of my code is based on that thread but I still cannot get it to work... *sigh.
| [reply] |
I would do the same with an IE, trace the conversations on the network level with e.g. ethereal and compare them, looking specially into the NTLM credentials.
Something's different, and you'll find out :-)
--shmem
_($_=" "x(1<<5)."?\n".q·/)Oo. G°\ /
/\_¯/(q /
---------------------------- \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
| [reply] |
Not quite what you're asking, but it might be worth talking to your proxy administrator and see if they are willing to make an exception to authentication from a fixed IP address (if you're writing server code).
I have also had success using wget (works under cygwin for windows users, also seems to be available as a native windows binaries) when talking to troublesome proxies. Not as nice as doing it inside Perl, but sometimes you have to go with what works (if you don't have the time to go poking inside TCP packets, as fun as that can be ;) | [reply] |