Server Tries to Disconnect from Itself
Traceroutes
For some reason, my other post didn't make it to the forum. I had a friend do a traceroute to my server, and did one from here to Google for reference. I'll dig up the chat transcript, redo the Google traceroute, and post back in a minute.
, leaving behind a single black feather.
Traceroutes
Friend's traceroute to me:My traceroute to Google:
Code: Select all
$ traceroute -e -P UDP -p 4534 76.203.173.136
traceroute to (76.203.173.136), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 21.154 ms 11.473 ms 15.757 ms
2 astound-69-42-20-1.ca.astound.net (69.42.20.1) 32.573 ms 42.670 ms 21.134 ms
3 76-14-1-122.sf-cable.astound.net (76.14.1.122) 31.723 ms 31.598 ms 33.045 ms
4 76-14-1-121.sf-cable.astound.net (76.14.1.121) 100.582 ms 102.659 ms 97.166 ms
5 xe-0-2-0.mpr3.sfo3.us.above.net (64.124.146.181) 11.510 ms 13.662 ms 14.187 ms
6 xe-0-0-0.mpr4.sfo3.us.above.net (64.125.31.146) 17.646 ms 13.951 ms 13.315 ms
7 xe-2-0-0.er2.sjc2.us.above.net (64.125.31.158) 13.176 ms 20.155 ms 12.752 ms
8 xe-1-1-0.mpr4.sjc7.us.above.net (64.125.27.93) 13.908 ms 15.387 ms 12.568 ms
9 above-att.sjc7.us.above.net (64.125.12.118) 15.843 ms 14.832 ms 13.757 ms
10 cr1.sffca.ip.att.net (12.122.114.18) 20.846 ms 21.666 ms 17.516 ms
11 12.123.155.117 (12.123.155.117) 15.684 ms 16.703 ms 18.743ms
12 151.164.54.98 (151.164.54.98) 14.201 ms 20.463 ms 15.822 ms
13 69.220.8.94 (69.220.8.94) 17.771 ms 16.461 ms 17.720 ms
14 bras36-g9-0.pltnca.sbcglobal.net (64.164.107.15) [last AT&T router] 20.545 ms 20.773 ms 17.056 ms
15 * * * [would be 76.203.173.136, but it's not getting there for some reason]
16 * * *
17 * * *
18 * * *
19 * *^C
Code: Select all
$ traceroute -e google.com
traceroute: Warning: google.com has multiple addresses; using 74.125.224.146
traceroute to google.com (74.125.224.146), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) [Time Capsule] 5.986 ms 2.455 ms 2.499 ms
2 192.168.1.254 (192.168.1.254) [modem] 12.247 ms 7.748 ms 8.903 ms
3 bras36-l0.pltnca.sbcglobal.net [first AT&T router] (151.164.184.117) 32.451 ms 17.064 ms 15.545 ms
4 64.164.107.2 (64.164.107.2) 12.070 ms 11.817 ms 12.621 ms
5 151.164.93.239 (151.164.93.239) 24.266 ms 207.103 ms 149.338 ms
6 ppp-151-164-52-215.rcsntx.swbell.net (151.164.52.215) 13.202 ms 12.550 ms 13.420 ms
7 gar7.sffca.ip.att.net (12.122.79.97) 13.301 ms 12.676 ms 12.523 ms
8 cr1.sffca.ip.att.net (12.122.110.118) 19.334 ms 17.735 ms 16.415 ms
9 cr1.sffca.ip.att.net (12.123.15.109) 15.831 ms 16.442 ms 15.904 ms
10 cr81.sj2ca.ip.att.net (12.122.1.118) 102.914 ms 37.486 ms 38.485 ms
11 gar4.sn1ca.ip.att.net (12.122.110.61) 14.633 ms 14.455 ms 20.397 ms
12 12.248.108.10 (12.248.108.10) 15.836 ms 21.384 ms 15.711 ms
13 216.239.49.168 (216.239.49.168) 17.113 ms 15.516 ms 14.662 ms
14 64.233.174.119 (64.233.174.119) 15.505 ms 16.139 ms 17.106 ms
15 74.125.224.146 (74.125.224.146) [Google] 16.365 ms 14.258 ms 16.319 ms
$
, leaving behind a single black feather.
Re: Server Tries to Disconnect from Itself
I'm no expert in reading traceroute output, but that means the problem is either that your nearest AT&T router does not forward the ping packet or that your modem is not accepting or not processing it. Since the AT&T router is out of your reach and it not forwarding packets would be quite odd, you should check your modem.