Forum Replies Created
May 29, 2020 at 09:35 in reply to: NX service not accessible #27834
Copying \lib\perl\POSIX.dll to \bin\POSIX.dll did indeed enable the NoMachine service to run without exiting. Thank you for the advice, and I look forward to seeing this fix made in the product itself.May 29, 2020 at 08:35 in reply to: NX service not accessible #27832
Thank you for the link; I’ll try it out.
One comment: in the workaround, \libperl\POSIX.dll should be \lib\perl\POSIX.dll (with a slash between “lib” and “perl”).March 26, 2020 at 18:26 in reply to: NX service not accessible #26226
I run Bitdefender Antivirus Free Edition. There are no events, quarantines, or exclusions noted for NoMachine files or processes.
I don’t use hard-drive encryption.
I’m using the default Windows Defender firewall, with private network exceptions allowing NoMachine Client, NoMachine Device Server, NoMachine Display Monitor, NoMachine Node, NoMachine Player, and NoMachine Server. See attachment.
Attachments:March 25, 2020 at 17:11 in reply to: NX service not accessible #26191
Thank you for your response.
I’ve uninstalled NoMachine, rebooted, reinstalled NoMachine, rebooted, set debug logging, and tried starting the server again. NoMachine reports “Server running”, but no process is listening on port 4000 (confirmed with netstat -an) and I get a connection timeout when attempting to connect to the server from a remote client instance.
If I click into Server preferences > Services on the affected machine, the NX service says it’s stopped. I can start it, but this makes no difference to netstat output or to client connection attempts, and the next time I check it, it shows as stopped again. The Service logs > Export button has no effect; I can select a directory, but no files are saved there.
Debug logs attached.