Britgirl

[Britgirl]

Biglia, nothing in the logs shows there is a problem in NoMachine, and it’s likely that there is system miconfiguration or something corrupt in the system. You should verify that “wkscli.dll” (Workstation service client) is valid and not corrupted. Also check that there are no multiple copies of the DLL which might be getting hijacked. Is this a corporate-managed PC with particular policies being configured?

[Britgirl]

pawelgl, restart is necessary after installing. Do you mean you have to restart the server every time you want to connect to any of the Windows hosts? When it happens, what message is shown? If it occurs again, please submit the logs from both the player and the server machines. To do that, follow the instructions here and then send them to forum[at]nomachine[dot]com. It could be a different issue, and if that’s the case we can create a new topic. Thanks!

[Britgirl]

Sorry, my mistake. I’ve corrected the path example I made.

[Britgirl]

Hi, can you also send us the .nx folder from the user’s home of the Windows computer (typically found in C:\Users\USERNAME\.nx)?

[Britgirl]

I’ve sent you a link to a new debug package.

[Britgirl]

Hello, we are planning to improve support for HiDPI displays in a future version (not version 9). With this implementation, NoMachine will be able to capture the screen of the server at native pixel resolution on HiDPI displays, but it will also introduce improvements to the appearance of the user interface on such displays.

[Britgirl]

Hi, the logs we received did not have debug enabled. Please enable debug as described in the instructions in my earlier reply, reproduce the problem again, then gather the logs. An updated journalctl and ps -ef should be provided so that they are aligned. Thank you.

[Britgirl]

Hi, I sent you an email with the link to download the debug package 🙂

[Britgirl]

NoMachine does not provide a package specifically for NixOS, you can check the list of officially supported distributions here: https://kb.nomachine.com/AR07H00568.

You can try installing the tar.gz to another directory and not /usr e.g

sudo tar zxf nomachine...tar.gz -C /opt/
sudo NX_INSTALL_PREFIX=/opt /opt/NX/nxserver --install redhat

[Britgirl]

Hi, thanks for submitting this. If you don’t need the server component for your computer (i.e you don’t want to be able to connect to this computer, but you only want to use it as a device to connect from), you could also try installing Enterprise Client which can also be installed using a regular account (without admin privileges).

[Britgirl]

Hi,

did you install just the client i.e Enterprise Client, or is it a client/server product such as the NoMachine free version? If you installed the latter, is the server running correctly and accessible from the system tray?

When it happens, can you check in the Task Manager if the nxplayer.bin process is running but its window does not open, or is there no nxplayer.bin process open at all?

It would be useful to see the NoMachine logs from the affected Windows host. Look for the .nx directory, on Windows the .nx folder is hidden. To find it, write the following in the address bar or the explorer, for example C:\Users\your_account\.nx). Also send the full nxtrace.log of that excerpt. Please send everything to forum[at]nomachine[dot]com.

[Britgirl]

Yes 🙂 We are preparing it and we will be sending you a link to a package for you to download.

[Britgirl]

Can you forward those logs to forum[at]nomachine[dot]com?

[Britgirl]

Hi, we are not able to reproduce the problem connecting to macOS 14 in our lab. Check that USB sharing is still enabled on the server side.  On the Mac server side, check the node.cfg file:

Disabling USB Forwarding
To forbid USB device sharing it is necessary to uncomment and set a proper value for the EnableUSBSharing key in the node configuration file:
client USB devices on the client can be forwarded to server side and made available within the session.
server USB devices on the server can be connected to the end-user’s machine.
both Client and server USB devices can be connected to remote and local sides respectively.
none Neither client or server USB devices can be connected.

More about this is here: https://kb.nomachine.com/DT10R00171#13.4

Are you responsible for the NoMachine server or was the instance created for you by the provider? It sounds more like an issue with Scaleway.

[Britgirl]

Can you share this dockerfile with us so we can check it? Send it directly to forum[at]nomachine[dot]com.

Similar topics have been submitted in the past

NXFrameBuffer failed to start in Docker

Problems with NoMachine in docker

Redis error after time

but in some cases users didn’t come back to us.

Edited: we have the following document for Docker users https://kb.nomachine.com/DT07S00242. Did you check this already?

[Author]

Posts