Skip to main content
danielp's profile

danielp

New Contributor

 • 

6 Messages

Closed

packet loss.

i've been having an extreme amount of packet loss for about a week now, it usually stays consistent anywhere from 2%-10% at most times but has also jumped up to 65% packet loss.  i just had a tec visit and he said that after he directly tested the line he was receiving no packet loss at all. he then suggested that it may be my modem that was the problem which was a DOCSIS 2.0 so i decided to upgrade to your DOCSIS 3.0 netgear gateway. the problem still persist, and i am still receiving packet loss.  can anyone figure out why i am still dropping packets? this problem is making gaming/streaming impossible.

 

Discussions

 • 

Updated 

5.5K

8

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

Can you post some of your data showing the packet loss? And when the packet loss is occuring, can you post a tracert to one of the servers play/stream.

Also, what are your signal levels? You can find them at the webpage 192.168.0.1 with user "admin" and password "password" and click on "Connection Status" tab. See page 21-22 of manual here for more info.

0

0

D

danielp

New Contributor

 • 

6 Messages

well i would assume the signal levels are fine, the field tech just gave me a brand new single band net gear gateway. i've been using pingtest.net to montor the packet loss
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 813000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK 112001_vm2.0_d.cfg
Security Enabled BPI+
Downstream Bonded Channels
Lock Status Modulation Channel ID Symbol rate Frequency Power SNR DOCSIS/EuroDOCSIS locked
Locked QAM256 133 5360 Ksym/sec 813000000 Hz -3.2 dBmV 38.5 dB DOCSIS
Locked QAM256 134 5360 Ksym/sec 819000000 Hz -2.8 dBmV 38.6 dB DOCSIS
Locked QAM256 135 5360 Ksym/sec 825000000 Hz -2.5 dBmV 38.6 dB DOCSIS
Locked QAM256 136 5360 Ksym/sec 831000000 Hz -3.0 dBmV 38.6 dB DOCSIS
Locked QAM256 141 5360 Ksym/sec 861000000 Hz -3.9 dBmV 37.7 dB DOCSIS
Locked QAM256 142 5360 Ksym/sec 867000000 Hz -3.6 dBmV 37.7 dB DOCSIS
Locked QAM256 143 5360 Ksym/sec 873000000 Hz -3.7 dBmV 37.8 dB DOCSIS
Locked QAM256 144 5360 Ksym/sec 879000000 Hz -3.5 dBmV 37.5 dB DOCSIS
Upstream Bonded Channels
Lock Status Modulation Channel ID Symbol rate Frequency Power
Locked ATDMA 2 5120 Ksym/sec 29800000 Hz 48.5 dBmV
Locked ATDMA 1 5120 Ksym/sec 36300000 Hz 48.5 dBmV
Locked ATDMA 3 5120 Ksym/sec 23300000 Hz 47.0 dBmV
Locked ATDMA 4 2560 Ksym/sec 18400000 Hz 46.5 dBmV

IP_ADDRESS,TEST_DATE,TIME_ZONE,PING,JITTER,PACKET_LOSS,SERVER_NAME,GRADE,MOS,DISTANCE_MILES

"70.173.15.16","9/13/2014 6:03 PM","GMT","57","77","2%","Los Angeles, CA","D","(3.96)","250"

"70.173.15.16","9/13/2014 6:04 PM","GMT","42","53","8%","Los Angeles, CA","D","(3.56)","250"
"70.173.15.16","9/13/2014 6:08 PM","GMT","44","56","5%","Newbury Park, CA","D","(3.87)","250"

"70.173.15.16","9/13/2014 6:14 PM","GMT","75","103","7%","Newbury Park, CA","D","(3.03)","250"

"70.173.15.16","9/13/2014 6:15 PM","GMT","21","3","2%","Newbury Park, CA","C","(4.27)","250"

