Forum Replies Created
May 16, 2014 at 14:26 in reply to: Fresh install cannot password authenticate #3644
could you please specify which protocol you use when you try to connect to the problematic server? Is it NX or SSH? In any case, please send us /usr/NX/var/log/nxerror.log from the server and compressed $HOME/.nx from client, after reproducing the issue. Before you try to reproduce the problem please make sure that client will not remove logs after you close it. To do so open the Player and go to Preferences -> Appearance and check “Don’t delete old log files on exit”.
Thank you.May 16, 2014 at 08:08 in reply to: Problems on MacOSX if in an AD domain? #3621
Regarding your second problem. Could you please give us the outputs of the following commands:
sudo -l -U <user>
Could you also tell us how do you put credentials for su / sudo commands on this Mac? Is it in username/password or username@domain/password or DOMAIN\username/password format? It would be very helpful if, after reproducing the issue, you would send us /Library/Application Support/NoMachine/var/log/nxerror.log file. You can attach it to the forum post, or it it’s too big (it shouldn’t be) – send it to issues[at]nomachine[dot]com. Thank you.
May 13, 2014 at 14:23 in reply to: Printer sharing working in Windows, not OS X? #3568
- This reply was modified 9 years ago by adp.
Yes, this issue should be fixed in nomachine_4.2.22_1. Can you confirm that you have installed this version on both client and server machines? So that your Mac OS host is also running 4.2.22_1? If so, this is a new issue and something different than problem tracked by trouble report ‘TR04L04395’. It would be useful if you’d provide a little bit more info. To be precise:
1) OS (with version) of the client machine.
2) OS (with version) of the server machine.
3) Where is the printer attached physically.
4) Exact steps to reproduce the issue.
Also it would be helpful if you could send compressed $HOME/.nx directories both from client and server side after reproducing the problem. Please note, that before collecting the logs you should make sure that they are not deleted after session ends. To do so please:
– On server side edit the /usr/NX/etc/node.cfg file, uncomment the following key and set it to ‘0’:
– On client’s side, open the Player and go to ‘Prefferences’ -> ‘Appearance’ and check the “Don’t delete old log files on exit”.
The logs may be too big to attach them on forum. In that case please send them to issues[at]nomachine[dot]comMay 8, 2014 at 14:10 in reply to: How to debug disk redirection #3496
Hi, we are trying to support all possible distro/WM combinations. ALTLinux is not currently in our supported distros list. See this article for more information:
That said, if you’re willing to help we can provide you with debug version of our library that is responsible for devices forwarding so that we could gather more debugging info. Please let us know, and we’ll give you more detailed instructions.May 8, 2014 at 10:40 in reply to: Fedora Linux firewall commands to enable NoMachine version 4.x #3489
Firewall rules in Fedora were added to NoMachine 4.2.15, so if you are not using the latest version (you say you are using 4.0) then this could be the reason for why it’s not working.
We have not been able to reproduce. If you -are- using the latest version, please send us output of the following command (ran as root):
iptables -L INPUT -n –line-numbers
It would be helpful to have the output before and after NoMachine installation, but the latter is more important.April 29, 2014 at 16:55 in reply to: Printer sharing working in Windows, not OS X? #3382
We confirmed that there is indeed a problem with printing when device is being shared from client on Mac OS. We’ve inserted a trouble report: https://www.nomachine.com/TR04L04395 . The fix for this issue will be included in the next update.
April 29, 2014 at 12:38 in reply to: Error: Cannot accept public key #3377
- This reply was modified 9 years, 1 month ago by adp.
There are a few steps that need to be carried out in order to make key-based authentication work with NX protocol. They are described in this article:
Could you make sure that you’ve followed them and check if this solves your issues?April 27, 2014 at 17:24 in reply to: Screensaver locks my screen in Debian 7 KDE desktop #3312
Could you please specify if the session is interrupted by screensaver (so the screen goes black and after slight movement of mouse or keyboard it returns) or by screen lock (session is locked and the password must be entered again to unlock it)? Secondly, could you please tell us what are your screensaver and energy settings?
To do so please, while inside the NX session, open K menu and click “System Settings” (If the icon is not visible right away, type System Settings in the search bar). Then click “Power Management” and please tell us what is set under “Dim Display” and “Suspend Session”. The “Button events handling” section may also be interresting.
Then please go back to “System Settings” and go to “Display and Monitor” -> “Screen Saver” and please share what’s set in the “Settings” section. So which options are checked and what are their values.
Thank you.March 20, 2014 at 13:29 in reply to: Prevent password authentication with NX protocol and key-based authentication #2746
This can be achieved by editing server.cfg and setting the EnablePasswordDB key to ‘1’.
This will set the server to allow password authorization only for users that are in server’s password DB. Since there will be no user in the database, no one would be granted the privilege of password login.
Key-based authentication will still work.March 7, 2014 at 18:47 in reply to: Authentication failed with error 6 #2669
Error 6 means that permission is denied for the user. If you say that you enter the proper credentials then we might need some more info to figure out what goes wrong. If you could send us to issues [at] nomachine [dot] com the following information from your CentOS host:
1) /etc/pam.d/nx, /etc/pam.d/su, /etc/pam.d/system-auth, /etc/pam.d/sshd, /etc/pam.d/password-auth files
2) output of the command (after reproducing the issue):
sudo grep -r nxexec /var/log/*
Thank you.February 24, 2014 at 09:40 in reply to: RSA key-based SSH authentication fails on NX 4.1.29 #2508
It appears that you are using NoMachine (free) which doesn’t support the SSH protocol. You can use key-based authentication with the NX protocol, a step-by-step how to is available here: http://www.nomachine.com/AR02L00785
If you need to use the SSH protocol, you should consider using NoMachine Worstation instead.February 20, 2014 at 10:24 in reply to: User Login with private key file #2442
Could you please reiterate, step by step, what you are doing to get the error message? From your post I understand that you have been successfully logging in as root to your machine using key authentication. Then you’ve created a new user (let’s call him USER1). Should this user authenticate using his username and password instead of the key or do you want USER1 to be authenticated also via key? In any case, please clarify the following:
1) Are you using NX protocol or SSH protocol?
2) Have you set proper authentication method in NoMachine GUI (Key or Password)?
3) In the case of key authentication – have you pointed NoMachine to the appropriate private key (the one for USER1). Have you put the public part in the appropriate place on the host?
Attaching (or send to issues[at]nomachine.com if file is large) log files from both sides of the connection would also be helpful to us. Please remember to set in Player’s settings to not delete logs (Setting -> Appearance -> Don’t delete old log files on exit), reproduce the issue and on the client side:
<your_home_dir>/.nx <– Compress this directory and send it to us
On the server side:
/usr/NX/var/log <– Compress this directory and send it to us.
Thank you.February 14, 2014 at 09:27 in reply to: Can’t authenticate / Timeout – Evaluation copy #2294
From the logs it appears that you are trying to connect using SSH. Are you able to ssh in to the server host with another Windows SSH client (e.g. Putty or other)?
Additionally, it would be a good idea to send us the <user’s home>/.nx/R-(newest-dir)/connection file of the whole .nx from the client side. Make sure you check ‘Do no delete logs’ in the player before reproducing the issue. Attach them in the forum, or if it’s a large file, send it to issues[at]nomachine.com
Thank you.January 27, 2014 at 16:34 in reply to: NoMachine 4.0.369 PAM and Kerberos authentication problem #1894
NoMachine should suit your needs out of the box without any additional server configuration. Please excuse the confusion caused by the EnableGSSAPIAuthentication key of our server’s config file. This key is obsolete and should no longer be used. This will be corrected in the upcoming 4.1 release.
And to answer your question – to use PAM with Kerberos in NoMachine the only steps you need to carry out are:
1) If you have already changed EnableGSSAPIAuthentication in server.cfg to 1, please change it back to 0 or comment it out. If you’ve just installed the server, you don’t have to do anything.
2) In the Player please be sure you’ve chosen NX protocol with password authorization.
3) Start the connection, enter your username and Kerberos password. That’s it. This procedure should have you authenticated with Kerberos using PAM.