My Comcast problems have even the Comcast techies stumped...

Toggle sidebar Toggle sidebar
S

SALvation

Senior member
Apr 10, 2001
964
0
0
I have a Comcast problem that currently has stumped 3 Comcast techies. Maybe you guys can do better...

I can reach every site on the Internet fine, except one, www.seriouszone.com. The site went down about 3 weeks ago and when it came back up, it never worked again from my home connection. I can see it from work, and my friends let me know it is up when it is down for me, so I know it's specific to me and not the site. I don't get any specific error, it just never comes up and says "site cannot be found". BTW, I'm using Windows XP and IE6.

I can't ping or FTP to the site either. When I try to tracert to it, I get this:

Tracing route to seriouszone.com [64.191.4.64]
over a maximum of 30 hops:

1) 8ms 8ms 7ms 10.65.64.1
2) * * * Request timed out.
3) * * * Request timed out.
4) * * * Request timed out.
5) 10ms 9ms 7ms 68.60.32.250
6) 16ms 17ms 16ms s1-gw32-chi-4-1.sprintlink.net [144.223.70.209]
7) 17ms 19ms 15ms s1-bb21-chi-4-2.sprintlink.net [144.232.26.33]
8) 33ms 32ms 33ms s1-bb21-spr-13-1.sprintlink.net [144.232.19.206]
9) 38ms 39ms 36ms s1-bb21-pen-10-3.sprintlink.net [144.232.8.161]
10) 41ms 37ms 37ms s1-bb25-pen-9-0.sprintlink.net [144.232.5.238]
11) 35ms 35ms 35ms s1-gw1-pen-10-0.sprintlink.net [144.232.5.6]
12) 53ms 55ms 54ms s1-hostnoc-1-0.sprintlink.net [144.228.171.178]
13-30) * * * Request timed out.

Now the weird thing is that no matter which site I tracert to, the 2nd, 3rd, and 4th hops always time out, but with the rest, I eventually get there. This is the only site I can't see. I remember from old tracert's that those hops are the Comcast servers.

I have tried deleting history, cookies, temp files, all that stuff. The Comcast guys can see it from there so they say it isn't a DNS issue. They have no idea. I don't have a router but I have ZoneAlarm. I tried uninstalling and reinstalling or just shutting it off but nothing works.

Any ideas guys? Thanks for any help.
 
guyver01

guyver01

Lifer
Sep 25, 2000
22,135
5
61
Originally posted by: SALvation
I have a Comcast problem that currently has stumped 3 Comcast techies. Maybe you guys can do better...

Tracing route to seriouszone.com [64.191.4.64]
over a maximum of 30 hops:

1) 8ms 8ms 7ms 10.65.64.1
2) * * * Request timed out.
3) * * * Request timed out.
4) * * * Request timed out.
5) 10ms 9ms 7ms 68.60.32.250
6) 16ms 17ms 16ms s1-gw32-chi-4-1.sprintlink.net [144.223.70.209]
7) 17ms 19ms 15ms s1-bb21-chi-4-2.sprintlink.net [144.232.26.33]
8) 33ms 32ms 33ms s1-bb21-spr-13-1.sprintlink.net [144.232.19.206]
9) 38ms 39ms 36ms s1-bb21-pen-10-3.sprintlink.net [144.232.8.161]
10) 41ms 37ms 37ms s1-bb25-pen-9-0.sprintlink.net [144.232.5.238]
11) 35ms 35ms 35ms s1-gw1-pen-10-0.sprintlink.net [144.232.5.6]
12) 53ms 55ms 54ms s1-hostnoc-1-0.sprintlink.net [144.228.171.178]
13-30) * * * Request timed out.

Any ideas guys? Thanks for any help.
Click to expand...


looks like the problem is with sprintlink.. a few days ago sprintlink had some serious problems... they lost a backbone router i think.... we had to reroute some of our routes away from sprintlink... looks like your ISP might have to do the same thing.... sprintlink isn't handing it off to where it's supposed to go...

the problem isn't really on Comcast's end... but since Comcast is peering with sprintlink, they should be able to open up a NOC ticket with Sprintlink for the routing problem.

Either THAT... or seriouszone.com is BLOCKING your IP Subnet due to past hack attempts.... is your friend also on Comcast, and is his IP address close in octet range, or different?

C:\Documents and Settings\Owner>tracert www.seriouszone.com

Tracing route to seriouszone.com [64.191.4.64]
over a maximum of 30 hops:

1 11 ms 60 ms 14 ms x.x.x.x
2 35 ms 43 ms 15 ms pos0-0-nycmnyq-rtr1.nyc.rr.com [24.29.100.65]
3 51 ms 16 ms 44 ms pos1-0-nycmnyk-rtr2.nyc.rr.com [24.29.100.57]
4 12 ms 15 ms 13 ms pos4-0-nycmnyk-rtr1.nyc.rr.com [24.29.101.233]
5 10 ms 9 ms 27 ms pos1-0-nycmnyw-rtr2.nyc.rr.com [24.29.98.9]
6 18 ms 13 ms 16 ms pos3-0-nycmnyw-rtr1.nyc.rr.com [24.29.101.241]
7 82 ms 27 ms 11 ms pos0-0-nycmnyrdc-rtr2.nyc.rr.com [24.29.98.225]
8 19 ms 38 ms 40 ms pop1-new-P3-0.atdn.net [66.185.137.9]
9 46 ms 11 ms 14 ms bb1-new-P0-0.atdn.net [66.185.137.1]
10 21 ms 19 ms 52 ms bb1-ash-P13-0.atdn.net [66.185.152.97]
11 17 ms 48 ms 18 ms pop2-ash-P0-0.atdn.net [66.185.139.210]
12 100 ms 118 ms 95 ms CogentTestPeering.atdn.net [66.185.141.242]
13 18 ms 44 ms 23 ms p13-0.core01.dca01.atlas.cogentco.com [66.250.7.21]
14 21 ms 20 ms 20 ms p4-0.core01.phl01.atlas.cogentco.com [66.28.4.18]
15 24 ms 53 ms 22 ms g49.ba01.b003003-3.phl01.atlas.cogentco.com [66.28.67.238]
16 21 ms 21 ms 22 ms BurstNet.demarc.cogentco.com [66.250.5.70]
17 74 ms 56 ms 36 ms pos-6-1-border.scr1.hostnoc.net [66.197.191.17]
18 32 ms 72 ms 35 ms 64.191.4.64

