reza

[reza]

Are you using LDAP?

How your installation is differ from?

Commands are not executed with help of sudo.

You can try to test them manually with:

$ sudo su - nx -s /bin/bash

$ /bin/ps awwxo ppid,pid,sid,comm,args

$ /bin/netstat -ln --protocol=unix

[reza]

There is no API or any other interface in NoMachine that you can use to control Player.

However you can use third party automatisation solutions like for example Sikuli – http://www.sikuli.org.

It’s a tool used by us and it works great.

[reza]

Hello,

It’s not only nxd that fails with signal 13. Even system tools like ‘netstat’, ‘ps’, ‘ck-list-sessions’ are failing in the same way.

Do you have AppArmor or SELinux enabled?

Can you check system logs to see why execution of all these commands is blocked?

[reza]

Yes, please pass that logs to us.

Thank you.

[reza]

We will need debug NoMachine server logs to investigate. Please follow the instructions here:

https://www.nomachine.com/AR07K00677

 

Then reproduce the issue and please gather logs.

Send them to forum[at]nomachine[dot]com

[reza]

NX user is a system user that help NX Server manage connections, session and other things. No one can log in as NX user and use that account.

If you need just a client please use NoMachine Client Enterprise, it doesn’t create a NX account.

[reza]

A problem you are experiencing is related to a way how NX identify host keys. Host keys are recognised with just a hostname without specifying port so multiple services exposed on multiple ports on the same host are treated as one. We are going to fix it soon.

In the meanwhile, if you are using a enterprise version of NoMachine, you can use SSH protocol or bind your tunnels into separate IPs assigned to loopback interface.

For example:

-L 127.0.0.2:4014:127.0.0.1:4000

-L 127.0.0.3:4015:127.0.0.1:4000

-L 127.0.0.4:4015:127.0.0.1:4000

…

[reza]

Remote login to Windows with empty password is forbidden by Windows policies:

https://www.nomachine.com/AR05L00802

Administrator GUI instead should allow authorisation with empty passwords, we have a trouble report about it:

https://www.nomachine.com/TR03M05052

[reza]

Right now defining interfaces to listen is not possible.

We will consider providing a config file key to control it.

However you can do workaround by moving nxd binary to nxd.bin and creating a nxd script.

Script can execute nxd.bin with additional argument ‘-l 127.0.0.1’.

[reza]

You can disable it in server.cfg by setting EnableFirewallConfiguration key to 0.

[reza]

Please keep in mind that ARMv7 packages are intended to work only on ARMv7 device (Raspberry Pi 2) running ARMv7 system (Debian, Ubuntu, Fedora).

If you are using Raspberry Pi or Raspberry Pi 2 running Raspbian (ARMv6 system) please use ARMv6 packages.

[reza]

It’s currently not possible to run NoMachine for Android on Chromebook. Chromeos-apk tool doesn’t work with applications that use native libraries. At least if application is compiled to ARM and Chromebook have x86 CPU.

https://github.com/vladikoff/chromeos-apk/issues/54

We will investigate if recompilation to x86 can solve that problem.

So currently a only possible way of using NoMachine on Chromebook is a NoMachine Web Player which is a part of NoMachine Cloud Server. You can see how it works by downloading NoMachine Cloud Server evaluation package.

Currently we are working on NoMachine Quick service intended to provide web access without the need for installing NoMachine Cloud Server. Please take a look at the bottom of this page:

https://www.nomachine.com/people

[reza]

Please take a look at corresponding feature request https://www.nomachine.com/FR02M02867.

Initial version will be compiled for ARMv7 armhf so you will need one of these images to play with it:

http://www.raspberrypi.org/forums/viewtopic.php?t=98997

http://sjoerd.luon.net/posts/2015/02/debian-jessie-on-rpi2/

ARMv6 armhf compilation for Raspbian is next in queue.

 

[reza]

Please assure that before starting gnome-session a correct DISPLAY environment variable is set.
Step 6: Run the desktop environment
$ DISPLAY=:0 nohup /etc/X11/Xsession gnome-session &

[reza]

You can limit access to your system by adjusting PAM configruation – http://www.linux-pam.org/.

As a alternative you can implement a script executed by NoMachine server after successful authorization.
Script can check who is already using NoMachine and return a error if there is already a session started by that user.

https://www.nomachine.com/DT01L00064#9

[Author]

Posts