ipconfig windows 2000 Pro 2

[digitrunner]

Hi hope someone can help me. I'm running win 2k pro on my laptop. Its an IBM thinkpad with 10 gig HD, 256 meg ram , pentium 400. Ive been using it for a while to surf the net. My problem is that lately I cant get on to the net and when I type cmd at the run prompt and then type ipconfig, I get a message saying that it is not a recognized internal or external command. Ipconfig was working fine before, I'm thinking it might be a corrupted resgitry entry. Is there an easy fix? Can I use my win2k disk to reinstal windows 2000 over the existing installation without loosing any of my current settings and will this fix the problem. I've racked my brains and I'm stumped. Thanks in advance.

 

[FilthPig]

You've probably lost your path because of some poorly-written installer for a program you installed. Right-click on my computer, select properties. Go to the Advanced Tab and click on Environment Variables. Under system variables, make sure that c:\winnt\system32 (or wherever your system32 directory is) is included in the PATH variable. Marc Creviere

 

[wolluf]

From a command prompt, type path. What's displayed should look something like this C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem (with possibly more entries - should have at least first 2). This is where windows looks to load software from (apart from current folder). Ipconfig is in C:\WINNT\system32. If your path statement has been corrupted, go to System Properties, advanced tab, click on environment variables button, click on path in system variables and click on edit button. Supply correct values (may need to reboot to take effect).

If your ipconfig.exe file is missing, its on the 2k install CD in \i386 (compressed as ipconfig.ex_). Use expand command (expand /? for params) to extract it.

 

[OWizard1]

Try this in the command prompt wntipcfg

 

[ChrystaWho]

I'm having similar troubles. I, for one, am not a computer guru, but I have a basic understanding of use and maintainance. Lately, I've been having some troubles with my internet, and I called the company. They tried basic troubleshooting and then went on to ask me to put in ipconfig in the command prompt. It does not work properly to just type ipconfig or ipconfig /all. I have to type the entire address. The file is there and it works when you type in the whole string (C:>windows\system32\ipconfig /all) But shouldn't it work by just typing ipconfig? Any ideas on what's wrong or if this could be related? I thank you sincerely for your response!

~Chrysta

 

[wolluf]

ChrystaWho

Have you checked your Path statement (as per my post earlier in this thread)? If its wrong, try changing it in system properties, advanced tab, environment variables button. System variables, path. It should look like C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem.

 

[ChrystaWho]

Wolluf,
Thank you for your response. I did check it and it was correct, except that I made a fatal flaw by doing things too quickly, as usual. Out of sheer stupidity, I neglected to open word before pasting your text into my variables line and just as quickly and automatically, hit enter. I tried remedying it by C&P your line, but it did not work. So now, my variables line says C:\WINNT\system32;C:\Winnt;C:\Winnt\System32\Wbem;C:\winnt\ipconfig

Like I said before, stupid mistake. Anyway,is there a standard list that I can retype in that line? Now, I can't even get my internet to run, and I'm sure it's from this...

Once again, I really and truly appreciate any help I can get! You all have NO idea how happy I am that I found you guys! You just might be able to save my sinking ship, and if not, then I still learned a great deal about system environment variables from you! Thank you again! =0)

 

[bcastner]

digitrunner, ChristWho:

Your error message is a classic example of a corrupted Winsock service. The corruption is in the registry entries for several key components of Winsock.

Run this utility, and check your TCP/IP settings after a reboot to make certain they are set again the way you want them:

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

96% confident this will sort the issue for you, and likely ChristWho.