General discussion

Locked

Why is initial access slow on network?

By jim_kinee ·
I have recently added a Windows 2000 w/SP1 system to an NT4.0 w/SP6A network. When opening a file by double clicking in explorer the file takes an unusually long time to open (30 seconds or more for a 20K file). When opening a similarly sized file through the application the file opens almost immediately (as it should). It does not matter what the application is as the problems exist using MS Office, TIFFs or Adobe Pagemaker files.

The Server and the W2K system are using TCPIP. All other machines on the LAN are NT4 or W95 using TCPIP and do not experience the same problem.

What could be causing the problem?

This conversation is currently closed to new comments.

85 total posts (Page 4 of 9)   Prev   02 | 03 | 04 | 05 | 06   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Why is initial access slow on network?

by jim_kinee In reply to Why is initial access slo ...

Poster rated this answer

Collapse -

Why is initial access slow on network?

by paradis In reply to Why is initial access slo ...

Several suggestions:

The name resolution issues probably aren't the reason for the slowdown; they would cause initial access to a remote machine to be slower, but once a connection is open, windows does not resolve the name again, it caches the address. I'd check them anyway, though, because NT and 2k DO use different name resolution mechanisms by default (DNS for 2k, WINS for NT4)

As for the explorer problem, try disabling Web View if it's on; Web View contains a preview pane that will attempt to display a preview of the currently selected file. Since opening a file from explorer also selects it in the explorer window, the system will attempt to load the file it it's associated app AND generate the preview at the same time, thus slowing access.

Aside from that, there will be a speed difference between using the open dialog and using explorer, since explorer must either load the associated application or communicate with it via DDE to open the file, depending on whether the app supports using DDE to control an existing instance.

For apps that do not support DDE, windows executes a new instance of the application and passes it the filename on the command line; for apps that support DDE and specify this in the registry, Windows checks if the app is loaded; if not it executes it. When the app is running, windows opens a DDE connection and instructs the app to open the file

Since the open dialog for an app is part of the application, the name of the file to openis passed (in-process, quickly) from the dialog to the app, and avoids the (slow) interprocess communication required for DDE and/or the (even slower) creation of a new process.

Collapse -

Why is initial access slow on network?

by jim_kinee In reply to Why is initial access slo ...

Poster rated this answer

Collapse -

Why is initial access slow on network?

by paradis In reply to Why is initial access slo ...

Several suggestions:

The name resolution issues probably aren't the reason for the slowdown; they would cause initial access to a remote machine to be slower, but once a connection is open, windows does not resolve the name again, it caches the address. I'd check them anyway, though, because NT and 2k DO use different name resolution mechanisms by default (DNS for 2k, WINS for NT4)

As for the explorer problem, try disabling Web View if it's on; Web View contains a preview pane that will attempt to display a preview of the currently selected file. Since opening a file from explorer also selects it in the explorer window, the system will attempt to load the file it it's associated app AND generate the preview at the same time, thus slowing access.

Aside from that, there will be a speed difference between using the open dialog and using explorer, since explorer must either load the associated application or communicate with it via DDE to open the file, depending on whether the app supports using DDE to control an existing instance.

For apps that do not support DDE, windows executes a new instance of the application and passes it the filename on the command line; for apps that support DDE and specify this in the registry, Windows checks if the app is loaded; if not it executes it. When the app is running, windows opens a DDE connection and instructs the app to open the file

Since the open dialog for an app is part of the application, the name of the file to openis passed (in-process, quickly) from the dialog to the app, and avoids the (slow) interprocess communication required for DDE and/or the (even slower) creation of a new process.

Collapse -

Why is initial access slow on network?

by paradis In reply to Why is initial access slo ...

Please forgive the duplication, my browser timed out on the first submission.

Collapse -

Why is initial access slow on network?

by jim_kinee In reply to Why is initial access slo ...

Poster rated this answer

Collapse -

Why is initial access slow on network?

by dcyr In reply to Why is initial access slo ...

I experienced the same problem and found it to be a problem generated by using some of the NT4 system policies. Specifically, I had drive letters that were mapped via a system policy. When I attempted to access the file via explorer, it took 3 timesas long. I removed that portion of the system policy and mapped drive letters through a logon script, and then the problem vanished. Have you considered watching the traffic with netmon? It may reveal something completely unrelated. Another tack to take is to open the file in explorer via my network places instead of a mapped drive.

Collapse -

Why is initial access slow on network?

by jim_kinee In reply to Why is initial access slo ...

Poster rated this answer

Collapse -

Why is initial access slow on network?

by Goodwin2000 In reply to Why is initial access slo ...

Are all the file associations correct in explorer? I've seen this on my job a couple of times where openiong a file through explorer would hang or err out due to incorrect file association information. Yet would open fine through the Application it was designed in, i.e. Excel.

Have you tried reloading just Explorer to see if the Explorer.exe may not be corrupt for some reason.

Hope this helps

Collapse -

Why is initial access slow on network?

by jim_kinee In reply to Why is initial access slo ...

Poster rated this answer

Back to Windows Forum
85 total posts (Page 4 of 9)   Prev   02 | 03 | 04 | 05 | 06   Next

Related Discussions

Related Forums