Access to files on sharedd folders sometimes slow

I'm in the process of moving our network fileshares from Netware 6.5 boxes to
Win2003 Server boxes (as we are phasing out Netware).

Some users (including myself) have noticed since the move that occasionally
an Office 2003 document will take a few seconds (10 -15 secs) to open. You
can then open the same document later and it comes up straight away. This
only happens occasionally and seems totally random. Clients are Win2000 or XP
(still have the Netware client on until the phase out project is complete).

Any ideas

Thanks
Dave

Are you running the fileshares on a Domain Controller? Check this article out:
http://support.microsoft.com/default...321098&SD=MSKB

"Dave Fitton" wrote:

> I'm in the process of moving our network fileshares from Netware 6.5 boxes to
> Win2003 Server boxes (as we are phasing out Netware).
>
> Some users (including myself) have noticed since the move that occasionally
> an Office 2003 document will take a few seconds (10 -15 secs) to open. You
> can then open the same document later and it comes up straight away. This
> only happens occasionally and seems totally random. Clients are Win2000 or XP
> (still have the Netware client on until the phase out project is complete).
>
> Any ideas
>
> Thanks
> Dave

No it's a dedicated fileserver - no other roles on there

"Jonas Back" wrote:

> Are you running the fileshares on a Domain Controller? Check this article out:
> http://support.microsoft.com/default...321098&SD=MSKB
>
> "Dave Fitton" wrote:
>
> > I'm in the process of moving our network fileshares from Netware 6.5 boxes to
> > Win2003 Server boxes (as we are phasing out Netware).
> >
> > Some users (including myself) have noticed since the move that occasionally
> > an Office 2003 document will take a few seconds (10 -15 secs) to open. You
> > can then open the same document later and it comes up straight away. This
> > only happens occasionally and seems totally random. Clients are Win2000 or XP
> > (still have the Netware client on until the phase out project is complete).
> >
> > Any ideas
> >
> > Thanks
> > Dave

"Dave Fitton" <(E-Mail Removed)> wrote in message
news:A79534B3-22F3-4DA9-885E-(E-Mail Removed)...
> No it's a dedicated fileserver - no other roles on there

Could be a physical problem. Bad Nic (or bad drivers), bad cables, bad
Switch Port (or hub port), bad cable termination at a patch panel. Could be
environment problems, like running ethernet cables over a flouresent light,
over heavy power cables in the building, etc. Don't always assume the
problem is software or is Windows.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

....and don't forget to check SPEED/DUPLEX settings on both the computer AND
the switchport. They should be put to the same setting. For example, you
should NOT have the server set to AUTO/AUTO and the switch port to 100/FD.

"Phillip Windell" wrote:

> "Dave Fitton" <(E-Mail Removed)> wrote in message
> news:A79534B3-22F3-4DA9-885E-(E-Mail Removed)...
> > No it's a dedicated fileserver - no other roles on there
>
> Could be a physical problem. Bad Nic (or bad drivers), bad cables, bad
> Switch Port (or hub port), bad cable termination at a patch panel. Could be
> environment problems, like running ethernet cables over a flouresent light,
> over heavy power cables in the building, etc. Don't always assume the
> problem is software or is Windows.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

Yes, that's right, infact some gigbit hardware had problems with the "auto"
not working very dependably and did better if each one was explicitly set.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Jonas Back" <(E-Mail Removed)> wrote in message
news:8A1BD11C-A855-4E57-8201-(E-Mail Removed)...
> ...and don't forget to check SPEED/DUPLEX settings on both the computer
AND
> the switchport. They should be put to the same setting. For example, you
> should NOT have the server set to AUTO/AUTO and the switch port to 100/FD.
>
> "Phillip Windell" wrote:
>
> > "Dave Fitton" <(E-Mail Removed)> wrote in message
> > news:A79534B3-22F3-4DA9-885E-(E-Mail Removed)...
> > > No it's a dedicated fileserver - no other roles on there
> >
> > Could be a physical problem. Bad Nic (or bad drivers), bad cables, bad
> > Switch Port (or hub port), bad cable termination at a patch panel.
Could be
> > environment problems, like running ethernet cables over a flouresent
light,
> > over heavy power cables in the building, etc. Don't always assume the
> > problem is software or is Windows.
> >
> > --
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> >