Windows Forum

Ask something
Discussion Locked

Delays when opening a network share

0 helpful
9 replies

by nate from ri

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running Win2000 Pro and logging into an NT4 server/domain. I also log into a netware 5 server using Novell Client v4.8. The PC is a Dell Optiplex GX1, 600MHz, 256MB RAM. The problem is when I access a share on an NT 4 server, the share can take upwards of a minute to finally open. Any further operations (cuts, copies, pastes, opens) also take a very long time. While browsing to the server I can quickly open the domain and even the server, but the shares within are always slow. My profile loads quickly off this server. I have no delays accessing Novell volumes, internet or any other network resources. The server operate at a normal speed from other clients including Win98 on the same PC. Printing through queues on this server is quick. Any ideas?

9 replies

by elmagoal

When Windows NT lists a directory (Explorer, DIR command, etc.) on an NTFS volume, it updates the LastAccess time stamp on each directory it detects. If there are a very large number of directories, this can affect performance.

To control this feature use Regedit to edit the key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

Add Value name "NtfsDisableLastAccessUpdate" of type REG_DWORD. Set it to "1" to prevent the LastAccess time stamp from being updated.Registry Settings:
Key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
Value Name: NtfsDisableLastAccessUpdate
Data Type: REG_DWORD
Data: (0 = disable, 1 = enable)

by jessed

(This only applies if you're using IPX for the NetWare.) Does the NT server have IPX/SPX Compatible installed? If so, is the frame type forced to that of the NetWare server? If IPX on your Win2K Pro box is higher in the binding order than IP (presuming that's what you're using on the NT side), it will try to use that protocol for everything. If IPX is on the NT server, but the frame type doesn't match, it will take a while to time out before switching to IP. This also supports the browse list coming up quickly, that's probably a WINS operation, which is IP only and won't even try with IPX.

Lots of variables in answering this question, but interested to see what the outcome is.

-jd

by jaystar

Nate,

I am currently experiencing the same situation. I, however, have noticed that only when viewing a share through My Computer or My Network Places do I get the slow down. When I am in any office 2000 product, I don't see it. If you could confirm this for me at your site I would appriciate it.

Thanks,
Jay Starling

by nate from ri

I checked that out and found the same delay through the office products. Please let me know anything else that you discover about this problem.

by chris

I am replying to this question only because I am looking for an answer to this problem too. About a week ago I read a very detailed discription of a similar problem, and a registry fix that resolved the problem. Why I didn't print the article then- I don't know :-(
Basically the article stated that when Windows 2000 connects to another machine, it is trying to look at the scheduled tasks on that machine. This may take a while to time out on Windows NT and Netware boxes. The registry hack the article recommended stopped 2000 from 'automatically' checking the scheduled tasks on remote computers.
I know this is a vague answer, but it seemed to fit the discription of your problem.

This discussion is closed to new replies.