Wierd Network Slowness

[krispeters]

There are 2 computers here that are having wierd network slowness issues. Both are running Windows XP Pro. If they try to access the network through windows explorer it takes about 5 minutes to pull up the list of file shares on that computer. Once the list of shares is up it's really fast to access the shares and pull files off the network. Browsing the internet using intenet explorer works fine and has no problems. I can ping the computers fine before, during and after it is doing this. Mapped drives are very slow to initially open using windows explorer. But the odd part is that mapped drives are very fast to access if they go to it from a command prompt. Even if they go to the mapped drive using the command prompt first, then go to it in windows explorer, it will be fast in the command prompt, but then slow for windows explorer.

 

[jegray]

Just wondering... Are you using Novell Clients on these PC's?

Josh.

 

[krispeters]

No we are not using Novell clients.

 

[jc999]

Got the exact same problem here...was just about to post it myself. Hadn't tried it from the command prompt before but its the same situation - no delay.

Got lots of 2000 machines that are setup on our domain with the same settings as XP but dont have this problem.

Any ideas appreciated.

 

[bcastner]

First, remove the search for Scheduled Tasks:

Open the registry editor.

Go to

HKLM/Software/Microsoft/Windows/CurrentVersion/Explorer/RemoteComputer/NameSpace

Export this key (in order to back it up) and then delete the key called

{D6277990-4C6A-11CF-8D87-00AA0060F5BF} (Task Scheduler).

Close the registry.

Second, be sure to check your 'Binding Order' in Network Connections > Advanced.

Third, there is a redirector patch. See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;811169

Fourth, some file asssociation issues can play a role, as can context menu handlers. See: thread779-647815

Fifth, the issue can be one of the autodisconnection parameter being too small.

On the server
HKLM\System\CCS\Services\LanManServer\Parameters\Autodisconnect=0x0000FF

Note: The preceding entry must be located on the computer that offers the share or shares. The valid value range if you edit the LAN Autodisconnect parameter in the registry is 0 to 4294967295 (0xffffffff).
For a Windows 2000 Server in a Domain, running either as a domain controller or as a server, the maximum value is 65,535 (0xffff). Values set above this will be returned to 0xffff after policy refresh. Windows 2000 Servers in a
workgroup may be set to any value as indicated.

On the client
HKLM\System\CCS\Services\LanManWorkstation\Parameters\KeepConn=65535

Value : KeepConn REG_DWORD 1 to 65535 seconds
Default: 600 (10 minutes)
The value of KeepConn specifies the maximum amount of time that a connection can be left dormant.

Sixth, there are SMB signing and Opportunistic Locking Issues that should be addressed:

http://support.microsoft.com/default.aspx?scid=kb;en-us;814112

 

[bcastner]

I note too the general issue is likely a DNS issue. XP more than any previous issue uses DNS as its primary name resolution method. If DNS is not set correctly for XP clients in a Domain, name resolution will be slow or may not work at all.

A good discussion and suggestions can be found here: faq779-4017

 

[krispeters]

Turning off the search for integrated task scheduler and XP's integrated .ZIP handler and then rebooting seems to have fixed it, but the problem was somewhat intermittent so if it comes back I'll let you know.