Forum Replies Created
-
Posts
-
Can you tell us how you downloaded the package and installed? i.e what browser did you use and how did you open the package? We’ve recently discovered an unusual behaviour in our packages when downloading via Firefox that we are investigating that causes the above error.
For the time-being, can you uninstall completely, re-download using a different browser, browse to the package using the Windows file explorer and install from there? Reboot again.
No it doesn’t interfere with other DisplayServerExtraOptions enabled. For the extra options you can us
DisplayServerExtraOptions "-option1 -option2 -option 3"Hi, thanks for your feedback. This has been discussed a couple of times on the forums already.When an object is dragged in the NoMachine session, the local cursor is locked to the remote cursor’s position, so that the dragged object will not lag behind the cursor. We understand that it can be preferable to not lock the cursor so we implemented an extra option which allows the display server to disable the automatic locking of the cursor.
On the server, in the node.cfg set:DisplayServerExtraOptions “-nocursorlock”
Our developers are working hard to bring you the mobile update (ios and Android) as part of v8’s early maintenance releases moving forward. This is our priority now.
We are working hard to get this fixed and as soon as possible. Please use the TR link that I posted in an earlier post to track the issue.
NoMachine packages installs out-of-the-box on Chromebook, just like on any other computer. You can get started by checking out tutorial here:
https://www.nomachine.com/getting-started-with-nomachine
Of course, you must first decide what to install on it. What OS is running on it?
For Android it’s downloadable from the Play Store. There you will find the client-side package which you can install on your Chromebook and use it to connect any other NoMachine server. Note, however, that the Android version available in the Play Store currently has some issues on Chromebook (you can search our forums for more details about that), so we can provide you with a new package via a private link like we have done with other Chromebook users. When we release version 8, you will then be able to go back to the Play Store to get updates etc.
If it’s running Linux you can download packages from the NoMachine website.
And which package do you install? On our website you can choose between NoMachine Free Edition and Enterprise Client. The Free Edition contains both the player and server components i.e you can install this package on the remote computer you want to access and you can also install it on the computer you want to connect from since it includes the connection interface, what we call NoMachine Player. In the Play Store, as I already mentioned, you will find the Player app for Android.
Are you connecting on LAN? Where is the NoMachine workstation and what is installed there?
Are you connecting from outside the network i.e over the Internet?
Which IP address are you using? It must be the public-facing IP address.
Please take a look at this article https://www.nomachine.com/getting-started-with-nomachine, section: “Using NoMachine for remote access to a computer over the internet”, it shows where to find the external IP.
Have you enabled port-mapping on your router?
It might also be useful check this article:
How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR04S01122We’ve not been able to reproduce this problem using the latest version of NoMachine installed on Linux Mint (default).
Ideally we would need some logs and node.cfg and server.cfg from server side machine to understand what’s happening. Please follow the instructions here and then submit to forum[at]nomachine[dot]com making sure to use the title of the topic as the subject of your email.
https://kb.nomachine.com/DT07S00244
Thanks.
I found the references to collecting logs and created them, then browsed through the results
Send them in anyway, we’ll take a look. Send them to the forum[at]nomachine[dot]com email like before.
Something I forgot to mention in my last follow up as a last attempt to see if it’s related to NoMachine software was to try disabling UDP from the connection sections. Go to Machines in your Player, right click the connection, click Edit and then Configuration -> Multimedia, make sure the box is NOT ticked. Do this before you gather any statistics and logs I requested earlier today.
Presently NoMachine remaps the keyboard modifiers to emulate the remote desktop keyboard, but we understand that users may need their own arbitrary keyboard mapping. We are planning to implement a way to redefine modifier keys (for example, Control, Option, Command on macOS; Ctrl, Alt, Super on Linux and Ctrl, Alt, Win on Windows) for users via the UI.
At the moment, we don’t have an ETA for this feature.
We have no problems with audio using Kubuntu default settings and installing NM version 8.2.3 out-of-the-box. Pipewire became default audio server in Kubuntu 22.10 and NoMachine has support for Pipewire (physical deesktop session) starting with the latest software update (8.2.3). Have you updated to this?
BlueNGray,
our own tests don’t show the issues you are encountering and we are not aware of specific issues related only to AMD.
Let’s look at the statistics which you can get from withing the session itself and the Windows player and Ubuntu server logs with debug enabled.
https://kb.nomachine.com/DT07S00243 – this document includes the instructions for server and player side logs.
You can also enable server side logs (Your Ubuntu machine) from the UI by going in to Server settings -> Status -> Server logs – 7
To retrieve statistics for your NoMachine session, run the menu panel within the session by Ctrl+Alt+0 or click on the page peel. Click on Connection, then click on ‘Take the statistics’ and save them on your local device.
The player logs you pasted are very strange and don’t give an indication of what could be happening. Are you using NoMachine Workstation with its default settings because some of the output is unexpected? Also, you have a Workstation subscription, version 7.10, which is entitled to receive technical assistance via our support channel, so you should really consider opening a ticket because debug needs to be enabled and logs extracted, generally a service that is reserved for those with subscriptions.
Please tell us the output of
grep ^Exec /usr/share/xsessions/*
sudo grep DefaultDesktopCommand /usr/NX/etc/node.cfgUnforunately, whatever image you pasted didn’t upload so we can’t see what settings you can’t toggle. Please use the attachment utility to include any screenshots in your follow-up. (i.e no pasting of images). Thanks.
We’re glad you appreciate the improvements we made to the desktop shared/not shared functionality. Also remember that if the computer is your own and you need to access it remotely, you can still connect even when the desktop is not shared provided that your user is also the owner of the remote desktop. Even if you explicitly disabled it in the server UI.