Cool Solutions

Improving File Copy Performance with Windows 7 and Novell Client


September 28, 2010 11:27 am





Copying files to or from a Windows 7 workstation and an OES2 Linux Server with NSS Volumes is a poor thing. You need much time and a lot of coffee…

Even if installing actual NIC-drivers, using the latest Microsoft Updates, and the most recent Novell Client 2 SP1 for Windows 7 ( IR3 at this time) the performance moves between 2 mb/s and 5 mb/s in a gigabit environment…. (in my case)

Too bad I think and in the same network environment but using Windows XP the performance is much(!) better.

So what to do?

The following three steps put me out of my misery:

  1. Deactivate the RDC (Remote Differential Compression) in Windows 7:
    Click Start – Control Panel – Programs – Turn Windows features on or off – uncheck RDC

    Even if Microsoft tells us, this has nothing to do with file copy performance (, the real world tells another story than the nice and blue MS World…

    In my case turning the RDC off increases copying files (small and big ones) to the NSS volume up to 40-50 mb/s. Copying files from the NSS volume to my Windows 7 (x64) Workstation goes up to 35-40 mb/s!!

  2. Turn off the TCP Auto Tuning and RSS (receive side scaling).

    Microsoft made lots of improvements to the TCP stack in Vista and Windows 7.

    The idea is a better usage in networks with big bandwidths and high latency.

    The improvements are features like: Receive Window Auto Tuning, Compound TCP, ECN Support, Fail-back Support when changing the default gateways, changes in identification of PMTU Black Hole Router and much more…

    That all is a very good thing (really!) – In theory and for sure in the short future… (and maybe if you have a pure blue network with Windows 2008 Servers only (SMB 2.0)…) but for all others these features will not be useful at this time.

    The main reason is, that the current NIC drivers are not using these features (not all but most of them) also older Routers and L3 Switches do not.

    So I turned these features off:

    • open cmd.exe as Administrator
    • check your current settings:

      netsh interface tcp show global
    • now type:

      netsh interface tcp set global autotuninglevel=disabled

      netsh interface tcp set global rss=disabled

  3. Now reboot your workstation and test copying files…
  4. So, these short three steps helped me to improve file copy with a factor of 10!
    (50 – 60 mb/s)

    Try it and check out if it’s good for you. I’m sure that it will not work in all environments but it’s worth it to try it….


0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.


  1. By:grimlock

    Unfortunately, these settings had no positive effect for me. RDC made no difference either way, and changing autotuning and rss actually slowed me down 2mb per minute. I ran the test several times using Teracopy which is kind enough to show you MB/s as it goes using a 3.7GB iso file for the test.

  2. By:tobiatnet

    I tried the changed settings and copy performance grows up to about 40 MB/s.

  3. By:skapanen

    tried disabling RDC, no apparent effect.

    I tested by copying a .ISO file and also ConsoleOne directory with small files.

    copy to NSS 30MB/s
    copy from NSS 40MB/s

    C1 dir:
    copy to NSS 1MB/s
    copy from NSS 1MB/s

    Also noticed that deleting ConsoleOne directory on NSS takes forever!

  4. By:jlobom

    We solved this problem changing this:


  5. By:nlandas

    Wow, I’m still seeing slow copy speed with Windows 7 and Windows 8.1 using the latest Novell client and fully patches OES2 and OES11 servers.

    I’ve applied all the listed fixes in this – rebooted and I still see 2-7MB/s on the OES2 and steadier 6-8MB/s on the OES11 servers. The network is not busy at this time of day so I should be able to get the best performance.

    Does anyone have other ideas? This should be a high priority for Novell as File and Printer services are still key services.