LDAP and NoMachine Enterprise Terminal Server

Forum / NoMachine Terminal Server Products / LDAP and NoMachine Enterprise Terminal Server

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #40314
    Mark
    Participant

    I have configured a new machine with NoMachine Enterprise Terminal Server. For the purposes of this though, I am only using the node as a single server; it is not part of a running cluster — that would be later.
    The machine resides in an AWS instance in London and has been configured to authenticate via Google Secure LDAP.

    I can connect to the instance using SSH and the correct username/password combination.

    I noticed that I was sometimes unable to login via NoMachine – after a few days away (looking at another NoMachine installation), I circled back and captured some logs.
    I ran the following command on the server in question
    tail -f /var/log/messages /var/log/secure /var/log/audit/audit.log /usr/NX/var/log/*log

    (see images)

    The command issue seems to be when nxexec is called but I am unclear how to debug this further.

    Can you help?

    Thanks in advance
    Mark

    #40330
    Britgirl
    Participant

    Hi,

    it looks like nexexec --auth is timing out. Try extending the timeout in the following key available in the server.cfg file

    #
    # Set for how long the server will wait for the authentication phase
    # to be completed on the system. By default timeout is set to 30
    # seconds. Increase this value when the authentication process on
    # the system takes longer. This setting applies also to two-factor
    # authentication.
    #
    #AuthorizationTimeout 30

    #40335
    Mark
    Participant

    Thanks, I’d already seen that

    Given that ssh connections are significantly quicker and both use PAM, I wondered whether we could add additional debugging to understand why nxexec timed out so many times

    #40389
    Mark
    Participant

    I increased the timeout to 60s and increased the debug level to 7

    I was still unable to login so have attached the nxserver.log file in the hope that someone in support is able to comprehend where the issue is

    #40408
    Britgirl
    Participant

    Hi, setting the key to 60s should be enough. If it’s not it could suggest something is wrong with your configuration. Additional debugging can be done but not via the forums. One of the team will contact you to provide further instructions.

    #40416
    Mark
    Participant

    Thanks – I will wait for someone to contact me.

    I do not believe that this will be a network issue though – as I stated, ssh connections are almost instant.

    The servers are located in an AWS facility and are authenticating against Google Secure LDAP servers

    #40427
    Britgirl
    Participant

    Thanks for the additional info. Please check your inbox

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

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