Britgirl

[Britgirl]

Hi, first you need to set up NoMachine software for your headless RPi server. NoMachine installs out-of-the-box, however, we have an article that includes some further tips and observations about headless Linux which you can read about in the following article: https://kb.nomachine.com/AR03P00973.

After you’ve installed the NoMachine on your RPi and the server is up and running, you can then add it to NoMachine Network. To do that go to Settings -> Network -> Machine -> Add. This generates a Machine Id and an Access Id. You don’t need a NoMachine account to do that. You basically install, proceed to Settings as mentioned and Add.

Now go to the device you want to connect from. Install NoMachine and create a NoMachine account. When creating an account, you get a 7-day Network Evaluation license to try (after that to continue connecting with the Machine Id you need to get a Network Subscription). Login on the Player where it says ‘Login to Network’ and create your first connection. You can do that by simply inserting the Machine Id in the Search field and then clicking Connect to new host….. or you can choose to click the Add button and enter the Machine Id in the Host field. Insert the Access Id when prompted. Insert the system credential of your account on the RPi.

You will find a step-by-step guide on how to connect with NoMachine with and without the Network service here:

https://www.nomachine.com/support/documents/getting-started-with-nomachine
https://www.nomachine.com/support/documents/getting-started-with-nomachine-network

[Britgirl]

Hi,  can you do a reboot of the Windows machine? After which, enable debug (Settings > Server > Security>scroll to bottom and select debug level, restart the nxserver, reproduce the error, and take new logs? Full instructions for extracting logs using the UI are available here: https://kb.nomachine.com/DT08U00298#1.  You can attach everything here or send direct to forum[at]nomachine[dot]com. Thanks!

[Britgirl]

Hi, we are checking our update servers, so thanks for reporting. To get to the NoMachine 8.18 update, when you see the notification about NoMachine 9, enable/tick the “Don’t ask again for this version” box and then click “Continue update” button. You should then see the notification about NoMachine 8.18 and a sentence that says “You chose to skip the update to NoMachine 9”.

[Britgirl]

No problem 🙂

[I] assumed at least the windows version would just auto upgrade to the latest version, I’m guessing the built-in updater only upgrades minor versions?

The built-in updater checks for all updates, major or minor. In the case of a major release, so when you have v8 installed and a v9 becomes available, it will first check that you are aligned with all the v8 updates. Then, if you are on the latest v8 update, it will notify you of the v9 availability.

Did you perhaps disable “Automatically check for updates” in Settings > Updates?

[Britgirl]

Hi, we have a Trouble Report for “Cannot print from Linux to Windows on a shared printer” – https://kb.nomachine.com/TR09V11210. Work has already been done to fix print problems on Windows/Linux client and server components. The fix has been scheduled for the next maintenance.

[Britgirl]

Hi, for online subscriptions, outbound access to port 443 (HTTPS) has to be allowed on the host where the Workstation is running (more about this is available here https://kb.nomachine.com/AR11U01209). Rest assured that work is already being done to extend proxy support for outbound web connections, currently desktop client connections can be configured to connect through a proxy. Until then, we can provide license files that do not need to be checked online, what we call “offline” or “on-prem” licenses. You will need these also for machines that are not allowed to connect to the internet at all, Our support or sales teams will be happy to provide what you need in place of the license files you need 🙂

[Britgirl]

Hi, we got the logs but strangely there were no server logs at all. In the nxd log it’s clear that a connection arrives to the server, and then finishes without any error. Maybe the logs from the client side would be useful at this point. Let’s try this way.

On the server side, go to Settings>Server>Security> scroll down to logs, and set the level to Debug. Restarting the server is requested to make change effective.

On the client side, go to Player Settings -> Security and check option ‘Don’t delete log files on exit’.

Connect to reproduce the error and then 1) click ‘Take the logs’ from the message dialog that you see, and then 2) go back to the server host and click ‘Take logs’ from the Settings>Server>Security. Restore log level 6- Standard to avoid verbose logs. Restarting the server is requested to make change effective.

Send everything by email (one attachment for the player logs, one for the server logs). Thanks!

[Britgirl]

We are able to reproduce it as well and are working on a fix. A workaround is to add this to the node.cfg on the Windows server side:

DisplayServerExtraOptions "-nodxgigrab"

The path to the node.cfg file depending on what Win architecture you have is C:/Program Files/NoMachine or C:/Program Files (x86)/NoMachine.

[Britgirl]

Hi, please update to the latest 9.1 release, a patch was included which fixes this issue.

https://kb.nomachine.com/TR10U11023

[Britgirl]

Thanks for that. We’ve queued it up for investigation. It’s likely that it is also reproducible on version 9. If we need any more info from you, we’ll come back to you.

[Britgirl]

Update: we checked the open source drivers and can reproduce it. So stick to the proprietary ones as recommended in the article https://kb.nomachine.com/AR02U01190 🙂

[Britgirl]

Hi, on the server side this is possible. There are two keys in the node.cfg file that let you set the specific path.

# Specify path of base directory where the node has to mount disks
# accessible only by the user who connected them. Base directory is
# "$(DESKTOP)" by default. $(HOME) and $(USER) are also accepted values
# and can be concatenated to specify path to a directory, for example
# "$(HOME)/Shares". Target directory must exist on the system.
#
#DiskSharingPrivateBasePath "$(DESKTOP)"
 
#
# Specify path to base directory where the node has to mount user's
# disks which are accessible to users running a session on that server.
# Base directory is "$(PUBLIC)" by default. $(PUBLIC) is /Volumes on Mac
# OS X, /media on Linux, C:\Users\Public on Windows Vista/7/8 and
# %ALLUSERSPROFILE% on XP. $(USER) is an accepted value and can be
# concatenated to specify path to a directory, for example "/tmp/$(USER)".
# Target directory must exist on the system.
#
#DiskSharingPublicBasePath "$(PUBLIC)" 

On the client side it’s not possible to change the path, but we are going to make it possible in one of the next updates.

[Britgirl]

Hi, thanks for coming back. It would have been useful to know if you can reproduce the problem with the test package – because to be honest, we did not include it in the 9.1 release (it was scheduled for the next maintenance) 🙂

Maybe something changed on your system since you first posted the problem, this might be the reason that you can no longer reproduce it?

[Britgirl]

Hi, a possible workaround (it depends on the drivers in use) is to do the following:

in the node.cfg on the server machine (/usr/NX/etc/node.cfg), change the following line

#DisplayServerExtraOptions

to

DisplayServerExtraOptions "-altcolorformat"

then restart the nxserver. (Settings -> Server -> Status, restart). Let us now the outcome.

[Britgirl]

Hi, can you provide us the following information?

– NoMachine version and OS version on the client side
– NoMachine version and OS version on the server side

[Author]

Posts