My friend just got a server from *****.com

It is great, it's fast as hell, they have some nice bandwith, no slowness what so ever, everythign is GREAT

Ping times are very good especially to sservers liek ftp.uu.net

64 bytes from ftp.UU.NET (192.48.96.9): icmp_seq=0 ttl=243 time=44.437 msec
64 bytes from ftp.UU.NET (192.48.96.9): icmp_seq=1 ttl=243 time=40.480 msec
64 bytes from ftp.UU.NET (192.48.96.9): icmp_seq=2 ttl=243 time=41.117 msec
64 bytes from ftp.UU.NET (192.48.96.9): icmp_seq=3 ttl=243 time=39.616 msec

[root@xtroot /tmp]# ping stormdata.net
PING stormdata.net (216.215.239.29) from 66.34.51.216 : 56(84) bytes of data.
64 bytes from 216.215.239.29: icmp_seq=0 ttl=243 time=39.720 msec
64 bytes from 216.215.239.29: icmp_seq=1 ttl=243 time=39.107 msec
64 bytes from 216.215.239.29: icmp_seq=2 ttl=243 time=38.954 msec

stormdata is ran off serverhost.com

So anyways
back to the story

Basically, yesterday, i logged into my dialtone server and tracerouted and pinged the ***** server it was fast and great
now today, I goto traceroute, it gives me some messed up stuff... I goto telnet, no route to host... What do you guys think:

r00tabega:~# telnet 66.34.51.220
Trying 66.34.51.220...
telnet: Unable to connect to remote host: No route to host

r00tabega:~# traceroute 66.34.51.220
traceroute to 66.34.51.220 (66.34.51.220), 30 hops max, 38 byte packets
1 ns.cr5000.net (66.33.25.224) 2999.640 ms !H 3000.140 ms !H 2999.837 ms !H

wtf??
can anyone here explain why this is happpening?

I called dialtone they said they could telnet and traceroute the ***** server fine

also the ***** server can't telnet to the dialtone server (my dialtone) and can't tracerout eor ping

But it can telnet and traceroute to another dialtone server.
my server is 66.33.25.224
It can't do **** all to that server, but it can with *.30 ?
wtf

any ideas ?

think a reboot would fix ?
any ideas ?

I just did a traceroute on our DI server to *****.com...
traceroute to *****.com (63.249.159.33), 30 hops max, 38 byte packets
1 64.65.56.1 (64.65.56.1) 54.932 ms 49.687 ms 48.248 ms
2 serial3-0-7.hsa1.mia1.level3.net (63.212.176.29) 1.896 ms 1.919 ms 2.049 ms
3 ge-6-0-0.mp2.Miami1.level3.net (64.159.0.17) 2.098 ms 2.041 ms 2.147 ms
4 so-5-1-0.mp1.Dallas1.level3.net (209.247.11.170) 30.102 ms 30.336 ms 31.255 ms
5 pos8-0.core1.Dallas1.level3.net (209.247.10.98) 29.838 ms 52.815 ms 29.899 ms
6 209.245.240.146 (209.245.240.146) 49.744 ms 49.479 ms 49.505 ms
7 dal-core-02.inet.qwest.net (205.171.25.49) 41.481 ms 41.841 ms 41.576 ms
8 dal-edge-07.inet.qwest.net (205.171.25.58) 49.636 ms 49.797 ms 50.025 ms
9 63.145.32.190 (63.145.32.190) 35.251 ms 35.080 ms 35.279 ms
10 gi4.core.propagation.net (66.34.255.2) 35.879 ms 35.101 ms 34.868 ms
11 *****.com (63.249.159.33) 42.936 ms 35.870 ms 35.358 ms

ya but thats *****.com man thats a diff ip

66.34.51.216
try that instead

