Cheers, padiap 0 LVL 59 Overall: Level 59 Windows Server 2008 47 Message Expert Comment by:Darius Ghassem2009-05-26 Once you did the reset did you restart the computer? 0 Message This is actually kind of interesting, was this VMware, Hyper-V or something else? There is an easy way to manage all of these requests... Meanwhile, download and update the network driver to the latest version. https://www.experts-exchange.com/questions/24347520/Windows-Server-2008-Network-Issues-Unable-to-contact-IP-driver-error-code-1753.html
Compatibility: Windows 7, 8, Vista, XP Download Size: 6MB Requirements: 300 MHz Processor, 256 MB Ram, 22 MB HDD Limitations: This download is a free evaluation version. Login. This article contains information that shows you how to fix Unable To Contact Ip Driver Error Code 1753 Vmware both (manually) and (automatically) , In addition, this article will help you In my case the box responded to pings too, the problem was weird Winsock corruption. –Corey May 20 '09 at 13:56 add a comment| up vote 0 down vote I've run
Personal tools Namespaces Article Search Main Page Applications AOL Internet Explorer MS Outlook Outlook Express Windows Live DLL Errors Exe Errors Ocx Errors Operating Systems Windows 7 Windows Others Windows This website should be used for informational purposes only. Edit: Can't ping anything if I don't login with the built-in Administrator account. (UAC on or off makes no different.) Can't ping 127.0.0.1 (access denied). The NIC is physically OK, I've both tried with another one and tried booting from a live Linux CD.
Thanks for the suggestion! cyr0n_k0r, Feb 21, 2010 cyr0n_k0r, Feb 21, 2010 #2 Feb 21, 2010 #3 xenios Gawd Messages: 992 Joined: Aug 8, 2008 where both machines vm's? More references: Windows 2008 Corrupt TCP/IP? (Ping access denied) Fixing a failed Hyper-V Guest Network Adapter Please note: we provide the third party link for technical reference. This issue is caused by not deploying properly with sysprep (system SID needs t be recreated) Thank you, Jon Edited by jonhwilliams Friday, March 18, 2016 5:33 PM Friday, March 18,
MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Courses Contribute Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store Headlines Website Testing Ask a Question If you want to give it a shot, just back up HKLM\SYSTEM\CurrentControlSet\Services\WinSock and HKLM\SYSTEM\CurrentControlSet\Services\WinSock2 first to be safe. Double click on the reg files to register, reboot the system to see how it works. This can be beneficial to other community members reading the thread. ” Proposed as answer by Kuricheti Monday, January 25, 2016 7:15 AM Tuesday, December 07, 2010 6:12 AM Reply |
Are you aComputer / IT professional?Join Tek-Tips Forums! http://www.tek-tips.com/viewthread.cfm?qid=1693938 Solved Windows Server 2008 Network Issues - Unable to contact IP driver error code 1753 Posted on 2009-04-22 Windows Server 2008 2 Verified Solutions 7 Comments 4,911 Views Last Modified: 2012-05-06 Generated Mon, 31 Oct 2016 00:27:18 GMT by s_hp90 (squid/3.5.20) You could try to point to the following registry paths: HKLM\SYSTEM\CurrentControlSet\Services\WinSock HKLM\SYSTEM\CurrentControlSet\Services\WinSock2 Backup the above registry.
As long as I leave the NIC on dHCP it works; After reconfiguring the new NICs for static IP address the issue is recurring. check over here Disabling the firewall doesn't seem to change anything. –MichaelGG May 20 '09 at 3:54 Not even local host? RE: Ping returns error code 1753 technome (IS/IT--Management) 5 Oct 12 10:14 "among them Server, Workstation and DNS" basically the primary organs of SBS are not functioning; a NIC/driver is an Download from here and here.
Join & Ask a Question Need Help in Real-Time? BTW, since the problemoccurs in Hyper-V, please post in our Hyper-V forums for a better assistance. Register now while it's still free! his comment is here general failure' i can not even ping the local loopback address 127.0.0.1 any help is much appreciated thanks rr Monday, December 06, 2010 5:13 PM Reply | Quote Answers 0
asked 7 years ago viewed 12203 times active 4 years ago Related 0Is netsh available on 64-bit Windows Server 2008?4Why is using ntrights.exe in Windows Server 2008 R2 giving error openpolicy I do NOT get this problem when logged in as a local administrator, or Domain accounts that are administrators or domain admins. Unlikely a NIC/driver issue, just a symptom.
C:\Users\c01>ping www.google.com Unable to contact IP driver. have you reset the services to default? Also i can not see any event id's being logged rr Tuesday, December 07, 2010 11:34 AM Reply | Quote 0 Sign in to vote I’m sorry to not notice Already a member?
But as soon as I log in as a user account without any special elevated permissions I am having the above error. Don’t let it get you down! The first vm was a cloned from my master image and promoted to a domain controller. http://centralpedia.com/unable-to/unable-to-contact-ip-driver-error-code-1753-windows-2008.html Please pay attention to perform the action.
Only ask questions with yes/no answers if you want "yes" or "no" RE: Ping returns error code 1753 utedasset (TechnicalUser) (OP) 22 Sep 12 02:48 ipconfig /all looks OK, nothing in It also seems NewSID has been retired (because everyone thinks it doesnt matter), and it also isn't supported on Server 2008. Click here follow the steps to fix Unable To Contact Ip Driver Error Code 1753 Vmware and related errors. Unable To Contact Ip Driver Error Code 1753 Vmware Error Codes are caused in one way or another by misconfigured system files in your windows operating system.