A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Windows Explorer extremely slow to load specific network folders



 
 
Thread Tools Display Modes
  #1  
Old February 2nd 10, 06:14 PM posted to microsoft.public.windowsxp.network_web
Mark W[_3_]
external usenet poster
 
Posts: 1
Default Windows Explorer extremely slow to load specific network folders

Hello,

We have a Windows Server 2003 domain environment with a NetApp FAS2020 SAN.

When we are on our client machines (XP SP3) or server machines (2003 R2) and
browse to specific folders on a share of the FAS2020, the folder can take
10-20 minutes or more to open. Sometimes it opens instantly, other times it
locks up as described above.

This happens whether the folders are accessed via mapped drive or UNC
sharename (\\servername\folder1\folder2).

We have done some packet captures while this is happening, and we see
filenames and abridged contents of what appears to be all files in the
subdirectories below.

NetApp is clueless on the issue and blames it on Windows.

Due to the traffic we are seeing on the wire, I also suspect that it may be
a Windows issue. Windows seems to be querying for every filename and some of
each file's contents.

However, we previously had the same directory structure on a Server 2003 NAS
machine and this was never an issue.

We have ruled out our AntiVirus product as the cause (Symantec Endpoint
Protection 11) due to this being an issue on unprotected machines as well.

The folder structure is large (154,000 files, 13,000 folders). A workaround
might be to break this up into different root level folders, but I feel that
that shouldn't be neccessary (especially as this has worked in the past).

Any ideas or comments?

Thanks!
Ads
  #2  
Old October 4th 10, 03:42 PM posted to microsoft.public.windowsxp.network_web
Phill Patton
external usenet poster
 
Posts: 1
Default some folders/files very slow to copy compared to others

I have this problem too.
Have you had any luck resolving it?

I pretty sure (for my case) that it has something to do with files being open/used by multiple users.
They don't have the rights to modify the files, but copying the files (as a test for slowness) shows they're slow. It's an NTFS volume. ONTAP release 7.3.3

I tried this test this morning before too many people had loaded their spreadsheets (which access these addins. xla and xll files)
Copy speed was normal. This afternoon it's worse than ever.

We are in the middle of migrating users from Office 2002 on Windows XP 32bit & Windows 2003 32bit to Office 2007 on the same OSes. The problem cripples Office 2007 when loading these addins.

I think it's probably some locking issue/bug.

Any ideas appreciated.


On Tuesday, February 02, 2010 1:14 PM Mark W wrote:


Hello,

We have a Windows Server 2003 domain environment with a NetApp FAS2020 SAN.

When we are on our client machines (XP SP3) or server machines (2003 R2) and
browse to specific folders on a share of the FAS2020, the folder can take
10-20 minutes or more to open. Sometimes it opens instantly, other times it
locks up as described above.

This happens whether the folders are accessed via mapped drive or UNC
sharename (\\servername\folder1\folder2).

We have done some packet captures while this is happening, and we see
filenames and abridged contents of what appears to be all files in the
subdirectories below.

NetApp is clueless on the issue and blames it on Windows.

Due to the traffic we are seeing on the wire, I also suspect that it may be
a Windows issue. Windows seems to be querying for every filename and some of
each file's contents.

However, we previously had the same directory structure on a Server 2003 NAS
machine and this was never an issue.

We have ruled out our AntiVirus product as the cause (Symantec Endpoint
Protection 11) due to this being an issue on unprotected machines as well.

The folder structure is large (154,000 files, 13,000 folders). A workaround
might be to break this up into different root level folders, but I feel that
that should not be neccessary (especially as this has worked in the past).

Any ideas or comments?

Thanks!



Submitted via EggHeadCafe - Software Developer Portal of Choice
Using ASP.NET Session with Silverlight and WCF Services
http://www.eggheadcafe.com/tutorials...-services.aspx

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 01:51 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.
Copyright 2004-2023 PCbanter.
The comments are property of their posters.