After a while, I'm unable to connect to google.

[LaKing]

I'm experiencing the following phenomenon.

Fedora-like Linux computers are affected, but other systems are not.

After a while, I can not connect to google and anything that is google related.

For instance, after 2 hours of system uptime, I still can connect to facebook and yahoo, but not to youtube or google. I can connect to fedoraforum, but can't search on it. ...

I can ping google servers, they all respond. I can dig them too.
But whatever I use, Firefox, chrome, or even wget, they all just hang.
After a time the connection times out. ...

If I start two PC's they seem to start to be bugged at the same time.
If I then reboot one of them, then it can to connect to google again.
The other one can connect after a reboot too, so only a reboot is fix.
Restarting the browser, the network, the router, .. doesn't fix it. Only a reboot.

I have a TP-Link router with the latest firmware.
Fedora 16, Fedora 15, CentOs 6, ... updated or not, all the same,
.. static IP, DHCP, doesn't matter all the same.

Any suggestions how to debug this, to find the source of this malfunction is greatly appreciated.

Thank you.

[DBelton]

That is Fedora doing you a favor by weaning you off of the GooglePlex

That is strange that it only affects google related sites and that you can still ping them. If it was a DNS issue, it would prevent you from being able to ping them as well. (or were you pinging them using the actual IP address instead of the URL?)

Just a thought.. Are you using a proxy?

[drewkenjo]

Just a thought: try http://173.194.34.16/. It's one of the google's ip. I think in case if browser has some issue with dns only it should work.

[RHamel]

I wonder if this story has anything to do with your problem.

[LaKing]

Thank you for your answers.

I'm not using a proxy. (But thought on using it to solve the problem)

It does not seem to be a DNS issue. When I run wget, it show's clearly that it connects to an ip at port 80, and hangs.

Also, dig gives the following IP's.

74.125.232.240
74.125.232.241
74.125.232.242
74.125.232.243
74.125.232.244

[RobertLaverick]

try "wget -4 http://www.google.com" or the same address that's not working and see if that makes a difference?

[David Batson]

Possibly NetworkMangler is the culprit. Often stops working after 2 or 3 hours of uptime. There are other network managers that are more reliable.

[LaKing]

I have Network Manager off, and use static IP's on the lan.

.. I had now a system up for 3 days, and google is still online. That means it's not the uptime, more a certain amount of traffic that's triggering the bug ....

[JEO]

Are you doing something that might make Google stop service, such as blocking their advertising or blocking cookies? Even just not installing flashplayer plugin might prevent their ads from running.

[LaKing]

wget -4 ... the same as without the -4.

Typing the google IP into the URL does not help either.

Nothing is blocked, flashplayer is installed.

It just hangs .... no go ogle

[JEO]

The only suggestion I have is to try running wireshark-gnome to inspect the packets going to and from google while the problem is happening to try to see what is going on.

[LaKing]

I left my secondary workstation one day online, while it was bugged. .. After several hours, it is accessing google atm. ..

... I will try wireshark next time. .)