Strange Output On Ping

I

Isarian

Hi all,

I'm working on a computer that suddenly had it's NIC drivers
disappear, and after reinstalling the drivers I get the following
output from a ping prompt:

C:\Documents and Settings\Owner>ping google.com

Pinging google.com [°ÿ] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=65ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241

Ping statistics for :
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 65ms, Average = 58ms

Any thoughts?
 
W

Wesley Vogel

http://72.14.207.99/ and http://64.233.187.99/ appear to be the same page.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>ping google.com

Pinging google.com [64.233.187.99] with 32 bytes of data:

Reply from 64.233.187.99: bytes=32 time=75ms TTL=239
Reply from 64.233.187.99: bytes=32 time=74ms TTL=238
Reply from 64.233.187.99: bytes=32 time=73ms TTL=239
Reply from 64.233.187.99: bytes=32 time=76ms TTL=238

Ping statistics for 64.233.187.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 76ms, Average = 74ms

C:\>ping 64.233.187.99

Pinging 64.233.187.99 with 32 bytes of data:

Reply from 64.233.187.99: bytes=32 time=75ms TTL=239
Reply from 64.233.187.99: bytes=32 time=76ms TTL=238
Reply from 64.233.187.99: bytes=32 time=75ms TTL=239
Reply from 64.233.187.99: bytes=32 time=75ms TTL=239

Ping statistics for 64.233.187.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 76ms, Average = 75ms

C:\>ping 72.14.207.99

Pinging 72.14.207.99 with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=95ms TTL=238
Reply from 72.14.207.99: bytes=32 time=95ms TTL=238
Reply from 72.14.207.99: bytes=32 time=94ms TTL=238
Reply from 72.14.207.99: bytes=32 time=96ms TTL=238

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 94ms, Maximum = 96ms, Average = 95ms

C:\>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
G

Guest

Isarian said:
Hi all,

I'm working on a computer that suddenly had it's NIC drivers
disappear, and after reinstalling the drivers I get the following
output from a ping prompt:

C:\Documents and Settings\Owner>ping google.com

Pinging google.com [°ÿ] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=65ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241

Ping statistics for :
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 65ms, Average = 58ms

Any thoughts?
Well from what im seeing the ping.com program probably got messed up
somewhere along the line. looks like the program normally takes the
retrieved DNS information and displays it, I would assume with no other
information that PING just got messed up and needs repaired or reinstalled,
just a guess im no programmer.
 
W

Wesley Vogel

Ping.exe not ping.com.

C:\WINDOWS\system32\ping.exe

Ping.com is from a trojan/virus/worm. CMD.COM, NETSTAT.COM, PING.COM,
REGEDIT.COM, TASKKILL.COM, TASKLIST.COM and TRACERT.COM are all created by a
trojan/virus/worm.

WORM_ALCAN.A - Technical details
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_ALCAN.A&VSect=T

Symantec Security Response - W32.Alcra.A
http://securityresponse.symantec.com/avcenter/venc/data/w32.alcra.a.html

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Lex Tech said:
Isarian said:
Hi all,

I'm working on a computer that suddenly had it's NIC drivers
disappear, and after reinstalling the drivers I get the following
output from a ping prompt:

C:\Documents and Settings\Owner>ping google.com

Pinging google.com [°ÿ] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=65ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241

Ping statistics for :
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 65ms, Average = 58ms

Any thoughts?
Well from what im seeing the ping.com program probably got messed up
somewhere along the line. looks like the program normally takes the
retrieved DNS information and displays it, I would assume with no other
information that PING just got messed up and needs repaired or
reinstalled, just a guess im no programmer.
 
I

Isarian

Ping.exe not ping.com.

C:\WINDOWS\system32\ping.exe

Ping.com is from a trojan/virus/worm. CMD.COM, NETSTAT.COM, PING.COM,
REGEDIT.COM, TASKKILL.COM, TASKLIST.COM and TRACERT.COM are all created by a
trojan/virus/worm.

WORM_ALCAN.A - Technical detailshttp://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_...

Symantec Security Response - W32.Alcra.Ahttp://securityresponse.symantec.com/avcenter/venc/data/w32.alcra.a.html

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

InLex Tech <[email protected]> hunted and pecked:


Hi all,
I'm working on a computer that suddenly had it's NIC drivers
disappear, and after reinstalling the drivers I get the following
output from a ping prompt:
C:\Documents and Settings\Owner>ping google.com
Pinging google.com [°ÿ] with 32 bytes of data:
Reply from 72.14.207.99: bytes=32 time=65ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Ping statistics for :
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 65ms, Average = 58ms
Any thoughts?
Well from what im seeing the ping.com program probably got messed up
somewhere along the line. looks like the program normally takes the
retrieved DNS information and displays it, I would assume with no other
information that PING just got messed up and needs repaired or
reinstalled, just a guess im no programmer.- Hide quoted text -

- Show quoted text -

So it was... well, that's no good. The computer belongs to a friend of
mine, and I have a feeling I now know where their recent identity
theft problem came from. I wiped it clean and reinstalled from
scratch, and it runs good as new now. Thank you for your advice and
time!
 
W

Wesley Vogel

The only thing that looked strange in your original post was this.
Pinging google.com [°ÿ] with 32 bytes of data:

This part [°ÿ]. Everything else looked fine.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Isarian said:
Ping.exe not ping.com.

C:\WINDOWS\system32\ping.exe

Ping.com is from a trojan/virus/worm. CMD.COM, NETSTAT.COM, PING.COM,
REGEDIT.COM, TASKKILL.COM, TASKLIST.COM and TRACERT.COM are all created
by a
trojan/virus/worm.

WORM_ALCAN.A - Technical
detailshttp://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_...

Symantec Security Response -
W32.Alcra.Ahttp://securityresponse.symantec.com/avcenter/venc/data/w32.alcra.a.html

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

InLex Tech <[email protected]> hunted and pecked:


"Isarian" wrote:
I'm working on a computer that suddenly had it's NIC drivers
disappear, and after reinstalling the drivers I get the following
output from a ping prompt:
C:\Documents and Settings\Owner>ping google.com
Pinging google.com [°ÿ] with 32 bytes of data:
Reply from 72.14.207.99: bytes=32 time=65ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Reply from 72.14.207.99: bytes=32 time=56ms TTL=241
Ping statistics for :
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 65ms, Average = 58ms
Any thoughts?
Well from what im seeing the ping.com program probably got messed up
somewhere along the line. looks like the program normally takes the
retrieved DNS information and displays it, I would assume with no other
information that PING just got messed up and needs repaired or
reinstalled, just a guess im no programmer.- Hide quoted text -

- Show quoted text -

So it was... well, that's no good. The computer belongs to a friend of
mine, and I have a feeling I now know where their recent identity
theft problem came from. I wiped it clean and reinstalled from
scratch, and it runs good as new now. Thank you for your advice and
time!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top