Could not run ipconfig command in Windows XP

Could not run ipconfig command in Windows XP

Sounds like you have been trying to resolve this issue for some time now. I understand how frustrating internal errors are. There are a few things that you can try to determine if the hardware has failed and a new network adapter will be required. Did this being after virus removal or anything significant happening to the machine at all? The steps to isolate the issue are the same regardless of the type of adapter the PC has installed in it. It is common for the IP stack to become corrupted. The first step I would try would be to reset it. The netshell commands are pretty simple. This allows for the user to attempt to repair the issue. In Windows XP TCP/IP is an essential part of the operating system itself and cannot be completely uninstalled.

1. Log into the PC as the administrator.
2. To open a command prompt, click Start and then click Run. Copy and paste (or type) the following command in the Open box and then press ENTER:
   cmd
3. At the command prompt, copy and paste (or type) the following command and then press ENTER:
   netsh int ip reset c:resetlog.txt
4. The following 2 registry keys will be rewritten to reinstall the TCP/IP stacks.
   SYSTEMCurrentControlSetServicesTcpipParameters
   SYSTEMCurrentControlSetServicesDHCPParameters
5. Reboot the computer.

I do not recommend removing the Winsock registry files. There are some fixes that would have you remove Winsock and Winsock2. Generally speaking removing these files is going to create additional .dll errors before any positive changes are noticed. If you have the original CD/DVD that came  with the PC there is another options to repair damage caused by overwriting files from third parties. This is about a 10 minute process and prevents the hassle of reinstalling the operating system completely.

1. Log into the PC as the administrator.
2. Open the command prompt.
3. Type sfc/scannow, press enter.
4. If any repairs are completed, you must restart the computer.

System file checker is a good solution when there is a question about the integrity of a protected file on your PC. Since you are using Windows XP you will need the original installation CD/DVD to complete this command.

If you are using Norton Anti-Virus you can also attempt the following registry edits. There has been a known issue with uninstalling this program. If you don't have an active key for this product remove it before you start using other programs. It creates software conflicts with every other anti-virus program on the market.

1. Log into the PC as the administrator.
2. Start, select Run.
3. Type regedit, click ok.
4. Open the following folders: HKEY_LOCAL_MACHINE, System, CurrentControlSet, Services, DHCP.
5. Double click the key DependOnServices
6. The last item in the list should be SYNTDI. This is the only edit you will make. Remove it.
7. Close regedit.
8. Restart the PC.

If you are comfortable with completing registry edits there are 2 files you will need to look for using the following steps.

1. Log into the PC as the administrator.
2. Start, select run.
3. Type regedt32.exe, click OK.
4. Look for subkeys:
    *HKEY_LOCAL_MACHINESystemCurrentControlSetServicesDHCP
    *HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNetBT
5. Double click the key DependOnServices
6. Delete any references to SYMTDI or NISDRV.
7. Close regedit.
8. Restart the PC.

I offer a warning when editing registry files. If you are not comfortable with completing those changes they are best left alone. Any mistake made there can render your PC completely useless. The error you are receiving is generally one that can be corrected and does not require that you replace the hardware. If you have already tried some of these fixes and still experiencing this error, or if you are not comfortable using the advanced commands I would suggest a clean install of Windows XP. The issue is in the files of the operating system and reinstalling it will resolve the issue. I do not recommend an OS upgrade until the error has been resolved. You don't want to take a chance on upgrading to Vista and have the corrupted file follow you from one OS to another. Good luck and if there are any other questions or errors that occur please post them accordingly.