• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Trace route question

I

Irishllama

[H]ard|Gawd
Joined
Nov 29, 2004
Messages
1,634
Alright, so I did a traceroute to my domain (www.woworg.com) Because I could not connect
Hop (ms) (ms) (ms)
IP Address Host name
1 0 0 0
66.98.244.1 gphou-66-98-244-1.ev1.net
2 0 0 0
66.98.241.16 gphou-66-98-241-16.ev1.net
3 0 0 0
66.98.240.4 gphou-66-98-240-4.ev1.net
4 1 1 1
129.250.10.105 ge-2-1-0.r00.hstntx01.us.bb.verio.net
5 1 1 1
129.250.3.47 p16-7-0-0.r02.hstntx01.us.bb.verio.net
6 8 9 8
129.250.2.195 p16-7-0-0.r01.dllstx09.us.bb.verio.net
7 8 8 9
129.250.2.185 p16-3-0-0.r01.dllstx09.us.bb.verio.net
8 9 9 9
204.70.194.70 bhr2-pos-5-0.fortworthda1.savvis.net
9 9 9 9
204.70.134.10 bhr1-pos-5-0.fortworthda1.savvis.net
10 9 10 10
216.39.66.146 -
11 10 Timed out Timed out
216.39.79.42 -
12 Timed out Timed out 10
72.232.2.187 toronto.dnsdc4.com



This is the trace route, eh what exactly does this mean? I see that it timed out twice, is this the reason I cannot connect to my domain?
 
It means it timed out at the last two hops either due to it being down or a firewall blocking it .

But I'd recommend asking in the Networking forum :)
 
Yeah, these days, a lot of routers, especially those inside a company (as opposed to 'public' routers) are either going to be firewalled or simply ignore the tracert packets. If you can get your hands on tcptraceroute, you might have better luck.
 
Well, I still can not connect to this domain, it just times out, and FF gives me a Problem loading page, I am not the only one with this problem. But if I use a proxy from some place close to the server up north, I can connect to it fine. Any clue why?

Thanks in advance
 
Well I did a traceroute and got similar, but slightly stranger results:

Code: 
Tracing route to woworg.com [72.232.2.187]
over a maximum of 30 hops:

  1    17 ms    11 ms    18 ms  73.76.48.1
  2    15 ms    23 ms    14 ms  68.87.212.197
  3    13 ms    14 ms    19 ms  68.87.212.9
  4    15 ms    16 ms    18 ms  12.117.240.9
  5    18 ms    15 ms    21 ms  tbr2032701.sffca.ip.att.net [12.123.12.53]
  6    16 ms    15 ms    15 ms  gbr2-a90s5.sffca.ip.att.net [12.123.12.22]
  7    19 ms    15 ms    18 ms  dcr1-so-3-0-0.sanfranciscosfo.savvis.net [192.205.32.110]
  8    21 ms    14 ms    19 ms  dcr2-so-5-0-0.SanFranciscosfo.savvis.net [204.70.192.150]
  9    28 ms    30 ms    23 ms  dcr1-so-2-0-0.LosAngeles.savvis.net [204.70.192.89]
 10    70 ms    55 ms    59 ms  dcr2-so-1-3-0.dallas.savvis.net [204.70.192.250]
 11    60 ms    55 ms    72 ms  bhr2-pos-4-0.fortworthda1.savvis.net [208.172.131.86]
 12    58 ms    56 ms    57 ms  csr2-ve241.fortworthda1.savvis.net [216.39.64.43]
 13    57 ms    58 ms    57 ms  csr1-ve242.fortworthda1.savvis.net [216.39.64.58]
 14    65 ms     *       58 ms  216.39.79.38
 15    60 ms    57 ms     *     toronto.dnsdc4.com [72.232.2.187]
 16    70 ms     *        *     toronto.dnsdc4.com [72.232.2.187]
 17    62 ms     *      163 ms  toronto.dnsdc4.com [72.232.2.187]

Trace complete.

The timeouts dont happen until the last few hops. And then they are intermittent. If this were a firewall or router blocking/ignoring ICMP, you'd see it more consistently for that hop. In the above output, each host that timed out also responded as well. In that case, it seems to me that they may be having some technical issues, or they are just massively overloaded.

I'm also wondering if they are having some sort of routing problem. Notice that the last 3 hops have the same IP? Seems kinda odd. Suffice it to say that ur host is having some issues.
 
Lugztaz said:
works for me :|
Click to expand...
Yeah Im at school atm, and it works here... Yet it does not work at home... Im begining to think its one of my ISP's router or something.
 
Irishllama said:
Yeah Im at school atm, and it works here... Yet it does not work at home... Im begining to think its one of my ISP's router or something.
Click to expand...
Sort of...it would most likely be a router at the other end, one of the ones giving sporadic results. I too get bizarre results:



4 32 ms 31 ms 38 ms dia-core-01.inet.qwest.net [205.171.10.41]
5 28 ms 50 ms 49 ms dal-core-02.inet.qwest.net [67.14.2.10]
6 30 ms 32 ms 31 ms dap-brdr-01.inet.qwest.net [205.171.225.53]
7 37 ms 26 ms 32 ms dpr1-so-1-2-1.dallasequinix.savvis.net [208.173.
178.145]
8 29 ms 33 ms 31 ms bhr2-pos-5-0.fortworthda1.savvis.net [204.70.194
.70]
9 31 ms 32 ms 32 ms 216.39.64.27
10 28 ms 31 ms 33 ms 216.39.66.26
11 * * * Request timed out.
12 * * 32 ms toronto.dnsdc4.com [72.232.2.187]
 
Hop 16/17 is No responce, Hop 15/17 finds IP but dose not resolve domain.

I still think it's a problem on your end, since i can still get to it.
 
You must log in or register to reply here.
Back
Top