Forum Replies Created
-
Posts
-
Hello,
it looks very likely to be: https://www.nomachine.com/TR04R09623
“The nxservice service starts and stops after 10-30 seconds”
workaround is inside.Please let me know if it helps.
This step:
“get the latest version of NoMachine on the web site”can be done using the command as:
wget https://download.nomachine.com/free/linux/64/deb -O nomachine.deb
it will download the most recent deb package.
Hello,
Generally you need to set up the key for every user in that user’s homedir/.nx/config directory. There is not a “one place for all users” directory.
“Error cannot accept public key” is a generic error message to avoid publishing sensitive security information. You will need to take a look in the logs on the server side where the exact error should be reported. It could be to do with a missing file, wrong permissions etc.
In case of problems with understanding, send to us nxserver.log and nxerror.log from C:/ProgramData/NoMachine/var/log directory.
Hello Zenith,
logs which you sent don’t have enabled debug for NXServer. And so I cannot help you.
Please to run this command on the server host:
sudo /etc/NX/nxserver --debug --enable server
You should see ouput as:
NX> 900 Debug mode enabled for: server
What does nxserver report to you when you run that command?
Hello Zenith, can you enable debug on server side using a command executed on your linux host (nxserver side) by root:
/etc/NX/nxserver --debug --enable serveror using sudo:
sudo /etc/NX/nxserver --debug --enable serverAfter enabling debug, please connect and login from your connecting client and with user ‘oem’.
When the problem appears again please share nxserver.log, nxerror.log files from /usr/NX/var/log/ directory and additionally /var/log/auth.log file,
and attach also server configuration file (/usr/NX/etc/server.cfg).All those files please send to forum[at]nomachine[dot]com with subject:
“cant-login-authentication-failed-please-try-again”Reproducing problem with enabled debug should allow us to find a reason for problem.
Regards
NX is using MDNS protocol for advertise its presence to other NoMachine computers, visible for example in third party tool – Wireshark.
Hello,
Preventing a user from logging in to an ED is achieved by ensuring that a user always logs in to the same host. You do this by setting “forward connection” to the specific ED for a particular user. If admin sets this for all users, then you can avoid showing ED hosts which are available and/or unavailable: the user will simply go the to ED which is for him only.
root@cs3:~# /etc/NX/nxserver –useredit adam –forward-connection ed1
NX> 106 Modifying settings for user: adamroot@cs3:~# /etc/NX/nxserver –userlist
NX> 149 NX users listUsername NX administrator Redirected to Trusted physical for Trusted virtual for Screen sharing Access Forwarded to
———- —————- ————- ——————– ——————- ————– ——- ————————————
adam enabled enabled 9de912ca-ae7b-45c2-8234-f75d363b086fHow user adam will connect to ED1? It depends on the serveradd options which are ‘ –forward-nx-methods token|system|tunnel’.
‘token’ and ‘system’ mean that nxplayer will disconnect from CS and connect directly to ED1, where tunnel
means that whole connection will go through CS. You can check how your forwarding methods are set using:
/etc/NX/nxserver –serverlistand modify using /etc/NX/nxserver –serveredit
There is a FR03R03953, “Displaying the number of users connected to the child servers”
which should be release soon in a maintenance update for v6. This might be of interest to you as well.The value of server configuration file SSHAuthorizedKeys, need to be the same as value of SSHD’s AuthorizedKeysFile config key. When is different
authentication base on pair keys will doesnt work.NXServer config file should be in: /usr/NX/etc/server.cfg
SSHD config file: /etc/ssh/sshd_configHell ndavrr,
in the NX player on Windows 7 you should use the IP of the ubuntu machine (which I understand you are doing). The port depends on the protocol (not display), for sessions using the NX protocol, the default port is 4000; for SSH connections the port is 22.NoMachine Player first connects to the NoMachine server, asks for authorization and then you choose a session to attach to or you create one.
Hello davide445,
in your logs there is no any sign of connection to nxd port (4000).
Last connections were on 14th August and since then there is no any attempt.
Please ensure that you are using the correct address/IP of the targeted Windows host, and also that your Windows host replies to ping run from the host where you run nxplayer, and uses the sam IP.Hello jsmiley,
please share logs with us. If it is so easy to reproduce, please enable debug, restart nxserver and send logs to forum[at]nomachine[dot]com making sure to use the topic’s title in the subject.
Detailed instructions on how to collect logs are described in following article:
How to gather debug logs for support requests
https://www.nomachine.com/DT10O00163Regards
/b.Hello,
access from WAN will work when nxplayer will be able to reach a nxserver’s socket. And it depends rather on your network/router configuration, not on NX. That’s why reinstall/reboot etc doesn’t help.
There article should help:
How to connect to NoMachine when the server is behind a NAT router or a firewall
https://www.nomachine.com/AR11L00827The NoMachine /var/log directory is:
%PROGRAMDATA%/NoMachine/var/log on Windows Vista, 7, 8, 8.1 and 10 or,
Documents and Settings/All Users/NoMachine/var/log on Windows XP.as described in:
How to gather debug logs for support requests
https://www.nomachine.com/DT10O00163Attach it to your reply here or you can send to forum[at]nomachine[dot]com making sure to use the topic’s title in the subject.
Hello jjgalvez,
please enable debug, restart nxserver, reproduce the problem and send logs to forum[at]nomachine[dot]com using as mail’s subject, the title of that forum’s thread ‘Frequently getting booted off’.
The whole procedure of how to collect logs is described in the article:
https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)regards
Hello,
speaking with the administrator of that remote computer probably will be the fastest way to solve login problem.Generally, an unexpected close/terminate/kill of nxplayer will immediately close the NX session on the server side. So this should be not the reason for any problem.
Anyway, first please send the nxplayer logs, so we can verify if the problem is with authorization, or later with reconnect. You can find those logs in your home/.nx directory, the most recent directory starting from R- should contain ‘connection’ which includes valuable information. Send it please to forum[at]nomachine[dot]com making sure to reference the title of the topic in the subject of the mail.
Regards
Hello,
please enable debug, reproduce issue, then gather logs as described in article: https://www.nomachine.com/DT10O00163 and send to forum[at]nomachine[dot]comPlease ensure that mail’s subject is ‘Cannot write to .Xauthority’ so we can track properly that
issue. If you could attach also the /etc/pam.d directory, it might be useful.
To make one file which contains the whole pam.d directory, run in a terminal:
tar -zcf myownpamd.tar.gz /etc/pam.d