Cannot reach Google

I cannot connect to Google , or search.msn.com .

I tried to ping both Google and search.msn.com, and get a time out. Then
I ran a traceroute to Google:

Tracing route to www.google.com [207.44.194.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dmp-amd-1800.mshome.net [192.168.0.1]
2 27 ms 15 ms 15 ms adsl-64-160-235-254.dsl.lsan03.pacbell.net
[64.1
60.235.254]
3 29 ms 15 ms 15 ms dist1-vlan50.lsan03.pbi.net
[64.161.163.214]
4 13 ms 14 ms 30 ms bb1-g1-1-1.lsan03.pbi.net [67.116.100.115]
5 28 ms 30 ms 15 ms sbc-above-oc12.lax2.above.net
[151.164.89.66]
6 28 ms 30 ms 15 ms so-4-0-0.mpr1.lax9.us.above.net
[64.125.30.125]

7 28 ms 30 ms 30 ms so-6-0-0.mpr3.sjc2.us.above.net
[64.125.30.129]

8 59 ms 61 ms 62 ms pos2-0.mpr1.dfw2.us.mfnx.net
[208.184.232.81]
9 59 ms 62 ms 62 ms so-3-0-0.cr1.dfw2.us.above.net
[216.200.127.213]

10 74 ms 77 ms 62 ms so-4-0-0.mpr1.iah1.us.above.net
[64.125.31.37]
11 74 ms 76 ms 77 ms 216.200.251.29.ev1.net [216.200.251.29]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Seems something is wrong over at ev1? Can anyone shed some light on this?
Anyone else having this problem?

--
Adrienne Boswell
Please respond to the group so others can share
http://www.arbpen.com

I cannot connect to Google

Same here. Looks like google.com & www.google.com have been unavailable
since sometime this afternoon (Pacific time). However, I am able to reach
www2.google.com & www3.google.com from here.

"RFI Admin" <rfi (AT) ruralfree (DOT) net> wrote

I cannot connect to Google

Same here. Looks like google.com & www.google.com have been unavailable
since sometime this afternoon (Pacific time). However, I am able to reach
www2.google.com & www3.google.com from here.
Pulls up fine on the West Coast (CA)

James Taylor
www.AICompany.com

Gazing into my crystal ball I observed "James"
<james.NtaySPAl (AT) aicPLomEApSanEy (DOT) com> writing in
news:iWOeb.6852$YO5.4046254 (AT) news3 (DOT) news.adelphia.net:

"RFI Admin" <rfi (AT) ruralfree (DOT) net> wrote in message
news:2oMeb.5294$La.310 (AT) fed1read02 (DOT) ..

I cannot connect to Google

Same here. Looks like google.com & www.google.com have been
unavailable since sometime this afternoon (Pacific time). However, I
am able to reach www2.google.com & www3.google.com from here.
Pulls up fine on the West Coast (CA)

I'm in Glendale, California, using SBC DSL. I have a friend who lives
about 10 miles away, also uses SBC DSL and is having no problems, however,
at this time 23:44 I still cannot get www.google.com or search.msn.com .
Running a trace route, I'm still timing out right after ev1.net, hop 12.


--
Adrienne Boswell
Please respond to the group so others can share
http://www.arbpen.com

I'm in Glendale, California, using SBC DSL.

www.google.com is still unreachable this morning from my location. I'm in
Las Vegas, NV using Cox.

Seems something is wrong over at ev1? Can anyone shed some light on this?
Anyone else having this problem?

--
Adrienne Boswell
Please respond to the group so others can share
http://www.arbpen.com

Read this:
http://www.spywareinfo.net/sept30,2003#searchjack

It's a new virus, dubbed "Trojan.Qhosts".

Discussed here:
CERT:
http://www.cert.org/incident_notes/IN-2003-04.html
Symantec:
http://securityresponse.symantec.com...an.qhosts.html
Network Associates:
http://vil.nai.com/vil/content/v_100719.htm

It infects your system, changes your DNS.

It's because of a Windows IE problem whereby clever code in a webpage
can trigger a problem with the Microsoft Html application handler and
execute code on your comptuer.

Symantec has as of yet no fix in norton antivirus for it. I
downloaded the "Live update" for 10/1/2003, and it didn't find it. I
then downloaded the "intelligent update"
(http://securityresponse.symantec.com.../US-SAVCE.html)
which you have to do manually, and so far, the scan has found nothing.
Luckilly, the page on symantec's response says that a fix will be
comming out in next week's live update.

Also posting this to:
microsoft.public.win2000.security
microsoft.public.security.virus
microsoft.public.windowsxp.security_admin
alt.internet.search-engines
microsoft.public.windowsnt.protocol.tcpip

Will Dunn
Systems Administrator
Netmar Web Services






Adrienne <arbpen (AT) sbcglobal (DOT) net> wrote

I cannot connect to Google , or search.msn.com .

I tried to ping both Google and search.msn.com, and get a time out. Then
I ran a traceroute to Google:

Tracing route to www.google.com [207.44.194.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dmp-amd-1800.mshome.net [192.168.0.1]
2 27 ms 15 ms 15 ms adsl-64-160-235-254.dsl.lsan03.pacbell.net
[64.1
60.235.254]
3 29 ms 15 ms 15 ms dist1-vlan50.lsan03.pbi.net
[64.161.163.214]
4 13 ms 14 ms 30 ms bb1-g1-1-1.lsan03.pbi.net [67.116.100.115]
5 28 ms 30 ms 15 ms sbc-above-oc12.lax2.above.net
[151.164.89.66]
6 28 ms 30 ms 15 ms so-4-0-0.mpr1.lax9.us.above.net
[64.125.30.125]

7 28 ms 30 ms 30 ms so-6-0-0.mpr3.sjc2.us.above.net
[64.125.30.129]

8 59 ms 61 ms 62 ms pos2-0.mpr1.dfw2.us.mfnx.net
[208.184.232.81]
9 59 ms 62 ms 62 ms so-3-0-0.cr1.dfw2.us.above.net
[216.200.127.213]

10 74 ms 77 ms 62 ms so-4-0-0.mpr1.iah1.us.above.net
[64.125.31.37]
11 74 ms 76 ms 77 ms 216.200.251.29.ev1.net [216.200.251.29]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Seems something is wrong over at ev1? Can anyone shed some light on this?
Anyone else having this problem?

Tried this fix. Didn't work. I can connect to google 2 however. That's
the answer for now, I guess.

Gazing into my crystal ball I observed "codex"
<bro.theo. (AT) worldnet (DOT) att.net> writing in
news:49%eb.17789$yU5.13907 (AT) nwrdny01 (DOT) gnilink.net:

Tried this fix. Didn't work. I can connect to google 2 however.
That's the answer for now, I guess.

Well, I went to symantec's site that Will was nice enough to post,
and I went into the registry and changed/deleted a few keys are per their
instructions, rebooted twice, and I'm okay again.

I did run spybot and anti-virus in that time also, found no spies, and
cleaned a virus (not the virus mentioned in the article).

Here's Will's link:
http://securityresponse.symantec.com...an.qhosts.html


--
Adrienne Boswell
Please respond to the group so others can share
http://www.arbpen.com

Tried this fix. Didn't work.

You may need to manually remove the bogus entries from your /windows/hosts
file. Edit the hosts file with Notepad, Wordpad or any other text editor.
After saving the file you may need to reboot for the changes to take effect.

When you try to open the google page with Internet Explorer for the first
time after editing the hosts file, hold down the Shift & Ctrl keys while
clicking Refresh. That will do a 'super reload' which will force IE to get a
fresh version of the web page and not use any cached information. You should
now see google's page.