Forum Replies Created
February 22, 2021 at 10:44 in reply to: ClientSession: Failing reason is ‘The session negotiation failed.’. #32088
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.February 22, 2021 at 10:04 in reply to: Performance issue –> reboot necessary + CredentialsStoring Bug? #32080
No further feedback has been submitted by the user so we can consider this solved.February 22, 2021 at 09:53 in reply to: NoMachine 7.0.209 on Windows10 – cannot connect to due to “Error is 108” #32079
The patch was made available in the release of version 7.1.3.
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
No logs received, so closing this.
No logs have been received and I am closing this topic. If you are able to submit logs as described by Totne, please submit them directly to forum[at]nomachine[dot]com and submit a new topic with the details. The version is now 7.1.3, so you should update to this before reporting back.
I can no longer make them any smaller than the default size of a new window.
You are right and we will fix this. When we redesigned the UI, we didn’t take into consideration the need for such small session windows. You’re the only one that has actually brought this to our attention, but this doesn’t mean it deserves less attention. Thank you for pointing this out to us and we will put it right. I can provide a download link for the earlier version and send it to you in the meantime. Is that ok?
I would advise you to update both NoMachine client and server software to 7.1.3 and tell us if the problem is still there. If it is, submit logs as Fisherman suggested.
I assume you are using the latest version of NoMachine. What version of Linux MX are you using? It’s not clear if it’s the server or client, so please clarify. In any case, we checked with the latest 19.3 in our labs and didn’t have any issues.
Is it headless? Check this article for some useful tips:
How to solve black screen and other possible problems on headless machines
Erans, can you tell us which university’s facilities you are connecting to and have you asked your administrator for further assistance if this is a set-up arranged for your faculty?February 15, 2021 at 12:31 in reply to: AirPlay: “The selected movie won’t play on your display” #31976
As soon as the screen is forwarded (not just with NoMachine, also macOS’s own remote desktop tool) and you can try with others, DRM protection is triggered. NoMachine can’t avoid this.February 12, 2021 at 09:45 in reply to: AirPlay: “The selected movie won’t play on your display” #31931
It’s probably the system which prevents the recording of the content potentially covered by copyright.
Further reading: https://en.wikipedia.org/wiki/Digital_rights_management
The attachments you sent were from the client-side computer, we need them from the server-side (the machine you are connecting to).February 11, 2021 at 10:01 in reply to: NoMachine time lag after remote computer inactivity/lock screen #31922
Can you tell us the version of Xubuntu? What desktop environment is it?
Hi, thanks for your feedback.
Once you’ve closed all connections, and the server isn’t active, why keep a systray icon?
If you don’t want to see the icon in the system tray, you can of course select ‘Quit the player’ as well, not just shut down the server. Then next time you need to start a session or access the NoMachine settings, you can open it from the applications menu or session shortcut on your desktop. The icon will appear again in the systray.
Use of the systray….this is the usual “integration” problem in the target desktop environment. What the target desktop environment offers is the system tray, where those making the software are supposed to place the most frequently accessed functions.
If you don’t use it, people complain that you don’t use it. If you use it, people complain that you use it. It’s a tough world 🙂
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.
But, as mentioned, doing one thing well and doing more can bring inconvenience for those who preferred an application that did less, better still, one thing. It’s a tough world.