Can't get to SVTP through Road Runner cable

[SciFiHiFi]

I'm looking for any ideas on why I can't surf to SVTP on any computer connected to my Road Runner cable modem. My connection is working fine otherwise. I can get here using a proxy site or through a VPN.

I've tried reseting my cable modem and I've taken my routers out of the loop to rule them out. Also I've tried a few different public DNS's.

Thoughts?

 

[VirtualSVT]

um...what do you get when you try to connect?

 

[SciFiHiFi]

A whole lot of nothing, as if the site or my connection were down.

 

[Admin]

I'm looking for any ideas on why I can't surf to SVTP on any computer connected to my Road Runner cable modem. My connection is working fine otherwise. I can get here using a proxy site or through a VPN.

I've tried reseting my cable modem and I've taken my routers out of the loop to rule them out. Also I've tried a few different public DNS's.

Thoughts?

did you do a tracert?

 

[SciFiHiFi]

Admin

As with most ISP's, Road Runner blocks ICMP traffic for various security reasons. This renders standard tracert and ping commands useless.

 

[Admin]

Admin

As with most ISP's, Road Runner blocks ICMP traffic for various security reasons. This renders standard tracert and ping commands useless.

Most ISP's do NOT block ICMP traffic, very few do.
From a cursory look, Road Runner does not appear to be one of them. Re: tracert blocked? - dslreports.com


is it possible your firewall is blocking ICMP requests?

 

[SciFiHiFi]

You're right about the ICMP traffic. I saw my tracert failing after getting one hop inside road runner and just assumed they were blocking it.

I can successfuly tracert and ping through my routers, also I have taken them out of the loop for testing so I think I can safely rule them out.

Here's a trace of when it's working. Hop 4 is usually where it fails.

Tracing route to SVTPerformance.com [64.182.71.85]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 12 ms 10 ms cpe-76-175-48-1.socal.res.rr.com
3 11 ms 9 ms 25 ms gig0.lamdca1-cda4.socal.rr.com [76.167.7.93]
4 * 14 ms 16 ms tge4-0-0.lsanca1-rtr1.socal.rr.com [76.167.2.56]

5 16 ms 15 ms 16 ms ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
6 22 ms 25 ms 21 ms ae-3-0.cr0.sjc30.tbone.rr.com [66.109.6.6]
7 25 ms 22 ms 72 ms ae-1-0.pr0.sjc10.tbone.rr.com [66.109.6.137]
8 25 ms 21 ms 22 ms 216.156.84.25.ptr.us.xo.net [216.156.84.25]
9 33 ms 32 ms 31 ms 207.88.13.110.ptr.us.xo.net [207.88.13.110]
10 66 ms 66 ms 76 ms 207.88.12.45.ptr.us.xo.net [207.88.12.45]
11 64 ms 63 ms 69 ms 207.88.14.34.ptr.us.xo.net [207.88.14.34]
12 68 ms 65 ms 67 ms 207.88.185.30.ptr.us.xo.net [207.88.185.30]
13 66 ms 64 ms 82 ms 64.182.192.41
14 76 ms 67 ms 66 ms 85-71-182-64.cust.propagation.net [64.182.71.85]

I'm surprised no one else is reporting this problem.