Problems with google..

Either your DNS settings have been lost in your router. I would try another computer, but the same connection to isolate the issue.

I have seen an extremely dodgy & very poor quality service ISP in Australia (Dodo) with it's DNS unable to connect to google. Dodo refused to admit the problem was on their end, yet when we borrowed Telstra's DNS server while still on the phone, it worked perfectly. Changed back & forth and still they refused to accept it.

Anyhow, I would perhaps try another computer first, then have a look for an alternate DNS if other websites ARE working for you.

To flush the DNS cache in Mac OS X terminal copy&paste:

dscacheutil -flushcache

Do this in your Terminal.app:

$cd /private/etc

$sudo nano hosts

Delete all of the lines like this (there may be lots of them...I had about 6 lines):

91.224.160.26 google.com

91.224.160.26 google.ae

91.224.160.26 google.as

Then control-x to exit and save.

I also did dscacheutil -flushcache (not sure if it was needed)...

Apparently, you got snagged by a trojan. It looks like an adobe flash installer, but it changed your hosts file so that your google page was redirected someplace else.

Hope this works.

System Preferences/Network- Unlock padlock. Highlight Airport. Network Name-select your name. Click on the Advanced button. Airport/Preferred Networks-delete all that is not your network.

Place a check mark next to "Remember networks this computer has joined." Click the OK button and lock the padlock. Restart your computer.

http://support.apple.com/kb/TS1920 Mac OS: How to release and renew a DHCP lease

Mac OS X 10.6 Help: Solving problems with connecting to the Internet

Solutions for connecting to the Internet, setting up a small network, and troubleshooting

nanettefrombradenton wrote:

hmm that didn't fix the problem. There were no lines like that to delete.

this is so frusterating!

I take it you are only having issues with Google's site? All the others work OK?

What did you find in your hosts file? If there were more than nine or ten lines or you see any reference to Google, paste the show us the entire contents.

nanettefrombradenton wrote:

There is nothing in the host file.

Nothing? There should be at least this:

• ##
• # Host Database
• #
• # localhost is used to configure the loopback interface
• # when the system is booting. Do not change this entry.
• ##
• 127.0.0.1 localhost
• 255.255.255.255 broadcasthost
• ::1 localhost

and possibly one more line. Not having that should not cause the issue you are having, but it might cause other issues down the road.

What you are seeing is exactly what users infected by the QHost.WD Trojan described here http://www.f-secure.com/v-descs/trojan_bash_qhost_wb.shtml are now seeing. As the article describes, those people were tricked into downloading and installing a FlashPlayer update toward the end of July which directed all their Google requests to a fake Google site. Did you do anything like that? That site was only up for about a day and then went blank. About a week ago, the page you saw showed up which simply means the server is ready to host a web site, but nothing is there yet. What I don't understand is how this could be happening to you without your hosts file having been corrupted.

To verify that this is the same rougue page, Launch the Network Utility application and select the Ping tab. Enter "www.google.com" (without the quotes) in the address field and press return. Results?

Please launch the Network Utility application and select the Ping tab. Enter "google.com" (without the quotes) in the address field and press return. Post the output. Then do the same in the Lookup tab.

You did install the trojan and you do have a hacked hosts file.

By far the easiest way to fix the hosts file is to restore it from a Time Machine (or other) backup that predates the installation of the trojan. If that's not possible, then do the following.

Select "Go to Folder..." from the Finder menu bar. In the text box, enter "/etc" (without the quotes.) A Finder window will open on the "etc" folder.

Double-click the file named "hosts" in that folder. It should open in TextEdit. At the top of the file, you should see something like this:

##

# Host Database

#

# localhost is used to configure the loopback interface

# when the system is booting. Do not change this entry.

##

127.0.0.1 localhost

255.255.255.255 broadcasthost

::1 localhost

fe80::1%lo0 localhost

Below that, you'll see some other lines. Delete everything below the last line shown above. Don't try to save; you won't be able to. Instead, select "Save As..." from the file menu in TextEdit. In the Save dialog, deselect the option to add a ".txt" extension to the file name, if it's selected. Save the file to your Desktop. You should now have a file named exactly "hosts" with no extension on your Desktop, having the contents shown above.

