I don't believe the packet loss at this point. Time for a command application. Download Fping from:
The command line to run Fping to the .204 DNS is:
fping 126.96.36.199 -t 10 -c -D -T -L c:\temp\fping13mar.txt
-t 500 That runs a ping at 500 ms intervals. For test purposes, drop this to 10 for a fast run.
-c Runs continuously until stopped with a Control C
-D Stamps the result with a Datestamp
-T Stamps the result with a Timestamp
-L Writes the results to a text file, in this case located in the C:\temp folder.
Change the folder location if you prefer, or delete this altogether if you don't want
a text record
If you change the address to the CMTS address and run it at 10 ms intervals, you can asses very quickly if there is a packet loss issue to the CMTS. Run that for a minute or two at 10 ms intervals and then stop the run. You can then check the results, looking for packet loss. To run that for a longer period, I would set the time for 500 ms, -t 500 You can also specify the number of pings to run using something like -n 1000 instead of -c. After 1000 pings the application will stop. So, you can set this for a low interval run, and set the number of pings to run.
A simpler version of this is to run the normal ping command, using the CMTS as the target. Let that run for however long you want to run it, and then check the packet loss numbers when you stop the run. That will run the ping with a 1 second interval.
1. Run a trace to anywhere: tracert www.google.com
2. Look at the trace address. The first is the router or modem, the second will be the CMTS.
3. Use that CMTS IP address as the ping target: ping 99.xxx.xxx.xxx for example. That will run until you bail out of it.
Let the ping run for 24 hours if you want to. That's what I do. There is also the IPV6 ping to the CMTS to run as well. If you have IPV6 enabled in the modem, to run the IPV6 trace use:
tracert -6 www.google.com
The same situation applies, the first IP address is the modem or router, the second is the CMTS. Ping the CMTS using the IPV6 address.
The high time pings are the result of the modem firmware change in version .27.