Unable to reach US IP address

Apologies. I wasn't sure where to as this question. As I'm on FTTC I started it here.

For the past few weeks myself and 3 other people in the UK have been unable to connect to a friends Ventrilo server based in the US (IP: 64.233.245.236) No one else has this problem, just UK residents.

I cannot ping the IP though it is possible to Traceroute it.

Has anyone any ideas why this should suddenly have happened? The IP is not blacklisted as far as I can tell and it it is operated by a well known US ISP Wide Open West.

Of the other UK residents 2 are BT customers like me and the other is on Sprint.

I would be grateful for any ideas.

If this post should have to be moved to another forum. Please accept my apologies for the inconvenience.

The trick is to find the patterns in the trace routes

Those that work probably go via route A
Those that don't probably go via route B

Potentially a provider can rejig the routing, but these may cause loading or other issues for other sites i.e. fixing one routing issue might introduce ten others.

It is certainly contactable from the UK. I can trace to it and connect to the Ventrilo port on it fine (this is over an o2 mobile BB connection of all things!), but as you say it does not respond to pings.....

Text

1 23 45 67 89 1011 1213 1415 1617 1819 2021 2223 2425 2627 2829 3031 3233 3435 3637 3839 4041 4243 4445 4647

[email protected] ~ $ ping 64.233.245.236 PING 64.233.245.236 (64.233.245.236) 56(84) bytes of data.^C --- 64.233.245.236 ping statistics ---17 packets transmitted, 0 received, 100% packet loss, time 15999ms     [email protected] ~ $ traceroute 64.233.245.236 traceroute to 64.233.245.236 (64.233.245.236), 30 hops max, 60 byte packets 1  ubuserver (192.168.1.67)  0.248 ms  0.159 ms  0.133 ms  2  192.168.9.1 (192.168.9.1)  2.300 ms  2.634 ms  3.037 ms 3  172.16.200.22 (172.16.200.22)  633.670 ms  1648.385 ms  1648.594 ms  4  172.16.200.29 (172.16.200.29)  1788.460 ms  1798.643 ms  1838.246 ms 5  172.16.200.110 (172.16.200.110)  1838.579 ms  1848.297 ms  1858.138 ms  6  192.168.103.136 (192.168.103.136)  1888.602 ms  1887.432 ms  1897.222 ms 7  192.168.101.18 (192.168.101.18)  1897.577 ms  74.086 ms  79.199 ms  8  172.25.120.1 (172.25.120.1)  109.261 ms  109.571 ms  129.177 ms 9  192.168.103.161 (192.168.103.161)  139.145 ms  168.992 ms  178.953 ms 10  192.168.103.97 (192.168.103.97)  189.039 ms  198.878 ms  208.985 ms11  172.16.200.157 (172.16.200.157)  209.319 ms *  219.253 ms 12  172.16.238.57 (172.16.238.57)  219.609 ms  228.813 ms  228.958 ms13  172.16.238.246 (172.16.238.246)  159.945 ms  249.269 ms  78.989 ms 14  94-195-96-109.zone9.bethere.co.uk (94.195.96.109)  99.038 ms  109.350 ms  138.950 ms15  * * * 16  * * *17  XE1-0-3-0-GRTLONTL1.red.telefonica-wholesale.net (84.16.6.189)  168.738 ms  178.696 ms  188.660 ms 18  Xe3-0-2-0-grtnycpt3.red.telefonica-wholesale.net (213.140.38.221)  268.646 ms Xe4-1-1-0-grtnycpt2.red.telefonica-wholesale.net (94.142.119.65)  248.813 ms  169.991 ms19  Xe1-2-0-0-grtpaopx2.red.telefonica-wholesale.net (94.142.125.85)  220.028 ms Xe9-3-0-0-grtpaopx2.red.telefonica-wholesale.net (94.142.118.186)  219.544 ms  209.926 ms 20  213.140.55.86 (213.140.55.86)  209.997 ms ge6-0-137.ir1.paloalto-ca.us.xo.net (206.111.12.89)  200.313 ms 206.111.12.85.ptr.us.xo.net (206.111.12.85)  199.952 ms21  * 207.88.13.233.ptr.us.xo.net (207.88.13.233)  209.712 ms  209.921 ms 22  te-3-0-0.rar3.denver-co.us.xo.net (207.88.12.57)  209.817 ms  209.943 ms  209.826 ms23  * te-4-1-0.rar3.chicago-il.us.xo.net (207.88.12.21)  219.576 ms  210.193 ms 24  ae0d0.mcr2.columbus-oh.us.xo.net (216.156.0.62)  209.941 ms  239.956 ms  209.920 ms25  ae1d0.mcr1.columbus-oh.us.xo.net (216.156.1.29)  209.950 ms  200.077 ms  249.924 ms 26  216.156.103.30.ptr.us.xo.net (216.156.103.30)  239.713 ms  229.936 ms  239.762 ms27  * * * 28  * * *29  64-233-245-236.static.col.wideopenwest.com (64.233.245.236)  290.116 ms  229.851 ms  230.299 ms 30  * * *     [email protected] ~ $ telnet 64.233.245.236 3784Trying 64.233.245.236... Connected to 64.233.245.236.Escape character is '^]'.

