App start fails saying the RDP port is not open

[tristanRW]

The following command: timeout 5 nc -z "$RDP_IP" "$RDP_PORT" &>/dev/null; makes app startup fail, because it does not hear back over the rdp port, even though the VM is up and running RDP-server on said port.

This is also why setup.sh fails with Error 13 in some instances even though the VM is reachable through RDP. See #260. A fix should remedy both issues.

Maybe we can find an alternative to this port-check over netcat? Alternatively we could leave out the port-check entirely and just report the connection error if the rdp connection-attempt fails one step later in the connection-process.

[tristanRW]

I propose removing this netcat-port-check.

If the rdp-command fails, we can still print its error, or catch it and report the connection not being possible. Checking with netcat for the reason rdp failed is also a possibility.

In both cases the connection via rdp is at least attempted before the user is told it is "impossible". The current behaviour is especially misleading when connecting is possible, and works fine on re-run (of whatever app tried to connect).

[kamack38]

I had the same issue as mentioned here (timeout 5 nc -z "$RDP_IP" "$RDP_PORT" &>/dev/null; failing) and changing the gnu-netcat package to openbsd-netcat on Arch Linux fixed the issue. The gnu nc command runs around 10 seconds, while the OpenBSD implementation is instant.