Paul Williams said:
Sorry to butt in here. But desperation and all that.
Corentin... if you're connecting to an Exchange server through OWA; do you
have any problems with this...
///////snip!////////
A recent change to our Exchange server has rendered Entourage unable to
connect from outside of our domain. I now get a "bad username/password"
message when I try to connect from my Mac from home.
I suere don't have that. COuld it be a conenction to a backend server
instead of a front end one?? (though the backend servber should simply
not be accessible - period.)
OWA in Firefox and Safari is still working.
Then ther eis no reason why it shouldn't work. Entourage basically uses
OWA to get its Exchange data.
The change that was made by our Exchange admin (at the behest of the men in
dark suits) was to...
SSL 2.0 has been disabled
128 Bit SSL encryption is required
With a self-signed certificate?? In this case you'd have to import the
certificate in your X509Anchors and that's it (we don't have SSL at all
on our server :-( ),
What puzzles me is that if you have a certifcate problem, you should get
a Certificate warning, not a bad username one.
Could it be that the Exchange entry in your keychain is corrupted?? Did
you try deleting it to let Entourage re-create a fresh new one?
I am told that the certificate we use should be happy in the "128-bit"
scenario, so could it be that SSL 2.0 is all that Entourage can work with?
I don't think that this is the issue.
///////snip!////////
And now back to your regular programming...
Corentin