dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1465

jbob
Reach Out and Touch Someone
Premium Member
join:2004-04-26
Little Rock, AR
·Comcast XFINITY
Asus GT-AX6000
Asus RT-AC66U B1

jbob

Premium Member

[Connectivity] Modem requires power cycle

Been seeing an issue for the last several weeks. Things looking good and all of a sudden many sites seem hard to connect too. Usually Google related sites. When this happens I eventually just power cycle the cable modem. Once it boots back up everything is fine again.

Now that I've had to do it several times I'm trying to troubleshoot to see if I can narrow down what might be the issue. As of right now I'm not sure I can spot anything glaring.

The issue is going on at this time prior to power cycling modem(Zoom5341J). I have checked modem levels. All look normal. I have used the tools in my router(Asus RT-AC66R) interface to test Ping and Traceroutes. The router doesn't seem like the issue.

Some websites seem to work just fine while others like anything Google related experience slowdown. Microsoft and Yahoo related seem slowed.

One forum I frequent works very well however linked Youtube videos, that were working great earlier today, now show as white blanks on the posts. DSLR is working okay it seems at the moment of this post.

I just wanted to ask about some ideas to look for. Seems to be some kind of DNS issue but this is getting a little too deep for my knowledge. I am using Comcast default DNS servers.
TheDena
Premium Member
join:2014-07-08

TheDena

Premium Member

If you are concerned about the Comcast DNS servers, you could always try an alternative. Personally, I use the OpenDNS servers.

jbob
Reach Out and Touch Someone
Premium Member
join:2004-04-26
Little Rock, AR

jbob

Premium Member

Hey I wanna thank every ones suggestions. They really helped me troubleshoot my issue.

tshirt
Premium Member
join:2004-07-11
Snohomish, WA

tshirt to TheDena

Premium Member

to TheDena
I doubt it's a DNS problem , but he could ADD another DNS server (which would be checked if the Comcast DNS failed to respond) to see if that helps, total substitution leads to geo location, no DNSSEC, and other problems.
tshirt

tshirt to jbob

Premium Member

to jbob
jbob See Profile,
Can you please post this info, it really does help us help you in being sure we all can see the basics have been completed.
»Comcast High Speed Internet FAQ »How To Get Help!

Also can you ping/tracert google .com and post that too?
and use "resource monitor" (Windows) or similar to determine what the IP links are pointing at/ which is not responding?

dslcreature
Premium Member
join:2010-07-10
Seattle, WA

dslcreature to jbob

Premium Member

to jbob
Reminds me of what happens when IPv6 isn't working

plencnerb
Premium Member
join:2000-09-25
53403-1242

1 recommendation

plencnerb

Premium Member

said by dslcreature:

Reminds me of what happens when IPv6 isn't working

I was thinking the same thing.

Before I switched to m0n0wall, I ran pfSense as my router/firewall. My first indication that something was wrong with IPv6 was that my homepage (set as google.com) would take a really long time to load.

This was probably just over a year ago now, so google was one of the first sites (there was probably others, but I know google did have) both an IPv4 IP and IPv6 IP associated with it.

However it all worked, IPv6 had priority so to speak in my network, so if there was a site that did have an IPv6 IP, it would load that way. Of course, you would never notice which side (IPv4 or IPv6) that a site was using.

But, 100% of the time, if the google main page took a long time to load (like 10-20 seconds or more), I knew something was wrong with pfSenses IPv6 configuration. Meaning that even though psSense would show (from its configuration screens), that I had an IPv6 on the WAN side, and my desktop PC showed I had an IPv6 IP from pfSense, that IPv6 IP was no longer valid.

On a side note, I think the issue at the time for me was that pfSense was not able to renew the lease on the IPv6 IP side of things, and the lease would expire. Yet, the interface pages would not show that so I really no longer had an IPv6 IP. Yet, configuration wise, things thought I did which is why DNS tried to use that first (and then fail).

When this would happen, the result was always the same. Google's long load time equaled loss of my IPv6 IP. To verify this, I had 3 sites bookmarked to test my IPv6 connectivity. They would all fail.

