Forum Replies Created
-
Posts
-
Hi, the logs are actually clean. We think it stems from your system, and probably the drivers on your Ubuntu machine. You have some options to try:
1) check what video drivers your system is using and if they can be updated
2) try the Workstation evaluation and see if that fixes the issue
3) if you want to stick with the free version, then you can try switching off the x server and use the NoMachine’s own virtual display – more instructions are here: https://kb.nomachine.com/AR03P00973. If you choose this option, you won’t have access to the physical display as you do now.Sorry, I forgot to add some links to KB resources which are also useful:
How does the NoMachine Network Subscription model work?
https://kb.nomachine.com/AR09V01249Is there a limit to how many computers I can publish on NoMachine Network?
https://kb.nomachine.com/AR09Q01042Can I connect from multiple devices simultaneously with my User Id using NoMachine Network?
https://kb.nomachine.com/AR06W01296Hi and welcome 🙂
let me take your questions one by one.
I have a workstation at the office, a laptop for field work, and a workstation at home. Do I need a different subscription for all 3 computers?
Absolutely not! We would be grateful if you could point us to the place, on the Website, where we can improve the communication to make this point clear!
If we have two different subscriptions, how would we manage a large number of permanent connections. (Lets say over 1 thousand connections, where two of us might need simultaneous access to 3 or 4 at a time.) Would we be able to share connections?
I think this question is related to your last comment below:
We would love to see a licensing model for teams, where multiple technicians can share a pool of concurrent connections, and where security constraints can be placed on most of the technicians
We thought about that, and a lot, but the problem is that making such a “team” license is a bit complicated, it would also make things complicated for the vast majority of our users, confusing them, those at least interested in “multiple connections”; whereas our “normal licensing”, the one per-connection is crystal clear (the most clear on the market, according to what our users say). We’ll contact you in private to advise on what best fits your set up.
Hi, you are using version 8.4 on the server. You should update to the latest 8 (8.20) if it’s not possible for you to update to version 9. A number of Wayland-related issues have been fixed since 8.4. If you can update to the latest version 9, even better. Then if you reproduce the same issue, let us know.
Hi, we’re going to send you a debug package with further instructions. It contains a potential fix for “not able to select the monitor” issue after having set
--eglcapture no, but it also has debug logs enabled so we can investigate the slowness that you originally reported with--eglcapture yes. Check your inbox for emails from us 🙂Are you connecting from the macOS machine? What product do you have installed, the free edition or the Enterprise Client? File transfer is initiated on the server side, the machine that you connect to.
Take a look at the following resources:
https://www.nomachine.com/support/documents/sharing-files-between-computers-with-nomachine
https://kb.nomachine.com/AR06Q01033Hi, we are aware of an issue with multi-monitors not being detected in some cases and it will be fixed in the next update.
Hi, we are aware of an issue with multi-monitors not being detected in some cases. Are you able to send us the logs of the server side so we can check that it is the same issue? You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298. Attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks for your collaboration.
Thanks for letting us know. We have reproduced a similar issue with Fedora running on Wayland, it’s not possible to attach to the login manager.
Apologies for the late reply. Do you remember updating a new application or maybe updating your drivers in that period? We released 9.3 in December, so please update if you have not done so already. If you are still encountering the same behaviour, we can look at fresh logs.
This was fixed in December’s release, 9.3. Please make sure you update if you have not done so already.
We have opened a Trouble Report. Please use the following link to know when a fix has been released, https://kb.nomachine.com/TR01X11683.
We have opened a Trouble Report. Please use the following link to know when a fix has been released, https://kb.nomachine.com/TR01X11683.
Did you reboot the Windows machine?
On the Windows machine, go to Settings > Server > Updates and take a screenshot, and attach it using the upload attachment tool.