Tcp/ip Protocol Driver Service Failed To Start

2 Pages
←
1
2

You cannot start a new topic
You cannot reply to this topic

Tcp/ip Protocol Driver Service Failed To Start system cannot find the file specified

#16 iggyboy

New Member

Group: Members
Posts: 2
Joined: 28-January 11

Posted 28 January 2011 - 02:03 PM

I give to myself a reply! I tried carefully and I could solve a very difficult problem lasting since last Xmas! It was the only method working after a lot of attempts.I thank hublerb and all the forum where I came just today!

#17 tmt1630

New Member

Group: Members
Posts: 1
Joined: 25-June 11

Posted 25 June 2011 - 01:52 PM

hublerb, on 02 April 2007 - 11:50 PM, said:

REALLY REINSTALLING TCP/IP
Complete destruction and restoration of dead TCP/IP stack
Recovery from fatal failure or partial or complete corruption of TCP/IP.
For virus related problems, please consult tcpip.sys to ensure it is not a corrupt version before following these steps.

This solution is an alternative to reinstalling by partial method or by using winnt /unattend which I very much wanted to avoid.

Here is the hardcore method when nothing else is working. I have cobbled together these suggestions through various forums to offer them here as a concise solution. There are no guarantees! Back up anything relevant and set a system restore point to cover your ass. I discovered this method after all other solutions failed.

Related error messages:
"TCP/IP network transport is not installed" error message from active sync
TCP/IP driver missing from devmgmt.msc showing hidden devices
ipconfig produces immediate failure message :
Windows IP Configuration
An Internal error occured: The request is not supported.
Please contact Microsoft Product Support Services for further help.
Additional information: Unable to query host name.
"the specified device instance handle does not correspond to a present device" message regarding DHCP service in services.msc
net start tcpip >>> fails with system error 2, The system cannot find the file specified
ping error: "Unable to contact IP driver, error code 2"
Repair Local Area Connection: Failed to query TCP/IP settings of the connection. Cannot proceed.
"Tcp/ip Protocol Driver Service Failed To Start, system cannot find the file specified"
"The TCP/IP Protocol Driver service failed to start due to the following error: The system cannot find the file specified"

Failed repair methods:
netsh int ip reset resetlog.txt >>> no effect
non-full reinstall of TCP/IP using only the have disk method. >>> no effect
netsh Winsock reset >>> no effect
http://www.snapfiles.com/get/winsockxpfix.html >>> no effect
reinstalling network card >>> no effect

MY SOLUTION:::

Step #1
Full uninstall of TCP/IP ... no bullbleep.
----------------------------------------------------------------------
These steps are copied from http://support.microsoft.com/kb/325356
11. Locate the Nettcpip.inf file in %winroot%\inf, and then open the file in Notepad.
12. Locate the [MS_TCPIP.PrimaryInstall] section.
13. Edit the Characteristics = 0xa0 entry and replace 0xa0 with 0x80.
14. Save the file, and then exit Notepad.
15. In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.
16. On the General tab, click Install, select Protocol, and then click Add.
17. In the Select Network Protocols window, click Have Disk.
18. In the Copy manufacturer's files from: text box, type c:\windows\inf, and then click OK.
19. Select Internet Protocol (TCP/IP), and then click OK.
Note This step will return you to the Local Area Connection Properties screen, but now the Uninstall button is available.
20. Select Internet Protocol (TCP/IP), click Uninstall, and then click Yes.
RESTART

succesfull uninstallation of TCP/IP will remove numerous keys from the registry including
HKLM/system/CurrentControlSet/services/tcpip
HKLM/system/CurrentControlSet/services/dhcp
HKLM/system/CurrentControlSet/services/dnscache
HKLM/system/CurrentControlSet/services/ipsec
HKLM/system/CurrentControlSet/services/policyagent
HKLM/system/CurrentControlSet/services/atmarpc
HKLM/system/CurrentControlSet/services/nla
These represent various interconnected and interdependant services.

For good measure you should delete the following keys before reinstalling TCP/IP in step #2
HKLM/system/CurrentControlSet/services/winsock
HKLM/system/CurrentControlSet/services/winsock2

