Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 614
  • Last Modified:

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.
0
timgreen7077
Asked:
timgreen7077
  • 6
  • 4
1 Solution
 
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
 
timgreen7077Author Commented:
Yes I am using VMXNET3. It has been using that NIC for a while.
0
 
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
Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

 
timgreen7077Author 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
 
timgreen7077Author Commented:
Just tried it and got the same result. This is strange.
0
 
timgreen7077Author 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:
someone must have enabled it then, so there was a change to the VM!

same thing happens on a physical computer, if enabled!
0
 
timgreen7077Author 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
 
timgreen7077Author Commented:
The article pasted shows the fix
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now