Slow opening of files

[Les Desser]

After a disk crash and recovery, I have a problem where opening files
down the network (Word, Excel, etc.) or showing the file list is
preceded by a significant delay (maybe 5-10 seconds).

I have a server with W2K Server (same problem when trying with W2K Pro)
running on an EIDE drive and all date on second SCSI drive. The network
is set up as a simple Workgroup - no domains.

It all worked fine before the crash.

Any ideas what may be causing the delay? Once a file is opened and then
closed, the next open of the same file is fast. Open a different file
and we have a delay.

Thanks.

 

[G]

Do you have drive letter(s) mapped to the shared folder(s)? Sometimes that
will speed thing up significantly.

 

[Les Desser]

Do you have drive letter(s) mapped to the shared folder(s)? Sometimes that
will speed thing up significantly.

No - I will try it, but it worked OK before.

I now actually think the problem is with my W2K PC rather than the
server. Trying the same things from an other PC on the network seems to
work fine. Looks like time to do a Windows rebuild on by PC

 

[Jetro]

How big is SCSI partition?
HKLM\SYSTEM\CCS\Control\FileSystem, dword NtfsDisableLastAccessUpdate, value
1.

 

[Les Desser]

How big is SCSI partition?

2.6 GB NTFS 42% free

HKLM\SYSTEM\CCS\Control\FileSystem, dword NtfsDisableLastAccessUpdate, value
1.

What is the significance of that?

 

[Jetro]

Forget it.

 

[Marina Roos]

An 169-address is an address that the networkadapter gives itselfs if it
can't find a DHCP-server.
In Networkconnections, Advanced, Advanced you can set the bindingorder for
your lancards.

Marina

 

[Les Desser]

An 169-address is an address that the networkadapter gives itselfs if
it can't find a DHCP-server. In Networkconnections, Advanced, Advanced
you can set the bindingorder for your lancards.

Thanks - found it. That should solve the problem - I will test it
shortly.

However, even if the order is wrong, should not the delay only happen
the first time? Once Windows knows that \\Server is on adapter Y, it
should not look at X every time.