VMPlayer 12 timeout

[RonNewYork]

I am using VMPlayer 12.5.7 build-5813279 on Windows 10. i use it to run Windows server 2012R2.

After a period of inactivity (not sure how long), the VM disappears.

Is there a setting to prohibit this? Or at least extend the time out period?

ALSO (and this may be off topic for this forum), What is the specific difference in the Virtual Machine Settings between using a Bridged network connected to the host machine's NIC and VMnet1 (or 8)?

I would like the VMs to be able to reach the default gateway and the Internet, besides each other.

RON

[bluefirestorm]

After a period of inactivity (not sure how long), the VM disappears.

Is there a setting to prohibit this? Or at least extend the time out period?

I assume that when you mean disappears, the VM gets suspended. And the next time you open up the VM, it resumes. I don't think it is a setting of VMware Player but of the guest OS Windows Server 2012 R2. Most likely this is a Power setting that makes the guest OS to go sleep (which in turn makes VMware Player to suspend the VM).

What is the specific difference in the Virtual Machine Settings between using a Bridged network connected to the host machine's NIC and VMnet1 (or 8)?

There are 3 virtual switches. Bridged network uses virtual switch VMnet0. VMnet1 is the Host Only virtual switch while VMnet8 is the NAT switch. Both Bridged and NAT should get you to share the internet connection that you already have.

Probably the documentation will explain it a lot better than I do.

https://docs.vmware.com/en/VMware-Workstation-Player/12.0/workstation-player-12-windows-user-guide.p...

[RonNewYork]

I'll give Bridged and NAT another try. Neither seem to work now (but they did before; not sure why or what I did).

As for the VM suspending: no, I mean it disappears entirely. VMPlayer 12 closes.

[dariusd]

Is your Windows Server 2012 VM correctly licensed?

After Windows Server 2012 is installed without being activated, it will operate normally for an evaluation period -- I think it's 60 days or so.  After that, the OS is designed to run only for a short while, and then it will shut itself down... to encourage the user to properly license and activate it.  There should be an event logged inside the Windows guest OS (check the guest's Event Viewer) explaining the reason for the shutdown.  If that's what is happening, the guest OS will perform an orderly shutdown, and the VMware Player window will close.  You'll need to follow the licensing and activation procedure inside your Windows Server 2012 instance in order to keep it running normally.

Cheers,

--

Darius