I have a problem with a rather unusual case.
On my PC, I have a Windows 7 VM (yes, not ideal, but I don't have a choice at the moment) managed with VirtualBox, which I use, among other things, to manage the PC fleet with the Wapt console. I work on-site, sometimes from home, or even while traveling (4G connection).
When I'm on-site, my VM is configured this way at the network level, and my network's DHCP server assigns me a local IP address in the 192.168.xx range
When I'm at home, the VPN is launched by the host and my VM is configured in NAT mode with a 10.xxx IP address
In both cases, the machine's IP address in the console updates correctly.
Yesterday, from home, on this VM, I modified the host package to add a program to install. I clicked save to launch the installation when the machine shut down. In the evening, I shut down my VM but prevented the installation from completing.
This morning I arrived on site, modified the network settings of my VM as shown in the first screenshot, and started the VM. I logged in and launched the console. My machine appeared as reachable with my local network IP address, and I decided to shut it down again to run the package installation I had scheduled yesterday. However, everything didn't go as planned, and the installation failed before I had time to note the error message.
I launch the wapt console and look at the "Tasks" tab of my machine and I get the message:
Code: Select all
Impossible de récupérer l'action. Error on server:
EWaptTimeoutWaitingForResult('Timeout, client did not send result within 15.0 s')To test, I shut down my VM, switched VirtualBox back to NAT, and restarted. My VM obtained a 10.xxx IP address, and I launched the console. My machine appeared correctly with the new address, but the tasks remained pending or displayed a timeout error.
It's as if the Wapt server could see my machine but didn't really know where to send all that data.
