Even those who consider themselves tech-savvy sometimes run into glitches that defy explanation. For my home-based appellate practice, I have Road Runner Lightning high speed Internet service from my local cable company, Bright House Networks. It provides 40 Mbps download and 5 Mbps upload speeds. That is plenty for normal use, including streaming of audio and video.
Recently my cable modem (Motorola Surf Board SBG6580), which also functions as a router, starting dropping its connection to the Internet. I called Bright House and they came out with a replacement modem. That is when the mystery began. I still have three Windows XP computers at home. These are my ThinkPad notebook, Toshiba netbook, and an eight year old Toshiba notebook that still works as well as it did when new. With the replacement modem/router in place, the XP machines connected just fine to the Internet (via a wireless connection) and web page browsing was snappy as ever. Same thing with my son's notebook computer running Vista.
But my two Windows 7 PC's (my self-built primary desktop with an AMD quad cord processor) and my son's Acer gaming machine (with an Intel quad core processor) would connect to the Internet, but take forever to open web pages. This was odd because they were wired directly to the Ethernet ports of the Motorola modem/router and should have browsed at least as fast as the wireless XP machines, if not faster. Oddly, speed tests run on the two Windows 7 machines showed download and upload speeds at or near the promised 40/5 maximum. Even stranger, I have Windows Virtual Machine with XP Mode installed on my Windows 7 machine so I can run older software not compatible with Windows 7. When I opened a browser in the Virtual Machine window running XP with only 512 MB of allocated system RAM, browsing was perfect. If I tried to open the same web page in Windows 7, the page would open at least ten times slower on the regular Windows 7 desktop than in the XP Virtual Machine. I tried this with Firefox, Chrome, and Internet Explorer. The result was the same with each browser. How could the same connection over the same hardware, but with two different operating systems, be so different when run side-by-side?
Three visits from Road Runner's tech support people and at least eight hours on the telephone with their level 3 ("development") support team produced no answers. Yet another modem was swapped in. Same result. The problem had to be the way the modem communicated with the Windows 7 operating system. At this point, Road Runner tech support gave up and said they had no answers and no remedy for the problem.
I too was ready to give up. Then I decided to bypass the routing functions of the Motorola device, using it only as a modem to feed the Internet connection to my Linksys WRT400N router and have the Linksys handle routing and wired/wireless networking functions. That process involved disabling what is called "NAPT" mode in the Motorola's browser-based configuration pages. I did that, but could not get the Linksys to pull an IP address from the modem. Foiled again, I gave up and reset the Motorola modem back to NAPT mode. I reconnected everything as it was, resigned to slow Windows 7 web browsing forever.
Well, as soon as the modem went back into NAPT mode, Windows 7 browsing returned to normal. The slow web page loading problem was completely gone. No explanation. No logic. It just happened. Something about disabling then re-enabling the NAPT routing feature of the modem cleared-up the problem communicating with Windows 7 computers. Strange, but true.
A few days later, after installing the new Internet Explorer 9 (beta) browser, I experienced the rapidly flashing hourglass icon next to my mouse pointer that indicates a background Windows process running wild. Checking the system event viewer, it was clear that the Windows Live Mesh Remote Desktop Service was continually crashing, restarting, crashing, restarting - over and over again. This created a drag on the computer by consuming a considerable amount of RAM and processor cycles. I'd been using Microsoft's Free Live Mesh file synchronization service (soon to be replaced by Windows Live Mesh 2011) for over a year without problems. Why was this happening now?
The first clue in tracking down such mysteries is to look to recently installed or upgraded software. The only major change recently was the IE9 upgrade. Sure enough, a search of the web found several reports of incompatibility between the IE9 beta browser and the Live Mesh Remote Desktop Service. As soon as I uninstalled IE9, everything returned to normal.
The lesson is never give up trying to solve a mysterious tech problem. There will be an answer, even if the answer makes little sense. The secondary lesson is that even experienced users often run into problems that are hard to diagnose, much less solve. So don't bee too much in awe of anyone who claims expert status. They have their share of tech failures, just like the rest of us.