You are not logged in.
We have 4 workstations in our office, using WLAN and ADSL. Somehow I am the only one to experience this: after 2-3 days of uptime of my machine all Google sites start to become slow, and soon I'm unable to access anything that belongs to Google (not even YouTube). I can access any other site just fine.
I have to turn off my machine for 10 minutes, log back and Google is accessible again. Restarting the network does not help.
I use DynDNS to be able to ssh back from home, could this be related? Any other ideas why this could happen?
Offline
that's an odd problem... Have you tried using a different browser? (maybe chromium?) or clearing out all of your cookies and crap?
that's probably where I would get started.
Hofstadter's Law:
It always takes longer than you expect, even when you take into account Hofstadter's Law.
Offline
Haha, you must have broke the Patriot Act
.
Actually, don't think that is a Google problem, I'd be willing to be that it has something to do with routing. Have you tried checking the route with traceroute, or another similar program?
Setting Up a Scripting Environment | Proud donor to wikipedia - link
Offline
I've tried several browsers, but even lynx won't work, "host google.com" takes several minutes.
I've rebooted since, I can reach Google for now.
Traceroute is interesting...:
jfk karel ~ > traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 74.125.39.99
traceroute to google.com (74.125.39.99), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
...The strange thing is that I get the same result for any other hostname ![]()
We use wicd on all machines for the wlan btw.
The network is definitely up, ping, host, etc. works fine. Hmm.
Offline
Try to use mtr, I find it is a little "smarter" than traceroute.
Also have you tried to reboot your machine? Just in case it is some bug affecting only your machine. If things work well for everyone else the problem is most probably with your machine.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Do you see SYN flood (to host) messages in the router logs ? It's possible that the router's firewall "sees" the multiple connections of a browser (for example) as multiple attack and finally makes the router halt its services.
Offline
Thanks for the suggestions!
mtr, just like the plain traceroute, times out (100% loss).
I can't see anything interesting in the router logs, but will keep an eye on it.
Offline
Have you configured your firewall ?
iptables or such ? or configured the /etc/sysctl.conf file or something ?
maybe you should use an arch liveCD to try and check if you get the same results or not
If people do not believe that mathematics is simple, it is only because they do not realize how complicated life is.
Simplicity is the ultimate sophistication.
Offline
No, I've never set up a firewall or touched /etc/sysctl.conf.
I've just checked that no computer on our network can use traceroute, they all time out. We have Arch, Ubuntu and Xubuntu workstations, so I start to think it's not my setups fault.
Offline
Try to ping/reach other machines in your network when that happens, try to rule out the problems you can easily sort out locally (software problems, tired router
, whatever) and then after you're sure everything is ok start to look for the problem outside your local network.
Something like, ping router (which should be your gateway), ping other machines in your network, ping your machine from other machines, if all is ok check the ip of the gateway your router is using and ping it, in the same go check the dns servers, anything else farther from there I don't know, if that works then it can be a temporary network problem.
Reading the description of the problem again I thought of something, check your router config and see if you have it configured to have the adsl connection always on or if it is configured to turn off after a certain amount of time without internet activity, I would set it to always on. Also if you can borrow another modem/router then try that too, that modem/router you are using may be getting tired (read starting to show its age/failing).
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Yup, might be a good time to try a new/other modem. Will do that, thx!
Offline