No problem...
traceroute to 66.34.51.216 (66.34.51.216), 30 hops max, 38 byte packets
1 64.65.56.1 (64.65.56.1) 0.758 ms 0.526 ms 0.544 ms
2 s4-0-0.ar1.TPA1.gblx.net (64.209.252.61) 7.642 ms 7.896 ms 7.658 ms
3 pos5-1-155M.cr1.MIA1.gblx.net (206.132.248.42) 13.384 ms 13.518 ms 12.853 ms
4 pos0-0-622M.cr2.WDC2.gblx.net (208.178.174.82) 41.725 ms 41.697 ms 41.324 ms
5 so2-1-0-622M.br1.WDC2.gblx.net (208.178.174.62) 41.585 ms 41.684 ms 41.420 ms
6 206.132.150.162 (206.132.150.162) 41.529 ms 41.990 ms 41.600 ms
7 wdc-core-03.inet.qwest.net (205.171.24.69) 42.129 ms 41.834 ms 41.694 ms
8 hou-core-01.inet.qwest.net (205.171.5.187) 72.072 ms 72.279 ms 72.300 ms
9 dal-core-02.inet.qwest.net (205.171.5.172) 64.102 ms 63.931 ms 64.047 ms
10 dal-edge-07.inet.qwest.net (205.171.25.58) 72.102 ms 72.665 ms 72.484 ms
11 63.145.32.190 (63.145.32.190) 58.368 ms 57.343 ms 57.688 ms
12 gi4.core.propagation.net (66.34.255.2) 57.899 ms 57.574 ms 57.451 ms
13 66.34.51.216 (66.34.51.216) 59.334 ms 58.439 ms 58.514 ms

lol

I think a reboot might fix it

Reboots fix the most oddest problems

Looking at those figure.... Here's a pretty common traceroute from Australia to a US server lately (Google in this case) - read 'em and weep... I do

04/04/01 02:13:59 Fast traceroute google.com
Trace google.com (216.239.37.100) ...
1 202.138.46.26 132ms 126ms 126ms TTL: 0 (myd0104.myd.iprimus.net.au ok)
2 202.138.46.25 147ms 138ms 116ms TTL: 0 (eth02.myd.iprimus.net.au ok)
3 202.138.46.1 145ms 123ms 177ms TTL: 0 (No rDNS)
4 203.134.12.11 146ms 126ms 182ms TTL: 0 (No rDNS)
5 139.130.65.13 147ms 149ms 130ms TTL: 0 (serial5-1-1.cha11.brisbane.telstra.net ok)
6 139.130.247.238 155ms 132ms 135ms TTL: 0 (gigabitethernet3-0.cha-core3.brisbane.telstra.net ok)
7 203.50.6.29 133ms 132ms 138ms TTL: 0 (pos0-3.ken-core1.sydney.telstra.net ok)
8 203.50.13.18 145ms 144ms 133ms TTL: 0 (gigabitethernet0-0.ken-core4.sydney.telstra.net ok)
9 203.50.6.190 142ms 138ms 140ms TTL: 0 (gigabitethernet3-1.pad-core3.sydney.telstra.net bogus rDNS: host not found [authoritative])
10 203.50.126.62 355ms 363ms 385ms TTL: 0 (No rDNS)
11 198.32.176.11 364ms 356ms 364ms TTL: 0 (dix.above.net ok)
12 208.185.175.161 353ms 355ms 381ms TTL: 0 (sjc2-pao1-oc48-2.sjc2.above.net ok)
13 208.184.233.134 421ms 428ms 426ms TTL: 0 (dca2-sjc2-oc48.dca2.above.net ok)
14 208.184.233.126 422ms 436ms 430ms TTL: 0 (iad1-dca2-oc192.iad1.above.net ok)
15 208.185.0.122 426ms 432ms 429ms TTL: 0 (core1-iad1-oc48.iad4.above.net ok)
16 208.185.0.42 429ms 426ms 430ms TTL: 0 (main1colo1-core1-oc12.iad4.above.net ok)
17 64.124.113.173 427ms 423ms 421ms TTL: 0 (64.124.113.173.available.google.com bogus rDNS: host not found [authoritative])
18 216.239.47.26 430ms 420ms 419ms TTL: 0 (vabi1-gige-1-1.google.com bogus rDNS: host not found [authoritative])
19 216.239.37.100 431ms 429ms 440ms TTL: 43 (google.com ok)

Ouch,

Those look similar to the pings I get to Australia. I play a game, Ultima Online, with a friend over there and I average about 600ms... makes for horible gameplay :)