Posts Tagged slow
This post is a continuation of the saga of my Windows 7 upgrade. Previous Post – Upgrading to Windows 7 – More complicated that it should have been. This part of the saga should be the report on the successful upgrade to a new 802.11n wireless modem/router. Well, I hoping that things will sort themselves out when I reboot the machine.
I’ve ended up going for a Netgear DGN2000. Setting up the modem/ADSL side of things worked fine. But having a print of the old ADSL modems setting was necessary. The set up routine had one “annoying” property, it wanted the computer doing the set up connected to the unit via an cat 6 cable. So, one mercy dash to the mall, and 5 meters of cat 6 later, I had the setup completed.
Then the fun started. Getting the wireless network link up and running. This was a real “head banger” of a problem. Sill, not quire sure how the resulting combination is correct. The UI for the modem/router for the wireless links is “less then helpful”, not sure when the setting I chose are truly active, and when they are not. The other problem is the nomenclature between windows network device setting, and the modem are not consistent.
The other problem could have been trying to make the 11n connection, while the Ethernet net connection was active (and connected). This seemed to cause problems with making the connection, and with the built-in diagnostics. The windows diagnostics, seemed to get “lost” when there was an active Ethernet connection. I finally made the connection with the Ethernet unplugged.
The Residual Problems
At the moment I’m still running on the cat 6 connection to the router, and the internet. Why? Because the wireless was giving me 1MBps transfer speed. The intention of this upgrade from and 802.11g modem/router, was to get better than 54Mbps. At the moment I’ve achieved a great step backwards, speed wise!
Hopefully, a reboot (shutdown this evening, and start up tomorrow, will resolve this problem.
I’ve had a careful browse inside the modem/router configurations and nothing looks like it should be switched. The logs do not show anything “wrong”, so if the reboot does not fix the problem it will be some trawling the internet for clues.