Mapped drive from xp to w2k server slow

[sham14]

This is only from particular machine or two that mapped drive to a particular folder from xp client to w2k server is really slow - 20 - 30 secs to open a folder and sometimes it just hangs. Many of the subfolders (of problematic folder) are quite large - 1-4 gig but this slowness even happens on smallest of subfolder - with less than half a gig.
Can map drives to other folders on the same server with no problem.
Also when connecting to folder that has the problem from a terminal service connection it is absolutely fine - no slowness.
Tried disabling anti virus on mapped drive and recreating profile of user but with no success - also can't be network problem as other folders on server are fine from this pc.
Also using same profile on my own pc, I do not encounter problems.
Please any suggestions would be great.

 

[dholbrook]

Not clear if I understand completely the issue, but if the folder (and the subfolders under it are large, in the GB range, then the connection will not show up until the entire folder is browsed) is large, then the browse time across the network will be huge also. Note that the terminal services connection does not have the browse across the network issue, as you are only sending the desktop configuration across.

It appears you have a search issue that is compounded by having to send a huge amount of browsing data across a network. Try this:

On the server, create a new directory and share it. Into this directory, copy only one of the subdirectories from the original share, and see how long it takes to make the connection.

If this works fine, then you need to look at the network where these problem machines are located to see if you have a bottleneck happening. Try moving one of the desktops to a different hub and see if the problem goes away. If so, you have a network data collision issue to resolve on the original hub location. Also, you can try splitting up the share points to be smaller (lower level subdirectories) segments of the main directory, or dividing up how the data is stored on the server, putting only the data that needs to be shared in the share directory structure.

Remember that before the share will display, the entire directory-subdirectory structure will need to cross the network, and these are huge directories = lots of files = lots of data traffic. The fact that other directories work fine from the same server does not rule out the network as the bottleneck, as the data volume from these directories may be quite small and therefore fast to send.