We help IT Professionals succeed at work.

share too slow over wan

Gang, I have an office in Alabama that accesses shares over the WAN to San Diego. Accessing the shares is taking forever (minutes) to resolve the contents of the share. Im doing the same exact process with other offices farther away and it works fine as shares resolve in a few seconds. There is no saturation on the wan pipe. Is this a browning issues or smb ? Any ideas?
Comment
Watch Question

Commented:
Since your other shares from the hub are working fine, I'd check the speed of your broadband pipe in Alabama.  Check your router in bama, see what your traffic consists of.  You could have 5-10 users downloading multimedia that is choking your bandwidth.

Author

Commented:
Pipe looks good. This has been going on for months. If this were a routing issue which protocl should I focus on?

Commented:
Are there servers in Bama that you test by creating a share from San Diego?  See if the problem is two-way.

Workstations in bama the same as workstations in other locations that work fine?  OS, RAM, NIC, etc.

Author

Commented:


I've done more research. I've discovered the problem is not with mapped drives but auto created drives in RDP or citrix sessions. Why does a mapped drive resolve so much faster then a autocreated drive in a terminal server session (or citrix)?  

Commented:
You hadn't mentioned Citrix and/or Terminal Services until now.

To answer your question, I would gather that the more complicated the instance (TS/Citrix), the more technical "overhead" there would be.  TS/Citrix is an app running on a hosted server (200x).  I bet if you mapped a drive from the server itself, it would be fast.

So, back to your original post, the fast shares were coming from end points that were using simple AD mapped drives and the slow shares were coming from locations that were using Citrix/TS?

Author

Commented:
Yes, sorry for being vague and you are correct, mapped drives are much faster. However, the auto created drives resolve much faster from all my other AD sites. The only difference I’ve noticed is that this site is running a win2k3 sp1 DC and the others are win2k3 SP2 DC’s. May or may not be the issue. Im curious if anyone knows how what protocol, process or routing  technics rdp uses to handle auto created drives? It’s still using smb right? Is dns or wins routing a possible culprit?
Commented:
You might be in a nic flood. Upgrade to SP2.

See this thread on intermittent connectivity pertaining to SP1:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23681992.html