by Arlos » Wed Apr 13, 2005 10:06 pm
We were having issues with comcast too til I figured out what was going wrong and fixed a work-around from our end. What was happening to us was that Comcast was passing out bad DNS server information, which meant you could get anywhere you wanted if you used the IP address directly, but you couldn't get anywhere if you tried to go by name. Obviously the servers they were pointing people to are fucked.
For various reasons, I'd had cause to record the DNS server information we had gotten from Comcast in the past, and had set my PC up as a static IP behind our router, mainly so I could forward ports for BT to my machine, cause of WOW downloads. Anyway, one day recently, both housemates' DNS breaks. So, after research, I go look at the DNS information our router had gotten from Comcast and was passing on to us, and neither address in its table matched the old DNS information. So, went to both housemate's computers, set DNS to manual for the first 2 server addresses, and that fixed it, and simultaneously made us immune to further cases of the same issue.
If you don't mind some potential name lookup lag (no clue where these servers are geographically located), you could try the same work-around. The servers I know work are: 204.127.199.8 and 63.240.76.198. Just go into your TCP/IP properties and put those in there, and see if you suddenly start working again.
-Arlos