polizei11
asked on
Virtual Machines Lost Internet, Windows Server 2012
I have a Windows Server 2012 Standard (all updates) with 2 Virtual machines running. Both VM's are setup as 2012 Server as Active Directory Controllers. Both these VM's have been running in this configuration for 4 years. Yesterday they suddenly stopped communicating with the Internet. I can ping each machine from the other but I can not ping the Firewall. From the host machine I can ping the VM's but not vice versa.
David Johnson, CD
Ensure that the vm's are using an external virtual switch.
ASKER
As I stated in my post these machines have been successfully running for 4 years, all items are running, including using the virtual switch, set for outward communication.
My thinking is someone or something may have changed the switch properties, you checked and the switch defined in the virtual machines is in fact a external virtual switch? Just a belt and suspenders check. Is the physical network adapter that the vm's are using plugged in and operational?
ASKER
There were no changes to the system, Yes I checked the switches. and Yes the host machine has internet access with only a single connection.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"Nothing changed" and "they gave been running for four years" will nit resolve your issue.
Having the situation you are, following the suggestions provided which are:
1) confirm the host settings for the switch, as well as making sure no physical network changes were made, I.e. Switches retired, replaced, ..
2) confirm each VM's setting in accessing the LAN is as expected
updates are likely a coincidence I.e. Applied updates, rebooted, host, VMs other changes having been made in the physical environment manifested following a reboot.
....
Having the situation you are, following the suggestions provided which are:
1) confirm the host settings for the switch, as well as making sure no physical network changes were made, I.e. Switches retired, replaced, ..
2) confirm each VM's setting in accessing the LAN is as expected
updates are likely a coincidence I.e. Applied updates, rebooted, host, VMs other changes having been made in the physical environment manifested following a reboot.
....
ASKER
I should have said, there was ‘no changes as there was no access to this system by anyone but me’ updates are done quarterly an has been 2 months since updates. The system had been up for 108 days without a reboot as shown in the logs, so a reboot didn’t cause it.
I’m trying to demonstrate that the common causes may not apply here.
I verified all the settings on the host computer switch. There was no hardware, switches, firewalls replaced in our system.
I’m trying to demonstrate that the common causes may not apply here.
I verified all the settings on the host computer switch. There was no hardware, switches, firewalls replaced in our system.
NO changes, how are the IP set, static, reserved by DHCP?
check event logs to see whether it reports another system taking its IP, the mac address will be in the log.
check event logs to see whether it reports another system taking its IP, the mac address will be in the log.
could be a missing gateway, do an ipconfig /all on the vm's and check
ASKER
“The symptoms you describe are the symptoms of an internal switch host and each vm on the host. Remove and add again the switch as external” - lead me to the solution! At first I tried removing the internal switch, then adding it again to no avail. Still had the same issues.
I installed a second Ethernet cable and setup a new connection with proper connectivity, then I removed the internal switch, re-added it and bound it to the new connection and it solved the problem.
I guess there is some kind of corruption or physical issue with the 1st NIC.
I installed a second Ethernet cable and setup a new connection with proper connectivity, then I removed the internal switch, re-added it and bound it to the new connection and it solved the problem.
I guess there is some kind of corruption or physical issue with the 1st NIC.