Still having big trouble with Windows 7, ReadyNAS NV+ and offline files.

B. ReadyNAS NV+, 4.1.6

C. 802.11g router

D. Lenovo X201s, i7-640LM 2.13 GHz, 320GB 7200 rpm, 4 GB RAM, Intel 6200 wireless a/g/b/n; Windows 7 Pro 32

I just received laptop D as a replacement for laptop A. All is well, except for two problems that were NOT issues with the old

computer (A):

1. VERY slow transfer of files from NAS B (mapped as network drive) to laptop D, especially over wireless, though it’s not too

speedy over a cable either. For example, opening up a 1 MB jpg took over 5 minutes on laptop D over wireless, but only 15 seconds

over a cable. On laptop A, the process is no more than a couple of seconds either way. With laptop D, offline file sync is an

apparently un-ending process (wireless or cable), whereas with A it is very rapid (either way).

2. Offline file setup with laptop D basically doesn’t work. It is very slow, and gives thousands of errors (for jpg, pdf, xls,

doc, etc) – all saying something like “this file is in use and could not be copied”.

References
Relevant posts I have read include
-1 http://social.microsoft.com/Forums/en-US/Offtopic/thread/7185c13a-5901-4fcf-bf8e-c5336044f05d
-2 http://home.bott.ca/webserver/?p=226
-3 http://openmoonproject.com/nvidia-nvraid/readynas-nv-windows-7-wifi-problems/
-4 http://www.readynas.com/forum/viewtopic.php?f=21&t=33411
-5 http://www.readynas.com/?p=310

Solutions attempted
I have tried the following solutions:
*1 Mapping NAS B shares to a network drive using IP address rather than DNS.
No visible improvement.
*2 Command line: “netsh interface ipv4 show subinterfaces”, to see MTU preparatory to resetting it to 1430 (or 1460 or 1492).
Command not found. True whether I run the command as administrator or regular. Some suggest this only works in Vista.
*3 Setting “oplocks” on for the relevant share in NAS Frontview |Network |Performance
No visible improvement.
*4 Running IOMeter as described in -5 above.
laptop A Read 1.72, Read 1.07 MB/s
laptop D Read .04, Write .84 MB/s
Vastly lower than the ReadyNAS results, so perhaps I’m doing something wrong. But D results still far lower than A.

Solutions not attempted
!1 I have not tried Radiator 4.1.7 beta, though some suggest this may help.
I’m not keen to risk essential data (even backed up) on a beta.
!2 Some solutions suggest installing and messing with Samba.
That is far beyond my technical expertise.

Some additional info for the curious: If you want to validate that MTU is the problem, use “ping -f -l xxx” where xxx is the packet size. If you get the following response “Packet needs to be fragmented but DF set”, then that’s the problem. You can repeat the command by dropping the packet size until you get the usual ping response. BTW, “-f” is “do not fragment” and “-l” is “packet size”