the regular SSH Applet works fine for the same server though.
Release : 3.3.x, 3.4.x
Component : PRIVILEGED ACCESS MANAGEMENT
The reason why he was getting the error is because the TCP/UDP Putty Service was created with:
"C:\Program Files\PuTTY\PuTTY.exe" -ssh <User>@<Local IP> <First Port>
and the user attempted to update his local settings to:
<LOCAL PATH TO PUTTY.EXE> -ssh 127.0.0.10 9490
but since the TCP/UDP service was defined with Port 22:* - that port changed the next time the they used it. Advised that it needs to be updated to:
<LOCAL PATH TO PUTTY.EXE>-ssh <User>@<Local IP> <First Port>
Than everything worked fine.