dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
31405
share rss forum feed


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
Working fine here.


MacThrasher
Premium
join:2002-04-26
Chagrin Falls, OH
reply to biglair
Working fine in Chagrin Falls, Ohio

aguy1
Premium
join:2002-07-06
Chicago, IL
reply to biglair
I've been having the exact same problem in Chicago. All other domains are fine.


Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL
kudos:5
reply to biglair
can you ping or traceroute to them?

username19613
Premium
join:2007-08-01
North Royalton, OH

1 edit
reply to biglair
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
I start new work on
Premium,VIP
join:2002-05-30
Granite City, IL
kudos:101
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
kudos:5

1 recommendation

reply to biglair
drives me nuts when people pop in like this and never follow up on it


sandiego

@cox.net
reply to biglair
same problem here in san diego. no idea why. i can get to every other site. help please?

aguy1
Premium
join:2002-07-06
Chicago, IL
reply to Dennis
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
kudos:5
ok, whats the first 3 octets of your IP?

aguy1
Premium
join:2002-07-06
Chicago, IL
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.


Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL
kudos:5
reply to biglair
ok, well based off the original poster's domain...he isn't even an AT&T DSL customer. Looks like he's on a dedicated T1 or something.

So...whatever your issue is, it's probably not related to his.
--
My Blog. Because I desperately need the acknowledgement of others.

Mainegirl and my Beer Review's


rolande
Certifiable
Premium,Mod
join:2002-05-24
Dallas, TX
kudos:6
Yup. Dedicated circuit.

6  VIP-Medical-Mutual-Services-LLC-1156500.cust-rtr.ameritech.net (67.37.20.150)
 

aguy1
Premium
join:2002-07-06
Chicago, IL
reply to Dennis
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


Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL
kudos:5
Ok, that's rback2.chcgil.sbcglobal.net...I just logged in and got an IP in the same pool as you.

ip address 68.252.254.228 (applied)

I had no issues surfing to google, google news, or blogspot. i even just logged into my gmail for the heck of it.

Whatever the problem is, it's not AT&T
--
My Blog. Because I desperately need the acknowledgement of others.

Mainegirl and my Beer Review's

aguy1
Premium
join:2002-07-06
Chicago, IL

1 edit
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
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
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:
C:\Documents and Settings\Norman>ipconfig -all
 
Windows IP Configuration
 
        Host Name . . . . . . . . . . . . : KOZUE
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : aosake.net
 
Ethernet adapter Local Area Connection:
 
        Connection-specific DNS Suffix  . : aosake.net
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
        Physical Address. . . . . . . . . : 00-17-31-C6-CC-63
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.102.34
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.102.1
        DHCP Server . . . . . . . . . . . : 192.168.102.1
        DNS Servers . . . . . . . . . . . : 192.168.0.1
        Lease Obtained. . . . . . . . . . : Monday, September 10, 2007 20:53:15
        Lease Expires . . . . . . . . . . : Thursday, September 13, 2007 20:53:15
 
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


Comcast Guy

@comcast.net
reply to biglair
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.

aguy1
Premium
join:2002-07-06
Chicago, IL
reply to biglair
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
kudos:1
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...
 
#
# copyright (c) 1993-1999 microsoft corp.
#
# this is a sample hosts file used by microsoft tcp/ip for windows.
#
# this file contains the mappings of ip addresses to host names. each
# entry should be kept on an individual line. the ip address should
# be placed in the first column followed by the corresponding host name.
# the ip address and the host name should be separated by at least one
# space.
#
# additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# for example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
 
127.0.0.1       localhost
 
 


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
Dallas, TX
kudos:6
Reviews:
·AT&T U-Verse
·ViaTalk
reply to aguy1
So the interesting thing is that the last hop before you timeout is owned by Google.

whois -h whois.arin.net 209.85.250.237
 
OrgName:    Google Inc. 
OrgID:      GOGL
Address:    1600 Amphitheatre Parkway
City:       Mountain View
StateProv:  CA
PostalCode: 94043
Country:    US
 
NetRange:   209.85.128.0 - 209.85.255.255 
CIDR:       209.85.128.0/17 
NetName:    GOOGLE
NetHandle:  NET-209-85-128-0-1
Parent:     NET-209-0-0-0-0
NetType:    Direct Allocation
NameServer: NS1.GOOGLE.COM
NameServer: NS2.GOOGLE.COM
NameServer: NS3.GOOGLE.COM
NameServer: NS4.GOOGLE.COM
Comment:    
RegDate:    2006-01-13
Updated:    2006-06-01
 
OrgTechHandle: ZG39-ARIN
OrgTechName:   Google Inc. 
OrgTechPhone:  +1-650-318-0200
OrgTechEmail:  arin-contact@google.com
 

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
Reviews:
·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
kudos:1
reply to aguy1
downloadtracert.txt 1,550 bytes
I'm going to have to agree with rolande See Profile 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.