biglair
@antaressolutions.com | Can't access Google domains. Im in the cleveland area and I cannot access any google domains. (mail.googele.com, reader.google.com. www.google.com, blogspt.com, etc)
I can get to any other site, it's only google i can't access. Is anyone else having this problem? | |
|
 
Jon
Premium
join:2001-01-20
Lisle, IL | Re: Can't access Google domains. Working fine here. | |
|
|
aguy1
Premium
join:2002-07-06
Chicago, IL | I've been having the exact same problem in Chicago. All other domains are fine. | |
|
Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL | can you ping or traceroute to them? | |
|
 | aguy1
Premium
join:2002-07-06
Chicago, IL | Re: Can't access Google domains. Can't ping or traceroute to them. I've tried flushing the DNS cache to no avail. | |
|
| |
Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL | Re: Can't access Google domains. ok, whats the first 3 octets of your IP? | |
|
| | | aguy1
Premium
join:2002-07-06
Chicago, IL | Re: Can't access Google domains. Not at home now (working at a t-mobile hotspot -- in part so I could check my gmail) but will get back to you later today. | |
|
| | | aguy1
Premium
join:2002-07-06
Chicago, IL
| Thanks for your help. Problem has persisted now for at least five days.
IP address = 68.252.246.xxx
Don't know if results from nslookup google.com are useful, but, if so, here they are.
Server: dnsr1.sbcglobal.net
Address: 68.94.156.1
Name: google.com
Addresses: 72.14.207.99, 64.233.187.99, 64.233.167.99 | |
|
| | | | |
| | | | | aguy1
Premium
join:2002-07-06
Chicago, IL
1 edit | Re: Can't access Google domains. You are right. I just tried a friend's laptop. Connecting through the same wireless router, the friend's laptop can connect to (and ping) google. My laptop, as well as my wife's, cannot.
I can't find any differences in the settings. If the problem were limited to web access, I would suspect a setting in the browser, but the fact that ping works on one computer but not the other has me mystified.
Any ideas?
**Edited with One additional data point**
ipconfig /all on my wife's machine and mine both have a "host name" and "primary dns suffix" that seem to be set through work.
Friend's computer does not.
Could this be the problem? | |
|
| | | | | | NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| Re: Can't access Google domains.said by aguy1  :ipconfig /all on my wife's machine and mine both have a "host name" and "primary dns suffix" that seem to be set through work. Friend's computer does not. Could this be the problem? Could be. I don't think that I have ever seen a "Primary Dns Suffix" field populated for home users. I believe it has something to do with running a local DNS server on a LAN. The "Primary Dns Suffix" could also be related VPN, I expect...
Mine looks like this:
AFAIK, there will always be a "Host Name"; equal to whatever you named the computer when you set up the LAN (NetBIOS name).
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
|
username1961
Premium
join:2007-08-01
North Royalton, OH
1 edit | I am in Cleveland and I have no issues with google domains. I should mention that I use my own DNS servers not AT&T. Maybe the problem is with the DNS servers. I am also with the static IP plan | |
|
| 
David
No,there is another.
Premium,VIP
join:2002-05-30
Granite City, IL
clubs: | Re: Can't access Google domains. Well I just checked my google account and got there just fine with these domains
Connection Type
PPPoE
DNS 1
151.164.8.201
DNS 2
66.73.20.40 | |
|
Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL | drives me nuts when people pop in like this and never follow up on it  | |
|
sandiego
@cox.net | same problem here in san diego. no idea why. i can get to every other site. help please? | |
|
|
| 
rolande
Certifiable
Premium,Mod
join:2002-05-24
Powell, OH
clubs: | Re: Can't access Google domains.Yup. Dedicated circuit.
| |
|
Comcast Guy
@comcast.net
| Last night I had an issue where I could not access google.com for about 15 minutes then it worked. During that time, I could access gmail.com
Tonight I cannot access either normally.
However, and here's the weird part, I can ping google.com and get replies. So I can visit google.com with that IP.
I can only access gmail via httpS://gmail.com
THis is on 3 computers on my little home network. | |
|
|
sna
@comcast.net | Re: Can't access Google domains. i am having the same problem right now. i can't access google's homepage. i can access news.google.com or the other google sites but not www.google.com. i can also connect to google if I go through my work VPN first. | |
|
| |
Atul
@nationalcity.com
| Re: Can't access Google domains. I have similar problem from my wireless router. I am using Netgear and can access google domain if I use cable to connect to router but not using wireless connection. First I also believed that google is blocking my IP set but since I can use it from the same router, it is something else happening. I was also able to tracert till google network  | |
|
aguy1
Premium
join:2002-07-06
Chicago, IL
| I've done some additional testing. I can ping and tracert google through the router's ping test (on the linksys router pages). But not, as previously reported, from my laptop or my wife's. This has been going on for almost a week now and is very frustrating. | |
|
| psx_defector
join:2001-06-09
Allen, TX
| Re: Can't access Google domains. Post your complete trace.
You probably have some host file redirect or some other stupid thing going on. Obviously, Google ain't down, others are able to get to it via AT&T, down to the same router, and you can hit it via the Linksys trace utility. | |
|
| | aguy1
Premium
join:2002-07-06
Chicago, IL
1 edit | Re: Can't access Google domains. See above for trace. Thanks for your help. | |
|
| | | psx_defector
join:2001-06-09
Allen, TX
| Re: Can't access Google domains. I'm going to have to agree with rolande about something on the Google side blocking you.
Both my pipes route directly to the IP you posted, without issue. Of course, I'm not on the Chicago PoP, so it COULD be a problem there.
Try using an open proxy, just to make sure of that. »www.xroxy.com/proxy1196.htm
If you hit the website with the proxy turned on, then we know Google is blocking the IP block. If you can't hit it with the proxy, then it's something on your PC. | |
|
Jon
Premium
join:2001-01-20
Lisle, IL | Maybe I missed it but... Have you checked your host file yet? | |
|
| aguy1
Premium
join:2002-07-06
Chicago, IL | Re: Can't access Google domains. I'm afraid that no one will want to help once I ask this question, but what is a host file and where do I find it? | |
|
| |
Jon
Premium
join:2001-01-20
Lisle, IL
3 edits | Re: Can't access Google domains.C:\WINDOWS\system32\drivers\etc\hosts
Open it with notepad.
There may be more or less in there but you should see something like...
| |
|
| | |
p0o0o0h
@dell.com | Re: Can't access Google domains. I am located in Austin, TX accessing internet via AT&T DSL and no luck with google.com either.. | |
|
| | | aguy1
Premium
join:2002-07-06
Chicago, IL
1 edit | Host file is normal.
Now that I understand Domain Name Resolution better, I also checked the registry to make sure that priorities (DNS v. host etc.) are default. They are,
Tracert looks like this:
Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:
1 * * * Request timed out.
2 2 ms 1 ms 1 ms 192.168.0.1
3 8 ms 8 ms 8 ms adsl-68-252-255-254.dsl.chcgil.ameritech.net [68
.252.255.254]
4 * * * Request timed out.
5 9 ms 8 ms 8 ms bb1-g7-0.chcgil.ameritech.net [151.164.242.208]
6 9 ms 9 ms 8 ms ex1-p2-0.eqchil.sbcglobal.net [151.164.42.149]
7 * * * Request timed out.
8 58 ms 9 ms 12 ms 209.85.250.237
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
... (12-30 are identical to 10 and 11). | |
|
| | | |
rolande
Certifiable
Premium,Mod
join:2002-05-24
Powell, OH
clubs:
Host:
Linksys
AT&T Midwest
| Re: Can't access Google domains.So the interesting thing is that the last hop before you timeout is owned by Google.
When I traceroute to the same destination IP [72.14.207.99] I can get a few hops further into Google's network before I get timed out. That is perfectly normal to get timed out at the edge of the destination network by a firewall that doesn't permit those types of ICMP packets through.
In your case, you are not getting as far, before timing out. That would indicate that the IP address you are getting assigned from at&t is either being filtered by Google or they are blackholing return traffic to it for some reason.
The fact that we see more than one person complain about this same issue with Google on various parts of the DSL network leads me to believe that Google is doing some sort of auto blackholing of source IPs. In other words, the user who had the IP address before you was possibly part of a BotNet or a zombie and was proliferating bad crap at Google so they shut it down at the edge of their own transit access network. It would not surprise me at all.
Try to release your PPPoE session and get a new IP address and see if the problem goes away.
--
Ignorance is temporary...stupidity lasts forever!
»www.thewaystation.com/
»blog.thewaystation.com/ | |
|
| | | | | 
StillLearn
Premium
join:2002-03-21
Streamwood, IL
·AT&T Midwest
| Re: Can't access Google domains. said by rolande :The fact that we see more than one person complain about this same issue with Google on various parts of the DSL network leads me to believe that Google is doing some sort of auto blackholing of source IPs. In other words, the user who had the IP address before you was possibly part of a BotNet or a zombie and was proliferating bad crap at Google so they shut it down at the edge of their own transit access network. It would not surprise me at all. Try to release your PPPoE session and get a new IP address and see if the problem goes away. »www.theinquirer.net/default.aspx···le=40371 from June discusses the possibility.
If the problem occurs with a different IP, the person with the problem might look into getting his computer scanned for worms. It is possible that some worm has disabled google access for some reason. It is possible that Google is smart enough to block some computers early. | |
|
sonicnet user
@sonic.net
| I'm locked out of google.com too! I'm on sonic.net (which uses ATT DSL) in SF Bay area.
C:\Documents and Settings\Administrator>tracert www.google.com
Tracing route to www.l.google.com [74.125.19.99]
over a maximum of 30 hops:
1 * * * Request timed out.
2 10 ms 10 ms 10 ms 64-142-101-1.dsl.static.sonic.net [64.142.101.1]
3 17 ms 14 ms 12 ms 109.at-4-0-0.gw3.200p-sf.sonic.net [208.106.28.1
17]
4 15 ms 15 ms 15 ms 200.ge-1-2-0.gw2.equinix-sj.sonic.net [64.142.0.
210]
5 14 ms 14 ms 12 ms eqixsj-google-gige.google.com [206.223.116.21]
6 14 ms 13 ms 17 ms 209.85.252.2
7 * * * Request timed out.
8 * * * Request timed out.
Google must be blocking us!!! | |
|
| NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| Re: Can't access Google domains.said by sonicnet user :
I'm locked out of google.com too! I'm on sonic.net (which uses ATT DSL) in SF Bay area.
Your trace route does not show AT&T DSL transport. All AT&T DSL is on an AT&T ATM transport from the DSLAM to the aggregation router, which would show up as the first hop in a trace route from your DSL modem. Your first hop IP address tells me that your aggregation router belongs to Sonic, not AT&T. So your transport from the DSLAM to the Internet is provided by Sonic, not by AT&T.
You can see, in my trace route, where the AT&T aggregation router is. My first two hops are on premises (a Netgear FVS114 router followed by a SpeedStream 4100 DSL modem), but my third hop is an AT&T aggregation router:
Google must be blocking us!!!
They could be blocking Sonic, or a particular Sonic IP address. They could be blocking a particular AT&T IP address. But Google is definitely not blocking my AT&T IP address.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
|
anon1
@sonic.net
| Same problem here on sonic.net. I traceroute all the way up to the google domain and then time out... Anyone else?
It appears that if I had a computer that was already logged in before (save my password), that I can still access the google domain!
Weird. | |
|
googleuser
@rr.com
| I was having the same exact problem here in Frisco, TX (suberb of Dallas).
Cannot access google.com domains for 3+ weeks.
I read this post and learned that I could ping google.com and get to the site by IP, just not the google domain name.
I reset my home lynksys network router, now everything is fine. I currently use a Time Warner cable modem connected to a Linksys broadband wireless-b router.
Hope this helps. This has been a frustrating issue for me too! | |
|
sonicnet user
@sonic.net
| Summary.
1. Unable to access any google.com domain via Wireless connection.
2. Able to access google.com domain fine over Ethernet.
3. Able to access google.com domain from computers already logged in previously. For instance, if the computer was logged into gmail.com and "remember me" was checked, then that computer could still access gmail/google wirelelessly. (cookie?).
4. Zoom X6 Wireless ADSL modem with firmware 2.1.5.
5. WPA security.
Seems like others are having issues too!
»discussions.apple.com/thread.jsp···#5367320 | |
|
| aguy1
Premium
join:2002-07-06
Chicago, IL
| possible solution (if not explanation) It occurred to me that this problem started after I changed the encryption method on my wireless router to accommodate our babysitter's laptop (which did not, as I recall, support TKIP).
I therefore removed all encryption from the network and, presto, no more problems reaching google.
I haven't had time to really test this with and without different kinds of encryption to see if I can replicate both the problem and the solution, but those of you who are having this problem should give this a try. (A brief scan of the posts above suggests that everyone with this problem may be using a wireless router.) | |
|
| | 
Bink63
Tweet THIS
Premium
join:2002-10-06
Everywhere
| Re: possible solution (if not explanation) said by aguy1 :It occurred to me that this problem started after I changed the encryption method on my wireless router to accommodate our babysitter's laptop (which did not, as I recall, support TKIP). I therefore removed all encryption from the network and, presto, no more problems reaching google. I haven't had time to really test this with and without different kinds of encryption to see if I can replicate both the problem and the solution, but those of you who are having this problem should give this a try. (A brief scan of the posts above suggests that everyone with this problem may be using a wireless router.) I'm using a Linksys WRT-54G v.2 with Sveasoft Talisman Basic 1.1 and WPA (PSK) TKIP set for the wireless encryption. No problems hitting any of the Google sites from my laptop wirelessly from my DSL connection.
I'm thinking your DNS settings might be the culprit.
Regards,
Randy | |
|
| | |
davidt76
@alltel.net
| Re: possible solution (if not explanation) Similarfor me in NE Ohio, but affects just one machine of my 4 wired and unwired, and only www.google.com. I can ping the IP but not name. Using Lynksis WRT-54G version 6.
I upgraded firmware, switched to opendns, no joy. Works fine over dialup. Drives me nuts..
Just started less than a week ago. | |
|
| | | aguy1
Premium
join:2002-07-06
Chicago, IL | DNS is fine, see the above thread. I too had no problem when using tkip. It was when I set the router to TKIP+AES (some sort of hybrid mode for compatibility with older network adapters) that the problem began. | |
|
rolande
Certifiable
Premium,Mod
join:2002-05-24
Powell, OH
clubs:
Host:
Linksys
AT&T Midwest
| To be fair, I want to point out that this is NOT an AT&T issue. This is a problem for all Google users that are customers of ISP's with dynamic IP addresses.
If the original poster is not opposed, it might be better served moving this thread to an alternate forum where it can be discussed irrespective of the customer's ISP to address the larger issue of Google doing this kind of filtering.
--
Ignorance is temporary...stupidity lasts forever!
»www.thewaystation.com/
»blog.thewaystation.com/ | |
|
| aguy1
Premium
join:2002-07-06
Chicago, IL | Re: [Not an AT&T Issue] Re: Can't access Google domains. I'm not convinced we know what the issue is yet. Although Google is clearly doing something that causes the problem, I'm not seeing threads like this for ISP's other than AT&T. | |
|
| | |
| | | aguy1
Premium
join:2002-07-06
Chicago, IL
| Re: [TKIP v AES encryption] Re: Can't access Google domains. For what it's worth, I've confirmed the following:
Router (Linksys WRT54GX) set to TKIP encryption -- no problem.
Roter set to AES encryption -- google domains time out.
I'd have to agree that this certainly doesn't seem like an AT&T issue, although I have no idea why the mode of wireless encryption would result in google rejecting certain packets. (Could there be some interaction between the mode of encryption and NAT?) | |
|
| | NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| said by aguy1 :I'm not convinced we know what the issue is yet. Although Google is clearly doing something that causes the problem, I'm not seeing threads like this for ISP's other than AT&T. Check this thread:
»Can't access google.com?
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
|
| | |
rolande
Certifiable
Premium,Mod
join:2002-05-24
Powell, OH
clubs:
Host:
Linksys
AT&T Midwest
| Re: [Not an AT&T Issue] Re: Can't access Google domains. Like I said in my previous post... This is issue is non-discriminatory and is occurring across all ISPs with all different kinds of users and hardware. Again, this issue is not specific to AT&T or any single ISP.
Additionally, I believe there is a second issue at play that we are seeing crop up here related to Wireless vs. Wired clients on the same home network seeing different results with Google sites. I don't believe I have seen a clear explanation yet for this issue.
However, the completely blocked access issue has been well documented and posted about all over the place.
--
Ignorance is temporary...stupidity lasts forever!
»www.thewaystation.com/
»blog.thewaystation.com/ | |
|
Paul Gardner
@magma.ca
| I'm located in Ottawa, Ontario using a local ISP (magma.ca) and having pretty much exactly the same problem. I can't access any google domains whatsoever (eg. home page, mail, news etc.) and any sites with links to the google domain hang when attempting to access them (eg. google syndicated sites, google-analytics etc.). Sites with no link to google load without problem. I haven't found a non-google related site that doesn't load correctly.
This all started on or around September 14th for me. I'm using a wired connection only (BESFR41 v4.1 router using the latest firmware) on a DSL line with no encryption. Using my laptop connected to this same router, I can access all of these sites, so it doesn't appear to be the router. Both the laptop and the infected machine are coming from the same IP address as far as Google is concerned (dynamic IP assigned by my ISP). So if Google is rejecting the traffic, they're doing it based on my Ethernet MAC address?
The infected machine doesn't appear to have a virus as far as I can tell. I've been running Windows Live OneCare for a couple of months, it's coming up clean and I haven't had any other problems. Running Ad-aware and spybot also turned up nothing. Checking the hosts file, resetting WinSock, flushing the browser cache, dns, etc. also all turned up nothing.
While I can ping all of these sites, I can't bring them up in the browser (firefox or explorer) or perform a trace route to any of them. The packets aren't even making it part way into the network:
C:\Documents and Settings\Owner>tracert www.google.ca
Tracing route to www.l.google.com [72.14.205.99]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 17 ms 15 ms 17 ms qb-in-f99.google.com [72.14.205.99]
A tracert from the laptop works without problem. Here's the trace:
C:\Documents and Settings\Owner>tracert www.google.com
Tracing route to www.l.google.com [72.14.205.104]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 10 ms 9 ms 9 ms ottawa-hs-209-217-123-1.d-ip.magma.ca [209.217.
23.1]
3 9 ms 9 ms 9 ms 64.26.173.98
4 10 ms 9 ms 9 ms 206.191.0.98
5 11 ms 9 ms 9 ms border5-faste2-0.magma.ca [209.217.64.58]
6 141 ms 201 ms 129 ms 207.219.123.121
7 16 ms 17 ms 15 ms OTWAONPLBR00.bb.telus.com [154.11.6.227]
8 18 ms 15 ms 15 ms toroonnlbr00.bb.telus.com [204.225.243.161]
9 18 ms 15 ms 15 ms toroonxnbr00.bb.telus.com [204.225.243.142]
10 15 ms 15 ms 15 ms toroonxngr00.bb.telus.com [154.11.11.54]
11 18 ms 15 ms 15 ms 154.11.2.154
12 15 ms 15 ms 15 ms 66.249.94.90
13 28 ms 15 ms 25 ms 72.14.232.66
14 18 ms 17 ms 17 ms qb-in-f104.google.com [72.14.205.104]
Trace complete.
Looking at the network traffic on the infected machine in ethereal (packet sniffer), the replies coming back are all TTL exceeded (timed out). When attempting to load www.google.ca (or any other google domain site), I'm getting what looks like a broken network connection (see attached trace) - but it works flawlessly for all non-google sites from the infected machine, and for all sites (ie. including googles) from the laptop.
What's the common thread here? Am I being filtered and if so, anyone know how to find out? | |
|
Paul Gardner
@magma.ca | Update on my previous post - Uninstalling Microsoft LiveOneCare resolved the problem. | |
|
misbehave
join:2003-09-08
Renton, WA | I have been having the same problem since 2 weeks ago.
I am using Comcast cable in Seattle area. | |
|
|
|
|
|
·
·