On Sun, 2009-12-13 at 18:41 +1100, Brad Hards wrote:
> rpc reply data:
>
> [0000] 00 00 00 00 00 00 02 00 00 00 00 00 05 40 00 80 ........ .....@..
>
> RfrGetNewDSA: struct RfrGetNewDSA
>
> out: struct RfrGetNewDSA
>
> ppszUnused : NULL
>
> ppszServer : *
>
> ppszServer : NULL
>
> result : MAPI_E_CALL_FAILED (0x80004005)Hi Brad, Could this call be failing because Exchange 2010 require to query the new RPC Client Access Service? [1] > pullTimeStamp : * > pullTimeStamp : 0x00000000 (0) > result : ecNotEncrypted (0x970) > EcDoConnect : ecNotEncrypted (0x970) > MapiLogonEx : MAPI_E_LOGON_FAILED (0x80040111) > > > I've found an interesting article detailing why native Outlook 2003 clients can't connect to Exchange 2010 [2]. Outlook 2003 clients don't enable encryption by default when setting a MAPI profile. In the meantime this is default setting in standard Exchange 2010 installations. I'm not sure what kind of encryption is used between Outlook and Exchange, but I'd be tempted to say Kerberos. If this is the case, a correct setup + minor fixes in OpenChange Profile creation and EMSMDB connect calls may fix this. Finally we may definitely need to implement and use the Exchange2003 pipe versions (EcDoConnectEx and EcDoRpcExt2). [1] http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/uncovering-new-rpc-client-access-service-exchange-2010-part1.html [2] http://www.howexchangeworks.com/2009/09/cant-connect-outlook-2003-to-exchange.html -- Julien Kerihuel [email protected] OpenChange Project Manager GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
