Skip to main content

Exchange 2010 and Outlook 2003 clients - RPC connection issues solution

 Exchange 2010 and Outlook 2003 clients - connection issues


Having a hard time connecting to an Exchange 2010 mailbox using an Outlook 2003 client?
Here’s the deal. So as most of you already know Exchange 2010 introduces a new client access service named RPC Client Access. This service lives on the Client Access Server (CAS) and allows MAPI clients (Outlook) to connect to a CAS server just like pretty much all the other Exchange clients do nowadays (with WebDAV deprecated in Exchange 2010, even Entourage clients will need to connect to the CAS).
This means that Outlook clients no longer connect directly to an Exchange 2010 Mailbox server. Well, at least not when we’re speaking mailbox access (public folder connections will, after being authenticated by the RPC Client Access service on the CAS, be directed to the Mailbox server).
One of the default settings for the RPC Client Access service is that it requires encryption for RPC connections. You can check this setting using the following command: Get-RpcClientAccess | fl

This is not an issue if you use Outlook 2007 or Outlook 2010 since these Outlook versions have RPC encryption enabled by default, when you create a new Outlook profile, see below:

But guess what? Yes the old Outlook 2003 version behaves differently. You see, when you create a new Outlook 2003 profile, RPC encryption is disabled by default in this client version.

This means that if you migrate an Exchange 2003 or 2007 mailbox to Exchange 2010, or try to create a brand new Outlook 2003 profile against an Exchange 2010 mailbox, you won’t be able to connect to the mailbox. After authentication, you will instead receive a dialog box similar to the below (click on it to see it in full size):

The issue can be resolved in two ways. You can either enable RPC encryption in the Outlook 2003 profile (if you have many, you could do so via a GPO) or disable the RPC encryption requirement on the Exchange 2010 Client Access server. Enabling RPC encryption on the client is of course the recommended over disabling it server-side. If you insist on disabling this setting server-side, you can use the following command:
Set-RpcClientAccess –Server –EncryptionRequired $false

As you can see by running Get-RpcClientAccess | fl, the encryption requirement is now disabled, and you will be able to connect to your Exchange 2010 mailbox using Outlook 2003 clients that doesn’t have RPC encryption enabled (default mode).

Also check this: http://support.microsoft.com/kb/2006508/en-us

Comments

Popular posts from this blog

Question كيفية عمل share للـ outlook conntact لكل الـ Domain Users

  الحل بسيط جدا عايز الكونتاكت تتحدث دايما بحيث انك لما تضيف يوزر جديد يسمع في الكونتاكت اول حاجه بتدخل علي in office 2003 tools --- email account ---- add address book --- internet directory service (LDAP) type your server name then login info . mark this server require me to logon type any user on active directory and its password then save and close outlook and open it again now you will find all your active directory users in address book

3 things has to be done for better performance

  Tips from Goutham: 3 things has to be done for better performance: By default, XP displays extra graphic objects for menu items which can slow down your display. 1. To turn off these selectively... Right click My Computer Select Properties Click Advanced tab Under Performance, click Settings button To turn them all off, select Adjust for best performance Preference is to leave them all off except for Show shadows under mouse pointer and Show window contents while dragging 2. To speed up the display of the Start Menu Items, turn off the menu shadow. Right click open area of the Desktop Select Properties Click Appearance tab Click Effects button Uncheck Show shadows under menus 3. You can increase system performance by loading more of the system into memory. DO NOT attempt this with less then 512MBs of ram. Your system will become unstable. Click Start Click Run Enter regedit Click OK Go to HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Session Manager Memory Management Double cli

The difference between DNS and NDS

  Novell Directory Services(NDS) - Novell Directory Services (NDS) is a popular software product for managing access to computer resources and keeping track of the users of a  network , such as a company's  intranet , from a single point of administration. Using NDS, a network administrator can set up and control a  database  of users and manage them using a  directory  with an easy-to-use graphical user interface ( GUI ). Users of computers at remote locations can be added, updated, and managed centrally. Applications can be distributed electronically and maintained centrally. NDS can be installed to run under  Windows NT , Sun Microsystem's Solaris, and IBM's  OS/390  as well as under Novell's own  NetWare  so that it can be used to control a multi-platform network. NDS is generally considered an industry  benchmark  against which other products, such as Microsoft's Active Directory, must compete. Lucent Technologies plans to integrate NDS into its own QIP product