Desktop

Ask something
Discussion Locked

NT/W2K Slow retrieving files from server

0 helpful
14 replies

by sam.wagoner

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am using NT4 in a mixed 100mb switched network environment of Novell, NT, and UNIX servers. I have had this problem for over two years and am hoping someone can help me find a solution.

When first retrieving a file from any of the network servers, it will consistantly take 50 seconds or more for the 10-50K file to open in Word/Excel. Once that first file is open, opening other files is instantaneous even if the file is 1Meg or more. Work on the files for 15 minutes or walk away and the delay returns.

I have tried updating the NIC drivers, the Novell client to no avail. Removing Novell greatly improves the response time, but I can't permanently remove Novell.

We recently installed some Win 2000 workstations and the same problem appears but with a 20 second initial delay.

What could be causing the delay and how can it be reduced? Or is there a way to increase the 15 minute active connection time?

Any help will be greatly appreciated. We would like to solve this problem before it gets any larger.

Thanks,

14 replies

by sam.wagoner

Point value changed by question poster.

Had trouble posting question and didn't notice value reverted to 150.

by magetower

If you are running multiple network protocols you may be experiencing a problem with the workstations deciding what protocol to use when initially connecting to a server.

In the environment you mention you should be running a pure TCP/IP configuration if possible.

Some more info on your setup would help.

by sam.wagoner

I believe all the server using TCP/IP except for the Novell server. IS tells me the Novell server is running IP, but I get "Request Timed Out" when I try to ping it.

What other configurations do you need to know?

by dpalsen

My first reaction would actually be that it's the workstation that's slow, and not the network. It sounds like it's just taking forever for Word/Excel/Whatever to load, and then the document opens quickly, especially if successive documents open quickly and easily. Try a workstation upgrade first. Barring that, check to make sure you're actually running at 100Mbps. I've seen networks report 100, but they're actually at 10Mbps when I do some snooping, because they've switched to half-duplex.

by estebandelatorre

Multiple protocols may be the reason for delays. Once the wks comunicate with the nw server using ipx, it will try to browse any other drive mapped with the same protocol, and will try to access it via ipx...
Another issue is the client configuration tab, set client to "BEGIN SESSION AND RESTORE NETWORK CONNECTIONS", rather than FAST connection.

by james hardy

On the network card properties change the network speed setting from auto to 100Mb Full duplex,

by sam.wagoner

I upgraded NW client 4.6 to 4.81 and remove NIS from the UNIX server and the workstation. Overall performance it great except for the initial delay accessing the servers. 5-15 secs to NT, 50-53 secs on Novell. 15-25 secs on UNIX.
I would like tosee all of them below 15 secs if it is possible.

by yasirs

Hi,

Broadcast my friend , thats why the oldest network company lost NOVELL just loves broadcast and still won't give it up??? Anyways as per the problem well have maybe a work around to keep novell clients , servers across a router ( of course a IPX/SPX protocol enabled one ) also IPX in IP encapsulation can be sent across the router as un or multicast but NO BROADCASTS, it will improve the response as the broadcast can be just kept to their subnet , look for a Cisco solution or a multihomed PC solution though a premitive work about. Also the internal network browsing service whether Ms , Novell or Unix machines sux but that is due to the network technologies and the convergence time to cache the remotely available resources. An all unix , linux , solaris enviroment greatly increases the network responce time , after all they invented TCP/IP and UDP/IP.

This discussion is closed to new replies.