{"id":21201,"date":"2011-04-06T09:54:11","date_gmt":"2011-04-06T14:54:11","guid":{"rendered":"https:\/\/www.pcmatic.com\/blog\/?p=21201"},"modified":"2011-04-06T09:54:11","modified_gmt":"2011-04-06T14:54:11","slug":"windows-secrets-simple-change-pumps-up-windows-7-networks","status":"publish","type":"post","link":"https:\/\/www.pcmatic.com\/blog\/windows-secrets-simple-change-pumps-up-windows-7-networks\/","title":{"rendered":"Windows Secrets Newsletter: Simple change pumps up Windows 7 networks"},"content":{"rendered":"

PC Pitstop is proud to welcome our friends at Windows Secrets as guest contributors. The weekly Windows Secrets Newsletter brings you essential tips for Windows, applications, and computing on the Internet.<\/i><\/p>\n

<\/font><\/p>\n

\"windows<\/p>\n

By Fred Langa\/Windows Secrets<\/p>\n

Windows 7 has many good things going for it, but home networking is not always one of them.<\/b><\/p>\n

But with just two quick clicks within Win7’s Advanced sharing settings,<\/b> you can improve your local network throughput by as much as 12%.<\/p>\n

Windows 7 is the best Windows I’ve ever used, and I’ve used them all since version 1.0. But, like all software, it’s not perfect.<\/p>\n

One of the oddest glitches I’ve encountered with Microsoft’s newest OS is erratic local-networking performance. Occasionally and for no obvious reason, a Win7 LAN connection will slow to a crawl — giving you that less-than-nostalgic feeling that you’ve gone back to a dial-up connection.<\/p>\n

The problem seems completely random; I’ve never been able to reliably reproduce it. But I’ve seen the problem enough to know it’s not some figment of my imagination. And even when everything’s operating normally, I’ve had a sneaking suspicion that my Win7 networking is running slower than it should.<\/p>\n

Trust me; I’m not alone in this belief. Do a quick search on the phrase win7 slow network<\/b> and you’ll see what I mean.<\/p>\n

<\/a> <\/p>\n

<\/p>\n

<\/p>\n

Two likely culprits in the slow-LAN mystery<\/p>\n

<\/b>
<\/big>
<\/small><\/p>\n

I’ve always suspected that the prime suspect in Win7’s sometimes-sluggish network speed is the OS’s HomeGroup<\/i><\/b> feature, which is enabled by default. A homegroup is a kind of self-configuring workgroup that automatically sets up file- and device-sharing between Win7 machines on a local network.<\/p>\n

(Not familiar with HomeGroup? See Microsoft’s HomeGroup product feature page<\/a>. More details are available on this MS Help page<\/a> and in the Microsoft Win7 Engineering blog<\/a>.)<\/p>\n

A homegroup is a godsend for people intimidated by networking. Although it’s easy to use, HomeGroup (like most black-box, self-configuring software) is a take-it-or-leave-it setup; you don’t know — and can’t change — which assumptions Microsoft built into the product.<\/p>\n

In that same vein, it’s designed to work under a wide range of circumstances — but not necessarily optimally for any of them.<\/p>\n

By default, Windows 7 also enables 128-bit encryption for home-network file-sharing (up from the 56-bit encryption used in earlier versions). But while heavy encryption might sound good, it does soak up some processing power and time. So I suspected that this extra encryption could also be a factor in Win7’s lackluster LAN throughput.<\/p>\n

But all of this was speculation — an educated guess. The only sure way to know was through testing.<\/p>\n

<\/a><\/p>\n

<\/p>\n

<\/p>\n

The HomeGroup vs. classic-networking faceoff<\/p>\n

<\/b>
<\/big>
<\/small><\/p>\n

My concept for measuring LAN performance was simple. I’d time how long it took to copy a large set of files across the network under carefully controlled conditions.<\/p>\n

First, I would copy the files using Win7’s default settings (with HomeGroup and 128-bit encryption enabled); then I’d copy the same files again, using the classic workgroup networking settings (with HomeGroup disabled and standard 56-bit encryption).<\/p>\n

To create a sizable set of test files, I cloned my for-real Documents<\/b> folder from the Win7 PC I use every day. That folder consisted of 2.59GB of data — an eclectic mix of 10,846 utterly standard files such as word processing documents, e-mails, text messages, spreadsheets, images, and .zip<\/b> files (all representing a wide range of sizes). There were no weird or nonstandard files, no system or hidden files, nothing to make the network transfer either unusually hard or too easy. They were, in all likelihood, similar to those you have on your system.<\/p>\n

In the first set of tests, I copied the files between brand-new, freshly installed, unmodified Windows 7 installations. I then did the same tests using my real-life systems, including the Win7 PC I’m using to write this article.<\/p>\n

In both cases, I copied the files from the source PC to an empty folder on the target PC, thus avoiding any file-overwriting problems or delays.<\/p>\n

While running the tests, I also shut down all other devices on my office network, disconnected the router from the Internet, and killed or suspended all software that wasn’t needed to run the tests (ensuring that no other factor would influence the results).<\/p>\n

<\/a><\/p>\n

<\/p>\n

<\/p>\n

Taking advantage of Win7’s Robocopy stats<\/p>\n

<\/b>
<\/big>
<\/small><\/p>\n

Once everything was set up, I used Win7’s little-known Robocopy<\/b> command to move my cloned Document folder across the network. (Robocopy stands for “Robust File Copy”; see its TechNet info page<\/a> for a thorough description of how it works.) Akin to Xcopy<\/b> in earlier versions of Windows, Robocopy can clone entire folder trees, including subfolders many levels deep.<\/p>\n

Making it truly ideal for my tests, Robocopy also gathers statistics on its own operation — such as how long the copy took, how many files and bytes were moved, and what the overall throughput was in bytes per second and megabytes per minute. It’s a handy tool!<\/p>\n

<\/a><\/p>\n

<\/p>\n

<\/p>\n

Classic networking trumps Windows HomeGroup<\/p>\n

<\/b>
<\/big>
<\/small><\/p>\n

Setting Win7 to use classic workgroup networking instead of HomeGroup (a painless, two-click change) resulted in an immediate increase<\/i><\/b> in networking throughput. On my systems, those two clicks boosted throughput by an impressive 12%. And since making that change, I’ve never seen one of those slow-as-dialup moments again!<\/p>\n

It was no fluke, either: the results were repeatable from test to test and machine to machine. Win7’s default networking settings (and not some other variable) were indeed the key.<\/p>\n

Here are typical throughput results I obtained:
<\/font><\/p>\n