PDA

View Full Version : Can't reach woodmann.com from home


TBone
September 24th, 2008, 10:49
I'm not sure how long this has been going on (several months, in any case), but I can't reach woodmann's server from home.

Traceroute from work to 71.6.196.237:
Code:
Tracing route to woodmann.com [71.6.196.237]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.254.254
2 5 ms 5 ms 5 ms 10.80.3.169
3 5 ms 5 ms 5 ms 66.196.212.65
4 5 ms 6 ms 6 ms ge-9-18.car2.dallas1.level3.net [4.71.170.17]
5 378 ms 207 ms 211 ms te-7-4-72.dllstx2wch010.wcg.level3.net [4.68.110
.14]
6 5 ms 6 ms 5 ms 64.200.249.125
7 46 ms 45 ms 45 ms dllstx1wcx2-pos4-0.wcg.net [64.200.249.70]
8 48 ms 48 ms 48 ms sndgca1wcx010-pos6-0.wcg.net [64.200.210.110]
9 49 ms 48 ms 48 ms sndgca1wce1-calfregional-gige.wcg.net [65.77.90.
42]
10 49 ms 49 ms 49 ms fc6196237.aspadmin.net [71.6.196.237]


Traceroute from home:
Code:
traceroute to woodmann.com (71.6.196.237), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 6.779 ms 7.957 ms 8.298 ms
2 71.244.41.1 (71.244.41.1) 13.388 ms 13.643 ms 15.341 ms
3 P3-3.LCR-04.DLLSTX.verizon-gni.net (130.81.49.54) 15.662 ms 15.884 ms 16.333 ms
4 130.81.29.182 (130.81.29.182) 17.715 ms 17.963 ms 18.383 ms
5 0.so-7-1-0.XT4.DFW9.ALTER.NET (152.63.0.173) 20.202 ms 20.462 ms 22.546 ms
6 0.so-7-0-0.XL4.DFW13.ALTER.NET (152.63.98.81) 22.959 ms 8.147 ms 7.057 ms
7 0.so-7-0-0.BR1.DFW13.ALTER.NET (152.63.98.69) 9.631 ms 10.127 ms 11.933 ms
8 192.205.33.169 (192.205.33.169) 39.381 ms 39.771 ms 40.217 ms
9 tbr1.dlstx.ip.att.net (12.123.16.2) 49.874 ms 50.153 ms 50.392 ms
10 cr1.dlstx.ip.att.net (12.122.18.161) 50.694 ms 51.805 ms 52.384 ms
11 cr1.phmaz.ip.att.net (12.122.28.182) 52.127 ms 52.868 ms 53.091 ms
12 cr1.sd2ca.ip.att.net (12.122.31.233) 47.485 ms 44.469 ms 44.488 ms
13 gbr1.sd2ca.ip.att.net (12.122.2.141) 45.044 ms 45.214 ms 47.598 ms
14 gar2.sd2ca.ip.att.net (12.123.145.177) 47.911 ms 48.140 ms *
15 12.86.27.90 (12.86.27.90) 50.485 ms 50.681 ms 50.903 ms
16 g4-2-6503.complexdrive.com (216.98.153.41) 51.089 ms 51.800 ms 52.058 ms
17 c5-po2.complexdrive.com (216.98.153.30) 59.236 ms 59.492 ms 59.903 ms
18 * * *
19 * * *
[...]


Not all that informative, I guess, since they take completely different routes. However, from the last addresses in the first traceroute, it looks like woodmann.com is collocated in San Diego, CA. I checked their website, and Complex Drive is apparently a collocation outfit in San Diego. That's where the traffic is getting lost. Does this mean anything to Woodmann? It's not a huge deal because I can ssh through to a friend's Squid server and get to it that way, but it looks like a routing issue that might be local to woodmann.com's colo. I just thought you should know about it in case it is.

Edit: A traceroute from the friend's comp in Houston goes out through alter.net like my home trace, but then goes through san diego via wcg.net like my work trace instead of through att.net.

JMI
September 24th, 2008, 14:44
I suspect the issue is with your own ISP. Running ping from my girlfriend's house takes 87ms to get to the server and that's starting from California. It has more to do with an ATT dial-up account then anything else.

You could always try a proxy server from your home.

Regards,

Woodmann
September 24th, 2008, 17:10
Howdy,

I dont know a whole lot about this stuff BUT,

Since we all take a different route to get here,
the only thing that could cause a problem is your
front end provider.

I would think that because my provider is Comcast,
I get better access to the biggest pipes.
Comcast is huge east of the Mississippi.
Hence they have the ability to negotiate the best deals for
service/access.

If you are on a dialup, I am willing to bet you get
treated poorly when network traffic is busy.
You kinda get put on infinite hold.

Perhaps this will explain it better.

Company A owns the biggest internet pipes in North America.
Company B has 40 million customers who want access.
Company C has 2000 dialup accounts.

Whos gets priority treatment?

Woodmann

Aimless
September 25th, 2008, 00:26
Quote:
[Originally Posted by JMI;77146]I suspect the issue is with your own ISP. Running ping from my girlfriend's house takes 87ms to get to the server and that's starting from California. It has more to do with an ATT dial-up account then anything else.

You could always try a proxy server from your home.

Regards,


What's your "GIRLFRIEND" like? 75 yrs? :P

Peace...

Have Phun

JMI
September 25th, 2008, 00:51
Nope! She's a "younger" woman.

Regards,

Woodmann
September 25th, 2008, 16:41
BWHAHAHAHAHAHHAAA........

Grampy has a chickie .

Woodmann