Forum Replies Created
-
Posts
-
Yes, NoMachine Web Companion is free.
You can get it here: https://www.nomachine.com/download/linux&id=23
Hi Martyn,
Are your 4 monitors client- or server-side?
If they’re client-side , you can opt to display the remote desktop ‘Fullscreen’ across all monitors in the menu panel (Ctrl-Alt-0 -> Display -> Fullscreen on all screens OR click the fourth little icon from the left at the bottom of the menu).
If the 4 monitors are server side and you need to be able to switch between each of the remote displays from the client, then what you need is the following feature request:
https://www.nomachine.com/FR11K02797
Your question about thin clients that support NoMachine, that’s really a question for the sales team. You can contact them directly from the NoMachine website: http://www.nomachine.com/contact-request
Hi earthadm,
please send the top output while you have 1 session running. Do the same for 4 or more sessions.
Check also if the memory use in any of the nxserver or nxnode processes increases over time. The memory use you report is definitely abnormal. It can be the symptom of a memory leak.
This is a known “limitation” forced by policykit on some Linux systems. Basically what happens while forwarding the USB device is a simulation of physically plugging in the device to remote PC. When that is done, in the case of a pendrive, the system will try to automount it, but the problem is that policy kit allows mounting only for user that is physically on this PC (more precisely, the owner of “active” session). All remote sessions are marked as ‘inactive’, so they are not allowed to mount external filesystems.
There is a way to grant yourself access to the files. You may open a terminal, create an empty mount point and mount manually (using sudo mount). If it was already auto-mounted for the user of the physical session, you may need to ‘umount’ it first.
Beduine,
This is a known bug and has already been fixed.
https://www.nomachine.com/TR10K03974
Can you update your installation to 366?
This will help:
How to terminate a virtual desktop session in NoMachine 4
https://www.nomachine.com/AR0100585I’m not aware of this particular problem connecting from client 4 to server 3.5.0 (from NoMachine). We’ll check again to make sure that compatibility between our versions is intact, but for freenx issues you should contact who’s responsible for that project.
It should be possible to set a different password, used just for NX, with the help of password db. Unfortunately there’s a bug on Windows and we are currently fixing it. So watch out for the fix in the next update.
With the products that support SSH, you can use passwordless authentication with the help of SSH private keys. SSH support is only available in NoMachine for the Enterprise products right now.
For the free version of NoMachine, which authenticates using the NX service, passwordless authentication will be available very soon.
Iceback, is it possible for you to manually update the client side installation to -366? Tests show that NIS authentication works out of the box. -365 fixed a minor bug which could be what you are encountering https://www.nomachine.com/TR11K04017.
Did you get errors when following those steps in the article?
I logged into the NX server (nomachines 4) and stopped lightdm
You shouldn’t have to stop lightdm.
DISPLAY=:0 /etc/X11/Xsession startlxde &
Try substituting DISPLAY=:0 with DISPLAY=:1. It’s better to have the virtual desktop running on a different display to :0.
Did you install NoMachine on the Windows (VM) host?
Do that, then point your client to the Windows IP address for the connection. If you configured the Windows host to have a bridged or a NATted network adapter (so that the IP address of the Windows computer is visible to the other computers on your LAN) this is all you need.