Google not working? - Page 2

LUVBUGZ · 10-03-2003, 01:39 AM

I went to start->programs->accessories->, but there was nothing about a command window.

juju · 10-03-2003, 01:49 AM

It's around there somewhere. :)

You can also go Start->Run, and then type "command" to bring it up, I think.

Beestie · 10-03-2003, 08:18 AM

Many ways to think of ping...

In general, "ping" is akin to the sonar pulse of a submarine. If you don't get a return ping, no one is there. A sub's sonar, however is a general ping - is anyone there whereas the ping we're talking about is domain specific - i.e., are [you] there?

Another reason to "ping" is to verify that one has a valid connection before running a big process. Sort of like waiting till the other person answers the phone before going into a long, cellar-like diatribe

Hackers use ping a lot too. And so do Worms.

Be sure that your ping to google didn't work. Just because it says "destination unreachable" doesn't mean google wasn't "up." You have to look at the packets received in the statistics to see how many of the ones you sent came back. If any of them came back then google (or whoever) is up.

SteveDallas · 10-03-2003, 09:09 AM

Ping is good for automated testing too... at work my network has maybe 15 or so gadgets that it needs to run properly (file servers, switches, etc.) I have a program that pings everything every few minutes. If any of the pings fail, I get an email sent to my cell phone telling me what's dead. Comes in handy. (Of course you need a backup in case the mail server itself or the internet connection is what's down!)

wolf · 10-05-2003, 10:36 PM

Quote:

Originally posted by LUVBUGZ
I went to start->programs->accessories->, but there was nothing about a command window.

Important computing safety tip: If you can't find it, you probably can't use it ...

(favorite early net ping story ... guy named a machine on his lan elvis just so he could get back the ping response "elvis is alive" ... )

russotto · 10-06-2003, 09:41 AM

red-october.navy.su% ping -c 1 dallas.navy.mil

LUVBUGZ · 10-06-2003, 10:59 AM

Quote:

Originally posted by wolf

Important computing safety tip: If you can't find it, you probably can't use it ...

Thanks for the tip Wolf, but if I lived by that I wouldn't even turn the damn thing on.

Razorfish · 10-06-2003, 02:15 PM

Something is definitely messed up somewhere. I reinstalled IE6 and even tried using Mozilla. Google just won't display for me. It's driving me nuts because I use Google a lot and I can normally figure out stuff like this (just an ego thing).

Undertoad · 10-06-2003, 02:42 PM

Have you tried traceroute?

Can you ping 216.239.53.99 ? That's one of the addresses google.com responds to for me, and if you can ping it, it means that what's actually failing for you is DNS.

If you can't ping that address, look for a traceroute tool somewhere, or use the cmd version of it, tracert.

Razorfish · 10-06-2003, 08:01 PM

Quote:

Originally posted by Undertoad
Have you tried traceroute?

Can you ping 216.239.53.99 ? That's one of the addresses google.com responds to for me, and if you can ping it, it means that what's actually failing for you is DNS.

If you can't ping that address, look for a traceroute tool somewhere, or use the cmd version of it, tracert.

Yea, I tried that and it just times out. The weird thing is that it was working fine until my internet service went down a few days ago. When it went down the Google main page would load but of course the search function as well as other websites would not work. I managed to fix it (network DNS error) but Google seemed to get "black-holed" in the process. I now use the built in search function on Mozilla, which seems to work better than msn, but not as good as Google. I just don't know

.

Undertoad · 10-06-2003, 08:19 PM

Traceroute (tracert on windowd cmd line) pings each routing point between you and the address, so that you can figure out where the weak link is. If traceroute is stopping right away, then it's blocked at your *machine* somehow. If it gets partway and stops, it's probably your ISP.

juju · 10-07-2003, 12:05 AM

You probably have google cache'd. That's why the main page loads.

Razorfish · 10-20-2003, 01:57 PM

I finally discovered the problem. About a week ago someone suggested to me I delete the references to Google in my hosts.sam file (the file contains the addresses of popular search engines and is used by browsers). This seemed to work

.

But at least something good came out of this. Back when I didn't know what was causing the problem I switched to Mozilla to see if it would work. Well, Google works fine now and iv'e now converted to Mozilla Firebird. It still has some bugs but it picks up where IE left off and all of the add on extensions work great.

earth1942 · 09-08-2006, 07:15 AM

Quote:

Originally Posted by Undertoad

Have you tried traceroute?

Can you ping 216.239.53.99 ? That's one of the addresses google.com responds to for me, and if you can ping it, it means that what's actually failing for you is DNS.

If you can't ping that address, look for a traceroute tool somewhere, or use the cmd version of it, tracert.

I have had the same issue where google and anything that uses google doesn't work. It stopped working after we got a new wireless router in our house. Only one computer on the wireless network is able to get to google (out of 4). The weird thing is that I have my Mozilla Thunderbird set to recieve my mail from mail.gmail.com server and it works just fine. But if I try to go to www.gmail.com I get timed out.