Can you post up you traceroute result? And can you telnet to the Ventrilo por on it? (port 3784 if it is running default)

Thank you both very much.

I did the following traceroutes

http://network-tools.com/

IP address: 64.233.245.236
Host name: 64-233-245-236.static.col.wideopenwest.com
64.233.245.236 is from United States(US) in region North America

TraceRoute from Network-Tools.com to 64.233.245.236 [64-233-245-236.static.col.wideopenwest.com]
Hop (ms) (ms) (ms)
IP Address Host name
1 0 0 0 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
2 26 26 26 4.69.145.254 vlan90.csw4.dallas1.level3.net
3 27 26 29 4.69.151.162 ae-91-91.ebr1.dallas1.level3.net
4 25 26 25 4.69.151.117 ae-14-14.ebr2.chicago2.level3.net
5 25 26 26 4.69.140.193 ae-5-5.ebr2.chicago1.level3.net
6 26 26 26 4.69.136.213 ae-1-10.bar1.cincinnati1.level3.net
7 29 29 29 4.59.40.18 wideopenwes.bar1.cincinnati1.level3.net
8 Timed out Timed out Timed out -
9 Timed out Timed out Timed out -
10 Timed out Timed out Timed out -
11 Timed out Timed out Timed out -

Trace aborted.

Retrieving DNS records for 64-233-245-236.static.col.wideopenwest.com...
DNS servers
dns2.wideopenwest.com [64.233.207.2]
dns1.wideopenwest.com [64.233.207.16]

Answer records
64-233-245-236.static.col.wideopenwest.com
A 64.233.245.236 3600s

Authority records
col.wideopenwest.com
NS dns1.wideopenwest.com 3600s
col.wideopenwest.com
NS dns2.wideopenwest.com 3600s

Additional records
dns1.wideopenwest.com
A 64.233.207.16 14400s
dns2.wideopenwest.com
A 64.233.207.2 14400s

Whois query for wideopenwest.com...

Results returned from whois.internic.net:


Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

Domain Name: WIDEOPENWEST.COM
Registrar: NETWORK SOLUTIONS, LLC.
Whois Server: whois.networksolutions.com
Referral URL: http://www.networksolutions.com/en_US/
Name Server: DNS1.WIDEOPENWEST.COM
Name Server: DNS2.WIDEOPENWEST.COM
Status: clientTransferProhibited
Updated Date: 07-sep-2011
Creation Date: 30-oct-1999
Expiration Date: 30-oct-2016





From http://ping.eu/traceroute/

traceroute to 64.233.245.236 (64.233.245.236), 30 hops max, 60 byte packets
1 * * *
2 hos-tr4.juniper2.rz13.hetzner.de 213.239.224.97 de 0.160 ms

