Getting HTTP Code 401 when OWA works fine
Brought to you by:
mguessan
Menu
▾
▴
#4 Getting HTTP Code 401 when OWA works fine
Hi,
Hope you can please help me. I was happy to find DavMail but unfortunately was not able to make use of it yet.
I can install it and get everything setup fine. When I follow the directions to setup the Exchange account through the Gateway in iCal, I get a message saying that the credentials were rejected. I use the exact credentials to log on to OWA and in Entourage.
I presently am not specifying a domain before my username. I tried adding it in case and no differences.
So in UserName i put my username or domain\username
In Password i put the password - which is 8 character alphanumeric - no spaces, no special characters, there is a Capital letter at the beginning.
I get the results shown in the log below and this for every type of config I do through the gateway.
Let me know if you need anymore info.
DEBUG log of gateway connection attempt
This may be fixed in latest SVN, which version of DavMail do you have ?
latest 3.2.0
Can you check with 3.3.0b1 ?
i have the same problem with exchange 2007. i'm only trying to access the calendar (no pop, imap) with thunderbird lightning.
server only accepts https, there is no form login, only basic auth. login path via browser is /owa, hence i configured https://servername/owa for the "OWA (exchange) url" setting.
here's the debug output: http://pastebin.com/m5b87dd14
i tried with 3.2.0, 3.3.0b1 and 3.3.0b2-608 - all the same.
is exchange 2007 calendar supported?
The pastebin log shows an authentication issue (401), you could try to increase log level to DEBUG to get more details
here's the DEBUG output: http://pastebin.com/f2644a226
hope it helps, owa works fine in the browser. it seems the PROPFIND webdav stuff shows problems.
same with 3.3.0-623, is it a config problem client or server side or with davmail & exchange2007 support?
I'm afraid this is a server side issue: the /exchange path is not available on your Exchange server.
/exchange is the Webdav root, also used by Microsoft Entourage.
we gave up on this.. if anyone has a working exchange 2007 (on win2003 / iis6) for davmail, please drop a line what has to be configured :)
it's working! we had some weird issues with v3.3.0-623 and our exchange server while we were trying to configure it. with lightning it was possible to write to a person's calendar but not read (it didn't show any entries). with evolution it was possible to read everything (all entries showed up), but it seemed write protected and no new event could be created...
now the new version v3.4.0 solved everything (without changing anything serverside). i guess it has to do with your changes in regards to authentication :) we are now able to use davmail with lightning/sunbird or evolution and exchange 2007.
the only thing left not working is public calendars, but that's another issue :) i guess you can close this one?
Great news, thanks for your feedback.
Closed then :-)
it seems that v3.6.1 broke things again.. we're receiving "401 authentication failed" error messages again and are unable to use the calendar. we are not using form based auth, maybe this new fix in 3.6.1 broke other auth types?
v3.6.0 works fine though.. as soon as i get to it, i'll post a debug log for 3.6.1. please reopen.
i've sent you the debug log of 3.6.0 and 3.6.1. but as far as i can tell, this is the problem, changelog 3.6.1:
Experimental: reactivate NTLM authentication
it seems 3.6.1 doesn't try any other auth mechanisms than NTLM and then fails.
as of 3.4.0 you disabled NTML auth and 3.4.0 was the first version to work here :)
This is fixed again in subversion: according to you log files, your Exchange server accepts Negotiate and NTLM, If NTLM does not work with standard HttpClient, this probably means that Exchange only accepts NTLMv2.
However, NTLMv2 is not supported by Apache HttpClient, I am working on implementing this in a custom authentication handler.
Latest subversion revision now activates NTLM only on 401 authentication failed.