Article ID: 969519 - View products that this article applies to.
After you install either the February 24, 2009 cumulative update that is described in Microsoft Knowledge Base article 961752 or the 2007 Microsoft Office suite Service Pack 2, you may experience the following symptoms.
This problem occurs because of a code change in Outlook 2007 that is included in the update from KB article 961752. After you install the update, Outlook always assumes that you are connecting to an Exchange 2000 Server mailbox, or later versions, and always uses the Referral service when you create a new profile.
If you have the "No RFR Service" registry value set to 1 on the Exchange server the server is effectively configured to always use DSProxy. However, Outlook does not support DSProxy after the installation of the update, and it cannot reach your global catalog server.
A global catalog server does not support the Referral service. Therefore, if you specify the global catalog as the Exchange server name and you do not have Exchange installed on the global catalog server, there is no way for the global catalog server to give you the Exchange server information.
In some topologies, a referral from the Exchange server for a GC returns an FQDN that is not routable from the client computer. For example, after you connect to an Exchange server by using a wireless router, the router cannot route traffic from the client to an FQDN such as “server.Domain.local." This is a typical FQDN that is returned by a Microsoft Small Business Server.
This can also occur on non-SBS servers in which the Outlook client and the Exchange server are in different domains. Such an Exchange server is typically a single Exchange server that is also a GC. If your DNS configuration cannot resolve the FQDN of the server in the other domain, you can use the nslookup command on the Outlook client to see whether it returns the correct IP address for the server. The following example shows a failed nslookup from a client for such a topology:
In this example, exchange01.contoso.com is the FQDN of the Exchange server in the contoso domain and dc01.fourthcoffee.com is the DNS server in the Outlook client domain (fourthcoffee).
To resolve this problem, install the update from the following article: For more information, click the following article number to view the article in the Microsoft Knowledge Base:
968858If you cannot install the update at this point, please use one of the following methods as a workaround until you can install the update.
(http://support.microsoft.com/kb/968858/ )Description of the Outlook 2007 hotfix package (Outlook.msp): April 30, 2009
Method 1Do not specify a global catalog server when you create your Outlook profile.
If you specify a global catalog server when you manually create your Outlook profile, and you do not have Exchange installed on the global catalog server, specify the name of an Exchange server in your organization.
If you use a .prf file to create your Outlook profile and the .prf file specifies a global catalog server for the Exchange mailbox server name, change the .prf file so that it uses the name of an Exchange server in your organization instead of a global catalog server.
Method 2Stop using the "No RFR Service" registry value on the Exchange server.
If you use the "No RFR Service" registry value on an Exchange Server 2003 server or on an Exchange 2007 server, you can solve this problem by following these steps:
Method 3If you use an SBS server that returns a FQDN that is not routable from the client computer, you can resolve this problem by following these steps:
Method 4Use a Hosts file entry for the FQDN of the global catalog server. If the nslookup command returns a "Non-existent domain" result for the FQDN of the GC, change the Hosts file on your Outlook client to include an entry that resolves the FQDN to the IP address of the server. To do this, follow these steps:
Before you install the update from Microsoft Knowledge Base article 961752, Outlook uses the following global catalog server connection logic when you create a new profile. When you create a new Outlook profile, the client has to know the name of your global catalog server. During the initial profile creation process, Outlook is not aware of the Exchange version that hosts your mailbox. Because of this, Outlook assumes that the Exchange server supports the DSProxy service and uses the Exchange server name as the global catalog server name. Therefore, Outlook prompts Exchange to proxy Name Service Provider Interface (NSPI) calls on to the actual global catalog server.
Note Exchange is fully aware of the global catalog servers to which it can connect.
After this initial connection is made, and Outlook successfully finishes its first start, Outlook caches the version of Exchange that hosts your mailbox. Because Outlook 2007 only supports connections with Exchange 2000 Server and later versions, Outlook knows that these versions of Exchange provide support for the Referral service (DSRefer). Therefore, Outlook uses the referral service on Exchange instead of using DSProxy to obtain the name of a global catalog server. As soon as Outlook has the name of the global catalog server, NSPI calls are made directly with the global catalog server.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/961752/ )Description of the Outlook 2007 hotfix package (Outlook.msp): February 24, 2009
Article ID: 969519 - Last Review: June 21, 2014 - Revision: 4.0