Britgirl

[Britgirl]

Some clarifications to your comments…

… won’t allow NoMachine to become visible to the distant computer.

NoMachine hosts are visible to other NoMachine clients when they are all on the same LAN (i.e in Machines computers on the same LAN show with a pipe icon).

Distant computer user entered the host’s local LAN IP ’cause presumably that’s the way NoMachine works

When the user is on the same LAN as the computer you want to connect to, the local LAN IP is used. When connecting over the Internet, you use the public IP address of computer. For most users, this is the IP address of the router that sits in front of the computer you want to access.

Did you already see https://docs.netgate.com/pfsense/en/latest/nat/port-forwards.html#figure-port-forward-example (for the Pfsense port forwarding configuration)?

[Britgirl]

Hi, we checked the logs and we see that encoding fails at a very early stage, at a point where it seems unlikely that it can be a NoMachine issue. Can you confirm in any way that the other apps you mention are using HW encoding and not a SW fallback? How have you checked that they are using HW encoding?

[Britgirl]

Hi, can you send us the logs from the OS you are connecting to (i.e the NoMachine Windows server).  Please use the following instructions:

https://kb.nomachine.com/DT07S00243
To enable debug on Windows, open a CMD console as administrator:

> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --enable all

Start a session as usual and then gather the logs:

> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --collect

The log archive is named as: NoMachine-log-.zip (e.g. NoMachine-log-2018.09.27-11.44.01.zip) and stored in: %PROGRAMDATA%/NoMachine/var/log/archives on Windows 10/11. Send them to forum[at]nomachine[dot]com. Thanks!

[Britgirl]

😀 ok, thanks for updating us. Happy nomachining!

[Britgirl]

Strange. This sounds more like a network problem. When you see that error, can you ping or ssh in to the Pi?

[Britgirl]

Did you install FF via snap? Make a test of audio in the virtual desktop, with any app not installed by snap, e.g vlc player. Does sound work?

Install FF this way: https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt-ubuntu-22-04

Then connect to the virtual desktop.

[Britgirl]

You can try with “custom scripts”, they’re also supported in the free version. Take a look at the following article:

Server Automation Interface: some examples to use custom scripts triggered on server/node events
https://kb.nomachine.com/AR02L00787

and any of the guides of the Enterprise products. Here’s the link to the Enterprise Desktop guide (like the free version but with more features) https://kb.nomachine.com/DT10R00171#11.3.

You could use, for example, UserScriptAfterSessionStart (in node.cfg) executed as user, not as user nx. Prepare your script and run it at disconnection to restore the previous monitor configuration.

#
# Specify absolute path of the custom script to be executed after the
# session start-up. The script can accept session ID, username, node
# host and node port as its input.
#
#UserScriptAfterSessionStart “”

or

#
# Specify absolute path of the custom script to be executed after
# the session is disconnected. The script can accept session ID, user-
# name, node host and node port as its input.
#
#UserScriptAfterSessionDisconnect “”

[Britgirl]

3093 3093 2024-05-23 15:28:39 406.174 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.

There are some permission denials occurring when NoMachine attempts to create the .nx directory in the user’s home. Check that user DV9G49 has rights to create it.

An option is to set the path by using the key below, in node.cfg
#UsersDirectoryPath ""

# Specify a different path to the default home to create the .nx
# directory for storing session files and user's logs. This doesn't
# apply to the nx user, the NoMachine reserved user necessary for
# internal operation. If it doesn't exist yet, a sub-directory is
# created for the user who's starting a session, named as username.
# The .nx directory is created under that sub-directory. E.g. if this
# key is set to /tmp/nxdir/, when user nxtest runs the first session,
# the /tmp/nxdir/nxtest/.nx will be created. The directory specifed
# in the UsersDirectoryPath key should be writeable for all users or
# alternatively, the administrator should create a directory with
# proper ownership and permissions, named as username, for each of
# the users who need to start sessions there.
#
#UsersDirectoryPath ""

[Britgirl]

Thanks for the screenshots. I was not clear in what I wrote yesterday, sorry for that. When I wrote “You can check if file-transfer is enabled by going to Server settings from the !M icon on the remote desktop > Security > Scroll down to “File transfers” and check that the boxes are ticked.” – you need to do that on the Red Hat host you are connecting to, not on the Mac. The settings panel you showed us are the server settings for your own Mac (so if you were to connect to your Mac from another client, those settings control the upload and download of files from and to your Mac as a server).

