WinBox sessions open without session ID

Hello,

Thank you for reaching out to Devolutions Support.

Could you please provide details about the data source you are using, as well as the version you were on before the issue occurred?

Best regards,

Hi,

We're now using an SQL Server data source, which we imported from the old MySQL data source we previously used. The previous version should be 2021.2.20.0.

Hello,

Thank you for the information. I will need to contact the Sales department to request an older license for the version you provided for me to start testing.

Before proceeding however, could you please try using the other parameter? It is possible that this might be what we are looking for.



Best regards,

Yes, Other parameters sets the session ID.

Hello,

Good news! I was able to partially recreate the issue you are facing. I have created a case for our developers, and I will keep you updated on any progress or advancements regarding this matter.

best regard

Hi,

I noticed that a session ID field was added. I don't know whether that was in response to my feedback, but it does not do anything to alleviate the situation. It is effectively the same as the Other parameters field, which was already available. What's needed is for Remote Desktop Manager not to include an empty quoted string ("") in the command line string when the session ID field is empty.

Hello,

Thank you for your follow-up and the clarification.

We’ve taken note of your feedback regarding the session ID behavior and will look into it in the near future.

Regards,

Hello,

We’ve updated RDM so that if both the Session ID and Other Parameters fields are left blank, RDM no longer sends an empty argument to WinBox. This restores its default behavior, where sessions are treated separately based on host, avoiding shared session IDs.

If WinBox still reuses a previously saved session ID, it may be persisting that value locally. You can manually reset it on your side if necessary.

This fix will be available in version 2025.2.15.

Regards,

Great. Thank you!

For posterity, I will add that, indeed, there additionally seems to exist a bug in WinBox wherein if you at any point specify a session name in a certain way, that name will be used as the default for any session going forward. This can be "fixed" by deleting %AppData%\MikroTik\WinBox\settings.cfg.viw.