Forum Replies Created
-
Posts
-
It’s possible that you have a nxs file in some other location which you forgot about.
From the Player, right click on the connection and select ‘Edit’. Click on “Reset saved preferences and password”.
This issue has only started occurring the last week, previously there were no issues.
What has changed on your computer, anything? Did you update something? What version of Avid is it?
and it only happens when using NoMachine Enterprise.What version of NoMachine are you running? It’s strange that NoMachine was working fine producing audio, and then all of a sudden, the audio quality decreases.
What OS are you connecting from?
“Reconnect” suggests that you can connect the first time and use the session, you then disconnect and then try to reconnect but can’t, which seems strange.
Anyway, take a look at the third option in this https://kb.nomachine.com/AR03P00973. Use the proper command to stop the X server according to your display manager and then restart the server.
What is the version of NoMachine on the Windows machine? What is the version of NoMachine on the server machine? What product, the Free Edition or something else?
What is the desktop environment on Ubuntu that you would like to connect to?
It would help us to know if what versions of the distributions, the desktop environments you are connecting to, and confirmation of the NoMachine version.
Thanks for those.
Are you able to also send us the nxtrace.log file on the client-side machine? The file is usually in %ALLUSERSPROFILE%\NoMachine\var\log.
1) Open the NoMachine UI on your computer -> Player settings -> Input and check option ‘Always show remote cursor pointer’.
Create a new session and see if both cursors jump.
2) Edit node.cfg on the server host and set:
DisplayServerExtraOptions "-nocursorlock"Create a new session and see if both cursors jump.
What do you observe?
Did you install package from our website or from the aur repository? We tried the packages from the aur repo on the fly and they indeed behave in the same way as what you are experiencing.
Related topic: https://forum.nomachine.com/topic/manual-command-entry-needed
For your issue, we’d like to see the stack from the server and also NoMachine logs as well.
On the server side, please see: https://kb.nomachine.com/DT07S00244#1.1
And then the journalctl from the server side as well.
Hi, NoMachine Free Edition is for access to the physical desktop of the remote machine. If, in the past, you used NX Free Edition, which offered what we now call connections “NoMachine virtual desktops”, you probably need NoMachine Workstation. The virtual Linux desktop functionality is a feature of the NoMachine Terminal Server Family.
You can read more about these products on our website at the following links:
NoMachine Free Edition – https://www.nomachine.com/everybody
NoMachine Workstation – https://www.nomachine.com/product&p=NoMachine%20Workstation
Differences between NoMachine Free Edition for Linux and NoMachine Workstation for Linux
https://kb.nomachine.com/AR10K00702What is the difference between physical desktop connection and virtual desktop connection?
https://kb.nomachine.com/AR10K00700Now that the app for mobile is aligned with its fellow desktop and server products, updates to the app will be much more regular. Like we wrote in the software update announcement at the time, “With this important milestone reached, the app can be kept actively aligned with NoMachine server products as development continues to move forward.”
Thanks for this additional info. We suggest you wait for the next mobile update and we can check that it fixes the TR 🙂
The Trouble Report is confirmed and still open. If nxserver is not running, the system info dialog doesn’t show.
You can safely shut down and/or reboot your machine if this message shows.Have you tried reducing the resolution, via Mint’s own system settings?
In System Settings, Accessibility, Desktop Zoom, click Enable zoom. Then you can increase or decrease screen with (Ctrl and +) or (Ctrl and -). If you want to be able to do this within the session, enable grab mouse and keyboard in the Player settings.