View previous topic :: View next topic |
Author |
Message |
ScuseMe
Trooper
Joined: Jul 24, 2003
Posts: 10
Location: USA
|
Posted: Sun May 02, 2004 5:41 pm Post subject: Can't access www.trojanhunter.com |
|
|
Hi,
Is anyone having problems accessing www.trojanhunter.com from the US - East coast?. I haven't been able to get to the site since Saturday. Also, I can't get to www.misec.net ; both sites get a "page unavailable" in IE.
When I do a live update, I can't connect to the US server, but I can connect just fine to the Swedish server.
Thanks. |
|
Back to top |
|
|
ScuseMe
Trooper
Joined: Jul 24, 2003
Posts: 10
Location: USA
|
Posted: Sun May 02, 2004 9:58 pm Post subject: |
|
|
I did a little more checking - it seems there is a problem with WilTel (wcg.net). My tracert for www.trojanhunter.com , www.radlight.com , etc. all time out when they hit one of the hosts in wcg.net. Even WilTel's main web page at www.wiltel.net won't load completely for me.
Oh well. |
|
Back to top |
|
|
claire
Site Moderator
Premium Member
Joined: Apr 21, 2002
Posts: 4853
Location: Belgium
|
Posted: Mon May 03, 2004 12:01 am Post subject: |
|
|
Hi,
Try to this
http://forum.misec.net/
_________________
Carpe Diem |
|
Back to top |
|
|
ScuseMe
Trooper
Joined: Jul 24, 2003
Posts: 10
Location: USA
|
Posted: Mon May 03, 2004 8:37 am Post subject: |
|
|
Hi Claire,
Thanks for the link, but it still times out for me. Here's my tracert to forum.misec.net as of Monday 5/3/2004 8:25 am:
Code: |
Tracing route to forum.misec.net [207.44.154.77] over a maximum of 30 hops:
1 18 ms 18 ms 18 ms 10.7.96.1
2 19 ms 18 ms 17 ms at-4-2-0-1716.CORE-RTR1.PHIL.verizon-gni.net [130.81.10.9]
3 20 ms 21 ms 20 ms so-0-2-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.7.217]
4 21 ms 21 ms 20 ms so-0-0-0-0.BB-RTR2.PHIL.verizon-gni.net [130.81.7.214]
5 21 ms 21 ms 23 ms so-6-0-0-0.BB-RTR2.NWRK.verizon-gni.net [130.81.7.186]
6 23 ms 23 ms 23 ms so-5-0-0-0.BB-RTR1.NY5030.verizon-gni.net [130.81.7.189]
7 22 ms 23 ms 23 ms so-6-0-0-0.BB-RTR1.NY325.verizon-gni.net [130.81.7.89]
8 22 ms 23 ms 24 ms so-0-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.4.10]
9 22 ms 20 ms 21 ms so-2-0-0-0.PEER-RTR2.NY111.verizon-gni.net [130.81.4.2]
10 20 ms 22 ms 20 ms nycmnyzlce1-pos3-1.wcg.net [64.200.68.49]
11 20 ms 21 ms 21 ms nycmny2wcx3-pos11-0.wcg.net [64.200.87.85]
12 22 ms 20 ms 20 ms nycmny2wcx2-pos10-0.wcg.net [64.200.87.77]
13 30 ms 30 ms 28 ms hrndva1wcx2-pos4-0-oc48.wcg.net [64.200.240.46]
14 29 ms 28 ms 30 ms hrndva1wcx3-pos9-0.wcg.net [64.200.95.74]
15 39 ms 39 ms 41 ms drvlga1wcx2-pos5-0.wcg.net [64.200.210.57]
16 40 ms 39 ms 39 ms drvlga1wcx1-oc48.wcg.net [64.200.127.49]
17 58 ms 57 ms 58 ms dllstx1wcx3-pos6-0.wcg.net [64.200.240.21]
18 59 ms 58 ms 57 ms dllstx1wcx2-pos9-0-oc48.wcg.net [64.200.110.73]
19 61 ms 63 ms 62 ms hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
<etc> |
And here's one to www.trojanhunter.com :
Code: |
Tracing route to trojanhunter.com [207.44.154.77] over a maximum of 30 hops:
1 16 ms 18 ms 18 ms 10.7.96.1
2 17 ms 18 ms 18 ms at-4-2-0-1716.CORE-RTR1.PHIL.verizon-gni.net [130.81.10.9]
3 21 ms 21 ms 20 ms so-0-2-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.7.217]
4 21 ms 20 ms 21 ms so-0-0-0-0.BB-RTR2.PHIL.verizon-gni.net [130.81.7.214]
5 22 ms 20 ms 21 ms so-6-0-0-0.BB-RTR2.NWRK.verizon-gni.net [130.81.7.186]
6 24 ms 23 ms 23 ms so-5-0-0-0.BB-RTR1.NY5030.verizon-gni.net [130.81.7.189]
7 24 ms 23 ms 23 ms so-6-0-0-0.BB-RTR1.NY325.verizon-gni.net [130.81.7.89]
8 22 ms 23 ms 24 ms so-0-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.4.10]
9 20 ms 21 ms 20 ms so-2-0-0-0.PEER-RTR2.NY111.verizon-gni.net [130.81.4.2]
10 20 ms 21 ms 20 ms nycmnyzlce1-pos3-1.wcg.net [64.200.68.49]
11 21 ms 21 ms 20 ms nycmny2wcx3-pos11-0.wcg.net [64.200.87.85]
12 20 ms 21 ms 20 ms nycmny2wcx2-pos10-0.wcg.net [64.200.87.77]
13 29 ms 31 ms 30 ms hrndva1wcx2-pos4-0-oc48.wcg.net [64.200.240.46]
14 30 ms 31 ms 30 ms hrndva1wcx3-pos9-0.wcg.net [64.200.95.74]
15 38 ms 39 ms 39 ms drvlga1wcx2-pos5-0.wcg.net [64.200.210.57]
16 41 ms 39 ms 39 ms drvlga1wcx1-oc48.wcg.net [64.200.127.49]
17 57 ms 58 ms 57 ms dllstx1wcx3-pos6-0.wcg.net [64.200.240.21]
18 59 ms 57 ms * dllstx1wcx2-pos9-0-oc48.wcg.net [64.200.110.73]
19 63 ms 62 ms 63 ms hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
<etc> |
I thought it would be fixed this morning, but I guess not
|
|
Back to top |
|
|
claire
Site Moderator
Premium Member
Joined: Apr 21, 2002
Posts: 4853
Location: Belgium
|
Posted: Mon May 03, 2004 11:37 am Post subject: |
|
|
I can reach at once Trojan hunter trough the link I posted
_________________
Carpe Diem |
|
Back to top |
|
|
ScuseMe
Trooper
Joined: Jul 24, 2003
Posts: 10
Location: USA
|
Posted: Mon May 03, 2004 1:01 pm Post subject: |
|
|
The problem with the host seems to be fixed now:
Code: |
Tracing route to trojanhunter.com [207.44.154.77] over a maximum of 30 hops:
1 19 ms 18 ms 18 ms 10.7.96.1
2 19 ms 18 ms 17 ms at-4-2-0-1716.CORE-RTR1.PHIL.verizon-gni.net [130.81.10.
3 44 ms 51 ms 19 ms so-0-2-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.7.217]
4 21 ms 20 ms 21 ms so-0-0-0-0.BB-RTR2.PHIL.verizon-gni.net [130.81.7.214]
5 22 ms 21 ms 21 ms so-6-0-0-0.BB-RTR2.NWRK.verizon-gni.net [130.81.7.186]
6 22 ms 23 ms 23 ms so-5-0-0-0.BB-RTR1.NY5030.verizon-gni.net [130.81.7.189]
7 23 ms 23 ms 24 ms so-6-0-0-0.BB-RTR1.NY325.verizon-gni.net [130.81.7.89]
8 21 ms 23 ms 23 ms so-0-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.4.10]
9 20 ms 21 ms 21 ms so-2-0-0-0.PEER-RTR2.NY111.verizon-gni.net [130.81.4.2]
10 22 ms 21 ms 20 ms nycmnyzlce1-pos3-1.wcg.net [64.200.68.49]
11 20 ms 21 ms 21 ms nycmny2wcx3-pos11-0.wcg.net [64.200.87.85]
12 20 ms 21 ms 22 ms nycmny2wcx2-pos10-0.wcg.net [64.200.87.77]
13 29 ms 30 ms 30 ms hrndva1wcx2-pos4-0-oc48.wcg.net [64.200.240.46]
14 30 ms 31 ms 31 ms hrndva1wcx3-pos9-0.wcg.net [64.200.95.74]
15 41 ms 39 ms 39 ms drvlga1wcx2-pos5-0.wcg.net [64.200.210.57]
16 41 ms 42 ms 40 ms drvlga1wcx1-oc48.wcg.net [64.200.127.49]
17 58 ms 57 ms 57 ms dllstx1wcx3-pos6-0.wcg.net [64.200.240.21]
18 57 ms 58 ms 57 ms dllstx1wcx2-pos9-0-oc48.wcg.net [64.200.110.73]
19 62 ms 62 ms 63 ms hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
20 65 ms 74 ms 64 ms hstntx1wce2-everyonesinternet-gige.wcg.net [65.77.93.54]
21 67 ms 68 ms 68 ms 207.218.245.120
22 69 ms 73 ms 72 ms misec.net [207.44.154.77]
Trace complete. |
Hop #20 was where the time-out previously occurred. Maybe Everyones Internet had a problem.
At least it's fixed now
|
|
Back to top |
|
|
|