Trace complete.

www.seriouszone.com resolves to 64.191.4.64

Do not contact either Los Nettos (ln.net) or Centergate Research Group (centergate.com) based on the results of this traceroute.

3 130.152.80.30 2.297 ms isi-1-lngw2-pos.ln.net [AS226] Los Nettos origin AS
4 66.28.28.33 7.262 ms f1.ba01.b000899-0.lax01.atlas.cogentco.com (DNS error) [AS16631] Unknown
5 66.28.6.245 9.918 ms g12-4.core01.lax01.atlas.cogentco.com (DNS error) [AS16631] Unknown
6 66.28.4.78 7.156 ms p5-0.core01.san01.atlas.cogentco.com (DNS error) [AS16631] Unknown
7 66.28.4.5 36.747 ms p6-0.core01.iah01.atlas.cogentco.com (DNS error) [AS16631] Unknown
8 66.28.4.46 56.456 ms p15-0.core01.tpa01.atlas.cogentco.com (DNS error) [AS16631] Unknown
9 66.28.4.142 60.806 ms p14-0.core01.jax01.atlas.cogentco.com (DNS error) [AS16631] Unknown
10 66.28.4.138 68.466 ms p5-0.core01.atl01.atlas.cogentco.com (DNS error) [AS16631] Unknown
11 66.28.4.126 80.541 ms p14-0.core02.dca01.atlas.cogentco.com (DNS error) [AS16631] Unknown
12 66.28.4.21 79.141 ms p15-0.core01.dca01.atlas.cogentco.com (DNS error) [AS16631] Unknown
13 66.28.4.18 82.598 ms p4-0.core01.phl01.atlas.cogentco.com (DNS error) [AS16631] Unknown
14 66.28.67.238 83.729 ms g49.ba01.b003003-3.phl01.atlas.cogentco.com (DNS error) [AS16631] Unknown
15 66.250.5.70 85.403 ms BurstNet.demarc.cogentco.com (DNS error) [AS16631] Unknown
16 66.197.191.17 91.724 ms pos-6-1-border.scr1.hostnoc.net (DNS error) [AS21788] Unknown
17 64.191.4.64 90.490 ms DNS error [AS21788] Unknown

 
Linux23

Linux23

Lifer
Apr 9, 2000
11,374
741
126
doesn't look like a DNS issue, because it is resolving to the IP address from the trace?

here is how my trace look:

1 1 ms <1 ms <1 ms 192.168.10.10
2 10 ms 9 ms 12 ms 10.104.96.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 11 ms 32 ms 11 ms 68.39.224.162
9 12 ms 12 ms 22 ms 12.124.179.81
10 12 ms 11 ms 18 ms gbr5-p80.n54ny.ip.att.net [12.123.1.202]
11 13 ms 14 ms 21 ms ar2-p310.cdknj.ip.att.net [12.123.192.9]
12 28 ms 29 ms 30 ms 12.119.155.82
13 28 ms 30 ms 28 ms 64.191.4.64


looks like comcast is routing me over att.net instead of sprint. maybe there is some sort of BGP route missing back to your subnet?

or maybe sprint does not know how to get to the destination host?

is your friend on comcast as well? if so, how does his traces lool?
 
ebaycj

ebaycj

Diamond Member
Mar 9, 2002
5,418
0
0
likely your IP Address or even your whole subnet have been blocked, either at the sprintlink.net router, or at the actual website, for some reason or another.

this is probably not your fault, or comcast's.

Ebaycj
 
narzy

narzy

Elite Member
Feb 26, 2000
7,006
1
81
just some FYI: Comcast techies don't know their ass from a hole in the ground (no offense to FFM but eather do ATTbi techs.) as for your problem, guyver01 summed it up quite nicely. (had the same problem here ate work. ATTbi infact...:Q)
 
iamwiz82

iamwiz82

Lifer
Jan 10, 2001
30,772
13
81
i had the exact same problem contacting one site. It ended up being an issue with the routings. For some reason, the DNS server i was on was not updating the IP addy on it, and i was being sent to an old IP.

Have you tried pinging it from work, writing down the IP, and then using the ip t oconnect at home?
 
L

lRageATMl

Senior member
Jun 19, 2002
327
0
0
Originally posted by: narzy
just some FYI: Comcast techies don't know their ass from a hole in the ground (no offense to FFM but eather do ATTbi techs.) as for your problem, guyver01 summed it up quite nicely. (had the same problem here ate work. ATTbi infact...:Q)
Click to expand...

your so right it's not even funny. I hate comcast...it's not fair that they are the only Cable Provider here (Montgomery County...MD)
 
guyver01

guyver01

Lifer
Sep 25, 2000
22,135
5
61
Originally posted by: narzy
as for your problem, guyver01 summed it up quite nicely.
Click to expand...

thank you :)

as a senior network tech at an ISP i gotta deal with these problems almost daily.... it's easy to troubleshoot, if ya know what you're doing and what to look at. :)



 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom