Launching an SSH Mindterm to access a Linux target device that is not accessible (due to tcp/22 is blocked, sshd is down or the target machine is down) causes delay in subsequent SSH Mindterm access. When the first failed SSH access attempt is started "loading" message appears flashing and the a blank SSH Mindterm window appears. After this, the subsequent SSH Mindterm access to different working Linux target device will get delayed, i.e. only after about 2 or 3 minutes the expected SSH Mindterm window appears and login happens.
The 1st failed SSH Mindterm access is blocking the subsequent SSH Mindterm launch for about 2 to 3 minutes.
The expectation is, regardless of the 1st failed SSH Mindterm access, the subsequent SSH Mindterm access should launch immediately and work normally.
Release : 3.4.x
Component : PRIVILEGED ACCESS MANAGEMENT
The 1st failed SSH Mindterm access is blocking the subsequent SSH Mindterm launch.
This is a known bug that is recorded in DE507465.
As of this article is written, we have a hot-fix for PAM 3.4.4. Please raise a Support Call ticket and request for CAPAM_3.4.4.01 hot-fix to address this issue.
This issue will be addressed in next PAM 3.4.6, PAM 4.0.2 releases and later.