I'm facing the same problem, additionaly i found that if u close the open
file from client the server still shows that file being used by that client
some time it close after long time, this is critical when a client cpu get
stuck while a file open other clients can't acces that file, I got some
information regarding this in microsoft website
http://support.microsoft.com/?kbid=150384
I edited the registry i feel i got some speed in file accesing but still i
face the problem when a client get stuck. this problem becs of when a client
close the file the server must disconnect that file, we have novell server as
file server i check this matter it's disconnecting closed file immediatly. i
thing if u find solution for this u can solve ur problem. I'm still tring to
get solutin for this if u hav any ideas pls reply

thanks
cani

"chris@groupinfo.com" wrote:

> Thank you for the reply. We did try stopping Symantec Antivirus on
> both the server and the client PC, and still the same results. We did
> finally narrow this problem down somewhat after quite a bit of testing.
> The problem seems to be with a specific share on our server that is
> used by multiple people (I showed about 54 concurrent on average at a
> given time). We compared two mapped drives from the client PC, both
> mapped to the same folder on the server's filesystem, one going through
> the specific share used by multiple people, and also a share only used
> by the client PC user. For example, one drive is mapped to
> "\\server\home\userfolder" and the other drive is mapped to
> "\\server\userfolder" ; both point to the same exact folder on the
> server. The performance on the share used by multiple people was quite
> poor (\\server\home\userfolder), and showed all the signs of our
> initial problem (Word/Excel writing back around 100 bytes/sec.).
> However the share used by only the client PC user (\\server\userfolder)
> was significantly faster.
>
> Our server has more than enough resources (dual Xeon 3.0 GHz, 2 GB RAM)
> and CPU usage is quite low (< 10%) and only about 25% of the physical
> memory is being used. Plus I would think that if the server was being
> taxed somehow that it would affect all shares.
>
> We are trying to find any information on this type of problem, and so
> far come up empty handed. Has anybody seen this type of problem
> before?
>
> Thank you again for all feedback and help!!
> --
> Chris
>
>