After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 270329 - Can't authenticate to server
Can't authenticate to server
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.0.2
Other All
: Normal major
: 2.1
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks: 323345
 
 
Reported: 2004-12-08 17:16 UTC by Tommi Komulainen
Modified: 2006-05-24 09:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
revert bug 67991 changes to exchange-account.c .. worksforme (1.89 KB, patch)
2005-02-21 09:00 UTC, Tommi Komulainen 		none Details | Review

Description Tommi Komulainen 2004-12-08 17:16:30 UTC 
Version: 2.0.3 really

Use SSL: Always
Secure Password

After upgrading connector from 2.0.2 to 2.0.3 my mailbox suddenly became
unavailable, I only get "Incorrect password" error dialog instead.  Backing
out the changes to exchange-account.c that supposedly fix bug 267991 my
account becomes functional again.

My username is defined as DOMAIN '\' USERNAME, but I tried several
variations for server and username field, using '/' and '@' instead, but
nothing works.
Comment 1 Sarfraaz Ahmed 2005-01-18 18:00:28 UTC 
Take the 2.0.3 sources, remove the existing account, then re-create
the same account with the fixes for 67991, and see if you still get
this error.
Comment 2 Tommi Komulainen 2005-02-21 08:42:52 UTC 
Tried that with 2.0.4, no help.  Now the error message is slightly
different, though: "Could not authenticate to server. (Password
incorrect?)"
Comment 3 Tommi Komulainen 2005-02-21 08:58:45 UTC 
And again the newly created account started working again after I
backed out the changes.
Comment 4 Tommi Komulainen 2005-02-21 09:00:34 UTC 
Created attachment 44816 [details] [review]
revert bug 67991 changes to exchange-account.c .. worksforme
Comment 5 Sarfraaz Ahmed 2005-02-21 09:58:50 UTC 
Ok, can you confirm if these are the steps you did after updating to
2.0.4 .. 

1. Remove old exchange account.
2. Recreate new exchange account with "DOMAIN\username".

And if you still get the "could not authenticate to server" problem,
can you send me the E2K_DEBUG outout ? That should help us figure out
whats going wrong there. I still think that the fix for 67991 should
solve this.
Comment 6 Sushma Rai 2006-01-03 09:23:27 UTC 
Tommi Komulainen,

Did it work for you in 2.0.4 (see comment #5) or later versions?
domain\username is supported now.
can you please update the bug?
Comment 7 Sushma Rai 2006-05-24 09:04:29 UTC 
Please re-open if you are still facing the issue.