ping

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

for some reason my ping command does not work for example this is what it
looks like when i put it in c:\ping 127.0.0.1 it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that i was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here
 
mike said:
for some reason my ping command does not work for example this is what it
looks like when i put it in c:\ping 127.0.0.1 it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that i was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here
Click to expand...

Don't write
c:\ping 127.0.0.1

Make it like this instead:
ping 127.0.0.1
 
Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.
 
R. McCarty said:
Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

mike said:
for some reason my ping command does not work for example this is what it
looks like when i put it in c:\ping 127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that i was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here
Click to expand...


sorry guys neither of these options are working .. cmd won't open from run it bliks real quick i have a shortcut for in on my desktop to open it up.. it seems that it is only ping that isn't working .. telnet works fine grrrr.. thanks for the help though
Click to expand...
 
Then try Start, Run (Type) Command [Enter]

- Some firewalls will "Alert" on Ping, make sure you've not
inadvertently blocked Ping.

mike said:
R. McCarty said:
Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

mike said:
for some reason my ping command does not work for example this is what
it
looks like when i put it in c:\ping
127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that i
was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here
Click to expand...


sorry guys neither of these options are working .. cmd won't open from
run it bliks real quick i have a shortcut for in on my desktop to open it
up.. it seems that it is only ping that isn't working .. telnet works
fine grrrr.. thanks for the help though
Click to expand...
Click to expand...
 
yea i have checked and doubble checked restarted and then checked again , i
downloaded nettools and i can ping from there . blah are there ne updates to
for comand prompt maybe dl a new one ha

R. McCarty said:
Then try Start, Run (Type) Command [Enter]

- Some firewalls will "Alert" on Ping, make sure you've not
inadvertently blocked Ping.

mike said:
R. McCarty said:
Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

for some reason my ping command does not work for example this is what
it
looks like when i put it in c:\ping
127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that i
was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here


sorry guys neither of these options are working .. cmd won't open from
run it bliks real quick i have a shortcut for in on my desktop to open it
up.. it seems that it is only ping that isn't working .. telnet works
fine grrrr.. thanks for the help though
Click to expand...
Click to expand...
Click to expand...
 
If you get different outputs, when you type "ping", as opposed to
"ping.exe", then search your hard drive for different versions of ping

eg put "ping*.*" in the filename box for search

Jon


mike said:
yea i have checked and doubble checked restarted and then checked again ,
i
downloaded nettools and i can ping from there . blah are there ne updates
to
for comand prompt maybe dl a new one ha

R. McCarty said:
Then try Start, Run (Type) Command [Enter]

- Some firewalls will "Alert" on Ping, make sure you've not
inadvertently blocked Ping.

mike said:
:

Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

for some reason my ping command does not work for example this is
what
it
looks like when i put it in c:\ping
127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that
i
was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here


sorry guys neither of these options are working .. cmd won't open from
run it bliks real quick i have a shortcut for in on my desktop to open
it
up.. it seems that it is only ping that isn't working .. telnet works
fine grrrr.. thanks for the help though
Click to expand...
Click to expand...
Click to expand...
 
You probably meant "cmd.exe" instead of "command.com".
Command.com is a 16-bit legacy command processor that
should not be used in WinXP.


R. McCarty said:
Then try Start, Run (Type) Command [Enter]

- Some firewalls will "Alert" on Ping, make sure you've not
inadvertently blocked Ping.

mike said:
R. McCarty said:
Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

for some reason my ping command does not work for example this is what
it
looks like when i put it in c:\ping
127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that i
was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here


sorry guys neither of these options are working .. cmd won't open from
run it bliks real quick i have a shortcut for in on my desktop to open it
up.. it seems that it is only ping that isn't working .. telnet works
fine grrrr.. thanks for the help though
Click to expand...
Click to expand...
Click to expand...
 
Maybe you should replace your Autoexec.Nt file. Copy the file from
C:\Windows\Repair to C:\Windows\System32 - otherwise, I'm out of
ideas.

mike said:
yea i have checked and doubble checked restarted and then checked again ,
i
downloaded nettools and i can ping from there . blah are there ne updates
to
for comand prompt maybe dl a new one ha

R. McCarty said:
Then try Start, Run (Type) Command [Enter]

- Some firewalls will "Alert" on Ping, make sure you've not
inadvertently blocked Ping.

mike said:
:

Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

for some reason my ping command does not work for example this is
what
it
looks like when i put it in c:\ping
127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that
i
was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here


