Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: TimeWarner/RoadRunner Connection Problem (Read 3076 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

TimeWarner/RoadRunner Connection Problem

Greetings, all!

I've been a long-time lurker of the HA.org forums and greatly enjoyed both the information and the camaraderie that exists amongst the members (unless you're still flaunting the greatness of -r3mix, of course! ). Anyway, on to my question/problem...

Recently I'd moved from my home state of Pennsylvania to Austin, TX. There I'd gotten a cable connection via Time Warner/RoadRunner. Much to my dismay, my attempts to bring up HA proved to be futile! Though I'm afraid I lack the networking skill to find where my problem lies exactly, I know that often a traceroute log of the connection attempt can come in handy. To that end, I've included it below:

Code: [Select]
C:\Documents and Settings\User>tracert hydrogenaudio.org

Tracing route to hydrogenaudio.org [209.152.181.169]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.0.1
  2    10 ms    19 ms    11 ms  10.37.160.1
  3     9 ms     7 ms     7 ms  srp4-0.austtxa-rtr1.austin.rr.com [66.68.2.254]

  4    18 ms    10 ms     8 ms  srp0-0.austtxrdc-rtr2.austin.rr.com [66.68.1.253
]
  5     9 ms    10 ms    10 ms  pos10-3.austtxrdc-rtr4.texas.rr.com [66.68.1.106
]
  6    18 ms    23 ms    17 ms  son0-1-1.hstqtxl3-rtr1.texas.rr.com [24.93.33.22
1]
  7    17 ms    15 ms    17 ms  pop1-hou-P0-3.atdn.net [66.185.133.149]
  8   136 ms   208 ms   222 ms  bb1-hou-P2-0.atdn.net [66.185.150.148]
  9    25 ms    22 ms    24 ms  bb1-dls-P6-0.atdn.net [66.185.152.132]
 10   138 ms   205 ms   211 ms  bb2-dls-P2-0.atdn.net [66.185.153.29]
 11    35 ms    47 ms    34 ms  bb2-kcy-P6-0.atdn.net [66.185.152.129]
 12   126 ms   202 ms   211 ms  bb1-kcy-P1-0.atdn.net [66.185.152.126]
 13    48 ms    48 ms    58 ms  bb1-chi-P6-0.atdn.net [66.185.152.124]
 14    48 ms    47 ms    49 ms  pop1-chi-P0-0.atdn.net [66.185.141.85]
 15    54 ms    47 ms    45 ms  Sprint.atdn.net [66.185.150.218]
 16    48 ms    47 ms    49 ms  sl-bb22-chi-5-0.sprintlink.net [144.232.20.90]
 17    52 ms    48 ms    47 ms  sl-bb23-chi-13-0.sprintlink.net [144.232.26.50]

 18    50 ms    57 ms    50 ms  sl-bb20-atl-10-0.sprintlink.net [144.232.8.133]

 19    50 ms    55 ms    57 ms  144.232.29.66
 20    59 ms    49 ms    51 ms  leg-208-30-205-130-RIA.sprinthome.com [208.30.20
5.130]
 21    49 ms    50 ms    50 ms  border6.pc2-bbnet2.acs.pnap.net [64.94.0.75]
 22    53 ms    50 ms    51 ms  itc-3.border6.acs.pnap.net [64.94.6.78]
 23    66 ms    68 ms    69 ms  suwC5.gig4-3.edeltacom.com [216.154.207.61]
 24    50 ms    50 ms    51 ms  suw0N.gig4-3-6.edeltacom.com [216.154.207.122]
 25    73 ms    67 ms    67 ms  66.0.192.252
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.


My IP currently is 70.112.212.141
  • and am only able to access HA via the use of an open web proxy service.

    I so greatly enjoy HA and the information contained within and would certainly appreciate knowing if there's anything that I can do from my end to allow me to access the site once again.

    Thanks for taking the time to read my post! 

  • : Dynamic, I should have noted.