I have Windows 10 VM that's connected to a Windows Home Server (2011). The Windows VM sees the Server just fine. I can connect to it through Windows (File) Explorer and run the Server's Dashboard. However, the connector software (Windows Server Launchpad) cannot connect once the VM has been shut down or restarted. It reports that the Server is offline, even though it's fully visible and accessible in File Explorer and through the Server's Dashboard software. Without the Launchpad connector, automatic backups of the Windows VM to the Server cannot happen. The only solution is to uninstall Windows Server Launchpad, restart the VM again, and reinstall Launchpad. Then everything works fine until the next restart (necessary for every Windows Update at a minimum). This gets incredibly tedious, mainly because the whole process takes about ten minutes, and it has to be done over and over and over and over. I'm suspicious that this may have something to do with Parallels Desktop's system of naming the paths to the Mac's host drives and folders, such that the Server is easily discoverable during installation of the Launchpad but somehow cannot be found after a restart because of some funny naming convention. The problem certainly does not occur on either of the two Windows PCs or any of the three Macs (one of which is the host for this Parallels VM) in the house, so it's not being caused by the Server Is this plausible? If so, does anyone have suggestion?
Hi milleron, Make sure bridged mode is selected as the network mode for the virtual machine and try assigning a permanent IP address for the virtual machine on your router then check.
