[SOLVED] unreliable network connectivity (ping plotter and tracerts)

avataranonymous

Honorable
Sep 11, 2018
16
0
10,510
Hello,
I'm having connectivity issues both WiFI and ethernet connections in my apartment.

I have comcast ISP and netgear GS208 ethernet switch.

pingplotter data


tracerts:

2 * 9 ms * 96.120.60.37
3 12 ms 12 ms 25 ms ae-122-rur02.beaverton.or.bverton.comcast.net [68.85.150.49]
4 598 ms 39 ms 32 ms ae-51-ar01.troutdale.or.bverton.comcast.net [68.87.216.105]
5 * 16 ms 22 ms be-33490-cr01.seattle.wa.ibone.comcast.net [68.86.92.217]
6 * 15 ms * be-10847-pe02.seattle.wa.ibone.comcast.net [68.86.86.226]
7 * 15 ms 13 ms 50.242.149.198
8 * * * Request timed out.
9 18 ms 17 ms 14 ms dns.google [8.8.4.4]

Trace complete.

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.204.189
2 617 ms 18 ms 20 ms 96.120.60.37
3 13 ms 18 ms 12 ms ae-122-rur01.beaverton.or.bverton.comcast.net [162.151.125.209]
4 13 ms 11 ms 14 ms ae-2-rur02.beaverton.or.bverton.comcast.net [68.85.243.154]
5 11 ms 12 ms 13 ms ae-51-ar01.troutdale.or.bverton.comcast.net [68.87.216.105]
6 * 17 ms * be-33490-cr01.seattle.wa.ibone.comcast.net [68.86.92.217]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * 14 ms * dns.google [8.8.8.8]
11 * 35 ms * dns.google [8.8.8.8]
12 * * * Request timed out.
13 * 16 ms 14 ms dns.google [8.8.8.8]

Trace complete.



Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.204.189
2 * * * Request timed out.
3 12 ms 9 ms 11 ms ae-122-rur01.beaverton.or.bverton.comcast.net [162.151.125.209]
4 11 ms 27 ms 19 ms ae-2-rur02.beaverton.or.bverton.comcast.net [68.85.243.154]
5 16 ms 15 ms 22 ms ae-51-ar01.troutdale.or.bverton.comcast.net [68.87.216.105]
6 20 ms 16 ms 15 ms be-33490-cr01.seattle.wa.ibone.comcast.net [68.86.92.217]
7 13 ms 15 ms 15 ms be-10846-pe01.seattle.wa.ibone.comcast.net [68.86.86.90]
8 15 ms 16 ms 14 ms 50.242.148.186
9 * * * Request timed out.
10 15 ms 16 ms 16 ms dns.google [8.8.8.8]

Trace complete.


Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.204.189
2 24 ms 10 ms 11 ms 96.120.60.37
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * 71.236.228.43 reports: Destination host unreachable.

Trace complete.

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.204.189
2 * * * Request timed out.
3 659 ms 12 ms 13 ms ae-122-rur01.beaverton.or.bverton.comcast.net [162.151.125.209]
4 11 ms 11 ms 11 ms ae-2-rur02.beaverton.or.bverton.comcast.net [68.85.243.154]
5 14 ms 13 ms 11 ms ae-51-ar01.troutdale.or.bverton.comcast.net [68.87.216.105]
6 16 ms 20 ms 19 ms be-33490-cr01.seattle.wa.ibone.comcast.net [68.86.92.217]
7 23 ms 19 ms 13 ms be-10846-pe01.seattle.wa.ibone.comcast.net [68.86.86.90]
8 14 ms 14 ms 20 ms 50.242.148.186
9 * * * Request timed out.
10 13 ms 13 ms 14 ms dns.google [8.8.8.8]

Trace complete.


Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.204.189
2 71.236.228.43 reports: Destination host unreachable.

Trace complete.

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.204.189
2 71.236.228.43 reports: Destination host unreachable.

