Internet Issues
Comprox
*chortle*Canada Join Date: 2002-01-23 Member: 7Members, Super Administrators, Forum Admins, NS1 Playtester, NS2 Developer, Constellation, NS2 Playtester, Reinforced - Shadow, WC 2013 - Silver, Subnautica Developer, Subnautica Playtester, Pistachionauts
in Off-Topic
My friend has stumped me. His internet has been flaking recently. Some sites won't load, or will load slowly. You wait a few hours and those sites will be working and others will not that were working before. We've gone straight into the modem (no router or such) with known working PC's to no avail. We've contacted his ISP and they can't help (and we even talked to a competent tech who did some pretty good testing). His neighbour, who is on the same ISP has no issues and since it is cable, they are obviously on the same node.
To give you an idea, here is a traceroute to google.com and google.ca
<!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec-->Tracing route to www.l.google.com [209.85.173.147]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms fortinet.sclibrary.ab.ca [192.168.128.1]
2 <1 ms <1 ms <1 ms 64.42.210.190
3 * * * Request timed out.
4 * * * Request timed out.
5 5 ms 5 ms 5 ms ge4-0-20.wana-calgab.ip.grouptelecom.net [216.18
.32.81]
6 * * * Request timed out.
7 22 ms 22 ms 22 ms pos1-0.peera-sttlwa.ip.grouptelecom.net [66.59.1
90.46]
8 21 ms 21 ms 21 ms six.sea01.google.com [198.32.180.17]
9 21 ms 22 ms 21 ms 209.85.255.63
10 * 33 ms 26 ms 66.249.95.208
11 28 ms 27 ms 28 ms 216.239.48.32
12 27 ms * 28 ms 64.233.174.103
13 * * * Request timed out.
14 29 ms 35 ms 36 ms 74.125.30.70
15 27 ms 27 ms 28 ms mh-in-f147.google.com [209.85.173.147]
Trace complete.
Tracing route to www.l.google.ca [209.85.173.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms fortinet.sclibrary.ab.ca [192.168.128.1]
2 <1 ms <1 ms <1 ms 64.42.210.190
3 * * * Request timed out.
4 * * * Request timed out.
5 5 ms 5 ms 5 ms ge4-0-20.wana-calgab.ip.grouptelecom.net [216.18
.32.81]
6 * * * Request timed out.
7 22 ms 22 ms 22 ms pos1-0.peera-sttlwa.ip.grouptelecom.net [66.59.1
90.46]
8 21 ms 21 ms 21 ms six.sea01.google.com [198.32.180.17]
9 21 ms 21 ms 21 ms 209.85.255.63
10 26 ms * 26 ms 66.249.95.208
11 28 ms 43 ms 28 ms 216.239.46.203
12 * 28 ms 27 ms 216.239.48.141
13 * * * Request timed out.
14 31 ms 27 ms 35 ms 74.125.31.70
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.<!--QuoteEnd--></div><!--QuoteEEnd-->
You will notice it appears to die out just before it hits google's server. The only part we have not replaced is the modem itself, could it causing such an issue?
To give you an idea, here is a traceroute to google.com and google.ca
<!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec-->Tracing route to www.l.google.com [209.85.173.147]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms fortinet.sclibrary.ab.ca [192.168.128.1]
2 <1 ms <1 ms <1 ms 64.42.210.190
3 * * * Request timed out.
4 * * * Request timed out.
5 5 ms 5 ms 5 ms ge4-0-20.wana-calgab.ip.grouptelecom.net [216.18
.32.81]
6 * * * Request timed out.
7 22 ms 22 ms 22 ms pos1-0.peera-sttlwa.ip.grouptelecom.net [66.59.1
90.46]
8 21 ms 21 ms 21 ms six.sea01.google.com [198.32.180.17]
9 21 ms 22 ms 21 ms 209.85.255.63
10 * 33 ms 26 ms 66.249.95.208
11 28 ms 27 ms 28 ms 216.239.48.32
12 27 ms * 28 ms 64.233.174.103
13 * * * Request timed out.
14 29 ms 35 ms 36 ms 74.125.30.70
15 27 ms 27 ms 28 ms mh-in-f147.google.com [209.85.173.147]
Trace complete.
Tracing route to www.l.google.ca [209.85.173.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms fortinet.sclibrary.ab.ca [192.168.128.1]
2 <1 ms <1 ms <1 ms 64.42.210.190
3 * * * Request timed out.
4 * * * Request timed out.
5 5 ms 5 ms 5 ms ge4-0-20.wana-calgab.ip.grouptelecom.net [216.18
.32.81]
6 * * * Request timed out.
7 22 ms 22 ms 22 ms pos1-0.peera-sttlwa.ip.grouptelecom.net [66.59.1
90.46]
8 21 ms 21 ms 21 ms six.sea01.google.com [198.32.180.17]
9 21 ms 21 ms 21 ms 209.85.255.63
10 26 ms * 26 ms 66.249.95.208
11 28 ms 43 ms 28 ms 216.239.46.203
12 * 28 ms 27 ms 216.239.48.141
13 * * * Request timed out.
14 31 ms 27 ms 35 ms 74.125.31.70
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.<!--QuoteEnd--></div><!--QuoteEEnd-->
You will notice it appears to die out just before it hits google's server. The only part we have not replaced is the modem itself, could it causing such an issue?
Comments
Haven't seen it before, but if you've eliminated everything else out maybe it's sending corrupted or malformed packets. Sure seems unlikely though.
I am by no means an expert, but it sounded like dropped packets to me also. Maybe there's a frayed wire somewhere along the line that's becoming disconnected every few seconds? but you tried replacing the ethernet cable(s) already? and the cable TV is fine (if he has it)?
You say the affected sites change only every few hours but are consistent within that time frame?
My first thought would be corrupted routing tables but those would be beyond your modem and your neighbor would likely (but not necessarily) run into the same problem.
tis a hard one.
at both the pole, and entering the modem. A TV filter could be the culprit, or the cable running from the pole to the house even.
at both the pole, and entering the modem. A TV filter could be the culprit, or the cable running from the pole to the house even.<!--QuoteEnd--></div><!--QuoteEEnd-->
Now that you mention that, my networking professor in college had that exact problem. He said he was seeing half of his packets dropped, and I believe it was Comcast. I'd check the signal strength before you replace the modem.
Thanks for the ideas!
Thanks for the ideas!<!--QuoteEnd--></div><!--QuoteEEnd-->
Yeah you always have to check that your modem is one that the ISP says will work with their service, and sometimes they change something that makes an older modem obsolete.
I've always wondered where the fiber-optic backbone that runs through my city has its uplink. I know it's somewhere downtown but I'm not sure. Probably multiple sites.
Hmm... I wonder what it takes to be your own ISP... (besides lots of money) Whee 86Gbps upstream! (well, maybe not that much)
<img src="style_emoticons/<#EMO_DIR#>/tounge.gif" style="vertical-align:middle" emoid=":p" border="0" alt="tounge.gif" />
Anyway, setup was mostly plug-and-play, which meant my parents could, fortunately, handle it. However, as is wont with wireless routers, the default settings left the network completely open. I shared this concern with my parents, but doubted that I could talk them through the procedure of securing (or better yet, disabling) the wireless network over the phone. I figured that it would be okay until I was home the next time, though.
Fast forward a couple of weeks, and I'm at my parents'. I go to disable the wireless functionality, only to discover that my father has already taken care of it - in his own way. Over the (unremovable, I might add) antenna, I find a snugly fitting metal "sheath." Faraday shield for the win.
at both the pole, and entering the modem. A TV filter could be the culprit, or the cable running from the pole to the house even.<!--QuoteEnd--></div><!--QuoteEEnd-->
This is the first positive thing I've ever heard anyone say about comcast. I've had nothing but horrible experiences with them. They're essentially a monopoly, as in most places I've lived, there's no choice besides them for cable speed internet or higher... but whenever something goes wrong (and it always does), it takes hours of waiting on hold to reach customer service, then days before they actually come and 'fix' the problem... and it flares up again 2 days later. and of course, there's the packet shaping, as has been mentioned... and I bet they were making Comprox's friend RENT that 10 year old modem for like $4 a month...
Verizon is about to install FIOS in my building, or so I've been told. I hope they hurry it up. I am dying to dump comcast. right now, I'm sitting on a cable box that doesn't work, and I'm not looking forward to calling about it and sitting on hold for an hour, so I hope the next time I can call, it's to cancel...
sorry for my little rant/derail =P
My experience with Comcast has been positive. Not only do I get through to support in minutes, but if a service tech comes out (and they come out relatively fast) they are extremely thorough, and won't hesitate to install a new cable run or remove *cough*HBO/premium channel*cough*filters that are affecting signal strength. <img src="style_emoticons/<#EMO_DIR#>/wink-fix.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink-fix.gif" />