Return
-
Title
A Windows Application Error occurred. EventID:0 Source:TPAMCONSOLE Description:sshd,sshd: PID 3412: error: kex protocol error: type 30 seq 1 [preauth] -
Description
A Windows Application Error occurred. EventID:0 Source:TPAMCONSOLE Description:sshd,sshd: PID 3412: error: kex protocol error: type 30 seq 1 [preauth] -
Cause
cli application failing to connect to TPAM -
Resolution
The CliUserAccount is attempting to connect to TPAM via SSH.Check the ApplicationLog.csv to determine where the failed ssh connection is coming from.The log entry should look something like this "sshd: PID 9944: Accepted publickey for CliUserAccount from IP x.x.x.x Address port 62328 ssh2 "The failure to connect is logging this error into the alertlog.csv file."A Windows Application Error occurred. EventID:0 Source:TPAMCONSOLE Description:sshd,sshd: PID 3412: error: kex protocol error: type 30 seq 1 [preauth]"Confirm the CliUserAccount on IP address x.x.x.x from the ApplicationLog.csvThe failure is likely caused by these:1. You are using an old ssh client which is causing the kex protocol error. e.g putty2. You need to upgrade the TPAM Cli’s on that machine (if they're using them) e.g plink3. You may need to regenerate the SSH keys the CliUser is using.