brotech

[brotech]

Hello,
please try to use those 2 commands one by one (replace username by targeted user, and run both commands as that user):

Xvfb :99 -auth /home/username/.Xauthority -screen 0 1024x768x24
DISPLAY=:99 /etc/NX/nxserver –startsession

The first one will run Xvfb server, and second start session on already created display.
Command xvfb-run could help also but it terminates Xvfb when application finishes.

The command nxserver –startsession will start the session and leave the session running in the background. This command will also report whether the session was started or failed.

You could also copy xvfb-run to own script for example ‘startvirtualsession’, and modify by removing clean_up function. It could vary on version of Xvfb.

[brotech]

Hello,

the described situation is completely normal if you install NoMachine Free version, which
doesn’t support virtual sessions. You can verify it on your SuSE host using command:
/etc/NX/nxserver --version

If you really have Workstation version installed, then please enable debug in server and node configuration file, restart your nxserver then connect and log in using NoMachine player. If you are automatically connected to the system’s desktop, please send the logs to forum[at]nomachine[dot]com?

Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.

Regards

[brotech]

Hello

In node configuration file (/usr/NX/etc/node.cfg) there is a key which allows to limit
the physical desktop display available:
#
# Specify the physical display or range of X server displays which are
# made available to NoMachine connections. It is possible to specify a
# single display by display number, e.g. :0, or by port, e.g. 6000.
# Range of displays can be specified as a dash separated list,
# e.g. :0-:7 or, by port number, 6200-6204. By default all displays
# detected as running will be made available for users.
#
#PhysicalDisplays :0

Set it to :0 and you should see only one display available.
Depending on the Linux distribution, after login to Login window
the user’s desktop could start on Display :1 so set a range as :0-:10
could be better on some distros, and on others :0 is enough.

[brotech]

Hello,
in case of headless please use the command from the article:

https://www.nomachine.com/AR04K00667

In the last section “Configure NoMachine to launch LXDE on Ubuntu 14.04” there is a nxsession
script which should work correctly.
Then set DefaultDesktopCommand “/usr/bin/nxsession” in node.cfg file.

 

[brotech]

Hello,
the problem is that the application run terminated immediately. We can see:
2017-05-11 22:50:06 957.673 2075 NXNODE ERROR! Application terminated too early.

So please check DefaultDesktopCommand key in node configuration key, and set it according to
to your needs. There is also article about: https://www.nomachine.com/AR04K00667

[brotech]

Hello,

the PhysicalDisplays key in node configuration file allows to define a range of physical
displays which are accepted, and all others will be ignored, so in your case range
0-100 should be good enough.

Regarding auto attach to physical desktop, nxserver needs to tell nxplayer that there
is no other choice, which means you need to disable the possibility to create different kinds of sessions, and then nxplayer will auto attach to physical desktop.

Rules are set per user, the user logged into the system, which is not necessarily the owner of the desktop. The set of rules, which you could set per user is for example:

sudo /etc/NX/nxserver --ruleadd --class session --type unix-console --value no --user
sudo /etc/NX/nxserver --ruleadd --class session --type unix-gnome --value no --user
sudo /etc/NX/nxserver --ruleadd --class session --type unix-xsession-default --value no --user
sudo /etc/NX/nxserver --ruleadd --class session --type windows --value no --user
sudo /etc/NX/nxserver --ruleadd --class session --type unix-remote --value no --user
sudo /etc/NX/nxserver --ruleadd --class session --type unix-application --value no --user
sudo /etc/NX/nxserver --ruleadd --class session --type unix-default --value no --user
sudo /etc/NX/nxserver --ruleadd --class session --type unix-xdm --value no --user
sudo /etc/NX/nxserver --ruleadd --class feature --type enable-multinode --value no --user 

If you apply this set of rules for, let’s say, user Adam, nxplayer will auto attach to physical desktop for user Adam. And it will still be possible for a different user to create virtual session. The rule without ”–user ” switch, will apply to all users.

[brotech]

