Forum Replies Created
-
Posts
-
We were able to reproduce the issue, so thanks for reporting.
Edit: the Trouble Report for this bug is here: https://knowledgebase.nomachine.com/TR03S10143. You can sign up to receive notification of the fix using the link above.
Hi,
did you enable port-forwarding on the router to which Computer 2 is attached? See here:
How to connect over the internet to NoMachine behind a NAT router
https://www.nomachine.com/AR10R01099You could try the tips suggested here:
https://forums.nomachine.com/topic/errors-trying-to-install-ubuntu-1804-using-wget#post-29994
and here:
https://forums.nomachine.com/topic/my-successful-story-in-setting-up-nvidia-driver-on-aws#post-27729
Hi Gatos,
very strange…..can you send us the player side logs (follow the instructions here: https://www.nomachine.com/DT11R00181#2) and then send them to forum[at]nomachine[dot]com.
After you’ve done that, could you then try disabling UDP? Do you still encounter the same the same behaviour?
Can you tell us what distribution and version you have installed on the NoMachine server? What’s the desktop environmen? What version of NoMachine? What product have you installed – the free version, Workstation? What’s the client OS and version?
Setting the automatic disconnection of the NoMachine user after a certain time of inactivity would mitigate the problem of users forgetting to log off and leaving the session open.
To enable this feature, edit /usr/NX/etc/node.cfg and set an appropriate value (in seconds) for this key:
DisplayAgentExtraOptions “-timeout s”
For example, to disconnect the user after 10 minutes of inactivity, set:
DisplayAgentExtraOptions “-timeout 600”
Hi, we have a Trouble Report currently open for Wayland:
Grabbing the keyboard doesn’t work when Wayland is enabled
https://www.nomachine.com/TR10P08952Can you check that Wayland is disabled/enabled?
echo $XDG_SESSION_TYPEuncomment or set:
WaylandEnable=falsein the:/etc/gdm3/custom.confand reboot. Does this help?
Hi, a new article has been inserted. Thank you for pointing out that the current article needed updating.
For version 6.10 onwards, you should use this: https://www.nomachine.com/AR03S01112. Let us know if you’re still having issues.
No, it isn’t supported. Windows RDP can run with virtual display drivers, so it can create three virtual displays mirroring the client displays and switch the user’s session onto those virtual displays. NoMachine copies the physical displays existing on the server side.
Since the 7.1.13 upgrade I’m plagued with out of focus servers displays where the mouse points somewhere else so I can’t click on anything.
We aren’t aware of out-of-focus issues or problems with clicking when connecting to Linux Mint. Although screenshots would help to understand what the actual problem is that you are encountering. What’s the Window Manager you are using? I take it this is the free version installed on the Linux side (you didn’t say).
This doesn’t happen every time but sometimes it requires closing the server window and retrying a dozen times before getting lucky. My client is Win7 and servers are Linux Mint 20.1 with Nvidia 1080 Ti GPUs and the 460.39 driver.
Strange, if something isn’t working with NoMachine, it would be showing this strange behaviour all of the time, not once every dozen or so times. I doubt that it is being caused by the GPU. So, clears steps to reproduce the problem (as well the as the screenshots already mentioned) would be useful to help us understand better.
Also, it’s inefficient that one must back out 3 steps to end editing display settings. Please add a Done button.
You can actually remove one step by clicking the small settings icons (which can be considered shortcuts) at the bottom of the menu (it’s the one on the far right) and this will take you directly to “Change settings”. Therefore it takes 2 steps, and not three. Designing menus and how it impacts usability is not as simple as it might seem and adding a Done button (something which we did of course already consider) proved not to be the best solution to coming out of the menu.
Also, I dislike the way the client window with all the servers displayed stays open and it spawns a new window to access a server. I can see how someone in tech support might like it that way but I often only need to access a single server. Please make it an option to use classic style or never closing style.
The multi-window player is one of the elements that make up the new design of the UI. This isn’t going to change. What you can do is place a connection shortcut on your desktop (or wherever you like) and by double-clicking you will open the session without the main window getting in the way. To create the shortcut, go to the folder where NoMachine connection files are store (by default on Windows it’s in Documents\NoMachine), right click the session file, click ‘New’ and select ‘Shortcut’.
Thanks very much for taking the time to provide this feedback. In version 7 we redesigned the interface in order to make the opening of, and access to, multiple sessions faster because this is the most common use we have found amongst our users and what our users asked us for more frequently. The connection links were removed from the systray to put these recent connections in the Machines panel which can be reached in two clicks (one click on the monitor, one click on ‘Main window’). This, by the way, also allows us to declutter the monitor: a space that we need as we move forward with our development roadmap. So, putting the links back in the Monitor is not possible.
From what you’ve written (and with a particular use-case as an example, so thank you), I understand that the window is not opening in your current Windows workspace. I think this should be fairly straightforward to fix. Would you like it to open in the workspace you’re in, or that the current workspace switches to the one where the NoMachine window is located?
Update to 7.1.3 please and resubmit a new topic with the logs as previously requested if you are still encountering the same behaviour.
It’s impossible to update NoMachine software without administrator privileges because it requires access to certain privileged sections of the User profile.
What you can do, instead, is a create local repository (apt for deb, yum for rpm) and put there new version of player each time we release it. And user’s machines will update from it, automatically. You should contact the sales team to check what the legal implications with regards to redistribution of the package.
We are working on a portable version which might satisfy your use case, certain services won’t be possible and these are outlined in the Feature Request:
Creating NoMachine free portable version
https://www.nomachine.com/FR11P03746