You receive a "The specified domain either does not exist or could not be contacted" error message when you try to establish a new Terminal Services connection to a Windows Server 2003-based terminal server

Article translations Article translations
Article ID: 902336 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

When you try to establish a new Terminal Services connection to a Windows Server 2003-based terminal server by using an account from a trusted interoperable Kerberos V5 realm, you may receive the following error message:
The specified domain either does not exist or could not be contacted.
Additionally, you cannot use the Terminal Server User Profile (TerminalServicesProfilePath) property, the Terminal Services Home Directory (TerminalServicesHomeDirectory) property, or other related Terminal Services properties that have been set on the user account.

Note Examples of trusted interoperable Kerberos V5 realms include the Massachusetts Institute of Technology (MIT) realm and the Heimdal realm.

Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information

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=support
Note 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.

Prerequisites

You must have Microsoft Windows 2003 Service Pack 1 (SP1) installed.

Restart requirement

You must restart your computer after you apply this hotfix.

File information

The English 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 tool in Control Panel.
Windows Server 2003, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformService branch
Msgina.dll5.2.3790.3851,419,26409-Aug-200523:45IA-64Not Applicable
Ws03res.dll5.2.3790.38558,88009-Aug-200523:45IA-64Not Applicable
Wmsgina.dll5.2.3790.3851,192,44809-Aug-200523:45x86WOW
Wws03res.dll5.2.3790.38559,39209-Aug-200523:45x86WOW

Windows Server 2003, Itanium-based versions with SP1
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Msgina.dll5.2.3790.25051,465,85609-Aug-200523:45IA-64SP1Not Applicable
Wmsgina.dll5.2.3790.25051,211,90409-Aug-200523:45x86SP1WOW

Windows Server 2003, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Msgina.dll5.2.3790.25051,193,47209-Aug-200523:45x64SP1Not Applicable
Wmsgina.dll5.2.3790.25051,211,90409-Aug-200523:45x86SP1WOW

Windows Server 2003, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msgina.dll5.2.3790.3851,192,44810-Aug-200503:02x86
Ws03res.dll5.2.3790.38559,39209-Aug-200523:59x86

Windows Server 2003, x86-based versions with SP1
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msgina.dll5.2.3790.25051,211,90410-Aug-200503:18x86

Workaround

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows


Warning You may want to remove a user's read permissions to the local Security Accounting Manger (SAM) database or to the Active Directory directory service to prevent the user from logging on to the terminal server. However, if you follow these steps, the user will be able to log on to the terminal server.

To work around this issue, change the Windows registry on the terminal server so that the following are true:
  • The Winlogon process ignores errors when it reads the Terminal Serves configuration data.
  • The Winlogon process reads the DefaultUserConfig data.
To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
  3. Click Edit, point to New, and then click DWORD Value.
  4. In the New Value #1 box, type IgnoreRegUserConfigErrors, and then press ENTER.
  5. Right-click IgnoreRegUserConfigErrors, and then click Modify.
  6. In the Value data box, type 1, click Decimal, and then click OK.
  7. Quit Registry Editor.
Note If you follow these steps, users may be able to log on to the Windows Server 2003 Terminal Services computer. However, users will not be able to read the Terminal Services properties on the mapped Active Directory account. Therefore, users will not be able to access the profile path of the Terminal Server User Profile (TerminalServicesProfilePath) property, of the Terminal Services Home Directory (TerminalServicesHomeDirectory) property, or of other Terminal Services properties that are defined on that account. To resolve the problem, install the hotfix.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party technologies that this article discusses are developed by organizations that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these technologies.

Properties

Article ID: 902336 - Last Review: June 20, 2014 - Revision: 4.0
Applies to
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
Keywords: 
kbautohotfix kbwinserv2003sp2fix kbbug kbfix kbwinserv2003presp1fix kbhotfixserver kbqfe KB902336

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com