| Git Clone URL: | https://aur.archlinux.org/nomachine.git (read-only, click to copy) |
|---|---|
| Package Base: | nomachine |
| Description: | Remote desktop application |
| Upstream URL: | http://www.nomachine.com |
| Licenses: | custom:"NoMachine EULA" |
| Groups: | network |
| Conflicts: | nxclient, nxmanager, nxnode, nxserver, nxwebplayer |
| Submitter: | FreeK |
| Maintainer: | runnytu |
| Last Packager: | runnytu |
| Votes: | 90 |
| Popularity: | 0.093385 |
| First Submitted: | 2014-07-24 15:45 (UTC) |
| Last Updated: | 2024-02-05 20:30 (UTC) |
Just a FYI. If your session terminates/crashes instead of locking it might be caused by this
https://knowledgebase.nomachine.com/TR02T10468
I had screen blacking enabled in nxserver settings and currently it seems to crash Xorg on session switch/lock.
% sudo pacman -Qk nomachine
warning: nomachine: /usr/NX/etc/NX/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/localhost/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/localhost/server.cfg.sample (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxclient.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxnode.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxplayer.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxserver.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/nxserver (No such file or directory)
nomachine: 13 total files, 10 missing files
Hi! If the "nxserver" does not listen to port 4000, then edit file "/usr/NX/etc/server.cfg", set "StartNXDaemon" to "Automatic", set "EnableFirewallConfiguration" to "1", then restart "nxserver". The problem should be fixed then.
Disregard. I had set the service to manual start (within the GUI settings) forever ago, uninstalled, and it remembered upon reinstalling.
@galvez_65 Still nothing relating to 4000 :(
$ sudo netstat -tulpn | grep nx
tcp 0 0 127.0.0.1:7001 0.0.0.0:* LISTEN 2636/nxnode.bin
tcp 0 0 127.0.0.1:22171 0.0.0.0:* LISTEN 2582/nxserver.bin
tcp 0 0 127.0.0.1:12001 0.0.0.0:* LISTEN 2636/nxnode.bin
tcp 0 0 127.0.0.1:25001 0.0.0.0:* LISTEN 2658/nxclient.bin
tcp6 0 0 ::1:7001 :::* LISTEN 2636/nxnode.bin
udp 8448 0 192.168.1.172:5353 0.0.0.0:* 2582/nxserver.bin
udp 0 0 0.0.0.0:5353 0.0.0.0:* 2582/nxserver.bin
udp 1280 0 0.0.0.0:46956 0.0.0.0:* 2631/nxexec
@parkerlreed I ran sudo netstat -tulpn to list it. Interesting when I run sudo netstat -atu (which is supposed to list open ports) it's not listed
@galvez_65 that's the thing. That's all my open ports related to nx. Nothing else shows up.
nxsever.service claims it's running fine and no errors/warnings.
@parkerlreed look for nxd, on my machine that's how it's listed
Did something change? nxserver seems to no longer be listening on 4000.
nxserver. 2003 nx 20u IPv4 39800 0t0 TCP 127.0.0.1:21277 (LISTEN)
nxnode.bi 2056 parker 14u IPv4 38680 0t0 TCP 127.0.0.1:12001 (LISTEN)
nxnode.bi 2056 parker 16u IPv6 39865 0t0 TCP [::1]:7001 (LISTEN)
nxnode.bi 2056 parker 17u IPv4 39866 0t0 TCP 127.0.0.1:7001 (LISTEN)
nxclient. 2078 parker 6u IPv4 39876 0t0 TCP 127.0.0.1:25001 (LISTEN)
I can't find any notes about a new port. The main nxserver seems to randomize.
Pinned Comments
runnytu commented on 2021-02-20 13:44 (UTC)
Since nomachine 7.1.3-2 the default behavior of the package is StartNXDaemon Manual and FirewallConfiguration 0 on a new installation, if you want to change this, you need to modify PKGBUILD build options with your desire behavior:
BUILD OPTIONS
Set to y to enable nomachine service autostart
_autoservice=n
Set to y to enable firewall autorules
_autofirewall=n
END BUILD OPTIONS