Step #2
Reinstall of TCP/IP
----------------------------------------------------------------------
Following the above substep #13, replace the 0x80 back to 0xa0, this will eliminate the related "unsigned driver" error that was encountered during the uninstallation phase.

Return to "local area connection"> properties > general tab > install > Protocol > TCP/IP

You may receive an "Extended Error" failure upon trying to reinstall the TCP/IP, this is related to the installer sub-system conflicting with the security database status.

to check the integrity of the security database
esentutl /g c:\windows\security\Database\secedit.sdb

There may be a message saying database is out of date
first try the recovery option
esentutl /r c:\windows\security\Database\secedit.sdb

this did not work for me, I needed the repair option
esentutl /p c:\windows\security\Database\secedit.sdb

rerun the /g option to ensure that integrity is good and database is up to date.

Now return to the "local area network setup"
choose install > protocol > tcp/ip and try again

reboot.
worked for me.

Hublerb, you saved me! This worked perfectly! Thanks! :clapping:

#18 Darkwood

Member

Group: Members
Posts: 15
Joined: 04-May 10

Posted 21 October 2011 - 04:19 PM

I was cleaning up a VERY infected computer, and it couldn't connect to the internet. It turns out that on that computer, it was IPSEC.SYS that was missing. Symptoms were very similar to this thread.

#19 Skisby

New Member

Group: Members
Posts: 1
Joined: 01-November 11

Posted 01 November 2011 - 08:13 PM

I had the same symptoms where:
Connection Repair gets "Failed to query TCP/IP settings of the connection. Cannot proceed."
Ping 127.0.0.1 gets “Unable to contact IP driver, error code 2”
In Device Manager with Show hidden devices, under Non-Plug and Play Drivers, IP Network Address Translator, NetBios over Tcpip, and TCP/IP Protocol Driver all have a yellow exclamation.
The Event Viewer System log shows a number of errors upon boot starting with Event ID 7000: "IPSEC driver service failed to start:... The system cannot find the file specified."

I tried most of the solutions suggested without repairing the problem including:
Winsockfix.exe, replacing tcpip.sys (which wasn’t missing), completely uninstalling then reinstalling the TCP/IP Protocol, and sfc /scannow (not recommended as in my case it made things worse).

What repaired the problem in my case was this:
1. System Restored to an earlier date and time where TCP/IP was working.
2. Xcopied, without overwriting any files, to the %windir%\system32\drivers\ folder from the same folder on a computer with the same hardware, version of windows, and Service Pack. In my case four system files were copied over: cdrom.sys, ipsec.sys, mrxsmb.sys, and netbt.sys.
3. Rebooted and TCP/IP started working.

#20 LvrBrd1892

New Member

Group: Members
Posts: 1
Joined: 06-December 11

Posted 06 December 2011 - 12:11 PM

Skisby, on 01 November 2011 - 08:13 PM, said:

Did you really follow "hublerb, on Apr 2 2007" instructions? The "hublerb, on Apr 2 2007" instructions worked for me and that's why i'd registered in this website.

#21 kmpdev

New Member

Group: Members
Posts: 1
Joined: 21-December 11

Posted 21 December 2011 - 02:30 PM

after trying numerous items across hundreds of websites my final solution was a missing ipsec.sys file. Copied from a good xp machine, rebooted and all worked fine.

before doing that I did the elaborate uninstall and reinstall of TCP/IP, copy of tcpip.sys, copy of lsass.exe, various MS fixes from knowledge base, then registry modifications of dependencies and discovered that ipsec.sys was needed by ipsec (most sites and services say lsass.exe). Once I copied ipsec.sys over (nothing special just from a usb drive using file explorer), rebooted and all internet services started working correctly.

I believe Kaspersky's free anti-virus removal tool deleted the file.

Hope this helps someone!

#22 kk0425

New Member

Group: Members
Posts: 1
Joined: 27-December 11

Posted 27 December 2011 - 11:22 AM

hublerb, on 02 April 2007 - 11:50 PM, said:

