Wolfbane Posted January 1, 2012 Share Posted January 1, 2012 Occasionally (this has been happening off and on for days now) I get error 324 on google.com (and any search page) using any browser. (Screenshot if it's needed for any reason: http://ScrnSht.com/xeonwc) This lasts for a few minutes, during which I can access all other websites perfectly. After a few minutes, Google works perfectly again. Does anyone have any idea why this would happen? Link to comment Share on other sites More sharing options...
articuno1au Posted January 1, 2012 Share Posted January 1, 2012 Are you using a dev build of Chrome? I've been encountering this from time to time on Dev builds >.< Link to comment Share on other sites More sharing options...
Xahid Posted January 1, 2012 Share Posted January 1, 2012 maybe DNS issue in your ISP ? Link to comment Share on other sites More sharing options...
Wolfbane Posted January 1, 2012 Author Share Posted January 1, 2012 Are you using a dev build of Chrome? I've been encountering this from time to time on Dev builds >.< I'm using v16, and this happens on the Firefox Nightly and IE 9 as well. maybe DNS issue in your ISP ? Maybe, that would be another thing to add to the list of reasons to hate Telecom NZ.It doesn't seem very likely though, because it only seems to happen with Google, and it happens for only a few minutes every so often for the last few days (or maybe weeks now). Link to comment Share on other sites More sharing options...
Slugsie Posted January 1, 2012 Share Posted January 1, 2012 While it's working grab the IP address for google.com (use PING GOOGLE.COM from a command prompt) and note the IP address - I get currently 173.194.67.103 but that is likely to change depending on which server you happen to hit. Then when it's next not working try using that IP address in your browser, and pinging both the IP address and google.com. That should help with diagnosing the problem. I'd say that the chances are that when you get the problem Googles internal load balancing is sending you to a server that has a problem that hasn't been spotted for some reason. Chances are that there is nothing you can do about it. Link to comment Share on other sites More sharing options...
Wolfbane Posted January 1, 2012 Author Share Posted January 1, 2012 While it's working grab the IP address for google.com (use PING GOOGLE.COM from a command prompt) and note the IP address - I get currently 173.194.67.103 but that is likely to change depending on which server you happen to hit. Then when it's next not working try using that IP address in your browser, and pinging both the IP address and google.com. That should help with diagnosing the problem. I'd say that the chances are that when you get the problem Googles internal load balancing is sending you to a server that has a problem that hasn't been spotted for some reason. Chances are that there is nothing you can do about it. Thanks, I made a note of the current IP and I'll see if it works next time I can't connect.I did try pinging google.com earlier when it wasn't working, it pinged successfully but I didn't record the IP. Link to comment Share on other sites More sharing options...
The_Decryptor Veteran Posted January 3, 2012 Veteran Share Posted January 3, 2012 The IP address can and will change, so that's not really important when it works, it's important when it isn't working though (Why record everything that works, when you could just record everything that doesn't?) Also, try using nslookup and tracert when it stops working (so nslookup www.google.com and tracert www.google.com), they'll show what the DNS server is returning, and the path the data is taking to Google's servers. Link to comment Share on other sites More sharing options...
Recommended Posts