CMD prompt ping issue Vista Ultimate

[pctech64]

Hello;
I'm trying to ping from the cmd and i got a message telling me ping is not a recognized command; if i try ipconfig the same result. I'm the administrator for my machine. Internet connectivity is working fine.
Any Ideas?
Thanks in advance.

 

[Turkbear]

Hi,
maybe this:

http://www.daniweb.com/forums/thread103875.html#

The postings by these folks mention checking your PATH variable and being sure those tools are installed..

Maybe it will point you to a solution...

NOTE: Site has a very annoying method of asking if you would like to join ( screen darkens and a pop-over box appears - it closes fine but still annoys)





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[PRPhx]

Here is another link, with any annoying method asking you to join. Has lots of good info.

http://www.vistax64.com/network-internet/228024-ping-ftp-tracert-not-working.html

It also mentions checking 1) The path, and 2) Make sure the ping command is actually there.

 

[linney]

Try right-clicking on the Cmd Prompt shortcut and select the "Run As Administrator" option. Perhaps with a few extra privileges "Ping" will stop hiding from you?

This is known as running "Elevated", and it is a term often used in Vista.

 

[pctech64]

I check what was told still can't ping from cmd; I'm the administrator for those who don't read the posts.
If I ping from windows\system32\cmd.exe I have no problems.
I tried typing the string to this path several times and diferent ways on the Env. variables and nada.
Help is welcome. I don't need to ping nothing at this time but want the command working for those cases I will need it; better fix it now; I think Java console installation screwed it all up. I got Mc Afee Enterprise Edition AV and it is not interfering.

 

[smah]

If you create a new user account/profile, does the new user have the same problem? And linney's suggestion to elevate your priviledges by right click and 'Run as Administrator' has to do with User Account Control, and it still appplies even if your normal user account has administrative priviledges.

 

[Turkbear]

Hi,
Given this:

If I ping from windows\system32\cmd.exe I have no problems.

it is almost certainly a path problem...Can you copy your current PATH variable and post it?







To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[linney]

What happens if you create a new shortcut from the Cmd.exe in windows\system32\cmd.exe and use it to replace the shortcut that you are currently clicking on?

 

[pctech64]

Here are the path

cmd %SystemRoot%\System32\cmd.exe

cmd %SystemRoot%\system32\cmd.exe

That is for both user variables and system variable

 

[linney]

The Environment Variable (for Path) should look something like this -

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0

The are located in Advanced System Settings/ Environment Variables/ System Variables/ Path

 

[pctech64]

I don't have nothing like that there

 

[Diancecht]

If I were a cracker and had compromised your computer, onw of the first thing I would have done is replace your cmd with a faulty one.

Maybe it's time for a system integrity check (virus, trojans, ...)

Cheers,
Dian

 

[strongm]

>I'm the administrator for those who don't read the posts

Erm ... the Vista administrator account isn't actually the administrator account ...

 

[linney]

If your Environment Variable Path doesn't make mention of %Systemroot%\system32 then you will have problems.

What do you have as a "Path"?

 

[pctech64]

linney read 5 posts back; that is the path

 

[linney]

We are talking about two different Paths as seen from these Command Prompts. I am trying to ascertain what you have in the second one.

C:\Documents and Settings\User> set comspec
ComSpec=C:\WINDOWS\system32\cmd.exe

C:\Documents and Settings\User> set path
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

 

[pctech64]

the way it all looks in the last post; is that the way it should look exactly in mine? if so; no, that is not what I have. Remember I can still ping fine if I use the command from the folder system32, but I can't use the feature or any other; ipconfig, traceroute arp etc if I just go to start run cmd.

 

[linney]

We have become side tracked trying to determine what you have as your Environment Variable Path. It is only one symptom that I am looking at, easily resolved and eliminated if you post your Environment Variable Path text as opposed to the Comspec Path.

If you enter this DOS Command at your Prompt (when you do start run cmd),

CD C:\WINDOWS\system32

and then enter the Ping command does it then work?

I am trying to work out if your C:\Documents and Settings\User prompt is not using the Environment Variable Path correctly.

Conversely if you place a copy of Ping.exe in C:\Documents and Settings\User and then launch Start Run Cmd, does Ping then work?

 

[pctech64]

no it does not works
I haven't tested to copy it to C:\ doc...
I'm using Vista Ultimate and it looks that ping.exe is not in the system34 folder; i have cmd.exe but don't see ping.exe

 

[linney]

Sorry for the references to Documents and Settings, I meant Users folder. I keep flitting between XP, Vista, and Windows 7, so sometimes I forget where I am.

If you are missing Ping.exe that would be a problem in trying to run it. Are you also missing IpConfig.exe, and the other utilities you tried to run?

In Vista Ultimate I can see some 2755 items listed in System32, do you have a similar total of items in your System32 folder? It will vary from machine to machine but that is just a rough sort of ball park figure.

Maybe running the System File Checker is a good idea. Alternatively replacing the missing files from another Vista (same SP version etc.) machine might be an option.

How to repair the operating system and how to restore the operating system configuration to an earlier point in time in Windows Vista

http://support.microsoft.com/kb/936212/#appliesto