Registered just to say thanks x1000 for this reply. I was having problems with my internet connection after removing a rootkit that was installed by xp internet security 2012, and none of the other methods like replacing tcpip.sys, ntbios.sys or acp.sys worked. This is what finally fixed my internet connection!

#23 Lobster1071

New Member

Group: Members
Posts: 1
Joined: 29-December 11

Posted 29 December 2011 - 08:13 PM

hublerb's instructions on "Really Reinstalling TCP/IP" worked great for me as well. Very, very good to know.

A client's system was infected with a rootkit virus. After I removed it, the whole TCP/IP was messed up. It wouldn't connect to the network or internet, and pinging anything from the command prompt would give the error "Unable to contact IP driver, error code 2"

I tried the LSPFIX utility, and every "netsh" reset command known to mankind. Nothing would work accept the TCP/IP fix hublerb posted.

It was much easier to do than it looked, and really saved me.

Thanks again.

#24 gringo_pr

Bleepin Gringo

Group: Malware Response Team
Posts: 85,548
Joined: 03-July 08
Gender:Male
Location:Puerto rico

Posted 02 January 2012 - 01:24 PM

:Run sfc /scannow:

Stop all running programs and make sure you are at a point in time when letting your computer work for a minute isn't going to be a problem.
Get Erunt. With this simple utility you can backup your registry before any changes are made and restore to these saved changes should it become necessary.
Make a registry backup with Erunt before continuing. You can also create a restore point for added insurance. (Start > All programs > Acessories > System tools > System Restore)
Click Start > run > type in sfc /scannow > Press Enter. This is the system file checker. What it does is scour your system and look for windows system files that are corrupt or missing. If it needs a file off of the XP cd it can grab it if you have the XP CD. If you DON'T have the XP cd all is not quite lost yet. We can try restoring system files from your computer's dllcache (which would possibly require a registry change).
After this process is complete you may need to reboot.

Note

I will be online from 5-31 to 6-4 in a very limited amount

I Close My Topics If You Have Not Replied In 5 Days If You Will Be Longer Please Let Me Know

If I Have Not Replied To One Of My Topics In 48 Hrs Please Bump The Topic

Please Only Copy And Paste Reports Into Topic - Do Not Attach

My help is free, however, if you wish to make a small donation to show your appreciation or to help me continue the fight against Malware, then click here -->

<-- Don't worry every little bit helps.

#25 Mubin

New Member

Group: Members
Posts: 1
Joined: 18-January 12

Posted 18 January 2012 - 08:51 AM

hublerb, on 02 April 2007 - 11:50 PM, said:

Signed up to say a big thanks to hublerb for this post. I saw these steps in other forum as well, but first I saw it here. So my thanks to you!!!

#26 LduN

New Member

Group: Members
Posts: 1
Joined: 03-February 12

Posted 03 February 2012 - 11:29 AM

If the steps above don't work try replacing the ipsec.sys file, once I did that it worked like a charm.

#27 3maj-inis

New Member

Group: Members
Posts: 1
Joined: 06-February 12

Posted 06 February 2012 - 07:13 AM

WINDOWS XP SP3
after virus attack

was no tcp/ip
IPCONFIG returned an error message
unable to query host name..........

we tried
1. tcp reset
2 with xp tcp/ip repair
3 with hardcore method of reinstalling tcp
it was not successfull

AFTER REINSTALLING SP3 EVERYTHING WORK FINE

This post has been edited by 3maj-inis: 06 February 2012 - 07:18 AM

#28 JohnnyBoston

New Member

Group: Members
Posts: 1
Joined: 09-April 12

Posted 09 April 2012 - 09:16 PM

hublerb, on 02 April 2007 - 11:50 PM, said:

Like others, I signed up just to say an enormous thanks to Hublerb for this great post! I had followed a dozen dead ends (all on my iPhone - I couldn't connect to the internet on my computer remember?!) before finally coming across this post. I followed all the steps, getting all the messages Hublerb described, rebooted and BINGO!! Thank you so much man - I thought I was staring down the barrel of a complete reinstall. 5 years on and your post is still helping people!

-John