SSH Conection Keep alive

[JimGwynn]

All - Need some emergency help
As we have moved all of our users to home workers we are experiencing excessive timeouts
Is there anyway using the SSH connection in the client launcher to set the Putty keep alive parameters?

Thanks

[Mike King]

What you can do is create a putty session and save it then instead of providing the host name to WindX provide the session name.

For example if the host is ourhost.yourdomain.com, then create a session in putty that will connect to that host and save it, for example, as myhost.  Now in the WindX SSH host name field specify myhost instead of the server name.

You can also use this to provide SSH keys and pre-define the userid/password.

[JimGwynn]

Mike - When I do that I get this message

User Override
UserID has been overridden by Session 'TEST'

[JimGwynn]

Here is a screen shot of my config

[JimGwynn]

Here is a better image

[Mike King]

This is because the system will use the userid from the session definition.  Set your userid on the session and resave then don't provide a user or password on the WindX screen.

[JimGwynn]

Thanks Mike that did work

For anyone else that may have a similar issue - Here is what we found and what works

We setup SSH access through a Network Load Balancer in AWS. This NLB has a fixed session timeout of 350s

What we did to solve this was Set the +A system parameter to 1.  By default this is set to 10 min causing the NLB to timeout sessions.

With this we did not need to touch any of the the users putty settings.

Thanks Again.