Forum Replies Created
-
Posts
-
Logs indicate that nxlsa module was already installed when you attempted to install NoMachine 8.2.3. Please, perform full reinstallation of NoMachine with all necessary reboots. One reboot after uninstallation and one reboot after fresh installation. Does it help?
To investigate further we need logs, please follow these instructions explaining logs gathering procedure:
Collect server side logs automatically
https://kb.nomachine.com/DT07S00243Send logs to forum[at]nomachine[dot]com, referencing the topic in the email subject.
Hello Will,
Does rebooting the system help? What’s the output of <NoMachine>/bin/nxserver.exe –status ran from cmd? Does ProgramData/NoMachine/var/log/nxtrace.log exist, if so, what’s the content of this file?
Hi,
Yes, ‘no_root_squash’ is an export option. What I meant is to mount directory exported with ‘no_root_squash’. It seems that you figured that out for yourself 🙂 Did it help?
Hello RSeJU17Cc4ch,
If your email address is a Microsoft account name NoMachine should work fine with it. The problem might be 2FA. How exactly is this implemented? Is this Microsoft’s 2FA or some third party extension to Windows’ authentication? Can you create local account on your host and see if it’s possible to authenticate with just password?
Hello,
Sorry for late reply. Can you check if mounting user’s home directory with no_root_squash option helps?
Hi,
Logs show that ‘nx’ account creation succeeds, but it’s not possible to correctly load user’s profile. It might be due to the aforementioned system administrator restrictions. Other possible cause is corruption of default user profile on your host.You can try to create a few user accounts and check if it’s possible to login on their desktops. If you experience any problems, please refer to this Stack Overflow thread:
https://superuser.com/questions/947398/cant-login-with-new-local-users-in-windows-10
Hello andowt,
You mentioned Active Directory SSO, do you mean Azure AD SSO? Error message ‘cannot create home directory of nx user’ suggests that something went wrong during nx account setup. Perhaps the system administrator imposed restrictions preventing normal user from new account creations. To investigate further we need logs, please follow these instructions explaining logs gathering procedure:
Collect server side logs automatically
https://kb.nomachine.com/DT07S00243Send logs to forum[at]nomachine[dot]com, referencing the topic in the email subject.
Hello fractal-admin,
When krb5 option is used, process accessing mounted directories need to have valid Kerberos credentials. This means that you either need to connect using Kerberos authentication with ‘Forward authentication’ enabled or password authentication with PAM stack for NX procotol configured so that it correctly obtains Kerberos ticket during authentication. The second option only works with virtual desktops.
NoMachine allows administrative operations to be performed on Linux only by root account or by demonstrating administrative privileges by being able to ‘sudo su’.
Hello gcollins,
Can you try to use root’s credentials in prompt asking for user with administrative rights?
Hello JMiller,
It looks like an issue with missing privileges of nx user account.
Please, check this reply: https://forums.nomachine.com/topic/first-time-connecting-session-negotiation-failed-error#post-34887Let us know if enabling missing privileges and restarting nxserver solves the issue.
Hello pvm,
If the problem is only with one of a few client machines this usually means some networking/connection issue. Can you ping server host from your client? If you make sure that server host is reachable, but problem persists, follow these instructions to gather full set of client and server-side logs:
https://knowledgebase.nomachine.com/DT11R00181
Send them to forum[at]nomachine[dot]com, referencing the topic in the email subject.