Re: Slow file-upload to share, 2003 server.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




"Anteaus" <Anteaus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:78AE0745-C902-4EC4-AA79-D57DA4CCCB86@xxxxxxxxxxxxxxxx
Seem to have solved it. There is evidently a problem with the onboard NIC
or
its driver, and the problem only goes away if this is fully deactivated.
Using a second NIC with the onboard still active -as I first tried- the
problem still manifests, hence confusing result.

"Anteaus" wrote:

Investigating a problem of slow upload of files to a server share.

When downloading files to a client, or when using the server console to
copy
files to or from another server, the LAN throughput is ~7MB/s which seems
about typical for a 100Mb/s link.

However, when uploading a file from a client to a server share, the
throughput is half that at best, and seems to suffer a further drop in
speed
after perhaps 30sec or so of copying, to as low as 1-2MB/s. From then on
the
speed fluctuates from 0.5MB/s to 3MB/s, and the total copy takes about
4-6
times as long as it should.

The client copies the same files to another (Debian) server at full
speed,
so I think we can rule-out a client problem.

There are no processor-intensive tasks running, and during the copy the
utilization of both CPU and LAN are moderate. A disk-to-disk copy on the
server is >10x the LAN speed, which suggests it's not a disk throughput
problem.

I've tried:
Updating LAN driver.
A different LAN card, RTL8139.
Changing various LAN card parameters, including forcing 100 Duplex.
Changed the relative priority of services/applications.
No joy.

Seems to me it cannot be a LAN interface or IP problem anyway, as the
server
can download AND upload files from/to its own console at full speed. It
looks
more like a problem with the server process itself.

Any suggestions?



This may possibly be due to the TCP Chimney feature that is enabled by
default on 2003 SP2 and 2008. It relies on offloading TCP functions to the
NIC, however if the NIC doesn't support it, you will see various issues, one
of which you've described. Read the following for more info and see if it
applies.

TCP Chimney and RSS Features May Cause Slow File Transfers or Cause
Connectivity Problems
http://msmvps.com/blogs/acefekay/archive/2009/08/20/tcp-chimney-and-rss-features-may-cause-slow-file-transfers-or-cause-connectivity-problems.aspx

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA
Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.


.



Relevant Pages

  • Re: SBS 2003 - SBS 2008 migration issues
    ... DHCP cannot work properly with the hyper-v role, and probably DNS, neither will the configuration wizards. ... clients losing the ability to use it after removing trend client, reseting winsock / removing network components / reinstalling teh client don't bring it back. ... When I add the 32 bit driver to the printer it simply tells me it's not a suitable driver, and to try adding the driver from a 32 bit client. ... If I install hyperV on the SBS 2008 will it run a win2k3 server? ...
    (microsoft.public.windows.server.sbs)
  • Re: Printer autocreation failing
    ... behaviour of a TS incompatible printer driver. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Tried installing that printer tray hotfix, ... Also tried updating the RDP client to the latest ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer autocreation failing
    ... reinstall the driver onto the TS box). ... Check in Printers and Faxes - File - Server properties - ... Also tried updating the RDP client to the ... box and installing the print queue from the remote server ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer autocreation failing
    ... redirection of the driver to the LJ4) and functional. ... Check in Printers and Faxes - File - Server properties - ... Also tried updating the RDP client to the ... box and installing the print queue from the remote server ...
    (microsoft.public.windows.terminal_services)
  • Network Admin-Myrtle Beach, SC
    ... SofTec I.T. has a terrific permanent opportunity with a premier client ... for a Senior Network Administrator. ... Configures and maintains the organizations LAN server and LAN ...
    (comp.dcom.sys.cisco)