hos-tr3.juniper2.rz13.hetzner.de 213.239.224.65 de 0.219 ms

hos-tr4.juniper2.rz13.hetzner.de 213.239.224.97 de 0.160 ms
3 core21.hetzner.de 213.239.245.81 de 0.213 ms 0.258 ms 0.190 ms
4 core12.hetzner.de 213.239.245.214 de 2.734 ms

core12.hetzner.de 213.239.245.29 de 2.798 ms 2.793 ms
5 juniper4.rz2.hetzner.de 213.239.245.26 de 2.787 ms 2.828 ms 2.823 ms
6 ae51.bar2.Munich1.Level3.net 62.140.25.101 gb 5.463 ms

ae55.edge7.Frankfurt1.Level3.net 195.16.162.253 gb 9.294 ms

ae51.bar2.Munich1.Level3.net 62.140.25.101 gb 5.463 ms
7 vlan60.csw1.Frankfurt1.Level3.net 4.69.154.62 us 119.016 ms

ae-0-11.bar1.Munich1.Level3.net 4.69.153.253 us 5.834 ms

vlan70.csw2.Frankfurt1.Level3.net 4.69.154.126 us 118.507 ms
8 ae-81-81.ebr1.Frankfurt1.Level3.net 4.69.140.9 us 117.433 ms 117.479 ms

ae-19-19.ebr1.Frankfurt1.Level3.net 4.69.153.246 us 122.541 ms
9 ae-47-47.ebr2.Paris1.Level3.net 4.69.143.142 us 119.266 ms

ae-45-45.ebr2.Paris1.Level3.net 4.69.143.134 us 121.460 ms

ae-48-48.ebr2.Paris1.Level3.net 4.69.143.146 us 120.642 ms
10 ae-42-42.ebr2.Washington1.Level3.net 4.69.137.54 us 118.922 ms

ae-41-41.ebr2.Washington1.Level3.net 4.69.137.50 us 118.796 ms

ae-44-44.ebr2.Washington1.Level3.net 4.69.137.62 us 119.681 ms
11 ae-48-48.ebr2.Washington12.Level3.net 4.69.202.62 us 119.276 ms

ae-47-47.ebr2.Washington12.Level3.net 4.69.202.58 us 120.102 ms

ae-48-48.ebr2.Washington12.Level3.net 4.69.202.62 us 119.276 ms
12 ae-6-6.ebr2.Chicago2.Level3.net 4.69.148.146 us 118.838 ms 121.406 ms 120.631 ms
13 ae-5-5.ebr2.Chicago1.Level3.net 4.69.140.193 us 118.626 ms 120.541 ms 119.295 ms
14 ae-1-10.bar1.Cincinnati1.Level3.net 4.69.136.213 us 121.011 ms 118.769 ms 118.690 ms
15 WIDEOPENWES.bar1.Cincinnati1.Level3.net 4.59.40.18 us 125.735 ms 125.212 ms 124.502 ms
16 * * *
17 * * *
18 64-233-245-236.static.col.wideopenwest.com 64.233.245.236 us 134.154 ms 141.040 ms 140.964 ms
19 * * *
20 * * *
21 * * *
No reply for 3 hops. Assuming we reached firewall.


Done Via CMD prompt just now...