Hello,
we added an article strictly related to your issue:

Troubleshooting NoMachine in a Active Directory Domain
https://www.nomachine.com/AR04O00925

If you have any problems, let us know.
Regards

[brotech]

Hello TeutonJon78.
We are trying to reproduce problem which you described. In the meanwhile could you enable logs in server and node configurations file, then restart Windows, and after a while compress var/log directory and send to us ?

The guide how to collect logs on windows is available here:
https://www.nomachine.com/DT07M00098

Please send them to forum[at]nomachine[dot]com with
“After update to Windows 10 CU (1703) “No available session on server” as a title of the mail.

Thank You

[brotech]

Hello,
everything looks fine so far. Please attach mentioned /usr/NX/var/log/node directory.
Could You also try to connect locally using nxplayer and then sent to us again nxd.log
file ? (By locally I mean, running nxplayer on problematic host and connect to 127.0.0.1
using it).

[brotech]

Hello Mark,
it looks similar as the issue described in another thread, which happens on Kubuntu 16.04 LTS.
The problem probably is related to internal network stack, and so far we have no clue about solution or even reason.

Could you please attach also logs from /usr/NX/var/log/node directory ? It will help to confirm if
is the same issue. Then, could You show a result of following system commands as:

cat /etc/hosts
ifconfig
ping -c localhost
uname -a

There is anything different which you are using on that problematic ubuntu host? Iptables, apparmor, network card etc ?

[brotech]

Hello, could You paste Your script ?
Hard to say if you are doing something wrong.

For sure custom script as

#!/bin/bash
sleep 10


will delay session start by 10 seconds.

[brotech]

Custom scripts UserScriptAfterSessionStart could be helpful here.

The script is executed after the application starts but before the desktop is exported to the client side. The node will wait for exit of that script. So you could wait for some seconds,
or check which process is the important one to wait for.

Node executes it using these parameters:
UserScriptAfterSessionStart “” session id, username, session type, display, main session id(*), main session type(*)

(*) ‘main session id’ and ‘main session type’ parameters are available only when the user connects to an already running virtual desktop (session shadowing).

Examples of scripts are here:
https://www.nomachine.com/AR02L00787

[brotech]

Hello linuxuser,
thank you for logs, based on them we could said that there is internal
problem with network stack or configuration. Internal local connection to localhost
is refused because it is wrongly recognized as a remote one.

Could you show us results of the following commands:

cat /etc/hosts
ifconfig
ping -c localhost

About NoMachine icon color, differences are just cosmetic and depend on themes and operating systems.Can you confirm you’re using different themes on notebook and on desktop?

[brotech]

Hello Romz,
instead of nxerror.log where there are often harmless errors, please take a look in: /usr/NX/var/log/nxserver.log file for any errors reported.

If nothing useful is there, please enable debug in /usr/NX/etc/server.cfg and /usr/NX/etc/node.cfg file, restart NoMachine server (sudo /etc/NX/nxserver –restart), then reproduce the problem (connect using nxplayer on windows and get error 138 connection timeout out and send to us /usr/NX/var/log/nxserver.log file to forum at nomachine.com.

Full instructions are here:
https://www.nomachine.com/DT07M00098

NoMachine server doesnt currently have problems when disabling IPv6.

[brotech]

Hello Albert,

problem appear on server side, so logs from server host will be more helpful. You can locate them at /usr/NX/var/log/ directory as nxserver.log and nxerror.log

You should enable debug in node and server configurations files first.
Those files are available at: /usr/NX/etc directory and its filenames are: server.cfg and node.cfg.
Please set SessionLogLevel key to value 7 and uncomment it. Check the following article here for more details: https://www.nomachine.com/DT07M00098

After enable debug please restart nxserver (sudo /etc/NX/nxserver –restart), reproduce problem and send to us logs at forum[at]nomachine[dot]com.

You can archive whole logs directory using: sudo tar -zcvf nomachineLog.tar.gz /usr/NX/var/log

[Author]

Posts