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 3 of 9)   Prev   01 | 02 | 03 | 04 | 05   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 ...

Not a DOS problem as far as I can tell. Thanks.

Collapse -

Why is initial access slow on network?

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

Jim - In Explorer, your PC needs load and open the application before it loads your file. When you already have the application open, it need only load your file.

Collapse -

Why is initial access slow on network?

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

This doesn't only happen when you double click a file. If you sincle-click certain files the system seems to wait to cache the info.

Collapse -

Why is initial access slow on network?

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

Are you using offline folders? I have the same behavior on a large offline folder (about 2G). I had to disable the offline folder and manually cleaned up the client cache directory (SystemRoot\CRC).

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 YammiMan In reply to Why is initial access slo ...

From my understanding, when a WIN2K system is added to an NT4.0 network, it defaults to being the master browser regardless of what was set on the NT boxes. This causes a slowdown in the determining on the network who the master browser actually is. To fix the problem, determine what box you want to be the master browser and set the other box to be a backup. It is recommended to use the WIN2K box to be the master browser.

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 A.R.H. In reply to Why is initial access slo ...

Adding Win2k means that dns is used for both internal and external file requests. Win2K is trying to find the host using dns. Is the win2k station set to use WINS? Even if it is, DNS has priority because it assumes the Win2k server is running dynamic dns. I think explorer makes different requests than most apps (especially win2k explorer!) so it is get lagged out looking for dns entries. Try a hosts file on the local machine to see if that speeds it up or make a dns entry in your local zone.

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 Slogmeister In reply to Why is initial access slo ...

I think Yammiman is right. Check your event logs on your NT server and see if there are massive amounts of browser elections going on. They may not be able to decide who is the master browser or not. There is a registry entry that will stop a machine from requesting to be the master browser, but I don't remember what it is. - It should be easy enough to find off Microsoft's site. Tr y it.

- Jason

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

Related Discussions

Related Forums