Forum Replies Created
September 30, 2021 at 23:12 in reply to: Logon screen disables mouse and keyboard input #35531
This worked for me also.June 11, 2021 at 16:06 in reply to: Can’t see local cursor #34015
I see it now, thanks.
The default for that appears to be off. That seems like a very poor choice for a default value.November 5, 2019 at 15:49 in reply to: MacOS start NX server at boot time? #24352
Yes, I can do that.October 30, 2019 at 14:43 in reply to: MacOS start NX server at boot time? #24316
It does appear that the daemon is running
ps -ef | grep -i nx
499 81 1 0 8:22AM ?? 0:01.02 /Applications/NoMachine.app/Contents/Frameworks/bin/nxserver.bin –daemon
0 259 1 0 8:22AM ?? 0:00.59 /Applications/NoMachine.app/Contents/Frameworks/bin/nxnode.bin –localsession
499 283 81 0 8:22AM ?? 0:00.01 /Applications/NoMachine.app/Contents/Frameworks/bin/nxd
0 337 332 0 8:22AM ttys000 0:00.00 grep -i nx
lsof -p 81 | grep -a LISTEN
nxserver. 81 nx 8u IPv4 0xd9cf5c8cb9495dbb 0t0 TCP localhost:21745 (LISTEN)
and a nmap command from another computer shows that it is listening on port 4000/tcp. And a connection from that other computer while at the login screen worked, and I was able to log in.
But, the behavior is inconsistent. I rebooted and tried again and the remote client showed <No available sessions on this server>. The ps and lsof command output was similar to that above. Log files for that instance have been emailed.October 28, 2019 at 09:08 in reply to: MacOS start NX server at boot time? #24272
macOS 10.14.6 Mojave
Was not installed through the command line.
Logs have been emailed.
NX> 111 New connections to NoMachine server are enabled.
NX> 162 Enabled service: nxserver.
NX> 162 Enabled service: nxnode.
NX> 162 Enabled service: nxd.
In this instance, the client appeared to be connecting then got an error: “Attempting to reconnect to ….. Error was: connection timed out. ”