Forum Replies Created
-
Posts
-
Not sure what the issue is with your installation or system configuration (cifs?), but we tested on-the-fly with Pardus and it works fine. What NoMachine errors are you seeing when trying to install or connect?
The NoMachine GUI is an integral part of every NoMachine server package, because it is not just a client but also an interface for server administration. Since a client is never automatically started unless the user does it, it has never been a problem. However if you need to configure an environment where users cannot start NoMachine connections from a machine working as a server, you could try to change the permissions of the ‘nxplayer’ binary to remove executable flags.
Try disabling hardware acceleration decoding. This is similar to another topic. Try the workaround there.
Select that icon and click ‘Edit’ and check what IP is being used. Check that this is the correct IP address just to make sure. Show me what you see.
If it’s correct, it could be a non-native firewall installed on the server perhaps? Disable it temporarily to test connecting without the firewall.
In a “normal” situation you would disable “Enable hardware accelerated decoding” during the connection, via the connection menu. So the user can already edit the settings like this for the player. But in your case this would not have had any effect because the crash seems to happen before the session is actually established.
You might want to take a look at the connection menu guide for explanations on what the various check boxes do. In your case, the guide for the menu panel on Linux is here https://www.nomachine.com/DT10R00167. Go to section 5.8.
Depending on your OS, they are all linked in the Configuration section here: https://www.nomachine.com/all-documents. You will find a lot of useful information there.
There is an article in our KB, linked from the Documents page, about the most common cfg settings.
The most frequently asked options for pre-configuring the client and the session behavior
https://knowledgebase.nomachine.com/DT11R00186Can you give us more details of the problem you are/were experiencing? I’m not sure how lag can be affected the change of resolution.
– connecting client and server OS and version details
– what are you changing exactly and where/how?From the logs it appears va-api is broken and is probably causing the crash of the player. Usually such problems are inner VA-API libs/drivers problems occurring with some specific system configuration, and are not related to NoMachine code.
Try changing this key in player.cfg:
“Enable hardware accelerated decoding”
to:
“disabled” (not to “false”).
Does this help?
I’ve attached it to this message.
Try sending it attached to an email to forum[at]nomachine[dot]com.
Ok, thanks for letting us know 🙂
We aren’t aware of any installation problems on Big Sur (Intel).
Hi, thanks for your topic, it provides some interesting information and food for thought 🙂
1) Would a user be able to click a link from a basic webpage that in turn opens NoMachine on their MacBook and loads a predefined config/connection based on their selection?
Yes, it is perfectly possible. From your webpage, users would click and download the NXS file which is then loaded to and run from the Player, and the session starts.
2) Is there already a better way of managing multiple/alternating users across different connections? I feel like a lot of companies using NoMachine on a larger scale must have encountered this already?
From what you’ve written in your post, the fact that you have multiple users, which change, and hot desk access (so users hop on to the first computer available), it would seem that Cloud Server comes close to what you need. Cloud Server centralises access to any number of NoMachine servers, in your case Enterprise Desktops. Once you’ve added your desktop nodes to the Cloud Server, anyone connecting to it in order to view the connections and available desktops will be able to see in their Machines panel if anyone is already connected to a specific computer. It already does this.
The use of profiles/groups would help you to display to your users the computers that they can access.
What the Machines panel doesn’t show in the current version is “who” or “since when” that user has been connected (like in your image). But this is an interesting feature to have and we could certainly consider adding it as information to show of a specific node (the administrator would be able to decide whether to allow such information to be visible).
I’m not sure whether you’ve already taken a look at this product. Consider that in version 8, which is coming soon, we have made significant improvements to the Cloud Server UI which will simplify remote configuration & management of multi-server set-ups considerably.
Edited 29/7: I’ve included a couple of screenshots of the upcoming Cloud Server interface. ‘Browse nodes’ is what the user sees when authenticating on the Cloud Server (that you can see the number of users connected is actually already available in version 7). ‘Add node’ and ‘Edit node’ show the much improved node management aspects 🙂
Try this….
On the computer (PC), when you open the NoMachine player to connect to your laptop, does the laptop show up in Machines? See fig 5 in the following tutorial https://www.nomachine.com/getting-started-with-nomachine to understand what I mean. Computer hosts will be identifiable with a “double pipe” icon. Connections are identified with a !M icon.
All NoMachine-enabled computers on the same LAN are visible by default in Machines. If you can see your laptop with the “double pipe” icon, double click on it to start the connection. Can you submit a screenshot of the Machines tab?
Hi, thanks for your appreciation of our software 🙂
The NoMachine client doesn’t start automatically, it can only be launched from the tray icon or from the Applications menu.
However we would like to understand what made you consider the client launched at system startup. Did you maybe think the NoMachine tray icon is only visible while a client is running?
Hi, if you are using Wayland you can try the advice in the following article
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://knowledgebase.nomachine.com/AR04R01083or disable Wayland.
