VRDP not available when quickly power cycling VM -> Fixed in SVN/3.1.4

[bauer40]

When shutting down a VBox with VRDP enabled, and immediatly starting the VBox again, the TCP port for VRDP can't be opened if there was a RDP session connected to the VBox.

To verify, start a VM with VRDP enabled (VBoxHeadless -s test). Next, connect an RDP client to that VM. Now, shutdown the host. When the shut down is done, the RDP Client will be disconnected by the server, leaving the TCP socket in the TIME_WAIT state.

After starting the VBox:

infra1# netstat -an|grep 7066
      *.7066               *.*                0      0 33232      0 LISTEN

After connecting an RDP Client:

infra1# netstat -an|grep 7066
      *.7066               *.*                0      0 33232      0 LISTEN
192.168.94.111.7066  192.168.94.22.1133   65535      0 33304      0 ESTABLISHED

Now, immediatly after the power-off of the VBox:

infra1# netstat -an|grep 7066
192.168.94.111.7066  192.168.94.22.1133   65448      0 33304      0 TIME_WAIT

When you try to start the VBox again (VBoxHeadless -s test), the VRDP port can't be openend, and the log reads:

00:00:00.040 VRDP: TCP server failed to bind to a port: 3389 [7066]
00:00:00.040 VRDP: TCP server closed.
00:00:00.040 VRDP: Failed to start VRDP-IN thread, rc = VERR_NET_ADDRESS_IN_USE
00:00:00.041 Warning: failed to launch VRDP server (VERR_NET_ADDRESS_IN_USE): 'VRDP server can't bind to a port: 7066'

Waiting with the restart of the VBox until the TIME_WAIT has been timed out by the TCP/IP stack, the VBox can normally start up and bind to the appropriate port.

[sunlover]

Thanks for the report. The problem will be fixed in the next VBox release.

[Sander van Leeuwen]

Please check if 3.1.4 beta 1 solves the problem: ​http://forums.virtualbox.org/viewtopic.php?f=15&t=27300