I have a win2k machine that does not recognize any network command I type at the command line, I mean ping, ipconfig, tracert etc... Does anybody has a fix for that? Your input would be very much appreciated.
Regards
Software/Hardware used:
ASKED:
December 29, 2004 5:37 PM
UPDATED:
December 31, 2004 3:12 PM
I get the command prompt either by start> programs> accessories> command prompt or run.I can run notepad from run fine. but I can not do run for example,it gives me an errror msge asking me to check the path.From the command prompt when I type ping x.x.x.x’ping’isn’t recognize as an internal or external command operable prgm or batch file. Thanks for replying.
Sorry I made a stupid mistake, I wanted to reply to your message and instead I reported it as offensive message, I really apologize to you, it is my first time using the site to post questions. I am so sorry. Thanks for your help.
Regards and sorry again.
Ok, W2K does not have msconfig program so you would get an error trying to run this command.
Notepad is in both the windows root directory and the system32 so if your path is working to the windows root directory, then notepad should work.
change to the system32 directory and run your network commands and let me know if they work.
when I change the directory to what you said, my commands work fine.
But how about the msconfig? do you have any idea?
Thank you very much for your help.
Regards.
Windows 2000 does not have the msconfig program. You can not run msconfig in W2k.
Now, that we know that your programs work by changing to their home directory, the problem is in your path statement.
The best advice I can give you is try and find a working W2k in your enviroment and copy the path statement. My W2k path statement looks like this
%SystemRoot%system32;%SystemRoot%;%SystemRoot%System32Wbem
You can change your path statement by right clicking on my computer, select properties, then advanced tab, enviromental variables, system variables, path then edit.
MSConfig is not included in Windows 2000, but if you can get a copy of MSConfig from XP or Server 2003 it will run on Windows 2000.
Msconfig does not come with Windows2000, but the XP version works fust fine.
A good alternative is a program called ‘Starter’ from Codestuff. It does everything msconfig does and more.
You can get it at http://www.download.com
How about “StartupCPL” or “Startup” alternative to msconfig, which is working fine with my win2k sever pc?
In my opinion, it appears that you may have ‘upgraded’ from a previous op. sys.
Do a ‘search’ for ‘msconfig*’
If you find directories such as:
C:WindowsHelp
you may also find a file: ‘msconfig.chn’ which is a Compiled HTML help file which opens with Microsoft HTML Help.
yuo may have:
C:WindowsPrefetch
This directory may contain:
msconfig.exe-35E4DAE9.pf
You may have:
C:Windows$NTServicePackUninstall$
This directory may contain:
msconfig.exe and msconf.dll
msconf.dll is a ‘Conferencing Utility dll from Microsoft Corporation: Version 5.1.2600.2180 @ 68KB whish I think identifies XP
You may have:
C:WindowsDllcache
This directory may contain ‘msconfig.exe’
You may have:
C:WindowsServicePackFilesi386
This directory may contain both,’msconfig.exe’ and ‘msconf.dll’
or,
You mahe have installed a program like:
PCHEALTH which resides in:
C:WindowsPCHEALTHHelpCTRBinaries
This directory may contain ‘msconfig.exe’
Please check the version and place both the ‘msconfig.exe’ and ‘msconf.dll’ in the ‘System32′ directory.
I do agree with others that your PATH is somewhat ‘messed-up’, possibly too long with things like:
c:windowsProgra~1whatever~1whatever~1 etc,etc,etc
Do as suggested and ‘clean-up’ your path with the provided path statement.
If you want to use ‘msconfig.exe’ because of familiarity make sure that you are not disabling functions you need or ‘editing’ path statements which conflict with what you wish to accomplish.
I suspect that ‘msconfig.exe’ can run from XP even with SP2 installed if the previous conditions of ‘upgrading’ and such are true.
Either way, I hope this helps.
Thank you.
first and foremost, when CMD and usuall TCPIP commands are issued (ping, tracert, ipconfig) and they return these errors, check the NIC in Network porperties and assure TCPIP is installed.
these errors are usuall when TCPIP is uninstalled/corrupted. (corrupted more common in 9x/Me)