VMWare

I have a VM that is running on a ESXi 5.1 update1a, and them VM is Win2003 R2, and vmware tools are installed. Just yesterday all of a sudden this VM can no longer connect to the network, in other words it can't ping anything including its own gateway, or any VMs that reside on the same standard switch portgroup. VMs that attempts to ping this VM also fails. Nothing has changed with the VM. I tried the following:

Disconnect/reconnect NIC
Remove and recreate NIC
vMotion VM in same cluster and vMotioned in different cluster
Connected old NIC and new NIC to DHCP port group and it failed to get a DHCP address
Repaired NIC using windows network repair
Cleared DNS cache
Rebuilt TCP/IP stack
Updated VMware tools

It's strange because it has a static IP and it still fails to connect to any network computer and they can't connect to it, via it's DNS name or IP address. The NIC on the VM shows connected and not disconnected, everything looks good. Any help or ideas would be great. Other VMs running on the same hosts and port group are experiencing no issues.
LVL 16
timgreen7077Exchange EngineerAsked:
Who is Participating?
 
timgreen7077Exchange EngineerAuthor Commented:
I found and article that mentioned disabling the IPSec service and rebooting the machine, and this fixed the issue.

http://www.conetrix.com/Blog/post/IPSEC-fails-to-start-with-Error-2-The-system-cannot-find-the-file-specified.aspx
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Make sure you are using the VMXNET3 network interface, and not the E1000, so replace the existing network interface.
0
 
timgreen7077Exchange EngineerAuthor Commented:
Yes I am using VMXNET3. It has been using that NIC for a while.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
have you tried adding a new nic, e1000 or vmxnet3?

just disable the old one, do not remove.
0
 
timgreen7077Exchange EngineerAuthor Commented:
Yes I have tried that. I added another VMXNET 3, I didn't try adding E1000, I disabled 1 VMXNET3 and tried using the new one, but failed. I even tried puting it in the DHCP port group but that failed to obtain and IP from DHCP.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
just try adding a e1000 nic.
0
 
timgreen7077Exchange EngineerAuthor Commented:
Just tried it and got the same result. This is strange.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
someone must have enabled it then, so there was a change to the VM!

same thing happens on a physical computer, if enabled!
0
 
timgreen7077Exchange EngineerAuthor Commented:
No one enabled it, unless it was enabled with a hotfix or patch automatically. Strange but its working now, and thanks for your help and time.
0
 
timgreen7077Exchange EngineerAuthor Commented:
The article pasted shows the fix
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.