"70.173.15.16","9/13/2014 6:16 PM","GMT","42","29","2%","Newbury Park, CA","C","(4.21)","250"

"70.173.15.16","9/13/2014 6:18 PM","GMT","59","84","3%","Newbury Park, CA","D","(3.78)","250"

"70.173.15.16","9/13/2014 6:27 PM","GMT","57","80","2%","Newbury Park, CA","D","(3.93)","250"

"70.173.15.16","9/13/2014 6:31 PM","GMT","44","53","2%","Newbury Park, CA","C","(4.17)","250"

"70.173.15.16","9/13/2014 6:32 PM","GMT","33","30","3%","Newbury Park, CA","C","(4.14)","250"

"70.173.15.16","9/13/2014 6:33 PM","GMT","34","35","2%","Newbury Park, CA","C","(4.21)","250"

"70.173.15.16","9/13/2014 6:35 PM","GMT","43","60","2%","Los Angeles, CA","C","(4.13)","250"

"70.173.15.16","9/13/2014 6:36 PM","GMT","37","31","4%","Los Angeles, CA","C","(4.04)","250"

"70.173.15.16","9/13/2014 6:43 PM","GMT","27","26","3%","Los Angeles, CA","C","(4.15)","250"

"70.173.15.16","9/13/2014 6:46 PM","GMT","64","78","4%","Los Angeles, CA","D","(3.70)","250"

"70.173.15.16","9/13/2014 6:53 PM","GMT","23","4","0%","Los Angeles, CA","A","(4.39)","250"

"70.173.15.16","9/13/2014 6:54 PM","GMT","33","26","2%","Los Angeles, CA","C","(4.22)","250"

"70.173.15.16","9/13/2014 6:59 PM","GMT","58","77","2%","Los Angeles, CA","D","(3.95)","250"

"70.173.15.16","9/13/2014 7:01 PM","GMT","58","76","7%","Los Angeles, CA","D","(3.40)","250"
"70.173.15.16","9/13/2014 7:02 PM","GMT","22","2","1%","Los Angeles, CA","B","(4.33)","250"

"70.173.15.16","9/13/2014 7:03 PM","GMT","38","32","3%","Los Angeles, CA","C","(4.13)","250"

"70.173.15.16","9/13/2014 7:05 PM","GMT","34","27","8%","Los Angeles, CA","D","(3.63)","250"

"70.173.15.16","9/13/2014 7:05 PM","GMT","34","27","5%","Los Angeles, CA","D","(3.96)","250"

"70.173.15.16","9/13/2014 7:06 PM","GMT","29","28","1%","Los Angeles, CA","B","(4.30)","250"

"70.173.15.16","9/13/2014 7:08 PM","GMT","28","28","3%","Los Angeles, CA","C","(4.15)","250"

"70.173.15.16","9/13/2014 7:13 PM","GMT","34","27","2%","Los Angeles, CA","C","(4.22)","250"

"70.173.15.16","9/13/2014 7:35 PM","GMT","30","30","3%","Los Angeles, CA","C","(4.14)","250"

"70.173.15.16","9/13/2014 7:36 PM","GMT","22","3","2%","Los Angeles, CA","C","(4.27)","250"

"70.173.15.16","9/13/2014 7:37 PM","GMT","48","55","2%","Los Angeles, CA","C","(4.15)","250"

"70.173.15.16","9/13/2014 7:55 PM","GMT","41","40","2%","Los Angeles, CA","C","(4.20)","250"

"70.173.15.16","9/13/2014 7:59 PM","GMT","34","26","1%","Los Angeles, CA","B","(4.30)","250"

"70.173.15.16","9/13/2014 8:19 PM","GMT","60","78","2%","Los Angeles, CA","D","(3.94)","250"

"70.173.15.16","9/13/2014 8:32 PM","GMT","22","2","5%","Los Angeles, CA","C","(4.02)","250"

