CMS 16 and SSH issues

[Stinney]

I know that there is an issue with CMS 16.1 and SSH. Unfortunately, the resolution is updating both the CMS server and client to 17 and for the few users that seem to constantly cause connection issues with their logins, the company doesn't want to spend any money on updating it.

So we're left dealing with the noisy few and we have to kill their login in CMS so they can login again.

However, there are also a lot more other users that never have a problem with this. I've tried to recreate the issue but can't. Does anyone know what the end user might be doing to cause their login to hang in CMS?

This has only been an issue since our security team forced us to change to SSH.

- Stinney
"Scire ubi aliquid invenire possis, ea demum maxima pars eruditionis est"

"To know where to find anything is, after all, the greatest part of education"

 

[ddog6601]

Maybe this will help:

thread690-1742983

 

[ddog6601]

I also noticed that some of the users that just use the " X " to close and not the "logout" first, tend to have more issues.
Are any of these people WFH users on wifi ? If they have a weak signal and are suddenly losing connection this might get them hung up as well !

 

[aujla0991]

Ask the users to use proper way to logout and then exit as ddog6601 mentioned, otherwise can create defunct processes for the logins.

Another thing, If user is querying bulk amount of data using designer or custom reports can lead to hang the session. You can upgrade the CMS supervisor to R17 LA31 which is backward compatible upto R12 CMS servers. Give it a try.