I posted this at another forum two days ago and have yet to get any replies, so I figured I may as well post it here, too. (Hi!)

Well, I just installed Debian (twice, as I had this problem the first time and thought I might have broken it after the installation), the newest AMD64 release, and no web pages or apt repositories will load except Google (including searches, videos, etc.), one other site I can't tell you about because it's a private chat server on the same internet company as me, and these random sites: ramblestrip.com, blogger.com (apparently hosted by Google), and blogsource.com. traceroute works for the sites that work, but it shows asterisks (timeouts) in some rows when trying to get to the sites that don't work. I tried using Epiphany, lynx, and Iceweasel with the same results. Anyway, all pages load fine on every Windows computer on the network--including the one I installed Linux on. Pinging works for all sites. Removing IPv6 things via Network Manager doesn't help. Typing in MySpace's IP address makes it attempt to redirect to "http://www.myspace.com", which, of course, won't load. Pages that do load do so quickly and correctly, and they're obviously not cached.

That's bizarre. Maybe this is an example of "Treacherous Computing" at work? (hahaha)

Can you visit the site in another OS? Maybe you can try to run a Linux live CD for Fedora or something that isn't derived from Debian and see if it loads in it.

If it doesn't work, then either the new Debian distro you're using is rejecting some sort of security thing in their server, or maybe Google really is going to blacklist Linux-based machines (but not theirs, of course).

I'm a newbie, though... so my advice is useless. XD

Sounds like an iptables or /etc/resolv.conf issue. Any changes made right before the problems began?

You wrote something strange there--"maybe Google really is going to blacklist Linux-based machines..." Google is one of the few sites that did work on it. Also, I did successfully get to other websites via Windows XP which is installed on that same computer. My Damn Small Linux LiveCD won't boot on it (it simply shows two of Tux after being told to boot).

Matir, this was a fresh install. No changes were made before my problem began to occur. I'll have a copy of /etc/resolv.conf (which I screwed with a while ago) posted momentarily.

(Yes, 192.168.0.1 is the router. No, there's no proxy. I can't think of any other obvious questions.)

Oh, and here's some extra info that probably won't help.

Just a long shot, try:
iptables -t mangle -A POSTROUTING -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 1400

A winnar is you!
...I mean, uh... That worked. Thanks a bunch.

(And yeah, my friend told me that I have to set up iptables to use that option upon boot, and I think I handled that correctly.)

I think I have a similar problem (explained here in full). However it's Google that doesn't work and most other sites that do work. The strange thing is that this behaviour only happens on a static IP address, with dhclient there's no problem. It could be to do with the company network my computer's on, though like the poster here, all the other Windows computers don't suffer this problem. At first I suspected it was a DNS problem, but the "host" command seems to return IP addresses instantaneously for Google, but another clue is that the very first part of the page loads, the title and the links to Google Images and so on, but no results. I also get this behaviour quite obviously with Facebook.

So what does iptables do? I tried the above iptables command but to no avail. How can I tell if this is an iptable issue here?