Discussion Locked

Server access from Win2k Client

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
What are the possible causes of "slow" writes to mapped network drives on a Win2k workstation using client32? Using a benchmark program indicates that read access speed is acceptable but writes to the server are slow (100-200 kbs when they should be 9 - 10 mbs). Using the same client on a WinNT station connected to the same switch port does not exibit this problem. Problem starts when the transfer size is larger than 4Kb. My possible suspects are; OS - Win2k, NIC Driver - 3C905C-TX Win2k driver, Client or registry setting. Anyone know the cause of this?

9 replies

by bigcheif

I once had a nic card that any time large transfurs would take place things slowed to a crawl. I changed out the nic card and everything worked fine. It may be that the new card had a different driver that solved the problem. This may not help but worth a try.

by dcrook8770

Sorry for the late reply.
It turns out that the problem was the NIC driver provided by Micro$oft. Even when searching for the latest version downloaded driver, W2k will "suggest" the driver provided by M$. You have to "Select" the 3rd party driver (3com, Intel, ect)

by prompt

Hi!
The first thing that I would check is the media type in device manager for your network card.
For example 100BaseTX_FullDuplex should work fine with a switch with same settings.
When set to auto it will likely be decreased speed

//ola

by dcrook8770

Sorry for the late reply.
It turns out that the problem was the NIC driver provided by Micro$oft. Even when searching for a newly downloaded driver, W2k will "suggest" the driver provided by M$. You have to "Select" the 3rd party driver (3com, Intel, ect)

by rogerndgreen

A while ago, there were a lot of postings in various newsgroups all relating to poor/variable performance of 3Com 3C905's, some of which I have also seem myself.
I agree with the other two suggestions. First of all, lock down your card & switch ports to use the same settings (speed, HD/FD), make sure that your client is set to use the required frame types (don't rely on the Auto setting)and if it don't work, try a different NIOC.
Intel's current ones are quite nice!

HTH

Roger

by dcrook8770

Roger, U get the points.
Sorry for the late reply.
It turns out that the problem was the NIC driver provided by Micro$oft. Even when searching for a newly downloaded driver, W2k will "suggest" the driver provided by M$. You have to "Select" the 3rd party driver (3com, Intel, ect). I just loath the way "lord" Gates minions think they are the greatest. With all the bugs I still see in W2k, I wonder why I havn't went to linux or something else just to prove a point. Unfortunatly, my parent company is about to make me convert entire network to M$ and Hexchange sever and the works just to conform.
You know the old story, If your friend jumped off a cliff, would you jump too.... (sigh)

by colin_joseph

If you are running a NT domain as well as a Netware shop, on Win2K professional you need to set the network access order correctly or the workstation will CRAWL. Right-click on My Network Places and go to properties. Go to advanced > advanced settings > provider order. If Netware resources will be accessed more frequently, put Netware at the top of the provider order. If NT resources will be accessed more, put NT at the top of the order. This will take care of most of the network-related performance problems.

by dcrook8770

Sorry for the late reply.
It turns out that the problem was the NIC driver provided by Micro$oft. Even when searching for a newly downloaded driver, W2k will "suggest" the driver provided by M$. You have to "Select" the 3rd party driver (3com, Intel, ect)

This discussion is closed to new replies.