sorry guys neither of these options are working .. cmd won't open from
run it bliks real quick i have a shortcut for in on my desktop to open
it
up.. it seems that it is only ping that isn't working .. telnet works
fine grrrr.. thanks for the help though
Click to expand...
Click to expand...
Click to expand...
 
Ping is sometimes blocked by ISPs to stop DoS attacks. But
ping 127.0.0.1 should work since that is the loopback on
your computer. Try ping localhost



--
The people think the Constitution protects their rights;
But government sees it as an obstacle to be overcome.
some support
http://www.usdoj.gov/olc/secondamendment2.htm



| yea i have checked and doubble checked restarted and then
checked again , i
| downloaded nettools and i can ping from there . blah are
there ne updates to
| for comand prompt maybe dl a new one ha
|
| "R. McCarty" wrote:
|
| > Then try Start, Run (Type) Command [Enter]
| >
| > - Some firewalls will "Alert" on Ping, make sure you've
not
| > inadvertently blocked Ping.
| >
| >
| > >
| > >
| > > "R. McCarty" wrote:
| > >
| > >> Doing this from the Run box ? Ping is an executable
in
| > >> C:\Windows\System32.
| > >>
| > >> All XP instances have the C:\Windows\System32 in it's
Path variable.
| > >> You don't need to preface the command with C:\ - Give
a command
| > >> and the System knows where to search/execute it from.
| > >>
| > >> If you invoke it from Run, it will open a Command
Prompt window
| > >> to show it's status - but will immediately close that
window after the
| > >> command finishes.
| > >>
| > >> Best to just open a Command Prompt window and invoke
Ping
| > >> from within the CP window. Start, Run (Type) Cmd
[Enter]
| > >> This way the status info remains, until you Exit the
CP window.
| > >>
message
| > >>
| > >> > for some reason my ping command does not work for
example this is what
| > >> > it
| > >> > looks like when i put it in
c:\ping
| > >> > 127.0.0.1
| > >> > it
| > >> > happens with ne addy i put in as well
| > >> > this is the next line to show up c:\
| > >> >
| > >> > i have no idea when this started hapening i am
almost positive that i
| > >> > was
| > >> > able to ping in the past. can somw one shed some
light here .
| > >> > also when i put in ping.exe i get all the options
to use in ping so
| > >> > something is fishy here
| > >>
| > >>
| > >> sorry guys neither of these options are working ..
cmd won't open from
| > >> run it bliks real quick i have a shortcut for in on
my desktop to open it
| > >> up.. it seems that it is only ping that isn't working
... telnet works
| > >> fine grrrr.. thanks for the help though
| >
| >
| >
 
mike said:
thanks guys . i tried all of the options still a no go
Click to expand...

Viral or Malware infection can cause this.

Update your antivirus, get Spybot S&D and Ad-Aware, update all and scan
in Safe Mode.

Steve
 
wow. forsome reson i decided to do ping.exe 127.0.0.1 and it pingged for the
prompt i also have to do the same steps for netstat ne way i ca load it into
the path so i don't hae to do .exe
 
cmd won't open from run it bliks real quick

You have a virus or a trojan.

10 to 1 when you type cmd in Start | Run, cmd.com is trying to open.

10 to 1 when you type ping in cmd.exe ping.com is what gets found.

Open a command prompt and type:

ping.exe /?

Hit your Enter key.

Ping help should be displayed.

You have a virus. cmd.com is *NOT* an XP file. ping.com is *NOT* an XP
file.

You have a trojan/worm/virus. cmd.exe is not part of the 16 bit MS-DOS
Subsystem. autoexec.nt and config.nt have nothing to do with cmd.exe.

When you type cmd in the Start | Run box, XP finds cmd.com instead of
cmd.exe. When a command is typed without an extension, XP looks for the
..com extension first before it looks for the .exe extension, if it finds
cmd.com, it will not even look for cmd.exe. Because XP finds cmd.com XP
thinks that it needs autoexec.nt and config.nt to run cmd.com.

cmd.com is *NOT* an XP file, it's added by a trojan/worm/virus.

If you were to type cmd.exe in the Start | Run box, cmd.exe might open if
the trojan/worm/virus hasn't rendered it useless.

Update your antivirus software and run a complete scan.

Also Known As: W32.Alcan.A, Win32.Alcan.A [Computer Associates],
P2P-Worm.Win32.Alcan.a [Kaspersky Lab], W32/Alcan.worm!p2p [McAfee],
W32/Alcra-A [Sophos], WORM_ALCAN.A [Trend Micro]

