Hi,
@v_enom wrote:
I didn't try this yet: "Use RDP in the office to connect to your Host and see what happens."
But I tried to connect direct to guest machine via RDP.
And there is no such problem. So it means that problem is exactly with vmware player via RDP.
Tests cases:
1. Connect to host machine via RDP - no freezes2. Connect to guest machine via RDP - no freezes
3. Connect to host machine via RDP and open guest machine via vmware player - bug!
In both scenario 1 & 2, you only have the RDP protocol that's being used. RDP gets it's own resources and is pretty efficient.
Scenario 3 is different. You connect via RDP and then use the local console from VMware Player. VMware Player uses a protocol similar to VNC. So you're connected via both RDP and the console.
The console thread runs at the host whereas the RDP thread will use what is available at the guest.
It's possible that there's some incompatibility somewhere, or that the console thread at the host is out of resources.
However it is not a very uncommon configuration. In fact I use it every now and then in that same setup too and so far no problems.
Personally however I prefer to use RDP to the guest directly as it is much smoother.
Like RaSystemlord says.. this needs studying of a variety of logs in order to figure out the culprit.
--
Wil
