Can’t create a virtual desktop

Forum / NoMachine for Linux / Can’t create a virtual desktop

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #23752
    Thonno95
    Participant

    Hi,

    I have an Enterprise Terminal Server with a Domain A, and a Terminal Server Node with a Domain B. (joined with Samba and Winbind).

    Domain A and Domain B are trusted so i can login in Domain A with Domain B users.

    I can log in, with NoMachine, to the Terminal Server Node but when i try to Create a new Virtual Desktop, connection loads until it gives me the Negotiation error due to the 120 seconds of inactivity.

    Can you help me please?

    Best regards,
    Thonno95.

    #23765
    Britgirl
    Keymaster

    Can you send us the logs of the problematic node? Follow the guidelines here: https://www.nomachine.com/AR10K00697 at

    Then send them to forum[at]nomachine[dot]com making sure you put the title of the topic in the subject. Thanks!

    #23766
    Thonno95
    Participant

    Hello:

    nxserver.log

    2019-09-26 10:04:15 285.432 12129 NXSERVER WARNING! User NETINT%%5caascione doesn’t exist in system.

    2019-09-26 10:04:15 285.640 12129 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: NETINT%%5caascione.

    2019-09-26 10:04:15 286.844 12129 NXSERVER WARNING! User NETINT%%5caascione doesn’t exist in system.

    2019-09-26 10:04:15 287.001 12129 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: NETINT%%5caascione.

    2019-09-26 10:04:15 287.674 12129 NXSERVER WARNING! Cannot get system groups for user NETINT%%5caascione.

    2019-09-26 10:04:15 287.809 12129 NXSERVER WARNING! Error is: 2, ‘No such file or directory’.

    2019-09-26 10:04:15 288.340 12129 NXSERVER WARNING! User NETINT%%5caascione doesn’t exist in system.

    2019-09-26 10:04:15 288.489 12129 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: NETINT%%5caascione.

    2019-09-26 10:04:20 353.730 11837 NXSERVER ERROR! Cannot acquire descriptor from pid 12129. Error is: 2 ENOENT No such file or directory

    2019-09-26 10:04:20 353.983 11837 NXSERVER WARNING! Failed to acquire descriptor from server 12129 and /tmp/session-4AFF79B328784FD8A63CE224ADD7D1CC.

    2019-09-26 10:06:35 374.284 12129 NXSERVER WARNING! Node did not ping since 120 seconds.

     

    nxerror.log

    Info: Handler started with pid 12090 on Thu Sep 26 10:03:58 2019.

    Info: Handling connection from 192.168.100.196 port 35462 on Thu Sep 26 10:03:58 2019.

    Info: Handler started with pid 12129 on Thu Sep 26 10:04:13 2019.

    Info: Handling connection from 192.168.100.196 port 35514 on Thu Sep 26 10:04:13 2019.

    12129 12129 10:04:15 287.461 Process: ERROR! Cannot get information for user ‘NETINT%5caascione’.

    12129 12129 10:04:15 287.515 Process: ERROR! Error is 2, No such file or directory.

    12129 12129 10:04:15 287.562 HostGetUserSystemGroups: WARNING! Can’t get username.

    12129 12129 10:04:15 287.602 HostGetUserSystemGroups: WARNING! Error is 2, ‘No such file or directory’.

    11837 11837 10:04:20 353.251 Ancillary: ERROR! Can’t connect to the requested socket.

    11837 11837 10:04:20 353.332 Ancillary: ERROR! Error is 2 ‘No such file or directory’.

     

    nxd.log

    Info: Server started with pid 11974 on Thu Sep 26 10:03:40 2019.

    Info: Listening for connections on any interface on port 4000.

    Info: Accepting connections from any host with encryption enabled.

    Info: Connection from 192.168.100.196 port 35462 accepted on Thu Sep 26 10:03:57 2019.

    Info: Connection from 192.168.100.196 port 35462 process 12090 started on Thu Sep 26 10:03:57 2019.

    Info: Connection from 192.168.100.196 port 35514 accepted on Thu Sep 26 10:04:12 2019.

    Info: Connection from 192.168.100.196 port 35514 process 12129 started on Thu Sep 26 10:04:12 2019.

     

     

    #23767
    Thonno95
    Participant

    I send the logs to the mail you mentioned, thank you!

    #23822
    mlyn
    Contributor

    Hello,

    there is a problem when the username forwarded to remote node contains a special character.

    We will fix it on next release, please follow up the: https://www.nomachine.com/TR09Q09418

    #23865
    Thonno95
    Participant

    Hello,
    when will it be fixed? (a.k.a. when is the patch coming out?)

    Thank you,
    Thonno95.

    #23868
    Britgirl
    Keymaster

    The patch has been queued up (and already fixed) for the next available maintenance, but I can’t say exactly when that will be. We can send you over a link to download a patched package. Can you tell me if you are using RPMs 64 or 32 bit?

    #23869
    Thonno95
    Participant

    Thank you for the information, Britgirl.
    I’m using 64bit RPM.

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

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