GAH
HA!!I found what caused this issue. Fucking MSN Messenger. It's been overloaded with so much junk. Back to gaim, I guess!
MSN has this "troubleshooting" tool which automatically launches when it can't figure out how to connect; oddly enough, windows messneger/gaim had no problems connecting!
I was looking more closely at it and it had a list of things it was checking up on, including "DNS", "Connection" and "
Hosts File". Once I saw that (this was after having fixed this problem already through the re-installation of TCP/IP on windows), I wondered if it was causing my problem.
Sure enough:
C:\>ping www.sidoh.org
Pinging sidoh.org [66.28.80.30] with 32 bytes of data:
Reply from 66.28.80.30: bytes=32 time<1ms TTL=64
Reply from 66.28.80.30: bytes=32 time<1ms TTL=64
Reply from 66.28.80.30: bytes=32 time<1ms TTL=64
Reply from 66.28.80.30: bytes=32 time<1ms TTL=64
Ping statistics for 66.28.80.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
127.0.0.1 localhost
10.0.0.15 sidoh.org
10.0.0.15 www.sidoh.org
10.0.0.15 sidoh.no-ip.org
Lession learned: Don't use MSN Messenger.