Jump to content

Can't Get To EV1 Or OCC...


d3bruts1d

Recommended Posts

Not sure if it's a router or what, but for the past 10 or so hours, I've not been able to access OCC or EV1 from my house.... I can access it just fine from work (that's how I'm here posting :P) and from a few other locations...

 

My guess is a misconfigured router with either UUNet or Comcast... As I can reverse look up both OCC and EV1...

 

Anyone else having this issue? Probably not, but worth a shot.. :P

 

 

Anyway, I'll be off and on for the next 5 or so hours... Of things don't get fixed soon, ya'll have a great weekend, and I'll see ya sometime....

 

 

l8r

 

 

 

BTW, Bosco... I think there is also the posibility that this is a Canadian Conspiricy... I'll be watching you mister....

Share this post


Link to post
Share on other sites

Here is a traceroute from the server to you:

I have masked your ip at the end for security reasons:)

 

[root@server httpd]# traceroute 68.47.xxx.xxx

traceroute to 68.47.180.171 (68.47.xxx.xxx), 30 hops max, 38 byte packets

1 216.40.224.1 (216.40.224.1) 1.489 ms 0.434 ms 0.283 ms

2 tayhou-223-3.ev1.net (207.218.223.3) 0.937 ms 0.584 ms 0.426 ms

3 ge-0-0-0.a03.hstntx01.us.ra.verio.net (128.241.2.101) 0.897 ms 0.899 ms 0.874 ms

4 ge-0-1-0.r00.hstntx01.us.bb.verio.net (129.250.30.209) 1.431 ms 1.013 ms 1.194 ms

5 p16-1-1-1.r21.dllstx01.us.bb.verio.net (129.250.5.4) 6.348 ms 5.836 ms 10.407 ms

6 p16-2-0-0.r02.dllstx01.us.bb.verio.net (129.250.3.31) 6.341 ms 5.958 ms 5.866 ms

7 p4-0.att.dllstx01.us.bb.verio.net (129.250.9.110) 6.523 ms 6.156 ms 6.433 ms

8 gbr3-p50.dlstx.ip.att.net (12.123.16.242) 5.988 ms 6.114 ms 6.317 ms

9 gbr4-p20.attga.ip.att.net (12.122.2.90) 35.622 ms 35.581 ms 35.813 ms

10 gbr1-p60.attga.ip.att.net (12.122.5.209) 36.270 ms 36.253 ms 36.182 ms

11 gar1-p360.attga.ip.att.net (12.123.21.1) 36.346 ms 36.468 ms 36.451 ms

12 12.124.59.102 (12.124.59.102) 41.119 ms 41.464 ms 40.426 ms

13 68.47.160.53 (68.47.160.53) 41.167 ms 40.871 ms 40.909 ms

14 * * *

 

68.47.160.53 is your ISP, so im guessing that hop 14 is your firewall blocking the traceroute to your machine. If so, then it looks fine from the server to you.

 

Run a traceroute from your system to the server and post it

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...