Telnet session prints key 2 times

Implemented

Telnet session prints key 2 times

avatar

Hello !

I'm trying to replace multiple tools that we use in my company by one and it seems RDM could be the solution.
However I've met some issues with Telnet sessions that we use to send commands to embeded devices.

The terminal opens properly and everything is displayed correctly on the screen.
Command also works fine.

The only problem is that the terminal window prints every key 2 times when I type :
It prints the key localy and then print the character that was sent back by the Telnet server.

For example when I type "hello", it prints "hheelllloo". Also the backspace can "erase" characters from the local window.

Apps like Putty or TeraTerms do not have the same issue.

I've tried to modify parameters of the Telnet session but nothing seems to work (things about echo or app mode).
The window has to send key presses to the Telnet server but not locally print them on the screen

Thank you for your help and have a good day !

All Comments (14)

avatar

Hello,

Thank you for reaching out to us regarding this,

I see, that is indeed odd.

Could you confirm which version of RDM you're currently using?

I'm also wondering if you could provide a screenshot of your entry "Properties" I would like to see the "Terminal" section if possible.

Let me know,

Best regards,

Samuel Dery

avatar

Hello,

I'm using 2022.3.24.0 "zip" portable

About the properties :There is not much to see. I've tried a lot of parameters but I always reverted to default everywhere.
The only thing I put was the adress and port.

forum image
forum image
Hope this helps

avatar

I was able to go around the problem by using the TeraTermPro integration in RDM.
However, it goes against the initial goal of having only one app.
I've already used it to replace other tools, especially for SSH sessions.
It will work fine for now but all the the features I wanted for the integrated Telnet tools are not accessible (like log files, post login commands and color changes)

avatar

Hello,

Thank you for your swift reply!

Would it be possible for you to enable the session recording feature on your Telnet entry by following these steps https://kb.devolutions.net/rdm_session_recording.html and enable the verbose logs https://kb.devolutions.net/rdm_send_ssh_logs.html ? Once this is done, reproduce the issue that you are currently experiencing and send us the logs that will be generated.

I will then be able to send them to our Engineering Department for analysis.

Best regards,

James Lafleur

avatar
Hello,

Thank you for your swift reply!

Would it be possible for you to enable the session recording feature on your Telnet entry by following these steps https://kb.devolutions.net/rdm_session_recording.html and enable the verbose logs https://kb.devolutions.net/rdm_send_ssh_logs.html ? Once this is done, reproduce the issue that you are currently experiencing and send us the logs that will be generated.

I will then be able to send them to our Engineering Department for analysis.

Best regards,


I do not have the session recording stuff because I'm using the free version for testing.
However I provided the logs with "output" mode and also the "event" mode added to it.

For context, I used the post login to type the "trace" command 2 times
Then I use "Enter" to get the CLI.
I type "trcfg", then Enter
I type "exit", then Enter
I type "trace", then Enter.
I did the same thing multiple times, only the output is slightly different depending on what the system was doing but that's not the part where the problem lies

If you need anything else, fell free to ask !

Hope this helps

session.log

avatar

Hello,

Thank you for your quick reply!

I will transfer this information to our engineering department and get back to you shortly.

Best regards

James Lafleur

avatar

Hello,

Our Engineering Department would like to know if you specify "echo off" or if it is automatic.
Also, could you please confirm that the logs you sent us are complete? They seem to end abruptly.

Best regards,

James Lafleur

avatar
Hello,

Our Engineering Department would like to know if you specify "echo off" or if it is automatic.
Also, could you please confirm that the logs you sent us are complete? They seem to end abruptly.

Best regards,


Hello again.

No I've not changed any parameter. Everything is on "default". For the "Local Echo" option, I've tried to activate or deactivate it to no avail.
About the end of the log file :
I just wrote the two logs to the same file but I haven't touched it. I just saved it after ending the Telnet Session

Thank you again for your help

avatar

Hello,

Perfect! Thank you for your reply, I will provide this information to our Engineering Department.

Best regards

James Lafleur

avatar

Hello,

I just wanted to let you know that our Engineering Department might have found the cause of this issue. We will keep you updated.

Best regards,

James Lafleur

avatar

Fantastic !

I suppose it will be implemented in the next update ?
I'll be going on vacation soon so I will probably not be able to test the fix if it comes out soon. I will try to get a colleague to test it if possible.

I wish you a Merry Christmas and a Happy new year in the meantime !

Thank you again for your help

avatar

You are correct! This fix should be available in RDM 2022.3.28.0. When this version will be released, the only change you will need to make is to change the "Local Echo" setting to "Force Off" and you should then no longer experience this issue.

A Merry Christmas and a Happy new year to you as well!

James Lafleur

avatar

The problem is indeed fixed in the 2022.3.29.0 version.

Thank you very much !

Happy New year and best wishes for 2023 !

avatar

Hello Lucas,

Glad to hear the issue has been fixed in the latest release.

Happy New Year as well!

Best regards,

Richard Boisvert