saldanad

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Login issues to NoMachine 5.2.21 #15071
    Avatarsaldanad
    Participant

    Thanks so much for all the assistance! You’ve been a great help. That was exactly the issue.

    in reply to: Login issues to NoMachine 5.2.21 #15046
    Avatarsaldanad
    Participant

    I actually did something wrong there, a bit of fat fingering when copy/pasting data into files. I have a new issue now that everything is squared away. The SSH debug shows me that everything worked however the client is giving me the following error.

    Error: /usr/NX/bin/nxexec: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

    So all the SSH issues are sorted out but this new error seems to be the only thing between me and a successful connection.

    in reply to: Login issues to NoMachine 5.2.21 #15045
    Avatarsaldanad
    Participant

    I’ve edited the authorized_keys2 file to contain only the part of the line containing

    ssh-dss *key here*

    all as one line and I’m getting the following error now

    debug3: secure_filename: terminating check at ‘/home/remotedba’

    buffer_get_string_ret: bad string length 813826490

    key_from_blob: can’t read key type

    key_read: key_from_blob

    **new key**

    failed

    debug2: user_key_allowed: check options: ‘ssh-dss **new key**

    debug3: key_read: missing whitespace

    debug2: user_key_allowed: advance: ‘**new key**

    debug2: key not found

    debug1: restore_uid: 0/0

    Failed publickey for remotedba from 10.9.3.50 port 59301 ssh2

    debug3: mm_answer_keyallowed: key 0x7fbbbb98a540 is not allowed

     

    in reply to: Login issues to NoMachine 5.2.21 #15039
    Avatarsaldanad
    Participant

    Ok, going forward I suppose troubleshooting just the system login will be helpful. I added the key to the authorized_keys2 file on the home directory. and got the attached in the SSHD debug log:

    debug3: secure_filename: checking ‘/home/remotedba/.ssh’

    debug3: secure_filename: checking ‘/home/remotedba’

    debug3: secure_filename: terminating check at ‘/home/remotedba’

    debug2: key_type_from_name: unknown key type ‘no-port-forwarding,no-agent-forwarding,command=”/usr/NX/bin/nxnode”‘

    debug3: key_read: missing keytype

    debug2: user_key_allowed: check options: ‘no-port-forwarding,no-agent-forwarding,command=”/usr/NX/bin/nxnode” ssh-dss *old key that was already in authorized_keys2*

    debug2: key_type_from_name: unknown key type ‘no-port-forwarding,no-agent-forwarding,command=”/usr/NX/bin/nxnode”‘

    debug3: key_read: missing keytype

    debug2: user_key_allowed: check options: ‘no-port-forwarding,no-agent-forwarding,command=”/usr/NX/bin/nxnode” ssh-dss *new key I added*

    key_read: uudecode *new key I added*

    failed

    debug2: user_key_allowed: advance: ‘ssh-dss *new key I added*

    debug2: key not found

    debug1: restore_uid: 0/0

    Failed publickey for remotedba from 10.9.3.50 port 57015 ssh2

    debug3: mm_answer_keyallowed: key 0x7f1160961540 is not allowed

    debug3: mm_request_send entering: type 22

    debug2: userauth_pubkey: authenticated 0 pkalg ssh-dss

    debug3: Wrote 96 bytes for a total of 2453

    debug3: mm_request_receive entering

    Connection closed by 10.9.3.50

    in reply to: Login issues to NoMachine 5.2.21 #15029
    Avatarsaldanad
    Participant

    I see what I did wrong initially now. Logs will be attached. Log 1 connection setup on Win10 client is set up as an SSH connection using System Login with a username and password and key. When I attempt this connection it immediately prompts for a username and password which errors out with “connection to the server lost”

    The second log is the same except I use the NoMachine Login with password and key. When I attempt this connection it gets as far as prompting me for a username and password and then fails with “Server configuration error”

    in reply to: Login issues to NoMachine 5.2.21 #15003
    Avatarsaldanad
    Participant

    This is output from setting the client setting to NoMachine Authentication using a key

    Jun  6 16:38:30 banssb-dev sshd[36128]: Accepted publickey for nx from 10.9.3.50 port 58740 ssh2

    Jun  6 16:38:31 banssb-dev sshd[36128]: pam_unix(sshd:session): session opened for user nx by (uid=0)

    Jun  6 16:38:39 banssb-dev sshd[36128]: pam_unix(sshd:session): session closed for user nx

     

    This is output from setting the client to use system login and key (2 attempts):

     

    Jun  6 16:36:54 banssb-dev sshd[36103]: Connection closed by 10.9.3.50

    Jun  6 16:38:18 banssb-dev sshd[36127]: Connection closed by 10.9.3.50

     

     

Viewing 6 posts - 1 through 6 (of 6 total)