timgreen7077
asked on
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.
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.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Make sure you are using the VMXNET3 network interface, and not the E1000, so replace the existing network interface.
ASKER
Yes I am using VMXNET3. It has been using that NIC for a while.
have you tried adding a new nic, e1000 or vmxnet3?
just disable the old one, do not remove.
just disable the old one, do not remove.
ASKER
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.
just try adding a e1000 nic.
ASKER
Just tried it and got the same result. This is strange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
someone must have enabled it then, so there was a change to the VM!
same thing happens on a physical computer, if enabled!
same thing happens on a physical computer, if enabled!
ASKER
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.
ASKER
The article pasted shows the fix