Losing Packets

First - packet loss between where & where? Second - have you considered the possibility of interference (RFI) from adjacent networks, microwave ovens, etc., etc.?

fordem wrote:
First - packet loss between where & where? Second - have you considered the possibility of interference (RFI) from adjacent networks, microwave ovens, etc., etc.?

Packet loss just playing any online game such as BF4. I get the packet loss symbol and get extreme rubberbanding. I also did ping 10.0.0.1 -t which is my gateway and I get request timeout for every like 30 successful attempts. I just started having this problem and nothing has changed in my setup.

So for all you know the packet loss could be occurring between your ISP and their ISP - which would be totally outside of your control and not indicative of a problem in your network.

Fire up command prompt and ping path google. See if you are finding packet loss/time outs along the path.

That would be "pathping".

dug_less wrote:
Fire up command prompt and ping path google. See if you are finding packet loss/time outs along the path.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\XXXX>ping google.com -t

Pinging google.com [2607:f8b0:4006:80a::1002] with 32 bytes of data:
Reply from 2607:f8b0:4006:80a::1002: time=22ms
Reply from 2607:f8b0:4006:80a::1002: time=25ms
Request timed out.
Reply from 2607:f8b0:4006:80a::1002: time=646ms
Reply from 2607:f8b0:4006:80a::1002: time=30ms
Reply from 2607:f8b0:4006:80a::1002: time=22ms
Reply from 2607:f8b0:4006:80a::1002: time=22ms
Reply from 2607:f8b0:4006:80a::1002: time=27ms
Reply from 2607:f8b0:4006:80a::1002: time=29ms

Ping statistics for 2607:f8b0:4006:80a::1002:
Packets: Sent = 9, Received = 8, Lost = 1 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 646ms, Average = 102ms

Can you try to Ping as well your router and see if it has packet loss. Do you get the same problem using a different device?

minions08 wrote:
Can you try to Ping as well your router and see if it has packet loss. Do you get the same problem using a different device?

Yeah I had the same exact problem.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\asus>ping 10.0.0.1 -t

Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time=1115ms TTL=64
Reply from 10.0.0.1: bytes=32 time=11ms TTL=64
Reply from 10.0.0.1: bytes=32 time=5ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=5ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 10.0.0.1: bytes=32 time=1622ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 10.0.0.1:
Packets: Sent = 16, Received = 15, Lost = 1 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1622ms, Average = 184ms
Control-C

I'm not sure if this will help, but have you tried the Mediatek USB driver from Mediatek's website rather than using Netgear's drivers?

I'm having the exact same issue with the A6210, except I just bought it yesterday to try to replace my malfunctioning A6200 (can't connect to 5GHz channels in the 3-digit range).

I was playing Final Fantasy XIV last night and kept getting intense lag spikes. I switched back to the A6200 and connected to the 2.4GHz network (since that's all available to me) and there was no issue at all.

Today I pinged google and my router both with the A6210 using both the latest Netgear driver and then the latest Mediatek driver. Both consistently resulted in an average of 15% packet loss.

I immediately ran the same tests with the A6200 and consistently had 0% packet loss.

Something is clearly going on, and I don't know if it's defective and I should get another unit or if it's just always going to do this.