Help with ISP tech support

[Pliablemoose]

I haven't been able to acess a few web pages for 4 days now. Called my ISP & talked to them about it with no results. Here's a couple of sample tracert runs:

C:\>tracert www.hardocp.com

Tracing route to www.hardocp.com [129.250.247.72]
over a maximum of 30 hops:

1 120 ms 120 ms 120 ms taylor-communications.Dallasdan.cw.net [208.17
140.10]
2 120 ms 120 ms 120 ms bar9-serial6-0-0-5-0.Dallasdan.cw.net [208.172
40.9]
3 120 ms 120 ms 120 ms acr1-loopback.Dallasdan.cw.net [208.172.130.61

4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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.

C:\>tracert www.fatwallet.com

Tracing route to www.fatwallet.com [128.242.179.150]
over a maximum of 30 hops:

1 120 ms 121 ms 120 ms taylor-communications.Dallasdan.cw.net [208.172.
140.10]
2 1011 ms 121 ms 120 ms bar9-serial6-0-0-5-0.Dallasdan.cw.net [208.172.1
40.9]
3 981 ms 121 ms 120 ms acr1-loopback.Dallasdan.cw.net [208.172.130.61]

4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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.


Suggestions?

 

[Keego]

Ask them if they can get to it from their office computers? dunno...

 

[Slikkster]

Doing a quick search of the last router to respond to your tracert, it looks as if another router commonly following that one in the path is: corerouter1.Dallas.cw.net (204.70.9.149).

Try doing a tracert to that router...

Obviously, though, your problem is either with the last good router not forwarding your packets, or the path(s) between it and subsequent routers is broken. Did you pass along your tracert info to this ISP?

They should easily be able to figure out where the breakdown is. Since you're routing from your home pc a few hops into their system, the problem isn't at your end.

 

[Pliablemoose]

Yep, forwarded it to them, they seemed a little clueless.

C:\>tracert 204.70.9.149

Tracing route to corerouter1.Dallas.cw.net [204.70.9.149]
over a maximum of 30 hops:

1 120 ms 120 ms 120 ms taylor-communications.Dallasdan.cw.net [208.172.
140.10]
2 120 ms 1032 ms 120 ms bar9-serial6-0-0-5-0.Dallasdan.cw.net [208.172.1
40.9]
3 882 ms 120 ms 120 ms acr1-loopback.Dallasdan.cw.net [208.172.130.61]

4 1081 ms 120 ms 120 ms corerouter1.Dallas.cw.net [204.70.9.149]

Trace complete.