Re: Entourage not connecting with Exchange Server
- From: Bill Bryson <wb03@xxxxxxxxxxx>
- Date: Wed, 31 Aug 2005 17:41:31 -0500
Nathan,
I've discovered another problem with how the current Entourage 2004 (11.1)
interacts with Exchange 2003 in regard to the Delegate process.
In the past, I had successfully used the Delegate tab in Edit Account to
make a "connection" to another person's account. Unfortunately, I made the
mistake at some point to allow or tell Entourage to save the password I used
at the time I made the connection. Today I was trying to use Delegate again
and got the infamous "Can't connect to the Directory Server" after entering
the account of the person that I was trying to access. I eventually looked
into the Keychain Access and discovered a keychain for Exchange was there
and with my OLD password. We are required to change our passwords every
90-120 days and I had just changed it earlier this week. I consider
Entourage's coding to be a bug since it never prompted for my current
password because it found the saved keychain. Would not the proper behavior
had been to use the password saved in the keychain and when it FAILED to
then prompt the user for password (which he could save back again).
Instead, the message is "can't connect to directory server". I've never
like the keychain stuff but if a "saved" password does NOT work, the user
MUST be prompted for the password.
Bill
On 8/26/05 6:28 PM, in article BF34F390.79DFF%nathanh@xxxxxxxxxxxxxxxxxxxx,
"Nathan Herring [MSFT]" <nathanh@xxxxxxxxxxxxxxxxxxxx> wrote:
> On 8/25/05 10:47:55 AM, "Nathan Herring [MSFT]"
> <nathanh@xxxxxxxxxxxxxxxxxxxx> wrote:
>
>> After some inspection, this seems to be an overly generic error string
>> representing of one of the following problems:
>> * SSL Handshake failed (though we should have reported why rather than this
>> generic error)
>> * Server doesn't support a compatible version of SSL
>> * Received an incorrectly formatted SSL record
>> * Received an SSL record with a bad MAC
>> * Some decrypted data does not appear reasonable
>> * Server refused renegotiation
>> * a close_notify alert has been received
>> * the SSL server requires a client certificate and we were unable to provide
>> one
>> * The server's certificate could not be verified.
>>
>> Obviously, the error message is not relevant to many of these cases, nor is
>> it
>> sufficiently specific in the last case, where it might be relevant. I will
>> bring this up with our User Assistance folks to see if we can get it
>> addressed
>> in a later release.
>
> I erred in this previous posting. Only the last error message is connected
> to the error string "Unable to establish a secure connection to the server
> because the correct root certificate is not installed." That error message
> is still not quite correct (there are many reasons beyond not having the
> correct root certificate that a certificate is not valid), but I thought I
> should clear up the mistake.
>
> -nh
.
- Follow-Ups:
- Re: Entourage not connecting with Exchange Server
- From: Nathan Herring [MSFT]
- Re: Entourage not connecting with Exchange Server
- Prev by Date: DESPERATE to rebuild database!
- Next by Date: Entourage won't send attachments
- Previous by thread: DESPERATE to rebuild database!
- Next by thread: Re: Entourage not connecting with Exchange Server
- Index(es):
Relevant Pages
|
