• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Routing problem

smack Down

Diamond Member
I'm trying to connect to a server but because of bad routing table so where between me and them I can't connect. I want to know who I complain to try and get this fixed. Is it my ISP problem? the servers ISP or some one in between. I know that the server is reachable for other people on the internet.

Tracing route to webservices.schedulesdirect.tmsdatadirect.com [206.18.98.175]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 8 ms 8 ms 7 ms c-3-0-ubr01.nashua.nh.boston.comcast.net [73.166.212.1]
3 8 ms 8 ms 7 ms ge-1-37-ur01.nashua.nh.boston.comcast.net [68.87.153.193]
4 7 ms 8 ms 7 ms 68.87.147.158
5 9 ms 9 ms 10 ms po-24-ur01.lowell.ma.boston.comcast.net [68.87.144.161]
6 11 ms 10 ms 9 ms po-21-ar01.needham.ma.boston.comcast.net [68.87.144.157]
7 18 ms 17 ms 17 ms 12.118.88.5
8 36 ms 39 ms 36 ms 12.127.5.62
9 42 ms 37 ms 37 ms tbr2.cgcil.ip.att.net [12.122.10.106]
10 40 ms 35 ms 35 ms 12.122.99.73
11 41 ms 41 ms 38 ms 12-122-254-50.attens.net [12.122.254.50]
12 40 ms 39 ms 40 ms mdf1-bi8k-2-eth-1-3.chi1.attens.net [63.240.128.174]
13 * ^C
 
What makes you think it's bad routing tables somewhere?

Are you saying it stops / hangs at the 13th hop ? That could just be a firewall or routing policy denying traceroute traffic.

Do you get any response from that site? (Like normal pages / index page comes up OK, but when you go to an encrypted / SSL page it hangs / fails)

Based on the output you posted, it all looks OK.

Let us know

Scott
 
Yes it stop at hop 13 and of course I can't connect to the site. And no it isn't someone denying traceroute traffic.
 
It looks like I'm a couple hops closer, but I get the same thing:


Tracing route to 206.18.98.175.tms-idc.com [206.18.98.175]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 172.16.1.28
2 9 ms 9 ms 9 ms adsl-xx-xx-xx-xx.dsl.emhril.sbcglobal.net [xx.xx.xx.xx]
3 9 ms 9 ms 9 ms dist2-vlan60.emhril.ameritech.net [68.22.72.131]

4 10 ms 9 ms 9 ms bb2-g10-0.emhril.ameritech.net [151.164.43.84]
5 10 ms 9 ms 11 ms 151.164.94.41
6 9 ms 11 ms 9 ms gar8.cgcil.ip.att.net [12.122.79.85]
7 11 ms 11 ms 11 ms tbr1.cgcil.ip.att.net [12.122.99.6]
8 11 ms 9 ms 9 ms 12.122.99.13
9 14 ms 13 ms 13 ms 12-122-254-50.attens.net [12.122.254.50]
10 15 ms 14 ms 15 ms mdf1-bi8k-1-eth-2-2.chi1.attens.net [63.240.128.186]
11 * * * Request timed out.
12 * * * Request timed out.
13 ^C

The above is through AT&T DSL at home (Chicago), but I got the same general response from a machine that is ~2 hops from the local NAP.

What kind of server is it?





 
I get to the server and get this nifty apache page:

--------------------------------------------------------------------------------

type Status report

message /

description The requested resource (/) is not available.


--------------------------------------------------------------------------------

Apache Tomcat/5.5.17



OP, what do you get?
 
Back
Top