LDAP and NoMachine Enterprise Terminal Server

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

Viewing 3 posts - 1 through 3 (of 3 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
    Keymaster

    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

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

You must be logged in to reply to this topic.