Forum Replies Created
-
Posts
-
Can 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.Hello 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.Hello SILKWINGS,
Please, check this reply: https://forums.nomachine.com/topic/first-time-connecting-session-negotiation-failed-error#post-34887
Hello 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.
Hello 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.
Hello 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!Hello 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?
Hello 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"?Hello 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.
The 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.
Hello Maykro,
What’s the output of the following command ran from command line on your Windows host?
C:\Users\HP>”c:\Program Files (x86)\NoMachine\bin\nxservice64.exe” –status nxlsa
You need to use path to NoMachine’s installation directory valid on your system.
Hello Maykro,
Please, follow this guide on how to export Windows event logs:
We need Windows Logs/System, Windows Logs/Security and Windows Logs/Application. Please send logs to forum[at]nomachine[dot]com, referencing the topic in the email subject.
Hello eh2006re,
Does the server-side keyboard layout match the one on the client-side? The most likely scenario is some kind of input mismatch between characters you type in your client and what is printed to the password field on the server. This could be due to the different mappings of keyboard keys between hosts. To verify if this is the case: start NoMachine connection to your Elementary server and type your password to some field in which cleartext input is printed. This can be a username field or password field with the option of visible characters enabled. Check if the password is printed correctly.
Hello giobaxx,
What exactly do you mean by Ubuntu freezing too often? Does it mean that NoMachine session becomes unresponsive or that Ubuntu OS hangs and a reboot of the system is necessary? If it’s the latter, you should check for possible clues in system logs, on Ubuntu those would be
'/var/log/syslog‘,'/var/log/kern.log'and'/var/log/auth.log'. If it’s a problem with the NoMachine session, please provide us client and server-side logs gathered according to:
https://www.nomachine.com/DT07M00098#7
https://www.nomachine.com/DT10O00163#1.1
and send them to forum[at]nomachine[dot]com, referencing the topic in the email subject.As for the errors you see inside the terminal, they match the problem described here:
https://askubuntu.com/questions/608330/problem-with-gnome-terminal-on-gnome-3-12-2
This doesn’t appear to be related in any way to NoMachine.