SSH authentication or connection failure message received when trying to discover linux servers that are not connected through centrify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2018 12:41 PM
I am running discovery and i am able to successfully discovery linux servers that are connected through centrify however any server not connected through centrify i am getting an error SSH authentication or connection failure. If i try to SSH into the server using putty i can connect fine. Unix team has also created a local admin account but i am still not able to discover. Thoughts?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2018 03:33 PM
Ok, so you can connect to the server with Putty, that's good. So we know the port is open, sshd is listening, and we know a credential that works.
Next steps:
- Can you connect with Putty from the mid server?
- Is the credential you're using a password or a public key credential? If it's public key, putty keeps its keys in a different format, and you will need to export them to the openssh format.
- You can set the mid server attribute mid.ssh.debug = true, then look in the agent log to see piles of debug information.
- Does it get past the kexinit exchange where algorithm are negotiated?
- Does it fail in userauth?
If you get to the debug logs, you may require some help as they're pretty confusing.