Draft 802.11n: How I Loathe Thee

[Jason Dunn]

<p><img src="http://images.thoughtsmedia.com//dht/auto/1222729192.usr1.png" border="1" /></p><p>I brought up this issue <a href="http://www.digitalhomethoughts.com/news/show/89911/why-802-11n-wireless-routers-shouldn-t-be-sold-in-stores.html" target="_blank">just a couple of months ago</a>, but I feel the need to rant again: I'm incredibly dismayed at how poorly some modern networking equipment operates together. Or, rather, doesn't operate well together. I have a brand new <a href="http://global.msi.com.tw/index.php?func=proddesc&amp;maincat_no=135&amp;cat2_no=582&amp;prod_no=1474" target="_blank">MSI Wind netbook</a>, and a brand new <a href="http://www.linksys.com/servlet/Satellite?c=L_Product_C2&amp;childpagename=US/Layout&amp;cid=1175243240869&amp;pagename=Linksys/Common/VisitorWrapper&amp;lid=4086933028B01" target="_blank">Linksys WRT310N</a>. The screenshot above shows just how successful these two pieces of hardware work together. I've loaded the latest firmware on the Linksys router, and the latest WiFi drivers onto the MSI Wind, and it still doesn't operate correctly. Everything seemed to be working great for the first two days - I successfully used FolderShare to push more than 45 GB of data onto the MSI Wind over the weekend, and the connection never dropped. Today, I can't get it to connect at all unless I repair the connection or disable then re-enable it. I'm completely baffled. It's not like I'm trying to connect some laptop from 2000 with a PCMCIA 802.11b card - this is a brand new netbook with a 802.11b/g chip. Why don't these companies test their gear to make sure they interoperate? I'll try fiddling with it for a few more days, but I'll likely end up returning this Linksys WRT310N and going back to my trusty WRT54G router. What a disappointment!</p>

[gdoerr56]

I've seen the same issue with the Intel 3945 card connecting to my trusty old WRT54G. It typically occurred when resuming from sleep or hibernate and I would have disable/enable the device to get it to work. My OS is Vista but I also saw similar issues with XP.

The most recent drivers from Intel seem to have fixed the problem.

[Kacey Green]

I don't remember 11 G taking this long to get finalized, or was it that they didn't sell it before it was finalized.

[Joel Crane]

Even 802.11b cards should be reliable. If they claim backwards compatibility, it should be backwards compatible!

My laptop has an 802.11b card, and its totally hit and miss as to whether I can connect to an AP or not. I can't identify what the problems are, it just plain wont connect. I've got another card on order for it.

Some of my stuff stays connected to my own 802.11g AP flawlessly, but some cards disconnect and won't reconnect, some cards just disconnect intermittently. Same brand stuff doesn't seem to help much.

The school network is even worse. With good signal, I get a 25 percent packet loss, even with my new 802.11n USB card.

WiFi is just getting worse, It seems like it was far more reliable 3 years ago. I have come to love ethernet cables.

[David Horn]

Jason - do you perchance have a Pocket PC / Smartphone connected to your network via WiFi? My X51v used to be able to screw up my Linksys router in such a way that it would stop my laptop (with an Intel WiFi chipset) from connecting at all.

[Jason Dunn]

I don't remember 11 G taking this long to get finalized, or was it that they didn't sell it before it was finalized.

No, 802.11g came quickly compared to 802.11n...the problem with 802.11n is the warring wireless factions, each one promoting their own type of wireless technology. It sucks because it makes things much worse for consumers.

[Jason Dunn]

Jason - do you perchance have a Pocket PC / Smartphone connected to your network via WiFi?

Nope, I haven't connected any Windows Mobile device to the router yet. :confused:

[Eriq Cook]

Same exact issue. New HP Pavillion 6600 series (running Vista Business) connecting wirelessly to Linksys WRT300N. Usually about 1-3 times per week my wireless connection just drops, and repair function doesn't work. To fix, I have to disable and then reenable the connection via Network & Sharing Center, then it works again--for a few hours or a few days before doing again. It's really annoying. And it happens while using the notebook. Not from coming back up from sleep or hibernation mode.

Running the latest firmware on the Linksys router & wireless driver on notebook. My WRT54G was a lot more stable. Think I'll be going back to it too.

[Joel Crane]

Jason - do you perchance have a Pocket PC / Smartphone connected to your network via WiFi? My X51v used to be able to screw up my Linksys router in such a way that it would stop my laptop (with an Intel WiFi chipset) from connecting at all.

Great, maybe that is what is going on with my network.

[edgar]

I had to shut down the N band - return speeds back to G levels (and drop multi channel) to get our work laptops (Dell 630C's) to connect reliably.

They would always connect LOCAL ONLY (!) after sleep or at power up . You had to disable-re-enable or simply disconnect/reconnect to the AP 3-4 times

Now we connect reliably.

[Jason Dunn]

I had to shut down the N band - return speeds back to G levels (and drop multi channel) to get our work laptops (Dell 630C's) to connect reliably.

Doesn't that just drive you nuts? I'm completely, totally, and utterly stunned by what a ridiculous situation the laptop and WiFi router vendors have put all their customers in.

[edgar]

Yes it does drive me absolutely nuts.

I should have bought a WRT64 old B/G router on ebay for $30

[Eriq Cook]

Yes it does drive me absolutely nuts.

I should have bought a WRT64 old B/G router on ebay for $30


I agree that it is silly that consumers have to deal with this, but I also realize that the "N" specification hasn't been completely finalized, so the manufacturers are coming up with their own implementation 802.11n. As a result we have these rediculous connection issues when connecting it with different brands of equipment.

I wonder if once the N draft becomes final, if this will begin to solve the compatibility issues we're seeing. Hard to tell.

[Merlin_AZ]

Jason, have you tried hard-resetting the router, and setting up again.
Many times that works.
You will need to use a paper clip and press the setup button on the new router for at least 30 seconds, then set up again.

[Jason Dunn]

Jason, have you tried hard-resetting the router, and setting up again.

No, I haven't - the router has been up and running for about a week though. What could have gone wrong with it in that timeframe? :confused:

[Merlin_AZ]

No, I haven't - the router has been up and running for about a week though. What could have gone wrong with it in that timeframe? :confused:
I've had issues with routers having connection issues at times, completely random disconnects, that were fixed doing a hard-reset.
Couldn't hurt, only the 2 minutes it would take to put your settings back in.
I've recently gotten a Linksys 610N that had some issues after I installed the latest firmware, that resolved after a hard reset.
It was disconnecting several times an hour at times, where now, maybe twice a week.
I may flash the firmware and hard-reset again and see if that helps these very infrequent disconnects we have now.