GNOME Bugzilla – Bug 323619
NTLMv2 authentication problem
Last modified: 2013-07-23 14:33:02 UTC
Please describe the problem: Connection to an exchange server which only allows ntlmv2 authentication method fails. Steps to reproduce: 1. Create new account for exchange server. 2. Type the correct OWA URL, username, click "Authenticate". 3. Type correct (or any) password. Actual results: Evolution shows an error message: "Could not configure Exchange account because an unknown error occurred. Check the URL, username, and password, and try again." Expected results: Authenticate correctly, and able to finish the exchange account configuration. Does this happen every time? Yes. Other information:
Created attachment 55804 [details] NTLMSSP_NEGOTIATE phase packet dump NTLMSSP_NEGOTIATE phase packet dump exported with ethereal
Can you set Environment variable E2K_DEBUG=4 and run Evolution and get the traces, while you try to authenticate?
I followed the instructions found at http://www.gnome.org/projects/evolution/bugs.shtml to trace the exchange connector. The debug showed only the two following lines: Evolution Exchange Storage up and running E2K_DEBUG=4
You are trying to get traces for evolution-exchange-storage process. I wanted to see the debug outputs of *Evolution*, while you try to authenticate.
I attached the output of "env E2K_DEBUG=4 evolution" The debug shows "Could not connect to localhost: Connection refused". This is caused by evolution is not able to connect to another IMAP server at startup, so I think you can ignore the information above that line.
Created attachment 55975 [details] output of "env E2K_DEBUG=4 evolution"
well, I don't think you re-created the account after creating the exchange account. I don't see any exchange debug messages here.
Created attachment 56018 [details] results of E2K_DEBUG=4 Unfortunately this was done with evo 2.2.2, because 2.4.1 did not debug anything.
Hello! Was the last attachment useful? Or do you need any other information?
Yes that was useful, now we need to look at supporting it.
Has this been fixed with the release of Evolution 2.8? I'm keen to see this issue fixed as it prevents me moving from Outlook. Without a working exchange connector, I'm limited to pop3 access from other email clients but that limits the features I can use. I notice that Ubuntu 6.10 will have evolution 2.8. I'll give it a try when it's stable. Thanks.
No, I've tried with Evolution 2.8.0, and the results are the same.
I believe Evolution-Data-Server only implements NTLMv1.
If that is the case, I'd suggest Evolution should produce a more descriptive error message instead of: "Could not configure Exchange account because an unknown error occurred. Check the URL, username, and password, and try again." The error message should state that NTLMv2 had been detected, but Evolution only supports NTLMv1. That way users would know what's wrong instead of having to guess and then attempt to experiment with various settings. Accurate error messages would then allow Evolution developers to more accurately gauge how much of a problem this issue is and how much of the userbase is affected. Finally, although not often possible for users, information about how to reconfigure an Exchange server to work with Evolution would be useful. That way a corporate user would then be able to make the appropriate request to their IT department. Thanks.
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers. If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible). There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX. Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported. Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.