Windows 2003 access problem

[Burny1]

Hi all,

I have the following problem and cannot seem to get a sustainable solution. Since we moved over from Windows 2000 to XP, I keep on having very long lags when I try and access a mapped network drive.
If I go into explorer and click on my computer, explorer hangs for roughly 3 - 5 mins (depending on the machine I use) before it brings up my list of mapped drives. After that I can access the files. If I leave the machine for say 30min I go through the same rigmarole again. The only thing I can think of what it could be is that the workstation is trying to make an encrypted link to the server and then waits for 3 - 5min before it aborts the attempt and makes a normal connection. I have even set up a certificate server and imported the certificate to the clients, however it still does not want to work. Funnely enough, some of the workstations do not have the same problem, however they are exactly the same as the troublesome units. Any ideas on how I can solve this - apart from throwing Windows out and go Linux[}:)][;)]

[Perdition]

This may have something to do with scheduled tasks. Try the following on a client machine and see if it helps :

http://www.michna.com/kb/WxSlowNetworkBrowsing.htm

[mbs]

Somebody said to me the other day that this problem is caused by the indexing done by Windows, and that one should switch it off. Apparently, every time a networked drive is accessed, Windows will actively re-index its internals (or something), ostensibly to make a search/find go faster. Dunno if this is true or absolute BS - if you want to switch it off, it's apparently somewhere in the services. Personally, I'd go for Linux as a server, and use Samba for mapping networked drives to Windows clients...

[regardtv]

Uhm - might be mistaken here but I generally only see this on non-domain based networks.

I generally throw a single linux box with Samba 3 into the mix. I make it the master browser - problem seems to dissapear.... might be totally off track though.

[Perdition]

For some reason Windows 2003 Server and Windows XP have a few issues with networking. I've run into a few myself and the solution I posted above sorted out one of those issues for me, however the delay I had was more in the region of 20 seconds or so.

Other than the couple of networking issues with XP Windows 2003 is an excellent server OS, so I would not recommend throwing it out for Linux despite what the fanboys tell you [;)]

[Andre]

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by Perdition</i>
<br />This may have something to do with scheduled tasks. Try the following on a client machine and see if it helps :
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

Interesting one. There is one computer here with that problem. Just tried the fix and will see if it helps.

[Burny1]

Thanks guys[:D]

Will try it and give an update.

[dikbek]

Have a look at http://www.ss64.com/nt/slow_browsing.html

Also try googling "winxp slow network browsing"

[Burny1]

Hi all,

Well i tried the first fix mentioned and it did not make any dif. I played around a bit more and found that when I make a vpn connection into the server, all the problems with slow access disappears.

Any ideas?

Thanks for all the help guys!

Bernard

p.s Perdition - i'll try the links tomorrow. Thanks