Forum Replies Created
-
Posts
-
Can you tell us what IP address is being used? I.e you are definitely using the LAN’s IP.
Is it a virtual machine perhaps?
The logs would also be useful from the server. To gather those up, please follow the instructions here:
https://kb.nomachine.com/DT07S00243
You can attach them here or submit to forum[at]nomachine[dot]com.
Hi, the image you tried to link to is not available, so the URL has been removed. Please attach the image here that you would like to show us. Also confirm the NoMachine version on client and server sides and the OS as well. If Linux, the distro and desktop environment is also useful.
What is the system and desktop environment?
Is this an installed Workstation out-of-the-box or did you change something (or someone else maybe changed something?) It looks as if custom sessions are disabled. More info about this here: https://kb.nomachine.com/AR07P00989
Can you tell us the output of:
sudo grep AvailableSessionTypes /usr/NX/etc/server.cfg?You could also try this command as well:
sudo /usr/NX/scripts/setup/nxnode --availablesessionsetupOn the machine you are connecting to, (the server), can you check that the NoMachine service is running? To do that, go to the Windows system tray and find the !M icon, right click and select ‘Show server status’. Submit a screenshot please.
Also, check the exact product and version you have installed by going to Updates. Please do this on both Windows computers.
In NoMachine version 8 (for new installations), UPnP/NAT-PMP is disabled by default in the Free Edition. To get access to your computer over the Internet, NoMachine’s UPnP/NAT-PMP port mapping must be enabled by hand (‘Server settings -> Ports’ -> Select the service and click on Configure); or alternatively, your router can be configured with the appropriate port-forwarding rule.
More about this here: https://www.nomachine.com/AR10T01175
Does this help?
Hi, check out the article here in our knowledge base:
How to connect to Windows with NoMachine and an empty password
https://www.nomachine.com/AR05L00802We were able to reproduce a similar issue and compared the logs which show the same error. It affects only the 64-bit package. A temporary workaround is to use the 32-bit version. Try it and let us know.
The logs from the arc 380 continue to show the MFX_ERR_UNSUPPORTED error which we print as:
Info: Intel Quick Sync H.264 acceleration is not supported.
Info: Please consider updating your Intel drivers.It would have been useful to know the outcome of installing/building mediasdk using the other ways we mentioned in the articles provided for comparison. As things stand, it is likely that the issue is with the Linux drivers.
We are aware of a similar behaviour and need to verify if your problem is the same. If it is, we suspect a problem caused by a Wacom driver. So that we can confirm it’s the same issue or indeed a different one, please tell us whether you have a Wacom pen/tablet connected to that Windows client. Are you running a service running called “Wacom ISD Service”?
Still no future release schedule.
In response to this question, we don’t make a public a timeline of upcoming releases.
Apologies.
https://kb.nomachine.com/SU07U00247
You can access all SU using the link here: https://kb.nomachine.com/software-updates (or from the footer of the website, Software Updates)
Hi, version 8.8.1 was released in July for all platforms. You can check the software release announcement here:
https://kb.nomachine.com/SU07U00246
To stay up-to-date you can also subscribe to our news mailing-list if you wish. Go to the following URL and insert your email address:
Are you connecting to a Gnome desktop? We are aware of an issue on Alma Linux when connecting to Gnome. It is not present in the latest Red Hat or Fedora versions. It’s possible to run only 1 GNOME desktop per-user. This looks to be a limitation of dbus-GNOME on Alma Linux, not present on RHEL.
A possible solution is to adopt a different desktop environment like XFCE.
You should also check the DefaultDesktopCommand in node.cfg on the server. What is written there? Journalctl output would also be useful.
We were able to run one GNOME virtual desktop by NoMachine by using any of these command in /usr/NX/node.cfg (all on a single line):
DefaultDesktopCommand "env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus /bin/dbus-run-session gnome-session --session=gnome"or for GNOME classic:
DefaultDesktopCommand "env GNOME_SHELL_SESSION_MODE=classic DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus gnome-session"To try XFCE:
sudo dnf install epel-release sudo dnf group install "Xfce"Then set in /usr/NX/etc/node.cfg:
DefaultDesktopCommand “startxfce4