Trace complete.

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.204.189
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * 71.236.228.43 reports: Destination host unreachable.
 
Last edited:
I would start by researching if your modem has any diagnostic capability. You could try a web browser to 192.168.100.1 (many modems use that). Look at your signal strength and signal to noise. You really want downlink signal +5 to -7 db. Signal to noise 30db or higher. See this for an explanation -- https://pickmymodem.com/signal-levels-docsis-3-03-1-cable-modem/

thank you.

The status page has some entries i didn't find posted in the article. "not started" for most and an offline status?

modem status
 
I don't know. Mine doesn't say that. It might be ISP specific. It does seem strange to me. The cable modem status of "Offline" is the one that is odd to me. Do you have an ethernet input rather than a coax input?

Modem's plugged via coax. My roomie set it up and i moved in later. I tried WiFi on my desktop but it was horrible for gaming so i went back to my Ethernet cable and bought a Ethernet switch. However, all WiFi/cabled computers deal with internet issues currently.
 
Modem's plugged via coax. My roomie set it up and i moved in later. I tried wifi on my desktop but it was horrible for gaming so i back to my ethernet cable and bought a ethernet switch. However, all wifi/cabled computers deal with internet issues currently.
That "Offline" status is VERY odd to me. Is this a combo modem router or a standalone modem?
If it is a combo unit, then maybe the "Offline" status only changes if you use it as a standalone modem. Maybe there are different operational modes.
Maybe somebody else will see this dialog and have more background.
 
That "Offline" status is VERY odd to me. Is this a combo modem router or a standalone modem?
If it is a combo unit, then maybe the "Offline" status only changes if you use it as a standalone modem. Maybe there are different operational modes.
Maybe somebody else will see this dialog and have more background.

For clarity on my ends sake: When you say "standalone" does that mean it was purchased seperate and not the one that comcast provided? If so, I think it's a yes but I will double check with the roomie who set it up. He declined getting the comcast router as he didn't want to pay the monthly fee for the CC router and got the google router instead.


Also: The "status" page of the modem has various T3/T4 errors.
 
That "Offline" status is VERY odd to me. Is this a combo modem router or a standalone modem?
If it is a combo unit, then maybe the "Offline" status only changes if you use it as a standalone modem. Maybe there are different operational modes.
Maybe somebody else will see this dialog and have more background.



Aug 29 2019 19:39:033-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=04:4e:5a:36:ed:0b;CMTS-MAC=00:5f:86:93:a5:cc;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2019 19:38:533-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=04:4e:5a:36:ed:0b;CMTS-MAC=00:5f:86:93:a5:cc;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2019 19:38:433-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=04:4e:5a:36:ed:0b;CMTS-MAC=00:5f:86:93:a5:cc;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2019 19:38:233-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=04:4e:5a:36:ed:0b;CMTS-MAC=00:5f:86:93:a5:cc;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2019 19:38:233-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=04:4e:5a:36:ed:0b;CMTS-MAC=00:5f:86:93:a5:cc;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2019 19:38:133-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=04:4e:5a:36:ed:0b;CMTS-MAC=00:5f:86:93:a5:cc;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2019 19:37:433-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=04:4e:5a:36:ed:0b;CMTS-MAC=00:5f:86:93:a5:cc;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2019 19:37:333-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=04:4e:5a:36:ed:0b;CMTS-MAC=00:5f:86:93:a5:cc;CM-QOS=1.1;CM-VER=3.0;
 
For clarity on my ends sake: When you say "standalone" does that mean it was purchased seperate and not the one that comcast provided? If so, I think it's a yes but I will double check with the roomie who set it up. He declined getting the comcast router as he didn't want to pay the monthly fee for the CC router and got the google router instead.


Also: The "status" page of the modem has various T3/T4 errors.
If you are using the google router, then this is just a modem. I have reached the limit of my cable modem expertise ...