You experience a delay when you use your Windows XP computer to log on to a domain or to connect to a network resource

• After you type your password at the logon screen, the computer may appear to stop responding (hang). This behavior occurs from the time when Group Policy is processed until the time that a blue screen appears, just before the desktop icons appear. This can last several minutes.
• During the logon process, you see an "Applying Computer Settings" message for several minutes. However, you can log on the same computer quickly when the network connection is unplugged.
• There is a long delay when you try to open a network share.
• When you try to open a file that resides on a Distributed File System (DFS) share, it may take from 90 seconds to 15 minutes to open. However, you may be able to quickly open the same file by using the direct path of the file.
• When you use Microsoft Internet Explorer 6 to access shares on a Microsoft Windows NT 4.0-based server or on a Microsoft Windows 2000-based server, access to the shares may appear to stop responding (hang).
  
  Note You may gain access to the requested shares if you wait a long time, perhaps10 minutes or more.

Back to the top | Give Feedback

• The WebClient waits for a response from the proxy server. The response may never be sent. If the response is never sent, there is a delay until the WebClient times out. The default for this delay is 10 minutes.
• If the destination server does not support HTTP on TCP port 80, or if the destination server is offline, the proxy server may not send the expected HTTP error code back to the WebClient.
• If there is a dead external DFS server reference on the proxy where the request is passed, the delay can be because of the timeout for the external DFS connection failure.
• The Network Provider Order lists Web Client Network before it lists Microsoft Windows Network.
• The domain controller that is used for authentication runs a service that listens on TCP port 80. For example, the domain controller is also an Exchange server with Outlook Web Access (OWA).
• Internet Explorer's proxy server settings are not configured as Bypass proxy for local addresses. Also, local intranet Fully Qualified Domain Names are not entered in the exclusion list.
• The PATH statement variable contains a reference to a DFS link, such as the following:
  PATH=\\corp.domain.com\dfsroot\DFSLink;C:\WINDOWS\system32;

Back to the top | Give Feedback

Method 1: Install the latest Windows XP service pack

1. Right-click My Computer, and then click Properties.
2. On the General tab, under System, locate the service pack version.

Method 2: Configure Internet Explorer to bypass the proxy server

1. Start Internet Explorer.
2. Click Tools, and then click Internet Options.
3. Click the Connections tab, and then click LAN Settings.
4. If the Use a proxy server check box is not selected, go to the next method.
   If the Use a proxy server check box is selected, click to select the Bypass proxy server for local addresses check box.
5. Click Advanced.
6. In the Exceptions box, type the fully qualified domain names of all the local servers, and then click OK three times.

Method 3: Change the order of network providers

1. On the desktop, right-click My Network Places, and then click Properties.
2. On the Advanced menu, click Advanced Settings.
3. On the Provider Order tab, in the Network Providers list, click Web Client Network.
4. Press DOWN ARROW so that Web Client Network is the last provider in the list, and then click OK.

Method 4: Install the relevant hotfixes

Method 5: Adjust the installation of Internet Explorer

1. The Multiple UNC Provider (MUP) is notified that the client has to connect to domaincontroller1.domain.com, or just a NetBIOS name of the logon server. Available redirectors are informed.
2. WebClient tries to handle the request.
3. WinInet loads and reads the proxy configuration from the registry:
   HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings

   
   ProxyEnable
   ProxyOverride
   ProxyServer
4. If these three keys are set to use a proxy server, WinInet sends request to the proxy server. This may time out and fail. If it does, the WebClient service returns a negative response to the MUP.

	"ProxyEnable"=1
	"ProxyServer"="http://ProxyServername:PortNumber"
	"ProxyOverride"="*.intranet; domaincontroller1;*.domain.com;10.10.*;<local>"

1. In Internet Explorer, click Tools, and then click Internet Options.
2. Click the Connections tab, and then click LAN Settings.
3. Click Advanced.
4. In the Exceptions box, type the appropriate information.

function FindProxyForURL(url, host)
{
}

function FindProxyForURL(url, host)
{if (shExpMatch(host, "DCNAME*")) {                
     return "DIRECT";                                 
 } 

Back to the top | Give Feedback

• If it is possible, stop the service that listens on TCP port 80 on the domain controller or on the file server.
• Disable the WebClient service on the Windows XP client.

1. Click Start, point to All Programs, point to Administrative Tools, and then click Computer Management.
2. In the details pane, double-click Services and Applications.
3. Double-click Services.
4. Right-click WebClient, and then click Properties.
5. Click the General tab.
6. In the Startup type list, click Disabled.
7. Click Apply, and then click OK.

1. Disable the WebClient service.
2. Install a program that uses Web folders. For example, install Microsoft Office XP or a later version.
3. Delete your original network place.
4. Create a new network place.

Back to the top | Give Feedback

Windows XP WebDAV Redirector

Windows XP

 
  HTTP: User-Agent = Microsoft-WebDAV-MiniRedir/5.1.2600

Microsoft Office

HTTP: User-Agent = Microsoft Data Access Internet Publishing Provider DAV 

Notes

• By default on Windows Server 2003, the WebDAV client is not enabled for security reasons. You have to enable the WebClient service.
• Using Microsoft Office 2000 to connect to a Windows WebDAV share is only supported if Office 2000 is running on Windows 2000 or earlier operating systems. Using Office 2000 running on Windows XP-based computer to connect to a Windows WebDAV share is not supported.
• When you use Microsoft Office on a Windows XP-based computer, use the Office WebDAV redirector instead of the Windows XP file redirector. Generally, when you use Microsoft Office products, it is best to use files that are represented by their HTTP names instead of their UNC paths. For example, use "http://Device Name/Virtual Root/File Name" instead of "\\Device Name\Virtual Root\File Name."

URLScan blocks WebDAV requests

Registry setting for timeouts

Back to the top | Give Feedback