I have recently purchased a Vaio laptop with Intel WiFi Link 5100 AGN adapter. When connecting to my home network the connection initially shows 300Mbps and then drops to 130Mbps after a couple of seconds before climbing and stabilising at 150Mbps. No matter what I try I cannot achieve 300Mbps through this adapter.
The router I'm using is a Netgear RangeMax WNR854T set to 11n Max speed mode. My previous laptop used a Netgear WN511T PCMCIA adapter to connect to the network and connected at (and maintained) 300Mbps without any problems.
Can anyone suggest why my new laptop is unable to connect at the full 300Mbps?
-
It might have to do with the fact that most brands work best with something of the same brand.
-
Its irrelevant. The Intel is reporting the correct speed. It is currently impossible to get 300Mlbs in Draft N. Your Throughput speed, which is the actual speed, cant really exceed 144Mlbs. That is why it is Draft N. When N is ratified, it will support 300Mlbs+. No matter what it says, you cant get more than 300. It will say this usually if you pair the brands, but again, its impossible at this time. When it is ratified, any WiFi Certified Devices can get a simple firmware update and support 300Mlbs. The ones that arent, wont be able to. You 5100 is, just check if your router is.
-
OK, stupid question of the day then. On my desktop, running on a Lan line, my speed shows 1.0Gbps. I do not ever recall seeing 1.0 Gbps anywhere before. How many Mbps is 1.0 Gbps? However on my laptop it always shows 53 Gbps no matter what I do.
-
It shows 53, or 54 MLBS on your laptop, 53 GPBS is impossible. Which means your laptop card is a G Card.
-
The wireless #s I was referring to are from my laptop, sorry about that. My desktop is the one showing 1Gbps using Lan. I had just never seen 1.0 Gbps before.
-
Thanks for the info ahl395. So the next question is does the ratification process for n have a timeline?
-
Unable to achieve 300Mbps with Intel WiFi Link 5100 AGN adapter
Discussion in 'Networking and Wireless' started by MikeNE3, Mar 5, 2009.