Microsoft KB Archive/905464

= You cannot download shared resources on a Windows Server 2003 domain controller by using BITS 2.0 if the UNC path of the server points to itself =

Article ID: 905464

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

-



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:

256986 Description of the Microsoft Windows registry



SYMPTOMS
On a domain controller that is running Microsoft Windows Server 2003, a download is unsuccessful when the following conditions are true:
 * You use Background Intelligent Transfer Service (BITS) 2.0 to try to download shared resources from the domain controller itself.
 * You use the Universal Naming Convention (UNC) path of the domain controller for the download.

You do not experience this problem when you use the UNC path of another server. You also do not experience this problem when you use the UNC path of the domain controller from another computer.



CAUSE
This problem occurs because of a problem in BITS 2.0.

BITS 2.0 uses the Windows Server 2003 redirector. Because of the shadow loopback feature in Windows Server 2003, an operation that uses the UNC path of the local server is typically interpreted by BITS 2.0 as a direct disk I/O operation. Therefore, BITS 2.0 does not use the Windows Server 2003 redirector for the operation.



WORKAROUND
To work around this problem, use one of the following methods.

Method 1: Map the shared resources to a drive
Map the shared resources to a drive. Then, use that drive to download the shared resources.

Method 2: Disable the shadow loopback feature
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.

Add the DisableShadowLoopback registry entry to the Windows registry. Then, enable the entry. To add this registry entry, follow these steps:  Click Start, click Run, type regedit in the Open box, and then click OK. In the left pane, locate and then click the following registry subkey:

 On the Edit menu, point to New, and then click DWORD Value. Type DisableShadowLoopback, and then press ENTER. Double-click DisableShadowLoopback. In the Value data box, type 1, and then click OK.</li> Quit Registry Editor.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
Typically, the Windows Server 2003 redirector uses the shadow loopback feature to decide whether the local file system should handle an I/O operation. However, when you use BITS, the redirector handles the I/O operation even if the local file system would otherwise handle the operation.

Keywords: kbtshoot kbfileprintservices kbwinservnetwork KB905464

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.