Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterHi Doug, running virtual session/single applications is only possible on Linux platforms, in the Terminal Server family. This is due to licensing restrictions in Mac’s EULA. This was discussed briefly in another topic here: https://forums.nomachine.com/topic/use-a-mac-with-two-or-more-users-at-once#post-18277
March 29, 2019 at 15:03 in reply to: Local screen has corrupted regions after pop-ups and window moves #21888Britgirl
KeymasterI strongly suggest you update the NoMachine installation on the client. Also, confirm what NoMachine version is on the Centos side.
Britgirl
Keymaster@chiamarc, this should help you.
etc/group
etc/gshadowetc/NX
etc/pam.d/nx
etc/pam.d/nxlimitsetc/passwd
etc/polkit-1/localauthority/55-org.nomachine.d
etc/selinux/targeted/contexts/files/file_contexts
etc/selinux/targeted/contexts/files/
file_contexts.localetc/shadow
etc/systemd/system/multi-user.target.wants/nxserver.service
etc/xdg/menus/applications-merged/NoMachine-dir.menu
etc/xdg/menus/gnome-applications-mergedusr/share/polkit-1/actions/org.freedesktop.packagekit.system-network-proxy-configure.policy
usr/share/polkit-1/actions/org.freedesktop.pkexec.nomachine.policyBritgirl
Keymasterit is written “Physical desktop”
This is just a FYI 🙂 If you’ve installed the free version, you won’t be able to create a virtual desktop on the server. More about the differences between physical and virtual desktop is here: https://www.nomachine.com/AR10K00700
Britgirl
KeymasterThe user should have an account (local or domain account) on the target server and they should be able to authenticate on that machine. The authentication method in use is not relevant.
March 12, 2019 at 17:30 in reply to: "Authentication failed" connecting to v6.4.6 on Ubuntu 18.04.2 LTS #21719Britgirl
KeymasterGreat news! Thanks for letting us know 🙂
Britgirl
KeymasterThanks for letting us know!
Britgirl
KeymasterPlease try submitting the attachments again or send them directly to forum_at_nomachine_dot_com. Make sure you reference your topic when doing so.
In the meantime you might find some help here:
https://forums.nomachine.com/topic/double-nat-remote-through-internet
https://forums.nomachine.com/topic/cannot-connect-error-138https://www.nomachine.com/AR11L00827 – How to connect to NoMachine when the server is behind a NAT router or a firewall
March 8, 2019 at 10:40 in reply to: How to improve performance of NoMachine when it is used through Windows Remote Desktop #21691Britgirl
KeymasterYes, you are right: when I connect from B to C (this is setup 1), the performance is fast.
What to say? Well… Good for NoMachine, comparing the performance of RDP vs. NX, in this particular case.
Britgirl
KeymasterThis is planned. Please check the Feature Request we have inserted into the development roadmap.
March 5, 2019 at 14:54 in reply to: How to improve performance of NoMachine when it is used through Windows Remote Desktop #21669Britgirl
KeymasterYou could try turning off scaling (Fit to Window). See https://www.nomachine.com/DT10O00157#5 for more details.
Britgirl
KeymasterSystem requirements necessary for NoMachine software products are provided on the download pages of each product, so for example, Terminal Server, https://www.nomachine.com/download/download&id=55, and also in the relative Installation Guide, “Prequisites” section. For TS we indicate general guidelines of 1 GB RAM and 195 MB free disk space.
NoMachine is installed by default in /usr/NX so you must guarantee that the partition where you have installed it has the amount of space that we indicate. If you can’t clear up space on that partition for whatever reason, you can install NoMachine in a different location (/opt/NX) on a different partition, see the Installation and Configuration Guide paragraph 3 for further details about that https://www.nomachine.com/DT04O00139#2.3. Simply make sure that the new location on the alternative partition has enough space.
This is a good article for how to clean up Linux systems with the help of command line tools.
I have pointed you to the Terminal Server product because you have posted in the Terminal Server category, but you mention that you have installed Enterprise Desktop on the remote host you are connecting to. That product does not have the terminal server functionality (virtual desktops on Linux), just thought I’d clarify that. If you are using that, then please refer to its own guide. All guides are available here: https://www.nomachine.com/all-documents in the Installation section.
Britgirl
Keymaster2019-02-27 01:16:11 089.265 27763 NXSERVER WARNING! Error is: 28, ‘No space left on device’.
Looks like you don’t have enough room to even run a NoMachine session. What you need to do is have a clean of your server and make some space on your server host.
Britgirl
KeymasterJust to further clarify what is supported and not supported in the free version.
cdmackay asked:
is there any way for the NoMachine client to use the ssh-agent daemon already running on the client, so that I don’t have to type my private key pass-phrase every time I connect? That is when using key-based auth with the NX protocol.
If you are using the free edition of NoMachine, you can use key-based authentication, and you will use NX protocol.
If you want to use an ssh-agent, you must use SSH. SSH connections are only available in the Enterprise products. You might want to consider purchasing Enterprise Desktop instead of using the free version.
Britgirl
KeymasterYour question is a valid one. The FR was inserted quite early into our roadmap – when we were still developing version 4. We started initial work on it and as you know how development goes, initial ideas evolve, room for improvement is found, set-backs can occur. We had planned to make a beta version or a test version available to those who signed up (via the FR or in the forums) not so long ago. To say that it’s not a popular request would be an understatement and it’s for this reason we have to get it right, for our users 🙂
-
AuthorPosts