Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL | reply to biglair
Re: Can't access Google domains.
My god....why is this thread still open? |
|
AlphaOne
I see
Premium
join:2004-02-21
| reply to biglair
I haven't read the whole thread yet, but give this a try:
»[Wireless] Can't see Google, this time it's different
»Can't see Google, this time it's different
This is in regards to the use of WPA/AES if browsing google sites. Change it to TKIP, and all is well.
--
Join the DSLR Pub Games |
|
misbehave
join:2003-09-08
Renton, WA | reply to biglair
I have been having the same problem since 2 weeks ago.
I am using Comcast cable in Seattle area. |
|
Paul Gardner
@magma.ca | reply to biglair
Update on my previous post - Uninstalling Microsoft LiveOneCare resolved the problem. |
|
rolande
Certifiable
Premium,Mod
join:2002-05-24
Powell, OH
clubs:
Host:
Linksys
AT&T Midwest
| reply to NormanS
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/ |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| reply to aguy1
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 |
|
Paul Gardner
@magma.ca
| reply to biglair
Re: Can't access Google domains.
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? |
|
aguy1
Premium
join:2002-07-06
Chicago, IL
| reply to David
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?) |
|
David
No,there is another.
Premium,VIP
join:2002-05-30
Granite City, IL
clubs:
 ·DIRECTV
 ·magicjack.com
·AT&T Midwest
| reply to aguy1
Re: [Not an AT&T Issue] Re: Can't access Google domains.
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. That's because everybody is posting over here. the user "davidt76" above posted from an alltel.net ip. I am sure that at&t isn't going to have anything to do with that.
There's cox.net in here, a "sonicnet user" I know they have their own ATM pipes and such. I saw another domain of @rr.com from another poster.
--
If you have a topic in the direct forum please reply to it or a post of mine, I get a notification when you do this.
Koetting Ford, Granite City, illinois... YOU'RE FIRED!!
|
|
aguy1
Premium
join:2002-07-06
Chicago, IL | reply to rolande
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 | reply to Bink63
Re: possible solution (if not explanation)
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
| reply to biglair
[Not an AT&T Issue] Re: Can't access Google domains.
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/ |
|
davidt76
@alltel.net
| reply to Bink63
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. |
|
Bink63
Tweet THIS
Premium
join:2002-10-06
Everywhere
| reply to aguy1
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 |
|
aguy1
Premium
join:2002-07-06
Chicago, IL
| reply to sonicnet user
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.) |
|
sonicnet user
@sonic.net
| reply to biglair
Re: Can't access Google domains.
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 |
|
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! |
|
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 |
|
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. |
|
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!!! |
|
