Forum Replies Created
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.August 20, 2019 at 11:10 in reply to: Able to connect to Linux but not to Windows (dual boot PC) #23344
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.May 14, 2019 at 16:18 in reply to: Will not install correctly under Lubuntu 18.04, LXDE #22332
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
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
The 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
Attach 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.
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”)
regardsApril 29, 2019 at 09:14 in reply to: Forgot to disconnect session and cannot log in again #22151
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.
please enable debug, reproduce issue, then gather logs as described in article: https://www.nomachine.com/DT10O00163 and send to forum[at]nomachine[dot]com
Please 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
Lets focus on remote node. If you have correct permissions when logging in there using SSH, please create backup of /etc/pam.d/nx and then copy /etc/pam.d/sshd over /etc/pam.d/nx. After that, try to start NX session again on the TSN.
If your remote node uses pam_mount module, then this article might be helpful: https://www.nomachine.com/AR09N00902
we checked the output of strace command, and we don’t see anything suspicious. Environment seems to be set correct (DISPLAY/Xauthority), there is a connection to the X display from app, so everything looks OK.
As I understand in that mate desktop all other apps are working well, and there is no problem with running any application except this Java one, so please try to speak with the developers of that program, how to debug and why their application doesn’t appear on desktop.
we received the ss.output file, and clearly see that your app is connected to our Xserver.
Now lets see if output of strace command could give some additional information that’s useful for understanding why you can’t see the app.
Please run a command in terminal:
strace -v -f -o java.trace <program command line>
and share with us java.trace file.
Hello seems, that there is no clear message from your app in provided logs. There could be many reasons why the application doesn’t appear, for example, using fixed DISPLAY variable will provide a similar result.
Maybe the application reports error messages on its stdout? Could you try to run terminal in your mate desktop, then run your application and save the output if any appears?
Some information could also give a output of ss command, running when your Java application is running.
Run another terminal and execute there:
ss -xp > ss.output
then share with us ss.output file, and please provide also PID of your Java application.
based on your description, it’s unclear if you are connecting, logging in as NIS user and then
encountering the problem, or if it is a problem with the connection before the authorization stage.
If you get the problem with connecting to NX Server please attach the nxplayer’s session directory
locate at a userhome/.nx directory. Its recent directory started with R letter.
If the problem happens later (during or after authorization), then we would like to see
nxserver side logs, located at /usr/NX/var/log directory.
You can send a compressed file directly to forum[at]nomachine[dot]com or attach here.
no there is no ‘transparent’ mode. You can use Guests (thus avoiding log in on Cloud Server) but those connections will be logged as Guests on final host.
there is an article which describes this precise configuration:
How to set up key based authentication with NX protocol
Should there be any problems with access to authorized.crt file, they are reported in nxserver.log file instead of nxerror.log.
In the case of problems, please log on to the desktop of a different user, start terminal, su to root and execute command:
/bin/bash -c "cd ~ <user> 2>/dev/null && pwd"
where is the name of user which you are trying to authenticate with key-based authentication.
Does it return the proper home directory path?December 7, 2018 at 10:16 in reply to: Two nxserver.bin process active and nxnode.bin blocked #20720
Hello, if nobody is connected, there should be running one nxserver process (nxserver –daemon) which keeps all nx processes under control, and nxnode agent. When there is no session, the nxnode process is idle. When the system sees it as ‘not active’, it will wake up and start to work when someone connects.
We were not able to reproduce the behaviour of NX on OS X as in your case, so please share logs with us:
– Execute the command tar -czf stacks.tar.gz ~/Library/Logs/DiagnosticReports/nx*
– Execute the command sudo tar -czf nxvarlog.tar.gz /Library/Application\ Support/NoMachine/var/log/
In the Finder window you’ll find the files stacks.tar.gz and nxvarlog.tar.gz. \
Please send them to forum[at]nomachine[dot]com.