 Tcp/ip Protocol Driver Service Failed To Start, system cannot find the file specified |
Welcome Guest ( Log In | Click here to Register a free account now! )
Register a free account to unlock additional features at BleepingComputer.com
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.  |
 Mar 14 2007, 04:16 PM
Post
#1
|
|
|
New Member  Group: Members Posts: 1 Joined: 14-March 07 Member No.: 117,527  |
Today, I tried a wired connection which failed as well. Further investigation revealed this entry in the event log: "The TCP/IP Protocol Driver service failed to start due to the following error: The system cannot find the file specified. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp" The EventID is 7000 if that helps anyone. The link was no help to me. I have googled to exhaustion, but haven't found a solution. How do I fix this? How do I determine what file is missing, find it, and restore it? I need to use that computer to do some work for a client, so need to fix this ASAP. Please help me. Laz |
 |
 
|
|
Mar 14 2007, 04:37 PM
Post
#2
|
|
 Senior Member Group: Members Posts: 356 Joined: 29-April 05 From: New Zealand Member No.: 18,496 |
I take it this is everytime you start your laptop up? Try and start the service manually if that doesn't work then you may have to re-install Windows onto your laptop. It is not usual for the TCP/IP service to fail.
-------------------- I came, I saw, I conquered. - Julius Caeser
|
|
|
|
|
Mar 14 2007, 06:32 PM
Post
#3
|
|
 Forum Addict Group: HJT Junior Classmen Posts: 3,277 Joined: 7-January 07 From: UK Member No.: 105,123 |
Hello,
Are you on XP? If so, you can go to control panel, and select network connections, right click on the adapter that is causing you problems, select properties. on the new window that has opened, go through the list and see if internet protocol tcp/ip is there, if it isn't there, click install select protocol then select internet protocol tcp/ip from the list and install it. reboot and see if it all works. What security set up are you running, it might be prudent to post a hijackthis log in bleeping computers forum, just to be sure. Hope this helps -------------------- Regards
Alan |
|
|
|
|
Apr 2 2007, 11:50 PM
Post
#4
|
|
|
New Member Group: Members Posts: 1 Joined: 2-April 07 Member No.: 121,725 |
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. |
|
|
|
|
Dec 11 2007, 04:20 PM
Post
#5
|
|
|
New Member Group: Members Posts: 2 Joined: 11-December 07 Member No.: 175,893 |
Replacing the tcpip.sys worked for me. Found the problem PC had a WINLOGON hook infection. After fixing that, and finding no networking services, I discovered that tcpip.sys has been modified that very day. Replaced it with a copy from a good XP machine and all is well now....
|
|
|
|
|
Jun 29 2008, 07:18 AM
Post
#6
|
|
|
New Member Group: Members Posts: 1 Joined: 29-June 08 Member No.: 219,337 |
QUOTE(ricroz @ Dec 12 2007, 07:20 AM)  Replacing the tcpip.sys worked for me. Thanks for the tip, that really saved me some hassle. In my case, Windows noticed I'd replaced it (from my working machine) and wanted to restore it, and asked for the XP SP2 CD. That worked and after a reboot, seems okay now. Think I'll go run a virus check on it now ... Thanks again. Edit: yep was a virus, "Heur.Worm" running as a fake csrss.exe This post has been edited by aaardvark: Jun 29 2008, 07:44 AM |
|
|
|
|
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 5th September 2008 - 12:15 PM |
© 2003-2008 All Rights Reserved Bleeping Computer LLC.