Ethernet connection to VMs randomly stops working

[MikeW]

I have a Windows 7 and Windows 10 VM and every few days their network connections seem to stop working. I can still access them with VNC, but not RDP. And when I log in using VNC I see the yellow triangle on the network icon in the taskbar. This has happened several times, but it only happens once or twice per week.

 

I don't know if this is related, but I saw this in the unRAID logs:

 

Aug 11 15:22:22 unraid kernel: br0: port 4(vnet1) entered disabled state
Aug 11 15:22:22 unraid avahi-daemon[1911]: Withdrawing workstation service for vnet1.
Aug 11 15:22:22 unraid kernel: device vnet1 left promiscuous mode
Aug 11 15:22:22 unraid kernel: br0: port 4(vnet1) entered disabled state
Aug 11 15:22:38 unraid kernel: device vnet1 entered promiscuous mode
Aug 11 15:22:38 unraid kernel: br0: topology change detected, sending tcn bpdu
Aug 11 15:22:38 unraid kernel: br0: port 4(vnet1) entered forwarding state
Aug 11 15:22:38 unraid kernel: br0: port 4(vnet1) entered forwarding state
Aug 11 15:22:46 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound

 

Has anyone had any intermittent issues with the network connection becoming disabled in their VMs?

[jonp]

Hmm, nothing irregular about those log events.

 

Are other devices on the network and the unRAID server itself still accessible when this occurs?

[MikeW]

Yes, everything else seems to be still accessible over the network. Another data point: After rebooting both VMs they can access the Internet, but only the Win 7 VM will accept RDP connections. The Win 10 VM won't accept an RDP connection even after rebooting the VM.

 

I've had this happen before and only a reboot of the unRAID box will fix the RDP connection problem. Are there any other logs or commands I can run to try to diagnose the problem?

[jonp]

For the win 10 VM, can you confirm the account you are using to connect has a password set and that the VM is using the public bridge option?

[johnodon]

Yes, everything else seems to be still accessible over the network. Another data point: After rebooting both VMs they can access the Internet, but only the Win 7 VM will accept RDP connections. The Win 10 VM won't accept an RDP connection even after rebooting the VM.

 

I've had this happen before and only a reboot of the unRAID box will fix the RDP connection problem. Are there any other logs or commands I can run to try to diagnose the problem?

 

Two obvious questions about the WIN10 VM...

 

1.  Did you enable remote access for any version of RDC?

2.  Did you allow access via Windows Firewall?  (I disable Windows Firewall on all my WIN machines since I am the only one who uses them and know what to avoid)

 

John

[bungee91]

My Windows 10 vm defaulted to a public type of network which doesn't allow RDP connections. There was a guide I Google'd to figure out how to set it to private, and it then worked as expected.

[MikeW]

I'm pretty sure my Windows 10 WM RDP issue after rebooting was due to me misconfiguring something. I don't recall making any networking changes, but after I messed around with a "Homegroup" option I was able to RDP back into the VM.

 

But I have experienced about three times over the past two weeks where my Windows VMs lose network connectivity and I have to restart the VM to fix it. I'll try to get more information the next time it happens.