unable to reconnect
Remote Desktop Manager free: when I try to reconnect with Remote Desktop, it immediately pops up a message saying "Unable to reconnect". I click ok and the tab goes away. This only happens sometimes, though recently it seems like it is happening every time with one remote machine in particular.
This should probably go in the feature request section, but anyway, how about if there is an issue you let me try again and not just close the tab? And similarly, how about instead of always giving up when trying to use the connect when available, this program should keep trying. I have tried to use connect when available after rebooting a machine and it is guaranteed to start connecting before the machine is really ready and therefore, this feature of Remote Desktop Manager is useless because it will fail and won't try again.
All Comments (6)
Hello,
If you head over to your session's properties, under "User interface" you can enable the "Keep tab page opened on disconnect"
By doing so, if the session is disconnected, the tab will remain open, and you will get a list of options, including one that will reconnect when the session is available again! 
Best Regards,
Etienne Lord
Sorry, I wasn't clear. I do have that set and it happens anyway. I just tried and this time it didn't happen. It did connect. So, there's clearly some message that comes back from the target or some state in the application that is handled with the error I mentioned or somehow causes a bypass of this setting you mention.
Hello,
Quite strange, I will see if I can get more details on how the feature works exactly, keep you updated!
Best Regards,
Etienne Lord
Hello,
By default, this option will ping the host until he gets a respond and then will attempt to reconnect once it does. That said, if you head over to the "Is Online" tab of your session, you can check the Online Detection to "Port Scan", could you give that a try and let us know if that works better for you? 
Best Regards,
Etienne Lord
I am using Remote Desktop Manager Free. It does not have any such management tool. I think the main blame for trying to connect after a reboot lies with Windows. It appears to allow a TCP handshake (I assume), but then failure to follow through with the rest of the connection attempt as the operating system has not fully initialized yet. I guess this "Connect when available" is good just after starting a VPN connection, just not for after a reboot of the remote Windows machine. So, one would have to build a more robust connection process that keeps trying until it succeeds.
Hello,
I will look further into it with the engineering department. But the option mentioned in my previous post should indeed be available, even with the Free edition, make sure you check "Advanced Mode" :
Best Regards,
Etienne Lord