Well, I was actually directing you to a specific entry on the FAQ: http://wget.addictivecode.org/FrequentlyAskedQuestions#tool-x-not-wget It mentions a couple ways to get around sites that specifically block programs like wget, or don't like "jumping" links. -Micah
[EMAIL PROTECTED] wrote: > Thanks for the quick response. I looked on the FAQ and didn't see > anything relevant. I installed the latest code, but I still get the > same error. Any other suggestions??? > -----Original Message----- > From: Micah Cowan [mailto:[EMAIL PROTECTED] > > [EMAIL PROTECTED] wrote: >> Not sure if it's a bug, but NTLM authentication has just started to >> fail connecting to SharePoint running IIS, after it's been working for > >> years. The URL is accessible using IE or Mozilla using the same login > >> credentials. I've worked with our SharePoint team, and they are >> telling me that they have not changed any configurations on their >> side. I'm guessing that maybe Microsoft has recently updated/changed >> their proprietary protocol. Here's some debug info: > > Well, without having debug information from when it was working, it's > hard to say what could be going on. A tcpdump of the successful > transaction with Mozilla or IE could be very informative. > > It looks to me, though, that the NTLM authentication could actually be a > red herring: if Wget is sending a bad authentication, the server would > respond with 401 Unauthorized. The fact that it responds with 500 could > mean something else is wrong. > http://wget.addictivecode.org/FrequentlyAskedQuestions#tool-x-not-wget > gives a couple of common situations and workarounds. > > Failing that, you might try out newer versions of Wget, to see if they > solve your problem. The latest release is 1.10.2, and there is also the > current development version. For info on how to get these, check > http://wget.addictivecode.org/FrequentlyAskedQuestions#download > -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/