[[This worm drops the legitimate file compression DLL, BSZIP.DLL in the
Windows system folder. It does this so it can compress itself. It also drops
the following files in the Windows system folder:

CMD.COM
NETSTAT.COM
PING.COM
REGEDIT.COM
TASKKILL.COM
TASKLIST.COM
TRACERT.COM

These files contain the string MZ so that this worm can disable the
following Windows tool applications:

CMD.EXE
NETSTAT.EXE
PING.EXE
REGEDIT.EXE
TASKKILL.EXE
TASKLIST.EXE
TRACERT.EXE ]]
From...
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
 
autoexec.nt and config.nt have nothing to do with cmd.exe (Windows Command
Processor). These files are used with command.com (MS-DOS Prompt), not
cmd.exe.

If either autoexec.nt or config.nt are missing from C:\Windows\System32,
command.com will not open. And you can get one or both of these error
messages, depending on which one's missing.

---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------

---------------------------
16 bit MS-DOS Subsystem
---------------------------
C:\WINDOWS\System32\command.pif
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
---------------------------
Close Ignore
---------------------------

command.com looks for CONFIG.NT first, then AUTOEXEC.NT.

Either or both autoexec.nt and config.nt can be missing from
C:\WINDOWS\System32 and this has no affect whatsoever on cmd.exe.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
R. McCarty said:
Maybe you should replace your Autoexec.Nt file. Copy the file from
C:\Windows\Repair to C:\Windows\System32 - otherwise, I'm out of
ideas.

mike said:
yea i have checked and doubble checked restarted and then checked again ,
i
downloaded nettools and i can ping from there . blah are there ne updates
to
for comand prompt maybe dl a new one ha

R. McCarty said:
Then try Start, Run (Type) Command [Enter]

- Some firewalls will "Alert" on Ping, make sure you've not
inadvertently blocked Ping.



:

Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

for some reason my ping command does not work for example this is
what
it
looks like when i put it in c:\ping
127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that
i
was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here


sorry guys neither of these options are working .. cmd won't open from
run it bliks real quick i have a shortcut for in on my desktop to open
it
up.. it seems that it is only ping that isn't working .. telnet works
fine grrrr.. thanks for the help though
Click to expand...
Click to expand...
Click to expand...
 
Anything typed in command is passed too cmd for execution (watch cmd start and exit in Task Manager). It only will run Dos 5 commands if specified on the command line so Dos programs that used to shell to command get the results they expect.

Type in Start Run
command then in command ver
cmd then in cmd ver
cmd /k ver
command /k ver

Autoexec.nt have nothing to do with the console window. CMD and Ping are both Windows 32 bit programs. Only dos and Windows 16 bit programs use Autoexec.nt. Dos programs when each one loads. Win 16 when the first one is loaded.

The console window is not tied to any program. If one types ping in Start Run ping will create a new console window, write to it, and exit (and as no program owns the window it closes). Cmd or command is not involved at all. If one types cmd then cmd creates a console window and starts other colsole programs in that window.

I don't even understand his problem. What happens exactly when he type
ping 127.0.0.1
in a command prompt.
--
--------------------------------------------------------------------------------------------------
Read David defending the concept of violence.
http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
=================================================
Pegasus (MVP) said:
You probably meant "cmd.exe" instead of "command.com".
Command.com is a 16-bit legacy command processor that
should not be used in WinXP.


R. McCarty said:
Then try Start, Run (Type) Command [Enter]

- Some firewalls will "Alert" on Ping, make sure you've not
inadvertently blocked Ping.

mike said:
:

Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

for some reason my ping command does not work for example this is what
it
looks like when i put it in c:\ping
127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that i
was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here


sorry guys neither of these options are working .. cmd won't open from
run it bliks real quick i have a shortcut for in on my desktop to open it
up.. it seems that it is only ping that isn't working .. telnet works
fine grrrr.. thanks for the help though
Click to expand...
Click to expand...
Click to expand...
 
Try these under command.com:
- doskey.exe (appears to have no effect)
- command /f:on (not supported)
- cd /d d:\ (not supported)
- dir & cd \ (not supported)
Numerous advanced commands are not supported under
command.com, so why bother?

I also note that commands execute very sluggishly under command.com.

=======================
"David Candy" <.> wrote in message
Anything typed in command is passed too cmd for execution (watch cmd start
and exit in Task Manager). It only will run Dos 5 commands if specified on
the command line so Dos programs that used to shell to command get the
results they expect.

Type in Start Run
command then in command ver
cmd then in cmd ver
cmd /k ver
command /k ver