I would then reboot everything (Modem, psSense Box, desktop PC), which would fix the IPv6 problem, and google would then load fine.

So, as a suggestion the next time this happens, try to run any (or all) of these web pages and post your results.

Comcast's IPv6 Information Page
»www.comcast6.net/

XFinity IPv6-Readiness Test
»www.test-ipv6.comcast.net/

Test your IPv6
»www.test-ipv6.com/

The 2nd two, if IPv6 is working, should come back 10/10. In my case, when google would not load like it normally does (do to IPv6 not working anymore), they would come back as 0/10.

If that ends up being the case, then we can look at your router (Asus RT-AC66R) and make sure things are setup and configured correctly for IPv6.

--Brian

jbob
Reach Out and Touch Someone
Premium Member
join:2004-04-26
Little Rock, AR
·Comcast XFINITY
Asus GT-AX6000
Asus RT-AC66U B1

1 recommendation

jbob

Premium Member

I'm gonna try and run this down on the basis of it likely being an IPv6 issue. That was also suspect for me.
But I was thinking why does rebooting the modem seem to fix the issue if it may indeed be a IPv6 problem? I'm also thinking the router firmware implementation of IPv6 may also be suspect.

I've already identified some issues with DNS settings with this router. Might have to switch to Merlin firmware.

tito79
join:2010-03-14
Port Saint Lucie, FL

tito79

Member

i would just hook up directly a laptop to the network see how it behaves
jm101
join:2011-07-17
Oakland, CA
ARRIS BGW210-700
Ubiquiti UDM-Pro
Ubiquiti UniFi UAP-AC-PRO

jm101 to jbob

Member

to jbob
said by jbob:

Been seeing an issue for the last several weeks. Things looking good and all of a sudden many sites seem hard to connect too. Usually Google related sites. When this happens I eventually just power cycle the cable modem. Once it boots back up everything is fine again.

Now that I've had to do it several times I'm trying to troubleshoot to see if I can narrow down what might be the issue. As of right now I'm not sure I can spot anything glaring.

The issue is going on at this time prior to power cycling modem(Zoom5341J). I have checked modem levels. All look normal. I have used the tools in my router(Asus RT-AC66R) interface to test Ping and Traceroutes. The router doesn't seem like the issue.

Some websites seem to work just fine while others like anything Google related experience slowdown. Microsoft and Yahoo related seem slowed.

One forum I frequent works very well however linked Youtube videos, that were working great earlier today, now show as white blanks on the posts. DSLR is working okay it seems at the moment of this post.

I just wanted to ask about some ideas to look for. Seems to be some kind of DNS issue but this is getting a little too deep for my knowledge. I am using Comcast default DNS servers.

I've had a very similar problem. »[Connectivity] Random Connection Issues

jbob
Reach Out and Touch Someone
Premium Member
join:2004-04-26
Little Rock, AR

jbob

Premium Member

Except in my case Pings, as well as speed tests, are fine to Google even if Google and Youtube are flaking out at the time. Even the Line Quality - Ping Tests from this site check great.

NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

NetFixer

Premium Member

said by jbob:

Except in my case Pings, as well as speed tests, are fine to Google even if Google and Youtube are flaking out at the time. Even the Line Quality - Ping Tests from this site check great.

I have noticed on my SuSE Linux server, that if I ping a dual stack site it will default to an IPv4 ping (even though IPv6 is the preferred protocol). I have to explicitly do a ping6 to test IPv6 with the ping command:
webhost:/ # ping www.google.com
PING www.google.com (74.125.225.50) 56(84) bytes of data.
64 bytes from ord08s06-in-f18.1e100.net (74.125.225.50): icmp_req=1 ttl=55 time=30.2 ms
64 bytes from ord08s06-in-f18.1e100.net (74.125.225.50): icmp_req=2 ttl=55 time=29.8 ms
64 bytes from ord08s06-in-f18.1e100.net (74.125.225.50): icmp_req=3 ttl=55 time=29.8 ms
64 bytes from ord08s06-in-f18.1e100.net (74.125.225.50): icmp_req=4 ttl=55 time=29.1 ms
64 bytes from ord08s06-in-f18.1e100.net (74.125.225.50): icmp_req=5 ttl=55 time=29.5 ms
^C
--- www.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 29.146/29.736/30.215/0.419 ms
 
