Forum Replies Created
-
Posts
-
I forgot to ask whether connecting to the same server using the traditional player session also shows the same problem.
Do you mean you’ve installed Cloud Server for Evaluation on the Linux server? If so, telling us the distribution and its version on the server will allow us to investigate further. Also, the version of Chrome OS and the Chrome browser (I assume you are using Chrome browser) would be useful.
The next update will be before the end of the year. Provided you’ve signed up to the TR above, you’ll get an email to notify you of the fix.
Yes, it will be available on all platforms. The software is ready. We are testing it and working at setting up the infrastructure, which is not a minor task. It should be available in Beta shortly.
@recohen, what distro and version are you using? Also, confirm that what architecture you are using: 32bit or 64bit? Have you installed the right packages?
When connected to the Mac, execute Ctrl-Alt-A. This will show you all the monitors available. Or you can do it via the Connection Menu, as shown here in Fig. 15, clicking Change Monitor: https://www.nomachine.com/DT07M00087#5.1
Hi, thanks for letting us know.
It will be most likely be in the next release. I don’t have an ETA unfortunately, but you can sign up to receive a notification when it’s fixed: https://www.nomachine.com/TR10N07299.
Currently, NoMachine for Android is for the connecting client only. A ‘server-side’ version is planned, but as yet I cannot say when it will be available.
Can you tell us what OS you installed NoMachine on and confirm that you are indeed using the free version.
We’ve opened a TR since we’ve reproduced the problem. Sign up to be notified when a fix has been released. https://www.nomachine.com/TR10N07299
It would have been easier to create a user account for those you want to share your virtual Linux desktop with. The ‘automigrate’ key only needs to be changed when you want to share your desktop with other users, and those other connections are accessing it using -your- same user name. In other words, the open session won’t migrate to another computer when the same username connects to the running desktop.
Regarding your other question about license files. You certainly don’t need to show your license files to users connecting. The licenses activate the software according to the license type you are installing, and on the basis of that allow you to do a number of things. In your case, the Workstation license will allow 4 virtual Linux desktops and unlimited connections to those desktops (so if you want to give 5 users access to your virtual desktop session, that is possible).
Hi, someone will be contacting you from the appropriate office (depending on your location). As a rule a reply is dispatched in 1-2 working days. If you provided a phone number, it might be that someone tried phoning, but didn’t get a reply or left a message. What I suggest is you write to sales[at]nomachine[dot]com stating your CR ID and they’ll follow up.
@bigtractor after investigating thoroughly, we can now say what exactly is triggering ‘privileged mode’. It’s caused by the PTRACE parameter which is not provided by the default docker AppArmor profile.
It was enabled for Docker on Ubuntu 14.04 by default, so our article was fine for this platform. But not for 16.04. The same workaround also applies to OS X.
We’ve added a note for 16.04, so the article has been updated since you last wrote here. https://www.nomachine.com/DT08M00100
We have seen the same problem with users who have upgraded their Windows client to 5.1.54 where they cannot connect to the server. Deleting /users/USERNAME/.nx on the windows client and then recreating an empty nx director (mkdir /users/USERNAME/.nx) seems to resolve this problem.
We haven’t been able to reproduce this problem. The best way to proceed would to see the server side logs to check what’s happening if you encounter it again.