Forum Replies Created
-
AuthorPosts
-
CatoParticipant
Hello gcollins,
Can you try to use root’s credentials in prompt asking for user with administrative rights?
CatoParticipantHello 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.
CatoParticipantHello 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.CatoParticipantHello,
NoMachine doesn’t support passing of user’s credentials to the desktop of server host.
September 20, 2021 at 18:18 in reply to: Authentication error after restarting – if I reinstall, it works #35371CatoParticipantCan you please make sure that nx user privileges are preserved across reboots? If they are and the problem persists, gather server-side logs according to these instructions:
https://knowledgebase.nomachine.com/DT11R00181#1.4
Send them to forum[at]nomachine[dot]com, referencing the topic in the email subject.CatoParticipantHello likag16219,
Some log files appear to be missing. Please, reinstall NoMachine and if an issue persists gather server-side logs according to these instructions:
https://knowledgebase.nomachine.com/DT11R00181#1.4
Send them to forum[at]nomachine[dot]com, referencing the topic in the email subject.September 14, 2021 at 16:25 in reply to: Authentication error after restarting – if I reinstall, it works #35259CatoParticipantHello SILKWINGS,
Please, check this reply: https://forums.nomachine.com/topic/first-time-connecting-session-negotiation-failed-error#post-34887
CatoParticipantHello neidai,
It appears that ‘nx’ user doesn’t hold the privilege required for starting the nxnode process. In this case, most likely ‘Act as part of the operating system’ is missing. This is the list of all privileges needed by ‘nx’ account:
Act as part of the operating system
Log on as a service
Adjust memory quotas for a process
Replace a process level tokenYou can find all of them described here:
https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/user-rights-assignmentRemember that domain group policy can override local group policy settings.
CatoParticipantHello Tom,
Missing server.cfg file suggests some issue during installation process. Please, try reinstalling NoMachine on your Windows host and make sure that file is in place. Regarding possible authentication problem, does username or password you are using contain any special or diacritical characters? Is there any difference between keyboard layouts between client and server-side? What happens when you attempt authentication from client started on server host? Do you use local account or domain account?
If problems persist, gather server-side logs following these instructions:
https://knowledgebase.nomachine.com/DT11R00181#1.4
Send them to forum[at]nomachine[dot]com, referencing the topic in the email subject.As for users DB, by default it’s used only internally, no action is required to enable NoMachine access for accounts valid on system. If you can log on to Windows desktop, you should be able to connect to NoMachine Server using the same credentials.
CatoParticipantHello diana12,
Does the failure occur before or after authentication dialog? If it’s after authentication, what authentication method did you use?
Does the problem persist if you use local account instead of domain account? Please, reproduce the issue and gather server-side logs following these instructions:
https://knowledgebase.nomachine.com/DT11R00181#1.4
Send them to forum[at]nomachine[dot]com, referencing the topic in email subject. Thanks!CatoParticipantHello jkissane,
The errors mean that passwd structure describing the user account can’t be obtained for user “john.kissane”. This is usually caused by missing entries specifying user data source in
/etc/nsswitch.conf.
To make sure that your system is correctly configured, please run the following commands from terminal as root user on your NoMachine Server host:getent passwd john.kissane
getent group john.kissaneDo they produce correct outputs?
CatoParticipantHello ebiscaia,
For some reason, nxservice.log, nxerror.log and nxserver.log files are missing. Can you check if you can find them in
"ProgramData\NoMachine\var\log"
?CatoParticipantHello dropbrick,
It appears that ‘nx’ user doesn’t hold the privilege required for starting the nxnode process. In this case, most likely ‘Act as part of the operating system’ is missing. This is the list of all privileges needed by ‘nx’ account:
Act as part of the operating system
Log on as a service
Adjust memory quotas for a process
Replace a process level tokenYou can find all of them described here:
https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/user-rights-assignmentRemember that domain group policy can override local group policy settings.
CatoParticipantThe output of command indicates that the nxlsa.dll module, required by NoMachine Server, is correctly installed, but it wasn’t loaded by lsass.exe Windows service. Please, check if ‘nxlsa.dll’ file is present in ‘C:\Windows\System32’ directory. If it resides there, you need to perform another OS reboot.
CatoParticipantThere is a typo in command, it should be
--status nxlsa
, not-status nxlsa
. -
AuthorPosts