Tracing route to 64-233-245-236.static.col.wideopenwest.com [64.233.245.236]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BThomehub.home [192.168.1.254]
2 15 ms 15 ms 15 ms 217.32.142.12
3 15 ms 16 ms 15 ms 217.32.142.78
4 16 ms 16 ms 16 ms host109-159-245-146.range109-159.btcentralplus.com [109.159.245.146]
5 17 ms 16 ms 16 ms 31.55.165.95
6 16 ms 16 ms 16 ms 31.55.165.109
7 16 ms 15 ms 15 ms acc2-xe-4-2-2.mr.21cn-ipp.bt.net [109.159.250.244]
8 25 ms 22 ms 23 ms core2-te0-13-0-17.ealing.ukcore.bt.net [109.159.250.170]
9 24 ms 24 ms 64 ms peer2-xe-4-2-0.telehouse.ukcore.bt.net [109.159.252.49]
10 25 ms 25 ms 24 ms 166-49-211-192.eu.bt.net [166.49.211.192]
11 27 ms 27 ms 27 ms 195.66.224.130
12 115 ms 120 ms 118 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
13 124 ms 132 ms 132 ms te-3-0-0.rar3.washington-dc.us.xo.net [207.88.12.74]
14 122 ms 116 ms 114 ms ae0d0.mcr1.columbus-oh.us.xo.net [216.156.0.58]
15 131 ms 131 ms 132 ms 216.156.103.30.ptr.us.xo.net [216.156.103.30]
16 * * * Request timed out.
17 * * * Request timed out.
18 143 ms 147 ms 143 ms 64-233-245-236.static.col.wideopenwest.com [64.233.245.236]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


MrSaffron - I would agree with you but there's no way to specify which route I imagine?

For you, no you cannot control the route, but the ISP might be able to influence, but if its two or three links down the chain that is the issue it can make life more fun.

There was this recent issue with BT that looks to be down to routing issues
http://www.thinkbroadband.com/news/6260-bt-infinity-...

In reply to a post by Opabinia:

Done Via CMD prompt just now...

Tracing route to 64-233-245-236.static.col.wideopenwest.com [64.233.245.236]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BThomehub.home [192.168.1.254]
2 15 ms 15 ms 15 ms 217.32.142.12
3 15 ms 16 ms 15 ms 217.32.142.78
4 16 ms 16 ms 16 ms host109-159-245-146.range109-159.btcentralplus.com [109.159.245.146]
5 17 ms 16 ms 16 ms 31.55.165.95
6 16 ms 16 ms 16 ms 31.55.165.109
7 16 ms 15 ms 15 ms acc2-xe-4-2-2.mr.21cn-ipp.bt.net [109.159.250.244]
8 25 ms 22 ms 23 ms core2-te0-13-0-17.ealing.ukcore.bt.net [109.159.250.170]
9 24 ms 24 ms 64 ms peer2-xe-4-2-0.telehouse.ukcore.bt.net [109.159.252.49]
10 25 ms 25 ms 24 ms 166-49-211-192.eu.bt.net [166.49.211.192]
11 27 ms 27 ms 27 ms 195.66.224.130
12 115 ms 120 ms 118 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
13 124 ms 132 ms 132 ms te-3-0-0.rar3.washington-dc.us.xo.net [207.88.12.74]
14 122 ms 116 ms 114 ms ae0d0.mcr1.columbus-oh.us.xo.net [216.156.0.58]
15 131 ms 131 ms 132 ms 216.156.103.30.ptr.us.xo.net [216.156.103.30]
16 * * * Request timed out.
17 * * * Request timed out.
18 143 ms 147 ms 143 ms 64-233-245-236.static.col.wideopenwest.com [64.233.245.236]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


MrSaffron - I would agree with you but there's no way to specify which route I imagine?

Right - so you can traceroute to it just fine..... it is there at hop 18. Ignore the subsequent time outs, that's just a common ICMP misconfiguration causing the trace to continue.

Can you telnet to the Ventrilo port on it?

No no telnet. Assuming I did it correctly I am not familiar with Telnet.

From Telnet prompt I typed....open static.col.wideopenwest.com 3784


Thanks.

Yep that should do it, or just the command:

telnet 64.233.245.236 3784

If it fails to connect then something between you and that server is blocking traffic to that port - first place to start looking is at your own firewall / security software to see if it has any settings that restrict outbound connections (quite a sensible policy).

Can't ping it from my BT connection either.

Being unable to ping a server is not indicative of any problem, as many servers are configured to ignore pings. The fact that you can tracert it shows it's alive.

I think this topic would be better raised in your ISP's forum where you are more likely to find users with the same routing, or even General. It is not a fibre issue.