"SSH authentication or connection failure" in Linux/UNIX

[nikhilagr20]

Hi,

I have a Red Hat Linux Server in my environment. I have created a user with sudo privileges. When i am running discovery on it, it gives error "SSH authentication or connection failure". While I am able to login to this server via putty & able to run uname -a command successfully.

I have also enabled "debug_ssh = true" & "debug = true" in UNIX-Classify probe. Please find attached ssh.log file & screenshot of access given to user.

looking for a possitive reply.

Regards,
Nikhil Agarwal

[ishant_goyal]

Hey I am also facing the same issue. Did you got a solution for this. Somewhere i read that it could be because of ssh version on the destination server and to overcome we have to JSCH.jar instead of J2SSH.jar.

http://techydiary.com/the-transport-protocol-thread-failed-java-io-ioexception-the-socket-is-eof/

[ishant_goyal]

Hey I just found one solution for this. Please add a new parameter to your MID server mid.ssh.use_snc=true and try.

[gk13]

Hi Doug,

I know this is a fairly old thread but since you mentioned Centrify I hope you maybe have an answer: I'm currently facing the situation, that a customer of mine is actually using Centrify to manage credentials on UNIX systems. To SSH into a system they use their normal Active Directory accounts. Those are managed by Centrifyin the way of to what UNIX machines the AD account is allowed to login and what he is allowed to execute (they don't maintain any sudoer file or any local accounts on the unix machines - it's all managed by Centrify).

Is Disocvery and Service Mapping able to work with that kind of authentification?

[california123]

i added both parameters and tried but its not working mid.ssh.use_keyboard_interactive and mid.ssh.use_snc=true

can anyone help on this ?

[Dave Smith1]

Can you check the logfiles on the target server that you're trying to SSH into? They should be in /var/log/auth.log or /var/log/secure.

Run "tail -f" on the file in a terminal session then try another discovery, watch the logs scroll up.

Also: did you restart the MID server after changing the parameters?