Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[poopdawg27]

This configuration for me causes MASSIVE latency in games like 500ms+  where as using the G band gives me more like 20-70mbps and I'm not jumping about sporadically.  I tried enabling/disabling just about every QoS/multicast, tried every possible permutation of security, channel, 802.11 band configuration, and channel width.  It seems the only variable making the difference is connecting via the N band.  I have an unsolved thread over at notebookreviewforums here-

http://forum.notebookreview.com/showthread.php?t=376453

[Demonized]

There are more complaints about the 5300 chipset, regardless of the routers used. IMHO it's a driver issue.

[ttmcmurry]

Do you live in an apartment complex or a home in a neighborhood?

[poopdawg27]

hmm well ive always tried with the most up to date drivers on the intel website...and there are a couple other access points nearby, but all are running G-band.  Results on the N band would give me great *throughput* (faster transfer speed) but the connection would be extremely laggy.  Very very high latencies.

[Demonized]

there are so many variables that influence it. Distance, obstructions etc. So it is hard to say what's the  cause

[poopdawg27]

to give some further information, the 5300 works flawless with 300mbps N on other routers i've tried. 

[Clancy]

This configuration for me causes MASSIVE latency in games like 500ms+  where as using the G band gives me more like 20-70mbps and I'm not jumping about sporadically.  I tried enabling/disabling just about every QoS/multicast, tried every possible permutation of security, channel, 802.11 band configuration, and channel width.  It seems the only variable making the difference is connecting via the N band.  I have an unsolved thread over at notebookreviewforums here-

http://forum.notebookreview.com/showthread.php?t=376453

In your notebookreview thread, someone named "hovercraftdriver" made this suggestion:
"Also, if I may suggest TCP optimizer at Speedguide.net: http://www.speedguide.net/downloads.php ; it's a very nice app that eliminates/improves a bunch of latency/speed problems. If you are knowledgeable, you can configure your own settings. If not, there is an auto-configure option based on a few simple input parameters."

I had similar problems until I used the aforementioned tool. Using it, I found that my MTU was actually 1472 instead of the recommended 1492. I also calculated my TCP Receive Window and the combination of the 2 freed up everything. Check to see if you have the Windows QOS driver loading in your Network Connection Settings. If so, disable it as well.

[ttmcmurry]

I don't believe that changing the MTU is appropriate.  That only affects WAN communication (i.e. cable/dsl modem).  No matter the packet size on the LAN side, it always is 1500 on the way out to the internet unless the MTU is  changed. 

Both G & N use a 2376 bytes packet size (it's a standard!), you could change this.. but why?

I've suggested, in many posts on this forum, to try using InSSIDer.  Scope out your area and see what happens.  You may find that there is too much traffic on the 2.4GHz band to get reliable Wireless-G and/or N service.  It made all the difference for me in NYC.

[Clancy]

I don't believe that changing the MTU is appropriate.  That only affects WAN communication (i.e. cable/dsl modem).  No matter the packet size on the LAN side, it always is 1500 on the way out to the internet unless the MTU is  changed. 

Both G & N use a 2376 bytes packet size (it's a standard!), you could change this.. but why?

I've suggested, in many posts on this forum, to try using InSSIDer.  Scope out your area and see what happens.  You may find that there is too much traffic on the 2.4GHz band to get reliable Wireless-G and/or N service.  It made all the difference for me in NYC.

I can't dispute what you say. All I can offer is my real life experience with adjusting my MTU and Receive window size. Prior to these adjustments, I never got the band width (speed) I paid for.

[poopdawg27]

why would G work and the N not on the same 2.4 ghz band...  I used inssider and it seems my network is dominating channels 8-12 or so

[davevt31]

why would G work and the N not on the same 2.4 ghz band...  I used inssider and it seems my network is dominating channels 8-12 or so

Part of the WIFI "N" spec is that it has to be a "Good Neighbor" to any G/B Networks.  It will throttle down if it senses other networks.

[ttmcmurry]

why would G work and the N not on the same 2.4 ghz band...  I used inssider and it seems my network is dominating channels 8-12 or so

The short explanation is you have a G channel and one or two N channels (remember the 20/40 mhz width?).  The N channels can be in either the 2.4 or 5 GHz band, however the DIR-655 has only 2.4 GHz radios. 

Can you post a screenshot of inSSIDer on here so we can see what your environment looks like?  Use imageshack.com if you need to