"70.173.15.16","9/13/2014 8:44 PM","GMT","16","3","3%","Los Angeles, CA","C","(4.20)","250"

and these are the pingtest.net logs.

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

Not familiar with the data, sorry. I was talking just standard ping and tracert. Knowing that there is packetloss doesn't meaning much if you don't have the tracert to show where.

0

0

D

danielp

New Contributor

 • 

6 Messages

ah alright. how do i do a tracert?

0

0

D

danielp

New Contributor

 • 

6 Messages

and here the tracert and ping.

C:\Users\daniel>ping -n 50 cox.net

Pinging cox.net [68.99.123.161] with 32 bytes of data:
Reply from 68.99.123.161: bytes=32 time=64ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=66ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=70ms TTL=57
Reply from 68.99.123.161: bytes=32 time=66ms TTL=57
Reply from 68.99.123.161: bytes=32 time=66ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=64ms TTL=57
Reply from 68.99.123.161: bytes=32 time=67ms TTL=57
Reply from 68.99.123.161: bytes=32 time=66ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=68ms TTL=57
Reply from 68.99.123.161: bytes=32 time=66ms TTL=57
Reply from 68.99.123.161: bytes=32 time=73ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=89ms TTL=57
Reply from 68.99.123.161: bytes=32 time=72ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=67ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=64ms TTL=57
Reply from 68.99.123.161: bytes=32 time=70ms TTL=57
Reply from 68.99.123.161: bytes=32 time=64ms TTL=57
Reply from 68.99.123.161: bytes=32 time=66ms TTL=57
Reply from 68.99.123.161: bytes=32 time=79ms TTL=57
Reply from 68.99.123.161: bytes=32 time=72ms TTL=57
Reply from 68.99.123.161: bytes=32 time=119ms TTL=57
Reply from 68.99.123.161: bytes=32 time=72ms TTL=57
Reply from 68.99.123.161: bytes=32 time=66ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=68ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=67ms TTL=57
Request timed out.
Reply from 68.99.123.161: bytes=32 time=82ms TTL=57
Reply from 68.99.123.161: bytes=32 time=66ms TTL=57
Reply from 68.99.123.161: bytes=32 time=87ms TTL=57
Reply from 68.99.123.161: bytes=32 time=75ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Request timed out.
Reply from 68.99.123.161: bytes=32 time=74ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57
Reply from 68.99.123.161: bytes=32 time=67ms TTL=57
Reply from 68.99.123.161: bytes=32 time=65ms TTL=57

Ping statistics for 68.99.123.161:
Packets: Sent = 50, Received = 48, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 119ms, Average = 69ms

Tracing route to cox.net [68.99.123.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 11 ms 10 ms 10.98.0.1
3 8 ms 23 ms 17 ms 24-234-16-49.ptp.lvcm.net [24.234.16.49]
4 9 ms 50 ms 8 ms 24-234-6-44.ptp.lvcm.net [24.234.6.44]
5 64 ms 65 ms 66 ms dukedsrj01-ge-210.0.rd.at.cox.net [68.1.1.121]
6 68 ms 68 ms 67 ms 68.1.15.234
7 70 ms 65 ms 65 ms 68.99.123.4
8 * * 65 ms ww2.cox.com [68.99.123.161]

Trace complete.

0

0

C

ChrisL

Former Moderator

 • 

7.1K Messages

I took a look from here and I'm seeing some packet loss to the modem.  It may be time to arrange for a technician to come out and troubleshoot further. -Chris 

0

0

D

danielp

New Contributor

 • 

6 Messages

yeah they recently sent 2 techs out and neither of them could fix the problem, so i guess they are sending out a few others to check the node for my area?

0

0

C

ChrisL

Former Moderator

 • 

7.1K Messages

It does appear a maintenance ticket for your area was recently resolved and I'm not seeing any loss to your modem.  Are you still seeing problems? -Chris 

0

0

Recent Discussions