Setting up an SCP session on Mac OS X

Hello,

What version of RDM Mac are you running?

Could you give a try to RDM Mac 5.3.0.0?
https://mac.remotedesktopmanager.com/home/download

Best regards,

I'm running RDM version 5.2.0. I'm downloading 5.3.0 now and will give that a shot. Thanks

Just to confirm, Since this is not going thru the "check for updates" section within the RDM, There is still an upgrade path when I drag the app into my applications directory correct?

Installed 5.3.0.0 below are the results:

Status: Starting SSH negociation
Status: socket_callback_connected: Socket connection callback: 1 (0)
Status: ssh_client_connection_callback: SSH server banner: SSH-2.0-OpenSSH_5.3
Status: ssh_analyze_banner: Analyzing banner: SSH-2.0-OpenSSH_5.3
Status: ssh_analyze_banner: We are talking to an OpenSSH client version: 5.3 (50300)
Status: ssh_userauth_request_service: Failed to request "ssh-userauth" service
Status: SCP user successfuly authenticated by password
Status: echo %cd%
Status: %cd%

Status: pwd
Status: ssh_packet_channel_open_fail: Channel opening failure: channel 44 error (1) open failed
Status: ssh_packet_disconnect_callback: Received SSH_MSG_DISCONNECT: 2:server_input_channel_req: unknown channel 0
Status: Handshake error: -4001
Status: Disconnecting from SCP
Disconnected with code: -4001 (SCP_FAIL)

Hi,

We think it might be a libssh issue, but we're definitely unsure.

Could you tell me what is the server OS?

Could you also tell me if the scp command is installed on said server? (You can connect to it in SSH and try executing the scp command.)

Best regards,

Yes, I'm attempting to establish an SCP connection to our Nutanix platform (www.nutanix.com). I am able to establish a WinSCP connection to the controller VMs but not thru the RDM. The controller VMs are running a modified/proprietary CentOS 6.8.

Just checking if there are any updates to this question? I've updated to 5.3.1.0 now and I still am seeing the same results when attempting to connect to a Nutanix Controller VM.

Thanks

Hi,

We haven't fixed this yet.

We think libssh might be using an unconventional method to handle SCP server (it might be relying on the scp command being on the server to do this). Which is why I asked if you could SSH to the remote server and try to run the scp command on it. This might be the limitation.

We're working on a new SSH engine on which we'll have more control and which will offer more log information.

Best regards,