CPU pegged when browsing files over LAN

I setup Server 2003 for a small site and they are having major
performance problems browsing the shared filesystem, where opening a
folder might take as long as several minutes. During this time,
explorer goes non-responsive and they just have to wait it out or kill
the process.

This only happens over the network -- local browsing of the filesystem
from the server's console is lickity-split fast.

My first guesses were all the obvious places (duplex and speed
mismatches, name lookup errors, etc). Doing some traces, however, the
thing I noticed is that the CPU pegs at 100% utilization whenever
somebody starts opening folders, and this appears to be the culprit
entirely. The CPU does not peg when the same filesystem is accessed
locally, and there are no other obvious errors in the network
configuration.

The CPU shows the big hogs as lsass.exe and dfssvc.exe. Something is
amiss here, and I'm not really sure what it is, since I'm not entirely
sure what these things do and how they could be causing so much
difficulty for network clients only. Any advice appreciated.

Thanks!

(E-Mail Removed) (Eric A. Hall) wrote in message news:<(E-Mail Removed) om>...
> I setup Server 2003 for a small site and they are having major
> performance problems browsing the shared filesystem, where opening a
> folder might take as long as several minutes.

> The CPU shows the big hogs as lsass.exe and dfssvc.exe. Something is
> amiss here

Further experimentation reveals that this only happens when the
sharename is accessed, and DOES NOT HAPPEN if the administrative share
for the drive is used. For example if the E:\Storage share is opened,
the system collapses, but if the e$ hidden share is used and the
storage directory opened there is no problem.

Anybody got any ideas here?

Thanks!

Did you found what was the problem?? I'm having the exact same problem. This
2 processes take about 70% of the cpu when the network is used.

Any help is welcome.


"Eric A. Hall" wrote:

> (E-Mail Removed) (Eric A. Hall) wrote in message news:<(E-Mail Removed) om>...
> > I setup Server 2003 for a small site and they are having major
> > performance problems browsing the shared filesystem, where opening a
> > folder might take as long as several minutes.
>
> > The CPU shows the big hogs as lsass.exe and dfssvc.exe. Something is
> > amiss here
>
> Further experimentation reveals that this only happens when the
> sharename is accessed, and DOES NOT HAPPEN if the administrative share
> for the drive is used. For example if the E:\Storage share is opened,
> the system collapses, but if the e$ hidden share is used and the
> storage directory opened there is no problem.
>
> Anybody got any ideas here?
>
> Thanks!
>