Using domain login name like domain\user gives error

Forums / NoMachine for Windows / Using domain login name like domain\user gives error

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #5309
    AvatarDenys Krytskyi
    Participant

    I installed NM on Ubuntu and I try connect to Win machine which consists in domain.

    When I enter my domain credentials I get the following error

    Ooops! the session negotiation failed

    Error: Cannot authenticate to the requested node.

    But if I login with local user credentials it works.

     

    Below I attached log’s

     

    #5313
    AvatarBritgirl
    Keymaster

    Hi, please submit the logs again using the following contact, issues[at]nomachine[dot]com, and specifying the forum title in the subject.

    Thanks.

    Britgirl

    #5312
    AvatarDenys Krytskyi
    Participant

    connaetion
    HELLO NXSERVER – Version 4.3.30 – NoMachine
    NX> 105 Hello NXCLIENT – Version 4.3.30
    NX> 134 Accepted protocol: 4.3.30
    NX> 105 Set shell_mode: shell
    NX> 105 Set auth_mode: password
    NX> 105 Login
    NX> 250 Properties: username required for Vm-1264 port: 4000 service login: hls\dkrytskyi
    NX> 250 Properties: password required for Vm-1264 port: 4000 service login: ***************
    NX> 510 Error: Cannot authenticate to the requested node.

    #5574
    Avatarslavikca
    Participant

    I have same issue while connecting from Ubuntu to Win7 domain machine.

    Detailed log:

    4342 4342 16:10:39 203.030 ClientSession: Starting session at 0x1fd6930.

    4342 4342 16:10:39 203.195 ClientSession: Going to start session ‘/home/domainname/username/.nx/cache/3760bfcf-119b-468a-b166-9635c847af6c.nxs’.

    4342 4342 16:10:39 208.096 Connection: Finishing connection at 0x24322a0.

    4342 4342 16:10:39 208.106 ClientDaemonConnector: Stopping the current connection.

    4342 4342 16:10:39 208.116 Connection: Finished connection at 0x24322a0.

    4342 4342 16:10:39 208.120 Connection: Initializing connection at 0x24322a0.

    4342 4342 16:10:39 208.175 Connection: Initialized connection at 0x24322a0.

    4342 4342 16:10:39 208.185 Connection: Starting connection at 0x24322a0.

    4342 4342 16:10:39 208.191 ClientDaemonConnector: Starting a new connection to host ‘10.20.40.31’ on port ‘4000’.

    4342 4342 16:10:39 208.266 Connection: Started connection at 0x24322a0.

    Info: Connection to 10.20.40.31 port 4000 started at 16:10:39 208.924.

    4342 4342 16:10:39 210.709 ClientSession: Started session at 0x1fd6930.

    4342 5311 16:10:39 810.859 ClientSession: A valid certificate for this server was found.

    Info: Connection to 10.20.40.31 port 4000 closed at 16:10:39 895.335.

    4342 4342 16:10:39 895.344 Connection: Connection at 0x24322a0 failed.

    4342 4342 16:10:39 895.377 ClientSession: Runnable at 0x24322a0 caused the session at 0x1fd6930 to fail.

    4342 4342 16:10:39 895.384 ClientSession: Failing reason is ‘The session negotiation failed.

     

    Error: Cannot authenticate to the requested node.’.

    4342 4342 16:10:39 898.378 ClientSession: Stopping session at 0x1fd6930.

    4342 4342 16:10:39 899.573 Connection: Stopping connection at 0x24322a0.

    4342 4342 16:10:39 899.592 ClientDaemonConnector: Stopping the current connection.

    4342 4342 16:10:39 899.752 Connection: Stopped connection at 0x24322a0.

    4342 4342 16:10:39 905.457 ClientSession: Stopped session at 0x1fd6930.

    #5578
    AvatarBritgirl
    Keymaster

    A TR has been opened.

    Users cannot connect when the NoMachine server is installed  on a Windows Active Directory client
    https://www.nomachine.com/TR10L04643

    You may select the ‘Notify me when the TR is closed’ option to be informed when a fix for this issue is available.

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

This topic was marked as solved, you can't post.