D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: NeonSamurai on June 28, 2010, 08:42:02 AM
-
Ok details first,
Router: New DIR-655 Rev A4/Firm 1.21NA (& 1.34NA)
Laptop 1: Intel WiFi Link 5300 AGN
Laptop 2: Dell Truemobile 1300 WLan
Problem: Can't run laptop 1 in N mode and Laptop 2 in G mode at the same time on the router without experience large amounts of lag. Ping shows that the router seems to be alternately talking to each computer (one pings the router successfully, the other no response, with the roles changing every 5-30 seconds), and I get similar results when pinging from the router to either computer. Problem goes away once one computer is disconnected (or switching to N only), or by switching the router to G only mode (with both on).
What I've tried: QOS on/off, WISH on/off, 802.11 mode mixed n/g & mixed n/g/b, Channel width 20 & auto 20/40.
Other settings: WPA2 Only AES, Channel 4, transmission rate Best, Transmit power High, Beacon period 100, RTS & Fragmentation thresholds 2346, DTIM interval 1, WLAN Partition off, WMM Enabled, Short GI Enabled, Extra Wireless Protection Enabled.
Other things of mention, I've had this problem with 2 separate routers, both DIR-655 A4's (one came with 1.32NA and was flashed to 1.34NA), the first one got returned though as it was refusing to port forward properly. Also this problem only seems to exist in wireless and does not seem to affect any wired connections. There is also nothing unusual in the logs. I also scanned using inSSIDer and the wireless signal is steady and on a different channel far removed from other networks (everyone else and their dog in the area is on channel 11). I've also 30/30/30 reset the routers.
Ping looks like this:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=41ms TTL=64
Reply from 192.168.0.1: bytes=32 time=62ms TTL=64
Reply from 192.168.0.1: bytes=32 time=85ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
Reply from 192.168.0.1: bytes=32 time=43ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
-
The 30/30/30 reset has no effect at all on the DIR. Just wanted you to know.
I've seen this behaviour with the DIR before, but since upgrading to 1.3x versions it has not occurred anymore. Are you running with the latest wireless drivers?
Have you tried all channels? Even with no other Ap's around certain channels sometimes experience environment influence.
Do a test: start with your laptop next to your router and move away (and keep retesting every few yards). Also you might want to configure the antennas, but that is also depending on the location, walls ect