Slow connection to mapped drive
Posted on 2003-10-29
I have a problem with proper configuration of my system.
At work I have a few computers.
One is a server running Windows 2000.
The second is a workstation running Windows 98.
The third is a workstation running Windows XP Pro.
Now, I've mapped the server's partition on both workstations, but there's a high performance problem on XP one. When I enter the mapped drive from 98 running workstation and switch directories - I get an instant reaction, but when I do that from XP one - I get to wait about 10 or more seconds to get on the disk or sometimes to change a directory.
That's a little annoying, but I got used to that. The bigger problem is that I'm trying to do some remote work from home, where I have XP Pro too and I get the same problem as I do at work, but to a much bigger extent.
I've mapped the Windows 2000 server from my work to my PC at home. I get to wait a minute sometimes, just to see the root directory, not to say that "My Computer" and generally Explorer tends to stop for a few seconds from time to time as long as the remote drive is mapped.
At work I have a 10Mbit LAN and a 1024/128kbit DSL internet connection and at home I have 512/128kbit DSL. Everything works smooth, I can watch TV online (BBC NEWS), but can't get to connect to my work fast.
It gets on my nerves now. I'm trying to update my project's files from a repository and have to wait 2-3 hours just to check their status and that shouldn't take so much time just to check the dates of 1256 files.
That is why I don't recommend using ComponentSoftware RCS (Revision Control System) - an application so badly optimized for networked use it should never be released - the worst decision of my boss to use that one.
Should I change something with my TCP/IP settings? Anything with the Services or Policies should be changed? Please help!
Thanks for any working suggestions.
The damn thing makes me wait 10 secs just to start copying any file from that mapped drive at work...