I tried pinging this address above and I did get a response back. I was also trying to find the host.sam file but was unable to. Any ideas? Thanks in advanced!

- Jori

BigV · 09-08-2006, 10:34 AM

Quote:

Originally Posted by earth1942

I have had the same issue where google and anything that uses google doesn't work. It stopped working after we got a new wireless router in our house. Only one computer on the wireless network is able to get to google (out of 4). The weird thing is that I have my Mozilla Thunderbird set to recieve my mail from mail.gmail.com server and it works just fine. But if I try to go to www.gmail.com I get timed out.

I tried pinging this address above and I did get a response back. I was also trying to find the host.sam file but was unable to. Any ideas? Thanks in advanced!

- Jori

try here:

C:\WINDOWS\system32\drivers\etc\hosts.sam

Also, here's a link to way more than you ever wanted to know about hosts.

10-03-2003, 01:39 AM	#16
LUVBUGZ Not aging gracefully. Join Date: Aug 2003 Posts: 530	I went to start->programs->accessories->, but there was nothing about a command window. __________________ You can't catch me...don't even try...go do something else...see ya next year. Mama Loves You Baby Girl ~ May You Rest In Peace

10-03-2003, 08:18 AM	#18
Beestie -◊\|≡·∙■·∙≡\|◊- Join Date: Feb 2003 Location: Parts unknown. Posts: 4,081	Many ways to think of ping... In general, "ping" is akin to the sonar pulse of a submarine. If you don't get a return ping, no one is there. A sub's sonar, however is a general ping - is anyone there whereas the ping we're talking about is domain specific - i.e., are [you] there? Another reason to "ping" is to verify that one has a valid connection before running a big process. Sort of like waiting till the other person answers the phone before going into a long, cellar-like diatribe Hackers use ping a lot too. And so do Worms. Be sure that your ping to google didn't work. Just because it says "destination unreachable" doesn't mean google wasn't "up." You have to look at the packets received in the statistics to see how many of the ones you sent came back. If any of them came back then google (or whoever) is up. __________________ ♠ ♥ ♣ ♦

10-06-2003, 09:41 AM	#21
russotto Professor Join Date: Jan 2001 Posts: 1,788	Verify range to target... red-october.navy.su% ping -c 1 dallas.navy.mil

10-06-2003, 02:15 PM	#23
Razorfish Superhero Join Date: Sep 2003 Location: New England Posts: 104	?? Something is definitely messed up somewhere. I reinstalled IE6 and even tried using Mozilla. Google just won't display for me. It's driving me nuts because I use Google a lot and I can normally figure out stuff like this (just an ego thing). __________________ Mostly lurking

10-20-2003, 01:57 PM	#28
Razorfish Superhero Join Date: Sep 2003 Location: New England Posts: 104	problem fixed I finally discovered the problem. About a week ago someone suggested to me I delete the references to Google in my hosts.sam file (the file contains the addresses of popular search engines and is used by browsers). This seemed to work . But at least something good came out of this. Back when I didn't know what was causing the problem I switched to Mozilla to see if it would work. Well, Google works fine now and iv'e now converted to Mozilla Firebird. It still has some bugs but it picks up where IE left off and all of the add on extensions work great. __________________ Mostly lurking

10-03-2003, 01:49 AM	#17
juju no one of consequence Join Date: Jun 2001 Location: Arkansas Posts: 2,839	It's around there somewhere. :) You can also go Start->Run, and then type "command" to bring it up, I think.

10-03-2003, 09:09 AM	#19
SteveDallas Your Bartender Join Date: Jan 2002 Location: Philly Burbs, PA Posts: 7,651	Ping is good for automated testing too... at work my network has maybe 15 or so gadgets that it needs to run properly (file servers, switches, etc.) I have a program that pings everything every few minutes. If any of the pings fail, I get an email sent to my cell phone telling me what's dead. Comes in handy. (Of course you need a backup in case the mail server itself or the internet connection is what's down!)

10-06-2003, 02:42 PM	#24
Undertoad Radical Centrist Join Date: Jan 2001 Location: Cottage of Prussia Posts: 31,423	Have you tried traceroute? Can you ping 216.239.53.99 ? That's one of the addresses google.com responds to for me, and if you can ping it, it means that what's actually failing for you is DNS. If you can't ping that address, look for a traceroute tool somewhere, or use the cmd version of it, tracert.

10-06-2003, 08:19 PM	#26
Undertoad Radical Centrist Join Date: Jan 2001 Location: Cottage of Prussia Posts: 31,423	Traceroute (tracert on windowd cmd line) pings each routing point between you and the address, so that you can figure out where the weak link is. If traceroute is stopping right away, then it's blocked at your machine somehow. If it gets partway and stops, it's probably your ISP.

10-07-2003, 12:05 AM	#27
juju no one of consequence Join Date: Jun 2001 Location: Arkansas Posts: 2,839	You probably have google cache'd. That's why the main page loads.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)