Forum Replies Created
-
Posts
-
Hello hastur18,
NoMachine authentication on Windows supports local account names and domain account names only. This means that you need to check the local account name of Microsoft account which you attempt to use, on remote machine.
In order to do so:
1. Log on to desktop of machine you want to use, using Microsoft account.
2. Click on the search icon right to the start Microsoft icon.
3. Type ‘cmd’ and press enter.
4. Inspect path displayed in console, the last part should denote the user name,
it should be something like:C:\Users\<user_name>
Hello shoe54,
What’s the exact distribution and version of your Linux? Do you use any specific technology for users management, like LDAP or Windows AD?
Logs would be useful. Can you reproduce the issue and gather nxclient logs according to these instructions:
https://www.nomachine.com/DT10O00163&dn=How%20to%20gather%20debug%20logs%20for%20support#2.1.
Send logs to forum[at]nomachine[dot]com.
Thanks!
Hello MarkG,
Nxserver.log contains entries from nxnode process only. Did you increase log level in server.cfg too? Is nxserver process running? If it’s missing, run ‘<NoMachine_installation_dir>/bin/nxserver –restart’ command in terminal, as root user. Please check if you can connect as AD user using terminal SSH client or using NoMachine with SSH protocol. If it works, the problem is most likely related to PAM configuration.
To reuse SSH PAM configuration with NX protocol:
1. Start the terminal on server machine and su to root.
2. Create the backup of NX pam configuration:
cp /etc/pam.d/nx /etc/pam.d/nx.bak
3. Overwrite current configuration with sshd settings:
cp /etc/pam.d/sshd /etc/pam.d/nx
4. Check if problem is still present.
Hello mtariqgyahoo,
For some reason nxnode process is crashing on your Linux system. Consecutive failed attempts of restarting it, lead to generation of huge number of leftover files in /usr/NX/var/db/failed directory.
It’s possible to remove them by running in terminal:
sudo /etc/NX/nxserver –history clear
To prevent creation of the next files you can temporarily disable nxserver by running:
sudo /usr/NX/bin/nxserver –shutdown
Next, we should try to understand why nxnode process is not working correctly. Gather server-side logs from your linux machine according to these instructions:
https://www.nomachine.com/DT07M00098#1
Gather, if possible, backtrace of crashing nxnode according to:
https://www.nomachine.com/AR09L00810
Send backtrace and logs to forum[at]nomachine[dot]com.
Hello Zardoc,
We failed to reproduce the issue with NoMachine Device Service shutdown timeout. However, the shutdown times of service are on average longer than 5 seconds. We will try to make them shorter in future. You can increase WaitToKillAppTimeout value and check if this helps.
To investigate further the problem with nxnode’s exception, we need to check the logs. Please, follow the instructions from:
https://www.nomachine.com/DT07M00098#3
and send logs to forum[at]nomachine[dot]com.
Hello Zardoc,
We failed to reproduce the issue so far. What Windows and NoMachine versions are you using?
Hello socoho,
It appears that modifying NX PAM configuration results in creation of one systemd session for each NoMachine PAM session. I don’t see anything wrong with that. In case you wonder, there’s one session responsible for starting, monitoring and enabling remote access to your virtual desktop and one session managing current connection to this desktop.
As for DisplayOwner, the value of this setting can only be set manually. You place there the name of account which will own the virtual desktop created during startup of nxserver. This will only take place if you enable and set:
CreateDisplay 1
In other words, the behavior you described is correct.
Hello socoho,
Properly configured NoMachine server should be able to provide you with the same user’s experience you’ve got when using your desktop locally. In fact, physical display session allows users to operate directly on current physical desktop of machine. If this session is not present in the sessions list, you most likely need to add connecting user to group of NoMachine’s administrators.
To do so, run the following command from terminal, using root account:./nxserver –useradd <user_name> –administrator
Even if above instruction help you to use NoMachine in the way you desired, the behavior of virtual session you previously described is still incorrect. I suspect that the problem might be related to NX PAM configuration. Does the issue occur when you use NoMachine with SSH protocol? If not, you can try to reuse SSH PAM configuration with NX:
1. Start the terminal on server machine and su to root.
2. Create the backup of NX pam configuration:
cp /etc/pam.d/nx /etc/pam.d/nx.bak
3. Overwrite current configuration with sshd settings:
cp /etc/pam.d/sshd /etc/pam.d/nx
4. Check if problem is stil present.
5. If so, please check what happens when you use password authentication method instead of keys.
If problem persists despite modifying PAM, gather server-side logs according to instructions from:
https://www.nomachine.com/DT07M00098#1
Send them to forum[at]nomachine[dot]com.
Hello johninconifer,
You can disable NoMachine drivers in order to check if they’re preventing correct system reboot:
– Uncomment and change value of ‘EnableDiskSharing’ key in ‘NoMachine/etc/node.cfg’ file to ‘none’.
– Uncomment and change value of ‘EnableUSBSharing’ key in ‘NoMachine/etc/node.cfg’ file to ‘none’.
– Enter ‘NoMachine/bin’ directory using command line started as Administrator and run the following commands:
‘nxservice64.exe –uninstall nxusb’, ‘nxservice64.exe –uninstall nxdisk’,
‘nxservice64.exe –uninstall nxprinter’, ‘nxservice64.exe –uninstall nxnetwork’– Restart nxserver from command line started as Administrator using command:
‘nxserver.exe –restart’
Please, check if it’s possible to reboot the system now, without stopping NoMachine Device Server first.
Hello fred1,
Installation log file is missing from logs you previously sent us. File can be found in “C:\Users\<username>\AppData\Local\Temp”, where username denotes user account used during installation. File name format is “Setup Log <date>.txt”. In case of multiple Setup Log files, send us the most recent.
You can also check if your system correctly creates new user accounts. Create a new account and log on user’s desktop.
Hello Solidcore87,
Start terminal as non-root user, enter ‘/usr/NX/bin’ directory and run ‘./nxexec –auth’ command. This will start authentication process. Can you successfully authenticate here? Gather the output of command, remember to obscure sensitive information. Additionally, gather NoMachine server logs according to https://www.nomachine.com/DT07M00098#1. Send logs and command output to forum[at]nomachine[dot]com.
Hello antonioking,
Command ‘su <user_name>’ should result in changing current user with the one passed to command. If it’s not possible for you to authenticate using this command, it’s likely that authentication issue is unrelated
to NoMachine.This command: ‘grep nxexec /var/log/system.log > nxexec.log’ will generate nxexec.log file in current directory.
You can create archive of your log files by running from terminal (as root):tar -zcf mac_os_server.tar.gz /Library/Application Support/NoMachine/var/log’
This should generate mac_os_server.tar.gz in current directory.
Hello Solidcore87,
It’s highly unlikely that your problem with google authenticator comes from NoMachine. Did you check if it’s possible to authenticate with authenticator code using different service, e.g. SSH? Can you check for presence of .google_authenticator~ file in user’s home directory? It’s known that if this file exists, it can prevent the authentication.
Hello RheineAdithia,
We’re aware of some NoMachine’s issues on Windows XP 64, but we can’t confirm that these are the same problems you’re currently experiencing. Please, provide us with:
1. Service Pack version of your Windows XP installation.
2. Setup Log file. When you reproduce the issue and the window with error pops out, don’t close the error window. Gather NoMachine installation file from ‘Documents and Settings/<current_user>/Local Settings/Temp’. Get the last file with name starting with ‘Setup Log’.
3. NoMachine server logs. Reboot system, and gather log directory: ‘Documents and Settings/All Users/NoMachine/var/log’. Remember to compress folder before sending.Send all gathered logs to forum[at]nomachine[dot]com.
Hello elad.azary,
Make sure that you start nxplayer on the desktop of user who currently owns a valid Kerberos ticket. You also need to enable Kerberos authentication in /usr/NX/etc/server.cfg on NoMachine server host.
You need to change:
#EnableNXKerberosAuthentication 0
to:
EnableNXKerberosAuthentication 1
If this doesn’t help, gather NoMachine server logs according to
https://www.nomachine.com/DT07M00098#1
and send them to forum[at]nomachine[dot]com.