Article ID: 909094 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
You configure Kerberos authentication between the front-end and back-end servers that are running Microsoft Exchange Server 2003. In this configuration, the following event is logged in the Application log on the front-end server:
Event Type: Warning
For more information about Event ID 1000, visit the Microsoft Events and Errors Message Center (EEMC) at the following Microsoft Web site:
This problem occurs when you use a disjointed DNS namespace. For example, in a domain that is named "country.domain.com," you use a fully-qualified domain name (FQDN) for the front-end server that resembles the following name:
Feserver.Region1.country.domain.comIn this case, a request is made for a Kerberos Ticket in the domain "Region1.country.domain.com." However, this domain does not exist.
The resolution of this problem requires two steps:
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesYou must install Microsoft Exchange Server 2003 Service Pack 2 (SP2) before you apply the hotfix.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/836993/ )How to obtain the latest service packs for Exchange Server 2003
Restart requirementYou do not have to restart the computer after you apply the hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
To add the registry key automatically, click the Fix it button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.
Note: Because this change is related to a hotfix, you must install the hotfix in addition to running the Fix this problem wizard. If you only run the Fix this problem wizard and you haven't installed the hotfix, the problem will not be resolved.
Fix this problem
Collapse this imageExpand this image
Microsoft Fix it 50321
Collapse this imageExpand this image
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
After you install this hotfix, add the following registry key:
Note 0 and 1 are the only valid values. 0 is off, 1 is on.
Value name: DisableRealmHint
Data type: REG_DWORD
Value data: 1
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the terminology that Microsoft uses for software that is corrected after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684For more information about the naming schema for Exchange software updates, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
(https://support.microsoft.com/kb/817903/ )New naming schema for Exchange Server software update packages
Article ID: 909094 - Last Review: January 16, 2015 - Revision: 7.0