High Latency to Router

[eafshar]

When i ping my WRT310N router from my d-link DWA 556 wireless pci adapter.. i get a very unstable ping. it sometimes pings countinously at 1ms. and then starts to give packet loss or high pings

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 88ms, Average = 29ms

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=86ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=79ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 86ms, Average = 55ms

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=22ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=83ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 83ms, Average = 26ms

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=727ms TTL=64
Reply from 192.168.1.1: bytes=32 time=568ms TTL=64
Reply from 192.168.1.1: bytes=32 time=760ms TTL=64
Reply from 192.168.1.1: bytes=32 time=173ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 760ms, Average = 557ms

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=427ms TTL=64
Reply from 192.168.1.1: bytes=32 time=145ms TTL=64
Reply from 192.168.1.1: bytes=32 time=99ms TTL=64
Reply from 192.168.1.1: bytes=32 time=454ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 99ms, Maximum = 454ms, Average = 281ms

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=2512ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1098ms TTL=64
Reply from 192.168.1.1: bytes=32 time=833ms TTL=64
Reply from 192.168.1.1: bytes=32 time=665ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 665ms, Maximum = 2512ms, Average = 1277ms

No other computer suffers from such packet loss so its not the router. im using Dlink DWA 556 PCI adapter. I am using windows 7 pro x64 and seeing from http://forums.dlink.com/index.php?topic=3751.0
there seems to be no windows 7x64 fully compatible driver. i have also tried ATHEROS drivers.. it seemed to initially work for a few days until today where the packet loss and high ping has returned.

Does anyone know a solution to this problem? as there is no indication that d-link is going to release a better driver is there a 3rd part firmware i can use? why is there so much jitter between each connection attempt?

this is really disappointing as i have been looking forward to play Battlefield BC2.

 

[DelJo63]

OUCH! You likely known that it should be more like

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 [COLOR="Red"]time<1ms[/COLOR] TTL=250
Reply from 192.168.0.1: bytes=32 [COLOR="Red"]time<1ms[/COLOR] TTL=250
Reply from 192.168.0.1: bytes=32 [COLOR="Red"]time<1ms[/COLOR]TTL=250
Reply from 192.168.0.1: bytes=32 [COLOR="Red"]time<1ms[/COLOR]TTL=250

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I think you are on the right track -- the device or its driver. Being wireless, I assume you have encryption ON -- did you try it off? Which mode are you using and did you try forcing G-ONLY?

 

[eafshar]

well after trying many things.. i fixed my problem by changing the router broadcast channel and frequency. went from channel set on AUTO to 11. and the high ping to router is now fixed. something must have been interfering with it.