If you are not the administrator and can’t access the NoMachine server settings, you need to make a request to who is responsible for that machine. It is likely that file-transfer has been disabled in the configuration files of the server by whoever is (i.e the FT key has been set like this: EnableFileTransfer none in the node.cfg.)

[Britgirl]

Please submit that image to forum[at]nomachine[dot]com.

You can check if file-transfer is enabled by going to Server settings from the !M icon on the remote desktop > Security > Scroll down to “File transfers” and check that the boxes are ticked.

File transfers
Allow clients to upload files – enabled by default, it ensures that others connecting to this computer can send files to the server.

Allow clients to download files – enabled by default, it allows users connected to this computer to download files from the server.

You can also see an example in Section 2.5 in the following guide https://kb.nomachine.com/DT07S00237#2.5.

[Britgirl]

Are you connecting to the remote NoMachine server using the browser or is this a traditional connection from inside the Player? I ask because you mention “virtual clipboard” and this is only available in web-based sessions.

I do not see the “Transfer a File” option when I click on the !M icon.

Are you clicking on the !M icon on the NoMachine server side? Start your session to the remote computer, click on the !M icon and take a screenshot if there is no file transfer option.

Are you the administrator of the NoMachine server? Could it be possible that this option has been disabled on the server?

[Britgirl]

This is a bug we are aware of and it’s reported here: https://www.nomachine.com/TR04V11131, the fix is planned for the next update. In the meantime, please follow the instructions I posted here: https://forum.nomachine.com/topic/no-gpu-after-uninstalling-nomachine#post-47927, and I’m pasting them here as well:

As user root

Make a copy of the following files

/usr/NX/scripts/vgl/vglserver_config
/usr/NX/scripts/vgl/vglgenkey

making sure to place them in the same folder

– Uninstall

– Execute /vglserver_config -unconfig

– Reboot

[Britgirl]

Hi, for the logs from the NoMachine server you are connecting to you should run:

$ sudo /etc/NX/nxserver --debug --collect

If you are the root user, run the command above without ‘sudo’.

The log archive is named as: NoMachine-log-.zip (e.g. NoMachine-log-2018.09.27-11.44.01.zip) and stored in: /usr/NX/var/log/archives.

sudo tar -cvp --exclude 'cache*' --exclude 'images' --exclude 'temp' -f - path_to_user_home/.nx | gzip -c nxdir.tar.gz

For the moment, we do not need logs from the device you are connecting from. You would need to replace path_to_user_home, usually its “/home/username”, but it depends on the username and system path where user’s home directories are stored.

[Britgirl]

Hi, can you send us the logs?
It’s better to enable debug first, before reproducing the problem. Full instructions on how to gather logs can be found here:

https://kb.nomachine.com/DT07S00243

Also, if it’s Gnome which is failing, check for errors in “.xsession-errors” and system logs (journalctl). Attach these along with NoMachine logs and send to forum[at]nomachine[dot]com.

[Britgirl]

Hi, I’m not sure whether you’re asking about the labels or why you are seeing two connection icons. So I’ll try to be comprehensive in my answer 🙂

The pipe icon (located through local discovery) represents computers which are found on the same LAN. You can turn this off if you don’t want your server machines to advertize themselves on the LAN. See more about this here:

https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network

You can also turn off LAN computers from being shown in your local Player if you want as well, this is also explained in the above tutorial. It has a label (in the edit panel) which explains what it is: “Located through local discovery service”.

The other icon (!M) represents an nxs file, i.e a connection you created manually. It shows when you create a connection to that computer using the “Add” button or if you input the IP address in the ‘Search’ field. This connection file can also be from previous installations as it is stored in the .nx/cache folder.

Regular nxs connections can be used to connect to any NoMachine server whether it’s on a LAN or over the Internet. The labels you see are not dynamic. They don’t change on the basis of whether you have enabled port-forwarding or not. They are used to distinguish the difference between the types of connection: one for local discovery hosts, the other for direct connections (which for the majority of users that we have had feedback from “over the internet” clarifies the difference between the two).

Can you reattach your image? (don’t paste it in)

[Author]

Posts