webhost:/ # ping6 www.google.com
PING www.google.com(ord08s13-in-x14.1e100.net) 56 data bytes
64 bytes from ord08s13-in-x14.1e100.net: icmp_seq=1 ttl=55 time=23.0 ms
64 bytes from ord08s13-in-x14.1e100.net: icmp_seq=2 ttl=55 time=21.9 ms
64 bytes from ord08s13-in-x14.1e100.net: icmp_seq=3 ttl=55 time=30.1 ms
64 bytes from ord08s13-in-x14.1e100.net: icmp_seq=4 ttl=55 time=22.3 ms
64 bytes from ord08s13-in-x14.1e100.net: icmp_seq=5 ttl=55 time=21.9 ms
^C
--- www.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 21.933/23.896/30.175/3.168 ms
 
webhost:/ # ping6 -n www.google.com
PING www.google.com(2607:f8b0:4009:807::1014) 56 data bytes
64 bytes from 2607:f8b0:4009:807::1014: icmp_seq=1 ttl=55 time=27.2 ms
64 bytes from 2607:f8b0:4009:807::1014: icmp_seq=2 ttl=55 time=22.7 ms
64 bytes from 2607:f8b0:4009:807::1014: icmp_seq=3 ttl=55 time=21.8 ms
64 bytes from 2607:f8b0:4009:807::1014: icmp_seq=4 ttl=55 time=21.8 ms
64 bytes from 2607:f8b0:4009:807::1014: icmp_seq=5 ttl=55 time=21.6 ms
64 bytes from 2607:f8b0:4009:807::1014: icmp_seq=6 ttl=55 time=23.0 ms
^C
--- www.google.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5009ms
rtt min/avg/max/mdev = 21.693/23.088/27.245/1.926 ms
 

I don't see that behavior with Windows (it defaults to trying the default IPv6 protocol), but that may vary depending on the version of Windows being used.
jm101
join:2011-07-17
Oakland, CA
ARRIS BGW210-700
Ubiquiti UDM-Pro
Ubiquiti UniFi UAP-AC-PRO

jm101 to jbob

Member

to jbob
said by jbob:

Except in my case Pings, as well as speed tests, are fine to Google even if Google and Youtube are flaking out at the time. Even the Line Quality - Ping Tests from this site check great.

That's interesting. How often do you need to power cycle your modem?

jbob
Reach Out and Touch Someone
Premium Member
join:2004-04-26
Little Rock, AR

jbob

Premium Member

Doesn't seem to be any pattern. I have gone over a week several times without having to reboot.
jm101
join:2011-07-17
Oakland, CA
ARRIS BGW210-700
Ubiquiti UDM-Pro
Ubiquiti UniFi UAP-AC-PRO

1 edit

1 recommendation

jm101

Member

said by jbob:

Doesn't seem to be any pattern. I have gone over a week several times without having to reboot.

Oh. It seems like it is starting to act up more for us. Strangely enough sometimes just closing my browser and reopening it fixes the problem. Thinking that it is a problem with the Comcast Wireless Gateway.

Don't recall ever having this problem with our old TM722G/WRT54G set up. I wish that TM822s were easier and more affordable to get.

jbob
Reach Out and Touch Someone
Premium Member
join:2004-04-26
Little Rock, AR
·Comcast XFINITY
Asus GT-AX6000
Asus RT-AC66U B1

1 recommendation

jbob

Premium Member

Finally had the issue develop again well enough for me to try a few things as suggested. Tested using the IPv6 test site(s). Failed. Showed no IPv6 available.

So this time I rebooted the router. I had done that before in early stages of troubleshooting and I don't remember it making a difference.

Well this time rebooting the router fixed the issue. So looks like rebooting either the router or modem appears to clear the IPv6 problems.