Hello,My roommate and I recently upgraded our computers to Windows 7. He is running the 64-bit Home Premium and I am running 32-bit Home Premium.We are able to see each others' computers on the Homegroup. But when I connect to his shared folders it takes an extremely long time (over 30 seconds) to see the contents of the folder. When I attempt to copy a file from his shared folder to my computer it brings up the copy dialog box but never actually starts copying. Another example: when right-clicking on a shared mp3 file on his computer and going to Properties, ittakes about 45 seconds for the Properties window tocome up.Our Internet speed is normal (10-20 Mb/sec). It is only between computers that we have this issue.We have tried: disabling TCP Offload, disabling Chimney offload, setting Auto-Tuning to disabled, disabling RPC, resetting the router, factory resetting the router, contacting Netgear support which led to the tech changing some of our router settings without any result, disabling Windows Firewall and antivirus software...nothing seems to work.Our wireless router is in the living room connected to the cable modem. It is a NETGEAR WNR854T.My roommate's computer is:Dell Dimension 9200Intel Core 2 6600 2.4 GHz4 GB RAMWindows 7 64-bitconnected to the router with NETGEAR WN111v2 wireless USB adapterMy computer is:Alienware Intel Pentium D 3.0 GHz2 GB RAMNETGEAR WNDA3100 wireless USB adapterThe NETGEAR tech said the problem is not with the router. We have read/tried everything we could find online without success. Any help is greatly appreciated!

Does the issue occur when transferring data via Network location?Please share a folder on one of the Windows 7 machine and then access it by clicking "Network" on another computer. Then copy it for a test.Meanwhile, please also refer to the following steps to troubleshoot the issue.1. Temporarily disable wireless connection and use wired cable instead. Then, please check whether the performance is quicker when transferring data via wired connection.2. Move the computer near the Wireless AP to make sure the signal strength is enough and access the target computer again.3. Restart the computers in Safe Mode with Networking and access each other for a test.4. Upgrade the Wireless adapter driver for Windows 7.What's the result?Thanks,Novak

Thank you for your reply...Yes, the issue also occurs when using the Network location instead of the Homegroup. In response to the troubleshooting steps, #3 (Safe Mode) definitely improved performance. With both computers in Safe Mode with Networking, they do not see each other on the Network. However, if one computer is started in non-safe mode, the computer in Safe Mode can see the other, and browsing and file copy works fine.Moving the computer closer to the Wireless AP (#2) did not affect performance...the drivers were already updated as well (#4).We haven't tried using the wired cable yet due to logistical issues but are willing to do so.But based on the Safe Mode performance increase, does this offer any hints toward a possible solution? Thank you again.

Hi,First check hereto determine if the wireless network adapters are compatible with Win 7 and search for drivers. It appears the issue may be with the WN111v2. No Win 7 drivers yet. Try installing the Vista drivers here for it in compatibility mode. Method here.Try entering the router/ap and temporarily disable any wireless security. Save and exit. Make connection with the computers and test. OK yes or no.If yes, enter router/ap setup and disable WEP and set security for WPA or WPA2 with a new passphrase. Save and exit. Make connections from the computers and test.If no, enter router/ap setup and enable WPA or WPA2 anyway as itis more secure and theWin 7 seems to work better with those security protocols.What's the result?

Since the issue did not occur in Safe Mode with Networking, we can conclude that Internet Connection is fine and the issue can occur by incompatible third party programs. Please temporarily turn off firewall and antivirus program on each machine. If the issue persists, please perform a Clean Boot for a test. If the issue disappears in the Clean Boot environment, we can use a 50/50 approach to quickly narrow down which entry is causing the issue.