Forum Replies Created
-
AuthorPosts
-
April 1, 2019 at 14:32 in reply to: Unable to access !M monitor menu in order to transfer files #21910
BritgirlKeymasterDo you know what Linux distro is on the server and the version so we can investigated? If you are accessing a Uni server (I recognize the server name), the admin will be able to give you this info, or alternatively they can open a ticket.
In the meantime, there are two other ways to transfer files. One is by simple drag and drop. Dragging it to your local machine will leave it on the desktop. The other way is to share your disks, provided these have not been disabled on the server by the administrator. A tutorial about sharing disks is available here:
https://www.nomachine.com/accessing-files-on-local-or-remote-disk-drives
BritgirlKeymasterCan you tell us what this Java application is?
Could you also send us the stderr of that app? You can find it in userhome/.xsession-erros or /usr/NX/var/log/node/C-[display]-[sessionid]/client file. Attach it here or send it to forum[at]nomachine[dot]com.
BritgirlKeymasterHi 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 #21888
BritgirlKeymasterI strongly suggest you update the NoMachine installation on the client. Also, confirm what NoMachine version is on the Centos side.
BritgirlKeymaster@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.policy
BritgirlKeymasterit 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
BritgirlKeymasterThe 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 #21719
BritgirlKeymasterGreat news! Thanks for letting us know 🙂
BritgirlKeymasterThanks for letting us know!
BritgirlKeymasterPlease 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 #21691
BritgirlKeymasterYes, 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.
BritgirlKeymasterThis 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 #21669
BritgirlKeymasterYou could try turning off scaling (Fit to Window). See https://www.nomachine.com/DT10O00157#5 for more details.
BritgirlKeymasterSystem 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.
BritgirlKeymaster2019-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.
-
AuthorPosts
