Britgirl

[Britgirl]

Check your inbox Brian.

[Britgirl]

It could be a simple case of installing the 32-bit package instead of the one for 64-bit systems. Which package from our website did you install?

[Britgirl]

Hi,

double NAT requires configuring port-forwarding on both routers.  The NoMachine Network feature, to be released with version 9, will remove the need for IP addresses, port-forwarding and interventions on the router. In the meantime, please take a look at the instructions on how to set up port-forwarding here: https://kb.nomachine.com/AR04S01122#2.

Similar topics:

Double NAT – Remote through Internet

Using Tailscale for connectivity

NoMachine with Tailscale

[Britgirl]

Hi, can you tell us the Debian and Mint versions? Also, what is the desktop environment, Cinnamon for example? Are both sides Italian keyboard or another language? What do you get when you press ALT GR+@ in the session window? Is ALT GR working correctly with other keys?

[Britgirl]

On Windows the EC package can install without requiring admin rights. A portable version is in the works.

[Britgirl]

We’re not aware of any slowness on client side. What you can do is this:

– Launch Activity Monitor
– While the client is slow to update, do you see a NoMachine process with high %CPU values? What is the spike value?
– Select the NoMachine process with higher %CPU, and in the top Activity Monitor menu click the down arrow and select “Sample Process” in the popup
– Click “Save…” in the opening window to store the file. Zip up and send it to us by attaching here or directly to forum[at]nomachine[dot]com.

[Britgirl]

Hi,

nothing has changed in how connections (nxs files) and local machines (broadcast on the same LAN) are shown. Firstly, check whether NoMachine has access to the Documents folder. You can do that by going to “Files and Folders” on your macOS client (in Security Preferences). See the attached.

Attachments:

1. 

   image.jpg
   

[Britgirl]

Try with

sudo systemctl set-default multi-user.target

[Britgirl]

It looks like you have “start the server at system startup” disabled. Did you install NoMachine from the AUR repository? If so, take a look at my answer to this topic dealing with the same problem: https://forum.nomachine.com/topic/nxd-does-not-start-from-systemd-but-does-from-nxserver-restart-2#post-46344.

[Britgirl]

Yes we did, sorry for not coming back to you to confirm. Developers have prepared a debug package for you, it contains a potential fix. Can we send you a link to download with further instructions?

[Britgirl]

Make sure the correct key PhysicalDesktopSharing is configured to allow access to the physical display (disabled in Terminal Server products). By default it’s only available for admins and trusted users. Also check --useradd YOUR_USERNAME --administrator is set properly.

You might find these resources useful: https://kb.nomachine.com/AR01S01106
https://kb.nomachine.com/DT11R00174?s=physical%20desktop#12.4

Please ask the customer (or you on their behalf) to contact the team through the regular support channels.

[Britgirl]

Hi, you’re using an earlier version which is no longer supported. You can still get assistance through the provision of your subscription, so what I suggest you do is open a support ticket and ask the team for assistance. The forum is always dedicated to the most current version which is NoMachine 8. If you can’t update, we can provide some tips which you might consider.

From what you write, it seems you are using scripts to start the xserver automatically. So NoMachine starts, then the xserver. This means that NoMachine thinks there is no physical display and so starts its own virtual one. If you are using scripts, you could simply try sudo /etc/NX/nxserver --restart and you should see the session. In that case, add the restart command on the end.

Another possibility is that it’s related to Wayland, so take a look at the articles in our knowledge base https://kb.nomachine.com/AR02P00969 and https://kb.nomachine.com/AR04R01083. The latter one is about running a Wayland-based desktop in a Linux virtual machine.

[Britgirl]

Jessie, no worries, we were able to download the logs.

[Britgirl]

It looks like flatpak applications don’t work correctly on virtual display sessions. We are not able to reproduce all the problems. In our tests apps are listed, but it could be related to your desktop environment. We tested with Cinnamon. Apps can be started, but indeed it asks for auth many times during installation.

But the same problem occurs when installing even through SSH remote connections. There is even a bug report: https://github.com/flatpak/flatpak/issues/3001. So it’s not NoMachine related.

The workaround is to edit policy file:

/var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.Flatpak.pkla

and add there ResultAny=yes to section with: org.freedesktop.Flatpak.modify-repo

so the file should look like this:

$ sudo cat /var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.Flatpak.pkla

[Install Flatpak apps and runtimes]
Identity=unix-group:sudo
Action=org.freedesktop.Flatpak.app-install;org.freedesktop.Flatpak.runtime-install;org.freedesktop.Flatpak.app-uninstall;org.freedesktop.Flatpak.runtime-uninstall;org.freedesktop.Flatpak.modify-repo;
ResultActive=yes
ResultAny=yes

[Override parental controls for Flatpak apps]
Identity=unix-user:*
Action=org.freedesktop.Flatpak.override-parental-controls
ResultAny=auth_admin
ResultActive=auth_admin
ResultInactive=auth_admin

[Britgirl]

Thanks, we were able to download them (please ignore my previous message :-))

[Author]

Posts