psx_defector
join:2001-06-09
Allen, TX
| reply to aguy1
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. |
|
Jon
Premium
join:2001-01-20
Lisle, IL | reply to biglair
Maybe I missed it but... Have you checked your host file yet? |
|
aguy1
Premium
join:2002-07-06
Chicago, IL | 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 | 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 | 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 | reply to Jon
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). |
|
aguy1
Premium
join:2002-07-06
Chicago, IL
1 edit | reply to psx_defector
See above for trace. Thanks for your help. |
|
rolande
Certifiable
Premium,Mod
join:2002-05-24
Powell, OH
clubs:
Host:
Linksys
AT&T Midwest
| reply to aguy1
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
| 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. |
|
psx_defector
join:2001-06-09
Allen, TX
| reply to aguy1
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. |
|
sna
@comcast.net | reply to Comcast Guy
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
| 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  |
|
sonicnet user
@sonic.net
| reply to biglair
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!!! |
|
anon1
@sonic.net
| reply to biglair
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. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to sonicnet user
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 |
|
googleuser
@rr.com
| reply to biglair
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
| reply to biglair
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
| 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
| 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. |
|
