I can't connect
 

I can't connect to www.adventuregamers.com. On the Adventure Developers forum, Squinky suggested that it might have something to do with a server move and that I should try a proxy so I'm writing this through hidemyass.com. Figured you might want to know about it, and if anyone knows of a better solution, feel free to share.

if you ping www.adventuregamers.com (not through the proxy) what ip does it give? The move was quite a while ago, so it shouldn't be a problem for anyone at this point unless you have a tragically out of date DNS server.

PING www.adventuregamers.com (209.62.22.211): 56 data bytes

--- www.adventuregamers.com ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss

That's the right IP address. It seems like packets from you aren't making it to our server for some reason, though. Can you try:

tracert adventuregamers.com

This machine isn't running ipchains or iptables (yet) so I'm pretty confident it's not a firewall issue on our side

This is the result I get from Traceroute:

traceroute to www.adventuregamers.com (209.62.22.211), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 1.028 ms 1.541 ms 0.637 ms
2 hsrp1.geab-045-1.ephone.se (77.53.45.2) 21.578 ms 23.820 ms 26.466 ms
3 host-009.ephone.se (77.53.0.9) 27.353 ms 26.734 ms 27.282 ms
4 212.112.178.81 (212.112.178.81) 29.363 ms 28.794 ms 31.800 ms
5 sesto0001-rc1.ip-only.net (82.99.32.121) 34.482 ms 28.607 ms 27.006 ms
6 netnod-ix-ge-b-sth-1500.cogent.com (194.68.128.155) 26.993 ms 29.696 ms 26.528 ms
7 p2-2.core01.ham01.atlas.cogentco.com (130.117.0.193) 43.538 ms 42.589 ms 54.252 ms
8 p2-0.core01.dus01.atlas.cogentco.com (130.117.1.189) 63.084 ms 54.770 ms 55.466 ms
9 p1-0.core01.lon01.atlas.cogentco.com (130.117.1.225) 61.691 ms 61.972 ms 63.196 ms
10 p3-0.core02.jfk02.atlas.cogentco.com (66.28.4.189) 146.526 ms 134.028 ms 133.964 ms
11 p15-0.core01.jfk02.atlas.cogentco.com (66.28.4.13) 133.011 ms 133.251 ms 135.447 ms
12 p9-0.core01.atl01.atlas.cogentco.com (154.54.5.98) 161.169 ms 150.050 ms 151.473 ms
13 p10-0.core01.iah01.atlas.cogentco.com (154.54.5.89) 181.288 ms 181.495 ms 180.786 ms
14 v3527.na22.b015619-0.iah01.atlas.cogentco.com (66.28.65.106) 181.006 ms 182.269 ms 182.409 ms
15 * * *
16 * * *
17 * * *
18 * * *

...and then it continues with stars until 64, when it stops.

interesting...

[tabacco@dougtabacco ~]# traceroute 77.53.45.2
traceroute to 77.53.45.2 (77.53.45.2), 30 hops max, 38 byte packets
1 ev1s-209-62-22-209.ev1servers.net (209.62.22.209) 0.969 ms 3.576 ms 0.495 ms
2 gphou2-209-85-1-7.ev1servers.net (209.85.1.7) 0.442 ms 0.483 ms 0.438 ms
3 * * *
4 * * *

There's definitely a hop in there that's killing your connection, but I'm not sure why :(

I'll open a ticket with The Planet to see if they can fix it. The outbound traceroute looks like it might be timing out within their network. I also can't traceroute to anywhere else in your class C range :(

Now it works! :)

woo!