logan_gk's profile

logan_gk

New Contributor

 • 

7 Messages

Closed

Experiencing Lag during online gaming

Hi, I'm experiencing lag and stutter during online gaming. I've Cox Preferred plan and play game over wireless connection. I've tried restarting and rebooting modem several times but the issue still remains. I also tried playing game using the LAN connection but the issue persists. I've contacted customer support twice but they have only helped me by restarting the connection again and again.

For debugging purposes, I ran Speedtests (www.speedtest.net) and Pingtests (www.pingtest.net), and i figured out speed fluctuations, at times I get 63.2 Mbps and other time I get 12.2 Mbps. Also, I get 9ms, 12ms and other time 223ms and 300+ pings. These figures are from tests that I ran back to back when I started facing issues during gameplay. Please look into this issue.

I've Netgear C3700 DOCSIS 3.0 cable modem router and I'm using 2.4 GHz connection for wireless connection.


Thanks,

Gaurav K.

Discussions

 • 

Updated 

8K

12

0

0

L

logan_gk

New Contributor

 • 

7 Messages

Providing tracert for google.com

C:\WINDOWS\system32>tracert www.google.com

Tracing route to www.google.com [74.125.224.145]
over a maximum of 30 hops:

  1. 1 ms <1 ms 1 ms 192.168.0.1
  2. 29 ms 43 ms 9 ms 10.3.184.1
  3. 15 ms 17 ms 13 ms ip68-100-3-169.dc.dc.cox.net [68.100.3.169]
  4. 19 ms 13 ms 8 ms ip68-100-2-33.dc.dc.cox.net [68.100.2.33]
  5. 211 ms 12 ms 13 ms 68.1.4.246
  6. 10 ms 17 ms 16 ms ip70-167-150-18.at.at.cox.net [70.167.150.18]
  7. 195 ms 17 ms 38 ms 216.239.46.250
  8. 11 ms 13 ms 17 ms 216.239.48.163
  9. 36 ms 19 ms 29 ms 72.14.235.10
  10. 351 ms 28 ms 28 ms 209.85.142.58
  11. 84 ms 80 ms 84 ms 209.85.142.119
  12. 90 ms 81 ms 95 ms 72.14.237.50
  13. 108 ms 97 ms 92 ms 64.233.175.151
  14. 310 ms 77 ms 82 ms 209.85.250.251
  15. 133 ms 102 ms 191 ms lax02s20-in-f17.1e100.net [74.125.224.145]

Trace complete.

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

Try "Ping 192.168.100.1 -t 50" and see what kind of latency and packet loss you get. That will isolate the latency issues from router > modem or modem > Cox.

0

0

L

logan_gk

New Contributor

 • 

7 Messages

Thanks a lot for your reply.
Here is the ping report:

C:\WINDOWS\system32>ping 192.168.100.1 -t50

Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=13ms TTL=63
Reply from 192.168.100.1: bytes=32 time=760ms TTL=63
Reply from 192.168.100.1: bytes=32 time=35ms TTL=63
Reply from 192.168.100.1: bytes=32 time=103ms TTL=63
Reply from 192.168.100.1: bytes=32 time=98ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=10ms TTL=63
Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
Reply from 192.168.100.1: bytes=32 time=15ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=10ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
Reply from 192.168.100.1: bytes=32 time=867ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=14ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=136ms TTL=63
Reply from 192.168.100.1: bytes=32 time=20ms TTL=63
Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=14ms TTL=63
Reply from 192.168.100.1: bytes=32 time=10ms TTL=63
Reply from 192.168.100.1: bytes=32 time=16ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
Reply from 192.168.100.1: bytes=32 time=14ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=40ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=12ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=632ms TTL=63
Reply from 192.168.100.1: bytes=32 time=17ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=10ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63

Ping statistics for 192.168.100.1:
Packets: Sent = 66, Received = 66, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 867ms, Average = 45ms

 

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

Looks like your getting the latency spikes inside your network. Was that test done wired or wireless? If wireless, my guess would be interference. Do you have alot of wireless networks around you? How is the signal strength?

0

0

L

logan_gk

New Contributor

 • 

7 Messages

This test was done on wireless network. Yes, there are many wireless networks around. Will the "Enable Wireless Isolation" option help in such condition? Signal strength is excellent.

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

logan_gk said:
Will the "Enable Wireless Isolation" option help in such condition? Signal strength is excellent.

No. Wireless isolation is just the router controlling which computers can talk other computers on the network. Its used alot in guest network where you want them online, but able to see your file and printer sharing and other network access.

May want to see what channels others around you are on with inSSIDer or a simular program, then its trail and error. Your always going to get some erratic behavior since its wireless, it's just a matter of how little. Latency spikes are one of the reasons I don't game on wireless. CAT5e is so cheap these days.

0

0

L

logan_gk

New Contributor

 • 

7 Messages

Thanks for the suggestions. :)
I've already tried on CAT5e connection in as a single user. I was still getting some spikes. That's why I was concerned about the router. I'm not sure whether changing the router to Cox preferred routers(http://forums.cox.com/forum_home/internet_forum/f/5/p/30737/reply.aspx) will help.

0

0

L

logan_gk

New Contributor

 • 

7 Messages

Do you have any more suggestions? 

Thanks,

Gaurav

0

0

C

ChrisL

Former Moderator

 • 

7.1K Messages

@logan_gk

You may wish to also try these same tests from another PC to see if you get the same results or not.  This would give you a better idea whether you're troubleshooting a PC or router problem.

0

0

L

logan_gk

New Contributor

 • 

7 Messages

Hello Chris,

Thanks a lot for your reply. I've tried these tests with another PC/Laptop and results are somewhat the same. The netgear technician said that the router hasn't been configured correctly as it should be by your ISP.

0

0

E

EdwardH

Valued Contributor

 • 

755 Messages

The modem portion of the C3700 would be configured though us however that is not a supported wifi gateway from our end. Not saying it will not work with the service but the router is not a one we offer or support with our home networking setups. The CG3000 and CG4500 are the only ones that we support the router/wireless in house. But the router's configuration on a internal network would not cause latency spikes to that degree unless a port or some hand off for the home network was having a issue.

But just to amuse our curiosity and see if that is the case, if the gateway has a way to disable DHCP for the LAN connection and only use it as a wired modem to test it temporary we can rule out the settings on the router and if it is a hardware problem if it continues to show the spikes.
---

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

EdwardH said:
if the gateway has a way to disable DHCP for the LAN connection and only use it as a wired modem

See page 11-12 of this manual for info how to put gateway into bridge mode. Then ping 192.168.0.1 -t 50 from a wired connectionn and see if you still get packet spike or lag.

I wish Cox would get together with some of the open source firmware people and have them build custom config for cox customers. It could even be compatible across several brands. Its nice to see Cox going with Asus with Gigablast, I wish they could sell their products in store.

0

0

Recent Discussions