Error screen flashes and then closes while attempting to RDP into server

Hello,

I had a quick chat with the engineering department and it's not possible to let the tab opened with the error message in it, however, the error message should be present into the logs of RDM Mac.

To access the logs, simply go in Help -> Application Logs.

Best regards,

Well, I can't complain, after all I use the free version and it does have plenty to like. But, I strongly suggest that is changed. There is no such thing as "It's not possible" in a case like this. The way I got around the problem was using the Mac version of Microsoft Remote Desktop, which DOES work properly in this case and I got the error message, which allowed me to identify the problem: The environment is a Disaster Recovery/Sandbox environment where the AD infrastructure had my previous password instead of my current password. I was prompted to reset my password and then I was able to use RDM again after the password reset in the sandbox environment. If RDM does not display the error message long enough I would never be able to login... It's a major flaw in my opinion.

Thank you. Best, Raphael.

Hello,

Did you get the error message in Help -> Application Logs or not?

Please note that in embedded mode, we don't use Microsoft technology on Mac. We use a protocol name FreeRDP. I will check with the engineering department if some enhancement could be made, but I cannot promise anything.

Best regards,

Hi rferreira,

The "it's not possible" meant that it is not possible in RDM Free for Mac to leave the tab open with the error as it is now (i.e. there is no option to increase the delay or remove it all together). Of course this could be implemented. But honestly, fetching the error from the application log should work as a sufficient workaround in the current version of the application.

Best regards,

Thank you for both your replies Jeff and Xavier.

As I said, I am not a paying user. However, if I were a user that paid for the product, I would not consider this answer satisfactory. Expecting a final user to go into application logs simply to find out which error message the RDP target server returned while attempting login is not acceptable for a product that does RDP connections. The act of connecting remotely to a machine implies that the user will be shown the reason why s/he was not able to login. With the error screen flashing like this it becomes impossible for final users to know what problem they are facing with their login, unless they go treasure hunting inside extensive log files. How does one even know what to look for? And no, thanks much, but I do not want to know what to look for. I am just too busy doing my job to bother, as I am sure you all are very busy as well. :-)

I really don't want to come across as rude or prissy, but I just think this would be a reason for me to dislike a paid version of the product enough for me to consider stop using it, and hence stop paying for the product. Again, please take this as constructive criticism and feedback. For the moment I am perfectly fine using Microsoft's RDP client for Mac whenever I need to see the error messages, but other paying customers may not... Just some food for thought. Best, Raphael.

Hi,

Thanks for the feedback.

We've already filed the improvement ticket. We'll post back here when it is done.

Best regards,

Hi,

We already had an option in the Preferences for that (Preferences -> Advanced -> Connection -> Auto close embedded tab on disconnect). It didn't cover all errors though (including the one you were having). In the next release of RDM, if you uncheck "Auto close embedded tab on disconnect", the tab should remain opened indefinitely on a disconnection.

Best regards,

Hi,

RDM and RDM Free 2020.3.2.0 will be available shortly. The option (Preferences -> Advanced -> Connection -> Auto close embedded tab on disconnect) will now work for all RDP errors.

Best regards,