TCPIP Protocol Driver

C

cpaul123

New Member
Reaction score
0
I have a XP SP3 (Home) that had a virus 2012 on it that I think that I removed. After that I was updating all of the virus definitions and running more scans to make sure that I removed the virus. After a reboot I can't get an IP Address and the TCPIP Protocol Driver won't start -> This device is not present, is not working properly, or does not have all its drivers installed (Code 24).

This is what I have done...
Backed up the data to an external drive
Ran Malwarebytes and Superantispyware.
I ran MSERT and it didnt find anything.
I ran Winsock and TCP Repair Utility.
I tried installing a new NIC. - nothing
I tried installing a wireless NIC. - nothing

when i run ipconfig:
An internal error occurred: The request is not supported.
Please contact Microsoft Product Support Services for further help.
Additional Information: Unable to query host name.

I have googled this and tried a number of resolutions still coming back to it not working.
Nothing seems to be working...And I am driving myself crazy.

Has anyone ran into this and can lend me some help.

I booted it to an USB drive with Ubuntu and I was able to get to the internet...so it is definitely something within Windows.

Any help would be greatly appreciated.

THanks!
 
Grab a fresh copy of tcpip.sys from a known healthy XP rig of the same service pack level, copy it in (via command prompt or safe mode w/o network support).

Run into this a few times with some rigs bit by malware that tanks that file.
 
YeOldeStonecat said:
Grab a fresh copy of tcpip.sys from a known healthy XP rig of the same service pack level, copy it in (via command prompt or safe mode w/o network support).

Run into this a few times with some rigs bit by malware that tanks that file.
Click to expand...

You might also grab from that same healthy XP rig a reg export of the services\tcpip registry key if replacing the file doesn't work.
Code: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
 
FoolishTech said:
You might also grab from that same healthy XP rig a reg export of the services\tcpip registry key if replacing the file doesn't work.
Code: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
Click to expand...

Good point...depending on which particular tcp/winsock repair utility he ran...not all of them reset that to the same extent...if at all.
 
i tried the registry file with no luck...i am going to try and replace the tcpip.sys in safe mode now...
 
Dang...that tcpip.sys file has done it on the machines we've had which exhibit the behavior you're describing.

....actually there was one stubborn machine that it didn't work..had to system restore and then copy it over...and it got working again.
 
cpaul123 said:
Replacing the file in safe mode didnt work either...

thanks for the suggestions.
Click to expand...

You could not copy the new tcpip.sys over to the system, or did the new tcpip.sys file not fix the problem? If the first question is the problem, try doing it offline.
 
Last edited:
Okay I am just thinking out loud here.

What about a SFC scan?
How many dependencies are there for the DHCP client service?
What about uninstalling and re-installing the TCP/IP stack?
 
dbdawn -

What about a SFC scan? - ran it and it didnt find anything
How many dependencies are there for the DHCP client service? - AFD, NetBios over Tcpip, and TCP/IP Protocol Driver

What about uninstalling and re-installing the TCP/IP stack? - i did a few times with no luck.

i am re-running SFC scan again...and then trying the latest suggestion...which i think i tried already.
 
i just did the hardcore method and its still not working. I even ran Combo Fix and its service still isnt working.
 
i think i resolved this...i did a search for ipsec.sys and it was located in c:\windows\system32\dllcache so i moved it to the c:\windows\system32\drivers folder and i have an ip address and i can get on the internet...and the TCPIP Protocol Driver is happy...

That was painful!
 
cpaul123 said:
i think i resolved this...i did a search for ipsec.sys and it was located in c:\windows\system32\dllcache so i moved it to the c:\windows\system32\drivers folder and i have an ip address and i can get on the internet...and the TCPIP Protocol Driver is happy...

That was painful!
Click to expand...

I am glad you were able to fix the problem!
 
I've run into something similar on 3 machines last week with the fake scareware 2012 infection. Somewhere in the clean up process some of the networking related files are getting removed or trashed. With two of them the netbt.sys file was removed from Windows/System32/Drivers directory and replacing the file from an XP disk and rebooting solved the problem. Another was the TCPIP file you mentioned. I spent HOURS and HOURS working on this and finally got it fixed by copying over the TCPIP, netbt and one other sys file but the name of it has escaped me now.

I had the same thing happen again today on replacing the netbt.sys file worked again. What I found was, the DHCP service would not start because of dependency issues. Not sure what's going on and why these files are getting trashed but it can be a huge pain, that's for sure and it doesn't seem to be the exact same thing happening on ever machine, even though they are all XP and the infections are the same.
 
Well I spoke too soon! I'm having the same problem as OP and none of my methods have worked nor anything he suggested. GRRRR!!!
 
You must log in or register to reply here.

Similar threads

Appletax
[SOLVED] Intel Rapid Restore Driver Causes BSOD - DRIVER_POWER_STATE_FAILURE
Replies
3
Views
555
Appletax
Appletax
HCHTech
Quickbooks Enterprise 2024 multi-user issues
Replies
7
Views
226
Markverhyden
Markverhyden
Appletax
[SOLVED] Computer occasionally deletes audio drivers on Dell Vostro 7500
Replies
3
Views
559
Appletax
Appletax
sapphirescales
Looking For a Driver That Doesn't Seem to Exist
Replies
15
Views
767
sapphirescales
sapphirescales
frase
TPM CODE 15 ERROR
Replies
7
Views
354
lan101
lan101
Back
Top