Autoexec.nt have nothing to do with the console window. CMD and Ping are
both Windows 32 bit programs. Only dos and Windows 16 bit programs use
Autoexec.nt. Dos programs when each one loads. Win 16 when the first one is
loaded.

The console window is not tied to any program. If one types ping in Start
Run ping will create a new console window, write to it, and exit (and as no
program owns the window it closes). Cmd or command is not involved at all.
If one types cmd then cmd creates a console window and starts other colsole
programs in that window.

I don't even understand his problem. What happens exactly when he type
ping 127.0.0.1
in a command prompt.
--
----------------------------------------------------------------------------
----------------------
Read David defending the concept of violence.
http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
=================================================
Pegasus (MVP) said:
You probably meant "cmd.exe" instead of "command.com".
Command.com is a 16-bit legacy command processor that
should not be used in WinXP.


R. McCarty said:
Then try Start, Run (Type) Command [Enter]

- Some firewalls will "Alert" on Ping, make sure you've not
inadvertently blocked Ping.

mike said:
:

Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

for some reason my ping command does not work for example this is what
it
looks like when i put it in c:\ping
127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that i
was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here


sorry guys neither of these options are working .. cmd won't open from
run it bliks real quick i have a shortcut for in on my desktop to open it
up.. it seems that it is only ping that isn't working .. telnet works
fine grrrr.. thanks for the help though
Click to expand...
Click to expand...
Click to expand...
 
Type these in a command.com window and see what you get...

doskey /?
command /?
cd /?
dir /?

[[COMMAND.COM is included for backwards compatibility and is recommended
that it be used when old MS-DOS programs may not be able to be run in
Windows NT. ]]
COMMAND.COM vs. CMD.EXE
http://www.computerhope.com/issues/ch000395.htm


--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Pegasus (MVP) said:
Try these under command.com:
- doskey.exe (appears to have no effect)
- command /f:on (not supported)
- cd /d d:\ (not supported)
- dir & cd \ (not supported)
Numerous advanced commands are not supported under
command.com, so why bother?

I also note that commands execute very sluggishly under command.com.

=======================
"David Candy" <.> wrote in message
Anything typed in command is passed too cmd for execution (watch cmd start
and exit in Task Manager). It only will run Dos 5 commands if specified on
the command line so Dos programs that used to shell to command get the
results they expect.

Type in Start Run
command then in command ver
cmd then in cmd ver
cmd /k ver
command /k ver

Autoexec.nt have nothing to do with the console window. CMD and Ping are
both Windows 32 bit programs. Only dos and Windows 16 bit programs use
Autoexec.nt. Dos programs when each one loads. Win 16 when the first one
is loaded.

The console window is not tied to any program. If one types ping in Start
Run ping will create a new console window, write to it, and exit (and as
no program owns the window it closes). Cmd or command is not involved at
all. If one types cmd then cmd creates a console window and starts other
colsole programs in that window.

I don't even understand his problem. What happens exactly when he type
ping 127.0.0.1
in a command prompt.
--
-------------------------------------------------------------------------- --
----------------------
Read David defending the concept of violence.
http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
=================================================
Pegasus (MVP) said:
You probably meant "cmd.exe" instead of "command.com".
Command.com is a 16-bit legacy command processor that
should not be used in WinXP.


R. McCarty said:
Then try Start, Run (Type) Command [Enter]

- Some firewalls will "Alert" on Ping, make sure you've not
inadvertently blocked Ping.



:

Doing this from the Run box ? Ping is an executable in
C:\Windows\System32.

All XP instances have the C:\Windows\System32 in it's Path variable.
You don't need to preface the command with C:\ - Give a command
and the System knows where to search/execute it from.

If you invoke it from Run, it will open a Command Prompt window
to show it's status - but will immediately close that window after the
command finishes.

Best to just open a Command Prompt window and invoke Ping
from within the CP window. Start, Run (Type) Cmd [Enter]
This way the status info remains, until you Exit the CP window.

for some reason my ping command does not work for example this is
what it
looks like when i put it in c:\ping
127.0.0.1
it
happens with ne addy i put in as well
this is the next line to show up c:\

i have no idea when this started hapening i am almost positive that i
was
able to ping in the past. can somw one shed some light here .
also when i put in ping.exe i get all the options to use in ping so
something is fishy here


sorry guys neither of these options are working .. cmd won't open from
run it bliks real quick i have a shortcut for in on my desktop to
open it up.. it seems that it is only ping that isn't working ..
telnet works fine grrrr.. thanks for the help though
Click to expand...
Click to expand...
Click to expand...
 
You have a virus or a trojan.

Get rid of it.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Back
Top