Unable To Connect Ip Driver Error
Jul 04, 2015 SmartPCFixer is your best computer error expert. Get rid of unable to contact ip driver to fix unable to contact ip driver error code 5.
I can t connect my Dell Laptop to my home wireless or wired network. It sees the Wireless network and connects but it never receives an IP address, so it can t access the Internet. I ve tried uninstalling TCP/IP, the network cards and tried connecting directly to the cable modem without any luck. This PC worked fine before my wife took it on a trip. She says that the only thing she did was try to access a wireless network on her return trip. In researching the problem I tried deleting the WINSOCK WINSOCK2 entries from the registries but it didn t help. My guess is that I have corrupted file somewhere. When doing a ipconfig, I get an IP Driver, error code 2 error. Me and 2 other techie friends spent several hours trying to fix the problem to no avail. Has anyone else run across this problem and how did you fix it.
Yes I am using XP. I have tried deleting the WINSOCK WINSOCK2 entries in the registry but it didn t work. I tried doing IPCONFIG /ALL again and got a different message: An Internal Error Occurred. The request is not support. Unable to query host name. Please contact Microsoft.
I ve tried the netdiag /test:winsock but I get an error saying it can t access the TCP/IP entries in the registry. Any ideas on what this may be.
Saw a few posts where resetting the IP stack didn t work but might want to give it a try:
netsh int ip reset log_file_name
the log_file_name needs to be specified.
e.g. - netsh int ip reset ip_reset.txt
I have tried everything I know and two other guys in the office have as well. Any ideas. The only things I can add are when the machine boots it seems to hang I can do some functions command prompt but no access to network properties or exploring computer then it goes blank, and when it reloads everything is running. I installed a copy of Symantec Antivirus Corporate 10, and then tried to update the defs manually with no luck. The NIC passed all bios tests and the Dell32 tests. The lights are on on the NIC but the OS reports it is disconnected. Tried all above suggestions. HELP.
You can rebuild your tcp/ip stack by the following command line
Tried both with a reboot in between each and still no luck. I am at the point to reload OS, but I would love to find the fix.
Tried both with a reboot in between each and still no luck. - What exactly did you try.
Before a reload from scratch, and since you can boot, you might try either a reinstall or repair install. If it works it would sure save a lot of time.
Go to the location of your source files
This is probably the fastest and easiest
1. Insert and boot from your WindowsXP CD
2. At the second R Repair option, press the R key
4. Press F8 for I Agree at the Licensing Agreement
5. Press R when the directory where WindowsXP is installed is shown. Typically this is C: WINDOWS
6. It will then check the C: drive and start copying files
7. It will automatically reboot when needed. Keep the CD in the drive.
8. You will then see the graphic part of the repair that is like during a normal install of XP Collecting Information, Dynamic Update, Preparing Installation, Installing Windows, Finalizing Installation
9. When prompted, click on the Next button
10. When prompted, enter your XP key
11. Normally you will want to keep the same Workgroup or Domain name
13. Then you will have the same screens as a normal XP Install
14. Activate if you want usually a good idea
15. Register if you want but not necessary
17. At this point you should be able to log in with any existing accounts.
Sorry Bob. I tried your suggestions and then the thread after yours. Rebooting in between of course. I am trying the re-install option now.
The automated repair option took care of my problems. Had issues getting the unattended to work. Looks like a bad NIC and somehow that caused the IP issues. Everything is working and now the NIC fails the Dell tests. Thanks. THis was my first use of this board and I will be back.
Glad the repair option worked for you.
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 . I discovered this method after all other solutions failed.
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 :
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
netsh int ip reset resetlog.txt no effect
non-full reinstall of TCP/IP using only the have disk method. no effect
reinstalling network card no effect
----------------------------------------------------------------------
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.
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
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
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
Discussion in Networking started by cgrablew, Jun 30, 2005.
2. Delete the following files - c: windows system32 drivers tcpip.sys c: windows system32 dllcache tcpip.sys
3. From your original XP CD or i386 folder on local HDD find the following file - tcpip.sy_ and then expand this file to locations above eg expand c: i386 tcpip.sy_ c: windows system32 drivers tcpip.sys
4. When both files have been replaced reboot the PC.
So you would probably need to run something like the following -
Many hugs n kisses to hublerb for alternative options to the M way of doing things when refreshing the TCP stack and Winsock.
While this in itself didn t fix my entire problem, I know it didn t do any harm - and I am prepared for next time.
Final set of hugs n kisses to hemburyr for the final suggestion that did resolve the last of my issues following a very nasty trojan infection.
Great work guys. Keep up the good work - as I know you will
I could get NO tcp ip - when I typed ipconfig /all I got an error message
I tried ALL fixes for 3 days straight - reset EVERYTHING, nothing worked, and was just about to reinstall XP and then.
Finally the answer was so simple I am kicking myself - spyware/virus had replaced the tcpip.sys file with a new file.
Just delete tcpip.sys in system/drivers and the backup file created by the spyware tcpip.sys.flg in my case - it will automatically reset this file to the original 2004 file.
I have been working on a similar problem for 2 days now. All of a sudden my computer will not connect to the internet. I have tried several of the things suggested here however I have not yet tried what you did. I know where to find the tcpip.sys file however where do I find the file created by the spyware if there is one.
The spyware tcpip was in the same directory and just had a different file extention tcpip.sys.flg in my case - maybe do a search for anything called tcpip.
If you delete the proper windows version it should automatically re-create it straight away with the archived windows version, or you could try re-installing the latest service pack.
Anyway keep an eye on the date of tcpip.sys - if it is a unique date to the rest of the components in the system32/drivers you ve probably got a spyware version.
Short URL to this thread: https://techguy.org/376765
Oct 07, 2014 Error: unable to contact ip driver, error code 2 not able to connect to internet. HD Netcam I get the following error: Exception: :10 AM Camera 5.
- How to fix Unable To Contact Ip Driver -general Unable To Contact Ip Driver -general Failure error message codes are often triggered in one way or another.
- Crack for dfx7 2,check truck convoy,maplestory patch 55,unable to connect ip driver error code 5. So please help me in getting Ethernet driver code.
- Jul 27, 2001 To work around this problem, remove the NetBEUI protocol, or configurethe TCP/IP protocol correctly.
- Sep 11, 2011 Network Printer Error Message Unable to Connect you may see the following error message: Unable to connect.
- Ping error Unable to contact IP driver, error code 2. unable to connect ip driver error code 2 XP/Vista/7/8/10 Portable. Product Info, Manuals Downloads.
Can't get an IP address - IP Driver Error Code 2
2009. Ping error: Unable to contact IP driver, error code 2. The TCP/IP Error: unable to contact ip driver, error code 2 not able to connect to internet.
