Using AccuTerm 8.1.1.1136 we are connecting to a windows 2022 server running OpenSSH server.  Connection works and we can log in but the AccuTerm escape sequences are hit and miss.

For example we can issue the escape sequence to run on the caps lock without issue, but when running the escape sequence to turn off the caps lock nothing happens.  The sequences are “ESC:STX:L” for caps lock on and “ESC:STX:M” for caps lock off.

I turned on data capture and can see the correct data getting sent for the caps lock on, but either nothing is sent or the wrong sequence is sent for the caps lock off.

We can run “ESC:STX:?”, “ESC:STX:I” and get the correct responses.

Trying to change the terminal size to 132 or 80 characters, “ESC:STX:E” and “ESC:STX:N” nothing will happen.

We have tried running Bitvise instead of the Windows OpenSSH server and had similar results.

Changes to terminal type, character set/code, SSH configurations and more have had no changes.

While we are connecting to an OAS instance, I don’t believe that matters as I setup my SSH server to log into the cmd prompt and ran powershell scripts to execute the escape sequences with the same results.  This looks like an issue with AccuTerm and SSH not communicating correctly or the SSH server trapping some of the escape sequences.

I did try to send the ANSI escape sequences to change the caps lock setting and the both work.  We can’t just change to the ANSI process as we use AccuTerm to run VBScripts on the client system and the WED process is not working.

Can anyone help with SSH server and AccuTerm settings to get these two to play nicely together?

Let me know if more information is needed.

Thanks in advance.