Forum Replies Created
June 21, 2017 at 08:40 in reply to: Two-factor auth with Yubikey #15122
two-factor authentication with YubiKey is not supported yet, neither via NX protocol nor with SSH protocol,
but we have in plan to add it:
But at the moment, with some additional configurations is possible to authenticate
with YubiKey from Linux client to Linux server (via SSH protocol), but not from Windows client.
If you are interested to this solution, we can provide more details.February 2, 2017 at 12:29 in reply to: Authentication error with correct username #13671
We need some more information for our investigation.
Can you send us /etc/pam.d folder from Ubuntu also /usr/NX/var/log folder.
Also output of ‘cut -d: -f1 /etc/passwd’ command.
And user name you are trying to authenticate with.
Also output from ‘arch’ command and package name you have installed on Ubuntu.April 4, 2016 at 09:41 in reply to: Clean install – “Authentication failed, please try again” #10808
We used your pam config files but we could not reproduce the issue.
So please can you send us Centrifydc config file and
Please look at the following link:
It explains that you first should update Centrify and then OS.
Did you update everything as suggested in this article?
Also, here we have a newer version 5.3, whereas you have (5.2.4).
Updating to the recent release of Centrify might be an option for you?January 21, 2016 at 16:16 in reply to: [Windows 8.1 Pro] Installation hung on checking computer configuration #9726
We can reproduce this issue by installing to D:\Utilities\Remoting\NoMachine\x86\;
the installation hangs.
But if we install to D:\Utilities\Remoting\NoMachine\ then for us everything works fine.
So it is an installation path problem. This path is too long. It appears to be a limitation in Perl which sets limitations on the path. We’ll open a Trouble Report.
For now, we suggest to use a shorter path such as D:\NoMachine.December 18, 2015 at 09:58 in reply to: Server does not start properly on Jessie #9376
There is a second solution too.
You can follow all steps that where described in previous post. But instead of removing pam_mount entry you can add disable_interactive option next to pam_mount.so.
It should be like:
session optional pam_mount.so disable_interactiveJune 19, 2015 at 14:23 in reply to: NoMachine 4.6.4 PAM problem #7546
From the output of your command we can see that your OS is x64 bit architecture.
The package you have installed is for x32 bit architecture.
Please remove the current package and install nomachine_4.6.4_13_x86_64.rpm.June 17, 2015 at 12:24 in reply to: NoMachine 4.6.4 PAM problem #7515
Please can you run this command: ldconfig -p | grep libpam*
This command will help us to find what pam libraries are installed on your machine.