Now comes the part that usually scares people. Launch the Terminal application, copy or drag -- do not type -- the line of text below into the window, and press return:

sudo sh -c ' cat Desktop/hosts > /etc/hosts '

You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. Don't panic when you see that warning. Quit Terminal.

Do not type anything into the Terminal window except your password.

That will fix your hosts file. None of us here is able to verify personally that merely fixing the hosts file gets rid of the trojan and its effects. You'll be taking the word of the F-Secure organization for that.

nanettefrombradenton wrote:

This came up when i submitted the ping:

Ping has started…

PING google.com (91.224.160.26): 56 data bytes

64 bytes from 91.224.160.26: icmp_seq=0 ttl=54 time=127.905 ms

I concur with Linc, the IP listed is exactly that of the Trojan site. Not sure why you aren't seeing that in your hosts file, but please have another look, following his instructions.

Do you recall having updated Flash toward the end of July?

I have exactly this same problem. I checked my hosts file, which reads:

##

# Host Database

#

# localhost is used to configure the loopback interface

# when the system is booting. Do not change this entry.

##

127.0.0.1 localhost

255.255.255.255 broadcasthost

::1 localhost

fe80::1%lo0 localhost

Using the Network utility, a ping to www.google.com returns the following results:

Ping has started…

PING www.l.google.com (74.125.73.106): 56 data bytes

64 bytes from 74.125.73.106: icmp_seq=0 ttl=54 time=63.801 ms

64 bytes from 74.125.73.106: icmp_seq=1 ttl=54 time=60.193 ms

64 bytes from 74.125.73.106: icmp_seq=2 ttl=54 time=64.545 ms

64 bytes from 74.125.73.106: icmp_seq=3 ttl=54 time=58.229 ms

64 bytes from 74.125.73.106: icmp_seq=4 ttl=54 time=58.510 ms

64 bytes from 74.125.73.106: icmp_seq=5 ttl=54 time=58.276 ms

64 bytes from 74.125.73.106: icmp_seq=6 ttl=54 time=59.600 ms

64 bytes from 74.125.73.106: icmp_seq=7 ttl=54 time=101.432 ms

64 bytes from 74.125.73.106: icmp_seq=8 ttl=54 time=57.711 ms

64 bytes from 74.125.73.106: icmp_seq=9 ttl=54 time=57.481 ms

--- www.l.google.com ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 57.481/63.978/101.432/12.703 ms

Using the Network utility, a lookup to www.google.com returns the following results:

Lookup has started…

; <<>> DiG 9.6.0-APPLE-P2 <<>> www.google.com +multiline +nocomments +nocmd +noquestion +nostats +search

;; global options: +cmd

www.google.com. 896 IN CNAME www.l.google.com.

www.l.google.com. 18 IN A 74.125.73.105

www.l.google.com. 18 IN A 74.125.73.106

www.l.google.com. 18 IN A 74.125.73.147

www.l.google.com. 18 IN A 74.125.73.99

www.l.google.com. 18 IN A 74.125.73.103

www.l.google.com. 18 IN A 74.125.73.104

google.com. 535 IN NS ns2.google.com.

google.com. 535 IN NS ns1.google.com.

google.com. 535 IN NS ns4.google.com.

google.com. 535 IN NS ns3.google.com.

ns1.google.com. 358 IN A 216.239.32.10

ns2.google.com. 444 IN A 216.239.34.10

ns3.google.com. 375 IN A 216.239.36.10

ns4.google.com. 358 IN A 216.239.38.10

I can access other google pages, such as maps, but not the main www.google.com website. My iphone calls up this page on my home wireless network with no problem. This problem did not occur at all until I used mac update two days ago.

I have exactly this same problem.

No, you don't. Please start another thread to address your problem.

I have this problem:

When I try to used Google I get a pages that says:

"Safari can't connect to the server.

Safari can't open the page http://google.com/ because Safari can't connect to the server "google.com"/

I've cleared my cookies and have reset my computer. My Gmail will not load either.

anyone know whats going on?

Can you please explain to me how that is NOT the same problem?