IPCONFIG error, An internal error occurred. The request is not supported - No network connection
This happened after spyware/virus removal.
Network card is an Intel(R) Pro/100 VE diagnostics test ok.
I have performed the following attempts to repair
1. remove and re-install NIC
2. delete registry keys for WinSock and WinSock2
3. netsh int ip reset ipreset_log.txt
4. uninstall TCP/IP protocol driver, re-install
5. uninstall Intel Lan software
6. replace tcpip.sys in system32
7. Windows XP installation repair
any suggestions?
Network card is an Intel(R) Pro/100 VE diagnostics test ok.
I have performed the following attempts to repair
1. remove and re-install NIC
2. delete registry keys for WinSock and WinSock2
3. netsh int ip reset ipreset_log.txt
4. uninstall TCP/IP protocol driver, re-install
5. uninstall Intel Lan software
6. replace tcpip.sys in system32
7. Windows XP installation repair
any suggestions?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
phimuskapsi
No hidden devices
No hidden devices
1. Click Start, click Run, type Msinfo32, and then click OK.
2. Expand Components, expand Network, and then click Protocol.
3. You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
" MSAFD Tcpip [TCP/IP]
" MSAFD Tcpip [UDP/IP]
" RSVP UDP Service Provider
" RSVP TCP Service Provider
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
If the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on, such as proxy software, installed.
If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.
If there are more than ten sections in the list, you have third-party additions installed.
If there are fewer than ten sections, there is information missing.
Note These entries represent an installation with only the TCP/IP protocol installed. You can have a working Winsock and see additional entries if another protocol is installed. For example, if you install NWLink IPX/SPX, you will see 7 additional sections, for a total of 17. Below is an example heading of one of the new sections:
MSAFD nwlnkipx [IPX]
Also, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters.
If the Netdiag test fails, or if you determined that there is Winsock corruption by looking at Msinfo32, you must repair the Winsock2 key by using the steps in the next section.
Manual steps to recover from Winsock2 corruption
Windows XP with Service Pack 2 instructions
To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed, type netsh winsock reset at the command prompt, and then press ENTER.
Note Restart the computer after you run this command. Additionally, for computers that are running Windows XP SP2, there is a new netsh command that can rebuild the Winsock key. For more information, visit the following Web site:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx (http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx)
Warning Programs that access or monitor the Internet such as antivirus, firewall, or proxy clients may be negatively affected when you run the netsh winsock reset command. If you have a program that no longer functions correctly after you use this resolution, reinstall the program to restore functionality.
Note If these steps do not resolve the problem, follow the steps in the next section.
Windows XP without Service Pack 2 instructions
To repair Winsock if you do not have Windows XP SP2 installed, delete the corrupted registry keys, and then reinstall the TCP/IP protocol.
Step 1: Delete the corrupted registry keys
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
For more information about how to back up the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/) How to back up, edit, and restore the registry in Windows XP and Windows Server 2003
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. In Registry Editor, locate the following keys, right-click each key, and then click Delete:
HKEY_LOCAL_MACHINE\System\
HKEY_LOCAL_MACHINE\System\
4. When you are prompted to confirm the deletion, click Yes.
Note Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.
Step 2: Install TCP/IP
1. Right-click the network connection, and then click Properties.
2. Click Install.
3. Click Protocol, and then click Add.
4. Click Have Disk.
5. Type C:\Windows\inf, and then click OK.
6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.
If Internet Protocol (TCP/IP) does not appear, follow these steps:
a. Click Start, and then click Search.
b. In the Search Companion pane, click More advanced options.
c. Click to select the following three check boxes:
" Search system folders
" Search hidden files and folders
" Search subfolders
d. In the All or part of the file name box, type nettcpip.inf, and then click Search.
e. In the results pane, right-click Nettcpip.inf, and then click Install.
7. Restart the computer.
2. Expand Components, expand Network, and then click Protocol.
3. You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
" MSAFD Tcpip [TCP/IP]
" MSAFD Tcpip [UDP/IP]
" RSVP UDP Service Provider
" RSVP TCP Service Provider
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
" MSAFD NetBIOS [\Device\NetBT_Tcpip...
If the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on, such as proxy software, installed.
If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.
If there are more than ten sections in the list, you have third-party additions installed.
If there are fewer than ten sections, there is information missing.
Note These entries represent an installation with only the TCP/IP protocol installed. You can have a working Winsock and see additional entries if another protocol is installed. For example, if you install NWLink IPX/SPX, you will see 7 additional sections, for a total of 17. Below is an example heading of one of the new sections:
MSAFD nwlnkipx [IPX]
Also, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters.
If the Netdiag test fails, or if you determined that there is Winsock corruption by looking at Msinfo32, you must repair the Winsock2 key by using the steps in the next section.
Manual steps to recover from Winsock2 corruption
Windows XP with Service Pack 2 instructions
To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed, type netsh winsock reset at the command prompt, and then press ENTER.
Note Restart the computer after you run this command. Additionally, for computers that are running Windows XP SP2, there is a new netsh command that can rebuild the Winsock key. For more information, visit the following Web site:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx (http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx)
Warning Programs that access or monitor the Internet such as antivirus, firewall, or proxy clients may be negatively affected when you run the netsh winsock reset command. If you have a program that no longer functions correctly after you use this resolution, reinstall the program to restore functionality.
Note If these steps do not resolve the problem, follow the steps in the next section.
Windows XP without Service Pack 2 instructions
To repair Winsock if you do not have Windows XP SP2 installed, delete the corrupted registry keys, and then reinstall the TCP/IP protocol.
Step 1: Delete the corrupted registry keys
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
For more information about how to back up the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/) How to back up, edit, and restore the registry in Windows XP and Windows Server 2003
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. In Registry Editor, locate the following keys, right-click each key, and then click Delete:
HKEY_LOCAL_MACHINE\System\
HKEY_LOCAL_MACHINE\System\
4. When you are prompted to confirm the deletion, click Yes.
Note Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.
Step 2: Install TCP/IP
1. Right-click the network connection, and then click Properties.
2. Click Install.
3. Click Protocol, and then click Add.
4. Click Have Disk.
5. Type C:\Windows\inf, and then click OK.
6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.
If Internet Protocol (TCP/IP) does not appear, follow these steps:
a. Click Start, and then click Search.
b. In the Search Companion pane, click More advanced options.
c. Click to select the following three check boxes:
" Search system folders
" Search hidden files and folders
" Search subfolders
d. In the All or part of the file name box, type nettcpip.inf, and then click Search.
e. In the results pane, right-click Nettcpip.inf, and then click Install.
7. Restart the computer.
Another thing have you tried this:
cmd
C:\Windows\System32\ipconf
If that works then your environment variables are screwed up...
- right click on my computer
- select advanced tab
- select environment variables
- edit path
so it only reads PATH=C:\WINDOWS\SYSTEM32;C
cmd
C:\Windows\System32\ipconf
If that works then your environment variables are screwed up...
- right click on my computer
- select advanced tab
- select environment variables
- edit path
so it only reads PATH=C:\WINDOWS\SYSTEM32;C
ASKER
Logfile of Trend Micro HijackThis v2.0.0 (BETA)
Scan saved at 2:13:20 PM, on 8/22/2007
Platform: Windows XP SP2 (WinNT 5.01.2600)
Boot mode: Normal
Running processes:
C:\WINDOWS\System32\smss.e
C:\WINDOWS\system32\winlog
C:\WINDOWS\system32\servic
C:\WINDOWS\system32\lsass.
C:\WINDOWS\system32\svchos
C:\Program Files\Windows Defender\MsMpEng.exe
C:\WINDOWS\System32\svchos
C:\WINDOWS\system32\spools
C:\WINDOWS\Explorer.EXE
C:\Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe
C:\WINDOWS\System32\svchos
C:\Program Files\Analog Devices\Core\smax4pnp.exe
C:\Program Files\Common Files\InstallShield\Update
C:\Program Files\Common Files\Real\Update_OB\reals
C:\Program Files\Windows Defender\MSASCui.exe
C:\Program Files\QuickTime\qttask.exe
C:\Program Files\Adobe\Reader 8.0\Reader\Reader_sl.exe
C:\WINDOWS\system32\hkcmd.
C:\WINDOWS\system32\igfxpe
C:\WINDOWS\system32\ctfmon
C:\WINDOWS\system32\wuaucl
C:\Documents and Settings\agr\Desktop\icspo
C:\Program Files\Spybot - Search & Destroy\SpybotSD.exe
O2 - BHO: Yahoo! Toolbar Helper - {02478D38-C3F9-4EFB-9B51-7
O2 - BHO: Adobe PDF Reader Link Helper - {06849E9F-C8D7-4D59-B87D-7
O2 - BHO: (no name) - {53707962-6F74-2D53-2644-2
O3 - Toolbar: Yahoo! Toolbar - {EF99BD32-C1FB-11D2-892F-0
O4 - HKLM\..\Run: [SoundMAXPnP] C:\Program Files\Analog Devices\Core\smax4pnp.exe
O4 - HKLM\..\Run: [ISUSPM Startup] C:\PROGRA~1\COMMON~1\INSTA
O4 - HKLM\..\Run: [ISUSScheduler] "C:\Program Files\Common Files\InstallShield\Update
O4 - HKLM\..\Run: [TkBellExe] "C:\Program Files\Common Files\Real\Update_OB\reals
O4 - HKLM\..\Run: [Windows Defender] "C:\Program Files\Windows Defender\MSASCui.exe" -hide
O4 - HKLM\..\Run: [QuickTime Task] "C:\Program Files\QuickTime\qttask.exe
O4 - HKLM\..\Run: [Adobe Reader Speed Launcher] "C:\Program Files\Adobe\Reader 8.0\Reader\Reader_sl.exe"
O4 - HKLM\..\Run: [igfxtray] C:\WINDOWS\system32\igfxtr
O4 - HKLM\..\Run: [igfxhkcmd] C:\WINDOWS\system32\hkcmd.
O4 - HKLM\..\Run: [igfxpers] C:\WINDOWS\system32\igfxpe
O4 - HKCU\..\Run: [ctfmon.exe] C:\WINDOWS\system32\ctfmon
O4 - HKUS\S-1-5-18\..\Run: [DWQueuedReporting] "C:\PROGRA~1\COMMON~1\MICR
O4 - HKUS\S-1-5-18\..\RunOnce: [RunNarrator] Narrator.exe (User 'SYSTEM')
O4 - HKUS\.DEFAULT\..\Run: [DWQueuedReporting] "C:\PROGRA~1\COMMON~1\MICR
O4 - HKUS\.DEFAULT\..\RunOnce: [RunNarrator] Narrator.exe (User 'Default user')
O4 - Global Startup: Microsoft Office.lnk = C:\Program Files\Microsoft Office\Office10\OSA.EXE
O6 - HKCU\Software\Policies\Mic
O6 - HKCU\Software\Policies\Mic
O9 - Extra button: (no name) - {08B0E5C0-4FCB-11CF-AAA5-0
O9 - Extra 'Tools' menuitem: Sun Java Console - {08B0E5C0-4FCB-11CF-AAA5-0
O9 - Extra button: Research - {92780B25-18CC-41C8-B9BE-3
O9 - Extra button: Messenger - {FB5F1910-F110-11d2-BB9E-0
O9 - Extra 'Tools' menuitem: Windows Messenger - {FB5F1910-F110-11d2-BB9E-0
O10 - Unknown file in Winsock LSP: c:\windows\system32\nwprov
O16 - DPF: {02BF25D5-8C17-4B23-BC80-D
O16 - DPF: {13EC55CF-D993-475B-9ACA-F
O16 - DPF: {30528230-99f7-4bb4-88d8-f
O16 - DPF: {406B5949-7190-4245-91A9-3
O16 - DPF: {41F17733-B041-4099-A042-B
O16 - DPF: {4F1E5B1A-2A80-42CA-8532-2
O16 - DPF: {55E515F7-0FA2-4610-874E-0
O16 - DPF: {5ED80217-570B-4DA9-BF44-B
O16 - DPF: {B38870E4-7ECB-40DA-8C6A-5
O17 - HKLM\Software\..\Telephony
O22 - SharedTaskScheduler: Browseui preloader - {438755C2-A8BA-11D1-B96B-0
O22 - SharedTaskScheduler: Component Categories cache daemon - {8C7461EF-2B13-11d2-BE35-3
O24 - Desktop Component 0: (no name) - C:\Program Files\Messenger\profsyvyr.
--
End of file - 5684 bytes
Scan saved at 2:13:20 PM, on 8/22/2007
Platform: Windows XP SP2 (WinNT 5.01.2600)
Boot mode: Normal
Running processes:
C:\WINDOWS\System32\smss.e
C:\WINDOWS\system32\winlog
C:\WINDOWS\system32\servic
C:\WINDOWS\system32\lsass.
C:\WINDOWS\system32\svchos
C:\Program Files\Windows Defender\MsMpEng.exe
C:\WINDOWS\System32\svchos
C:\WINDOWS\system32\spools
C:\WINDOWS\Explorer.EXE
C:\Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe
C:\WINDOWS\System32\svchos
C:\Program Files\Analog Devices\Core\smax4pnp.exe
C:\Program Files\Common Files\InstallShield\Update
C:\Program Files\Common Files\Real\Update_OB\reals
C:\Program Files\Windows Defender\MSASCui.exe
C:\Program Files\QuickTime\qttask.exe
C:\Program Files\Adobe\Reader 8.0\Reader\Reader_sl.exe
C:\WINDOWS\system32\hkcmd.
C:\WINDOWS\system32\igfxpe
C:\WINDOWS\system32\ctfmon
C:\WINDOWS\system32\wuaucl
C:\Documents and Settings\agr\Desktop\icspo
C:\Program Files\Spybot - Search & Destroy\SpybotSD.exe
O2 - BHO: Yahoo! Toolbar Helper - {02478D38-C3F9-4EFB-9B51-7
O2 - BHO: Adobe PDF Reader Link Helper - {06849E9F-C8D7-4D59-B87D-7
O2 - BHO: (no name) - {53707962-6F74-2D53-2644-2
O3 - Toolbar: Yahoo! Toolbar - {EF99BD32-C1FB-11D2-892F-0
O4 - HKLM\..\Run: [SoundMAXPnP] C:\Program Files\Analog Devices\Core\smax4pnp.exe
O4 - HKLM\..\Run: [ISUSPM Startup] C:\PROGRA~1\COMMON~1\INSTA
O4 - HKLM\..\Run: [ISUSScheduler] "C:\Program Files\Common Files\InstallShield\Update
O4 - HKLM\..\Run: [TkBellExe] "C:\Program Files\Common Files\Real\Update_OB\reals
O4 - HKLM\..\Run: [Windows Defender] "C:\Program Files\Windows Defender\MSASCui.exe" -hide
O4 - HKLM\..\Run: [QuickTime Task] "C:\Program Files\QuickTime\qttask.exe
O4 - HKLM\..\Run: [Adobe Reader Speed Launcher] "C:\Program Files\Adobe\Reader 8.0\Reader\Reader_sl.exe"
O4 - HKLM\..\Run: [igfxtray] C:\WINDOWS\system32\igfxtr
O4 - HKLM\..\Run: [igfxhkcmd] C:\WINDOWS\system32\hkcmd.
O4 - HKLM\..\Run: [igfxpers] C:\WINDOWS\system32\igfxpe
O4 - HKCU\..\Run: [ctfmon.exe] C:\WINDOWS\system32\ctfmon
O4 - HKUS\S-1-5-18\..\Run: [DWQueuedReporting] "C:\PROGRA~1\COMMON~1\MICR
O4 - HKUS\S-1-5-18\..\RunOnce: [RunNarrator] Narrator.exe (User 'SYSTEM')
O4 - HKUS\.DEFAULT\..\Run: [DWQueuedReporting] "C:\PROGRA~1\COMMON~1\MICR
O4 - HKUS\.DEFAULT\..\RunOnce: [RunNarrator] Narrator.exe (User 'Default user')
O4 - Global Startup: Microsoft Office.lnk = C:\Program Files\Microsoft Office\Office10\OSA.EXE
O6 - HKCU\Software\Policies\Mic
O6 - HKCU\Software\Policies\Mic
O9 - Extra button: (no name) - {08B0E5C0-4FCB-11CF-AAA5-0
O9 - Extra 'Tools' menuitem: Sun Java Console - {08B0E5C0-4FCB-11CF-AAA5-0
O9 - Extra button: Research - {92780B25-18CC-41C8-B9BE-3
O9 - Extra button: Messenger - {FB5F1910-F110-11d2-BB9E-0
O9 - Extra 'Tools' menuitem: Windows Messenger - {FB5F1910-F110-11d2-BB9E-0
O10 - Unknown file in Winsock LSP: c:\windows\system32\nwprov
O16 - DPF: {02BF25D5-8C17-4B23-BC80-D
O16 - DPF: {13EC55CF-D993-475B-9ACA-F
O16 - DPF: {30528230-99f7-4bb4-88d8-f
O16 - DPF: {406B5949-7190-4245-91A9-3
O16 - DPF: {41F17733-B041-4099-A042-B
O16 - DPF: {4F1E5B1A-2A80-42CA-8532-2
O16 - DPF: {55E515F7-0FA2-4610-874E-0
O16 - DPF: {5ED80217-570B-4DA9-BF44-B
O16 - DPF: {B38870E4-7ECB-40DA-8C6A-5
O17 - HKLM\Software\..\Telephony
O22 - SharedTaskScheduler: Browseui preloader - {438755C2-A8BA-11D1-B96B-0
O22 - SharedTaskScheduler: Component Categories cache daemon - {8C7461EF-2B13-11d2-BE35-3
O24 - Desktop Component 0: (no name) - C:\Program Files\Messenger\profsyvyr.
--
End of file - 5684 bytes
Well the HJT log was pretty much useless, according to this it's clean...at this point I think all I can recommend is a total windows reinstall or try deleting all the protocols associated with the LAN adapter then reboot.
remove AV remove FIrewall restart ..try..remove not disable ...apart from the win firewall
ASKER
I have created a backup, will format reinstall and restore backup to see if issue comes back.
ASKER
Although no solution found I will give points as:
100 to souseran for being the first answer
and
400 to phimuskapsi for providing the most complete answers.
100 to souseran for being the first answer
and
400 to phimuskapsi for providing the most complete answers.
bmsjeff:
I had the same issue on one of my home PCs, googled for a few hours finally found this info on a different site. Thought I would post it here. I copied the file from my laptop to the desktop, and the problem was resolved.
"The file tcpip.sys in system32\driver is broken or missing.
expand from CDi386 or copy from others"
I had the same issue on one of my home PCs, googled for a few hours finally found this info on a different site. Thought I would post it here. I copied the file from my laptop to the desktop, and the problem was resolved.
"The file tcpip.sys in system32\driver is broken or missing.
expand from CDi386 or copy from others"
ASKER
I had replaced the tcpip.sys file. This didn't resolve the issue.
Did you tried to reset the winsock as following
netsh > winsock > reset
you will need to restart your computer after that and everything will get back as normal.
netsh > winsock > reset
you will need to restart your computer after that and everything will get back as normal.
This worked for me
http://se9.blogspot.com/2007/02/internal-error-occurred-ipconfig.html
If you encountered "An internal error occurred..." message while running ipconfig from the Windows command line, check that "Routing and Remote Access" (via services.msc) is enabled.
http://se9.blogspot.com/2007/02/internal-error-occurred-ipconfig.html
If you encountered "An internal error occurred..." message while running ipconfig from the Windows command line, check that "Routing and Remote Access" (via services.msc) is enabled.
Simply open the registry editor and dellete the following and reboot.
HKEY_LOCAL_MACHINE\System\
ck
>HKEY_LOCAL_MACHINE\System
ck2
HKEY_LOCAL_MACHINE\System\
ck
>HKEY_LOCAL_MACHINE\System
ck2
Like the author I had seemedly tried everything without resolve. The comment at bottom by IRH actually helped a lot. I enabled routing and remote access and IP config worked. However keep in mind I checked a similar laptop and this service was disabled yet IP config worked fine on that laptop. Not sure what the relation is for this laptop and why enabling this service is required in order for IPConfig to work. UPDATE: Also I just noticed when routing and remote access service is enabled and IPconfig was run it was not showing one of my network adapters (the hard wired). I updated the drivers on the internal ethernet card and used the method that allows windows to find the driver (selected yes one time only). This found a driver and installed. After that, ipconfig would work with Routing and remote access service disabled. I will see if this is a permenant solution.
ASKER