Forum Replies Created
-
Posts
-
Hello mg7134_1,
Please, check the content of /var/log/auth.log after failed authentication attempt on your server host. Look for entries containing ‘nxexec’ or ‘nx’. You should also try using SSH protocol. If this succeeds, your issue is most likely related to PAM configuration, which can be found in /etc/pam.d/ directory. You can try reusing sshd’s PAM configuration with NX protocol. To do so:
1. Start terminal on your Linux server host.
2. Create backup of your original NX PAM configuration by running in terminal:sudo cp /etc/pam.d/nx /etc/pam.d/nx.ori
3. Overwrite current NX PAM configuration with:sudo cp /etc/pam.d/sshd /etc/pam.d/nxHello tom5,
It’s possible that your problem is related to access control based on AD group policy. Please, check this article, which describes possible solution to your issue:
Hello prattu,
Logs suggest that you might be experiencing dependency issue. It’s possible that one of dlls installed on your system is in different version than required by NoMachine. It’s also possible that some library is simply missing. You can try
to copy POSIX.dll from:<NoMachine_installation_dir>\lib\perl\POSIX.dll
to <NoMachine_installation_dir>\bin directory.
If this helps, please provide us with output of
where posix.dllcommand ran in cmd started as Administrator.Hello whiterussiansp,
It’s necessary to have separate nx user account on each host for NoMachine to work correctly. When you install NM on one of the domain controllers, nx account is created as domain account. This will make it impossible to install NoMachine on the second domain controller. Currently we are not aware of any workaround which would allow to create local nx account on Windows domain controller host.
Hello RHCPNG,
It’s possible that your Windows 10 host is crashing. What is causing this is not visible in the NoMachine logs.
To get more information, please inspect ‘Reliability Monitor’ logs. This article describes how to do it:https://www.howtogeek.com/222730/how-to-find-out-why-your-windows-pc-crashed-or-froze/
Hello Aubert887,
NM works out-of-the-box with standard LDAP configuration. If you have specific queries about how NoMachine works with LDAP, please write them here. Assuming that your system is already configured for LDAP authentication, but for some reason it doesn’t work with NM, the first thing to check is PAM configuration. This article can be helpful in solving potential PAM-related issues:
Hello butsuriboy,
Start NoMachine Player on your NoMachine server host and try connection to localhost. Can you successfully authenticate in such scenario with both password and private key?
Regardless of result, please gather server-side logs according to those instructions:
https://www.nomachine.com/DT10O00163#1.4
Send them to forum[at]nomachine[dot]com
The logs will tell us if indeed there is an issue with password/private key authentication or if there is another reason for which you can’t connect.
Hello joshstillerman,
Two-factor authentication with NoMachine can only be achieved through PAM configuration. This usually means password + authentication code. Currently, it’s not possible to combine PAM with public key authentication.
Hello Jojo,
It would be the best if you just set password for your Windows account. In case you prefer to stick to using blank password, please check this reply on the same subject:
https://forums.nomachine.com/topic/mint-18-3-connect-to-win-7-with-no-display-or-keyboard#post-20178
Hello,
We have found that in some rare cases NoMachine Server is unable to find POSIX.dll, which prevents it from working properly. Workaround which may help is to copy POSIX.dll from:
<NoMachine_installation_dir>\lib\perl\POSIX.dll
to <NoMachine_installation_dir>\bin directory.
Hello Dalamar,
In order to access safe mode, you should press Ctrl + F8 during system startup. If it doesn’t work, due to startup process being too fast, every fourth failed startup you will be asked to select startup options.
There are few of them, some of them allowing to display desktop. Regardless of what you pick, you should be asked to choose user with Administrator’s rights. NX account is technically member of Administrators group, however, this is not an account which is meant to be logged on interactively. It’s for NoMachine’s internal use only. Please, pick another Administrator account. In the rare case your admin account got somehow accidentally removed or corrupted, you can try ‘Repair your computer’ option, accessible from Windows installer. Boot from your Windows installation media and choose ‘Repair your
computer’ instead of ‘Install now’.Hello Mohamed,
We need some clarification of the issue you are reporting. You are using terminal ssh client on your Mac host to connect to the server. On server you are attempting to run some nxserver commands requiring administrator’s rights. Please, confirm that our understanding of situation is correct.
What is the operating system of NoMachine server host on which you are trying to run nxserver commands?
What’s the output of id command ran after you switch to root account with ‘sudo su’?
What NoMachine version and product you have installed on the remote server?Hello mrosing,
The error means that some internal PAM module failure occured. PAM errors are usually written to /var/log/auth.log on Ubuntu host. Please, check if you can find anything useful there. Can you share the output of ‘grep -r “nxexec” /var/log/auth.log’?
You can also try modifying PAM configuration for NX protocol authentication, residing in /etc/pam.d/nx file. If the problem doesn’t occur when SSH protocol is in use, you can try to reuse SSH PAM configuration with NX. You can achieve that by running as root:cp /etc/pam.d/nx /etc/pam.d/nx.ori
cp /etc/pam.d/sshd /etc/pam.d/nx
Let us know if this solves the issue.
Hello Ice_Bird,
Please make sure that the user name you are providing during NoMachine connection is the valid Windows 7 account name. We don’t support Windows user friendly names. If you aren’t sure what is the proper account name, log on your user’s desktop on Windows 7 machine and start cmd. In console window you should see text with format: C:\Users\<user_name>, the last part is what you should use during NM connection. Your account also needs to have password set, it’s not possible to use empty password by default.
If none of above is helpful, gather server-side logs according to those instructions:
https://www.nomachine.com/DT10O00163#1.4
Send them to forum[at]nomachine[dot]com