You cannot access domain interlinks from a Windows Server 2003-based client computer that belongs to an untrusted domain

Consider the following scenario:

• In a network environment, you have a domain A and a domain B.
• Domain A has a fully qualified name, "a.com." Domain A also has a NetBIOS name of "A."
• Domain B has a fully qualified name, "b.com." Domain B also has a NetBIOS name of "B."
• Domain A and domain B do not have a trust relationship.
• A Windows Server 2003-based client computer, computer A, joins domain A.
• A Windows Server 2003-based server, server B, joins domain B.
• In domain B, you create two DFS links: \\b.com\root1 and \\b.com\root2.
• In domain B, you create another DFS link, \\b.com\root1\link. This link points to \\b.com\root2.

When you try to access \\b.com\root1\link from computer A in this scenario, the attempt is unsuccessful. Additionally, you may receive the following error message:This problem does not occur if one of the following conditions is true:

• Computer A does not join domain A. Instead, computer A joins a workgroup.
• Computer A does not join domain A. Instead, computer A joins domain B, or computer A joins a domain that has a trust relationship with domain B.
• You do not access the DFS link \\b.com\root1\link from computer A. Instead, you directly access the DFS link \\b.com\root2 from computer A.

This problem occurs because the interlink in the DFS referral response for \\b.com\root1\link1 is recognized only by:

• Windows Server 2003-based client computers in a workgroup.
• Windows Server 2003-based client computers that join a domain in a trust relationship with the domain whose namespace contains the DFS link.

This interlink is not recognized by client computers that join other domains. Therefore, the client computers that join an untrusted domain cannot traverse domain interlinks.

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: 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

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released 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 item in Control Panel.
Windows Server 2003 with Service Pack 1, x86-based versions Windows Server 2003 with Service Pack 2, x86-based versions Windows Server 2003 with Service Pack 1, Itanium-based versions Windows Server 2003 with Service Pack 2, Itanium-based versions Windows Server 2003, x64-based versionsWindows Server 2003 with Service Pack 2, x64-based versions

To work around this problem, do not access the DFS interlink from computer A. Instead, directly access the target DFS link from computer A.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.