Charlie, thank you for your post.
I am sorry that I wasn't more clear. The server OS is Windows 2003 R2 x64
(Intel) Enterprise Edition - SP2. The clients are all Windows XP SP2. The
problem occurs when listing the contents of the home directory folders on the
file server. Each group in the organization has its own folder. Each folder
has 100-350 folders in it, one for each users home folder. When listing
these folders through Windows Explorer, whether the console or from a network
share, it takes 10 seconds to 45 seconds to list the contents. Sometimes it
"times out" and does not list anything. We did not have this problem with
the old file server on the same physical network and connections.
Please help!
"Charlie Russel - MVP" wrote:
> First, some clarity - when you say listing folder contents is slow, could
> you tell me where you observe that? On the server console in Explorer? Or
> from a network share?
>
> If it's the second, then we need to know what OS's we're dealing with here
> on both the client and the server side of the equation. (I have my
> hunches...)
>
> --
> Charlie.
> http://msmvps.com/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "Bill Evans" <> wrote in message
> news:C1825F6F-B071-43DA-BD9B-...
> > Hello. I recently upgrade from a 4-year-old Dell server to a Quad Core
> > 64bit
> > server for file serving. Since the upgrade I have noticed that the
> > performance of file/folder access is not as it should be. It is very slow
> > listing folder contents. The data drive on the server is about 1TB
> > consisting of a few 300GB hard drives in a RAID5 array. Dell has been
> > unable
> > to help me resovle this issue over the last few weeks. They are saying
> > the
> > 1TB parition is too big and that we should not be using 5-300GB hard
> > drives.
> > However, that is the server they spec'd for us.
> >
> > Can someone help or shed some light on this? I have a hard time believing
> > that an older server is faster than the new one despite their comments.
> >
> > Thanks,
> >
> > - Bill E.
>