Hello,
I recently created a remote desktop collection using windows server 2012 R2 on an HP ProLiant BL620c G7 Blade Server (which has completely up to date firmware and drivers). There are 30 VM’s running on the server, and it is running great – for the most part.
My issue is that, it seems to be at random (maybe once every 48 hours), users will be disconnected from their session, and they are unable to log back into their session remotely. I can log into their session as a local user by going through hyper-v, however
once I am in there I notice that I have no internet or network access. To solve this problem, I have to go onto the network adapter of the VM, disconnect the virtual switch assigned to the VM, and reconnect it again. Doing this provides remote access to the
VM again.
I initially thought the issue came from the configuration of the virtual switch. The HP Blade Server has 4 10 gig NIC’s, and they were teamed into two teams (each team having 2 physical NIC’s). I created two separate external network virtual switches from
each Team. I also had “allow management operating system to share this network adapter” checked. I noticed a warning on the server side when a disconnect would occur which was Event 16945 “MAC Conflict: A port on the virtual switch has the same MAC as one
of the underlying team members on Team Nic Microsoft Network Adapter Multiplexor Driver.” Because this error occurred at the same time as a disconnect, I assumed that this warning message was causing the problem, and I was able to resolve it by redoing the
NIC team to where there of the physical NICs were teamed together and a virtual switch was created from them
without the checkbox that allowed management operating systems to share the network adapter. This left one NIC available for management purposes, and I haven’t seen the error message since, however disconnects still continue occur.
I do not see any helpful information in the event logs of the client VM when one of these disconnects occur, and the users are doing nothing out of the ordinary that would cause it to happen. In fact this problem has happened when a user has been disconnected
from their machine for over 10 hours.
Anyone have any thoughts as to what is going on here?
