Forum Replies Created
-
Posts
-
Do you mean the TR ‘s workaround does not help, or do you mean the keyboard is now working correctly?
You appear to have a double NAT there. So NoMachine has to go through two routers. You will need to forward the first port from external IP on Starlink to TPLink, and than from TPLink to the computer (https://kb.nomachine.com/AR04S01122). If you’re not in charge of both of these routers, you would need to contact who is in order to open the necessary ports to get access to your network from outside.
The upcoming NoMachine Network feature of version 9 will solve all these networking problems. There will be no need to know your computer’s IP address, or other network details. See this page for an introduction into what’s coming up: https://www.nomachine.com/network
It’s strange that you can connect from other clients without issues. As you said the problem appears to be on the Manjaro device you are connecting from, so for that we need the Player logs which were missing. See “Fourth Step: Collect Client Side Logs” in the link I gave previously.
Hi, there is a Trouble Report open about a similar issue. Could you check whether the steps to reproduce reflect your case and whether the workarounds also apply?
Hi,
there are currently no options to install “only nxhtd” or “only nxd”, but putting the NoMachine Web server on a different machine is definitely possible by design. Simply install the NoMachine package you’re interested in adopting which includes the web server (e.g., Enterprise Desktop, Workstation, any other Enterprise-oriented product etc) on both machines [VM_A, VM_B].
Then, configure VM_A according to the instructions in the NoMachine guide:
“How to configure a NoMachine server to connect web sessions on localhost or on different hosts”
https://kb.nomachine.com/AR06P00984The Webplayer on VM_A will connect exclusively to the nxserver [on nxd port ] on VM_B.
Additionally, you can limit nxserver on that host to allow only HTTP connections, which will disable NXD and SSH connections, preventing the NXD process from starting.
To do that, modify the “server.cfg” file:
”
ClientConnectionMethods HTTP
”To prevent “nxnode” from starting on that server, modify the “server.cfg” file:
”
AvailableSessionTypes “”
“Hi, take a look at point 4 in the following article:
https://kb.nomachine.com/AR04K00667#4
If there are multiple desktop environments, you can configure NoMachine to provide users the list of all the available desktop types installed and configured on the system (i.e. available in /usr/share/xsessions).
Set ‘xsessions=1’ in the ConnectPolicy key in /usr/NX/etc/server.cfg:
ConnectPolicy autocreate=1,autoconnect=1,automigrate=1,desktop=0,dialog=0,xsessions=1,udp=1
Removing the # from the key. Then when connecting, NoMachine will show all the DE options available.
Or to show XFCE, you can set the DefaultDesktopCommand key in node.cfg:
DefaultDesktopCommand “/usr/bin/startxfce4” (see point 2.1 of the same article).Hi, please submit the logs to forum[at]nomachine[dot]com. I see that the link was not visible in an earlier reply from Bilbotine, so here’s the link.
https://kb.nomachine.com/DT07S00243
Please use the title of this topic as the subject of your email.
Hi, please tell us what NoMachine software you have installed and the exact steps to reproduce the problem in the NoMachine remote desktop connection. Thanks.
Hi,
The X11 vector graphics mode is a server side configuration available in all of the NoMachine Terminal Server Products. These products support the NoMachine virtual desktop functionality. As written in that article, Enterprise Desktop does not support this functionality. Enterprise Desktop, like it’s free version counterpart, is for access to the physical display. By “virtual desktop functionality”, we refer to “NoMachine virtual desktop”, not the virtual desktop of the hypervisor technology you could be using.
How can !M detect if it connects to a virtual or physical display ?
For NoMachine, whether the OS is running on a virtual machine or a physical machine is irrelevant in terms of what NoMachine will detect. In fact NoMachine software can be installed on physical machines, virtual machines, cloud-based systems, wherever there is a desktop environment installed there. NoMachine will detect a display (an x server) and let you connect to it. On Linux, when connecting to a desktop which doesn’t have an X server running (e.g. it’s a headless machine), NoMachine is able to use its own display service, what we call an embedded X server, to let users connect seamlessly to the physical desktop on the remote machine.
When I’m connected with !M to this machine from a Linux PC, the desktop of the VPS is detected as a physical display. It seems quite strange, doesn’t it ?
Not at all. Enterprise Desktop is doing its job 🙂 On Linux systems, if it doesn’t detect a display when you request a connection, it will tell you and give you the option to start its own display service.
On the other hand, you want to run multiple desktops on the same Linux host (the virtual desktop functionality mentioned earlier), you need a NoMachine Terminal Server product. Try Workstation to start off with. This will let you run up to 4 NoMachine desktops concurrently.
Some additional information you will find useful:
https://www.nomachine.com/creating-nomachine-virtual-desktop-sessions-on-linux
https://kb.nomachine.com/AR10K0070000Hi, I’m not sure what you’d like to achieve in terms of running the LDM after the XFCE desktop session starts. Maybe try with #UserScriptAfterLogin “” and in the server.cfg, not node.cfg? Also check your permissions, and ownership of the effective user. This ‘afterlogin’ script is executed as user nx, so you need admin privileges.
More about custom scripts is available here:
Server Automation Interface: some examples to use custom scripts triggered on server/node events
https://kb.nomachine.com/AR02L00787and any of the guides of the Enterprise products. Here’s the link to the Enterprise Desktop guide (like the free version but with more features) https://kb.nomachine.com/DT10R00171#11.3.
At the moment it’s not possible for us to indicate a time-frame. Right now our priority is NoMachine 9.
We can tell you the Client Hello Extensions, though we would be interested in knowing why you are asking. We use the very minimum to support our case. It’s not the purpose of NoMachine to implement an extensible TLS system, but to implement NoMachine. If there is an extension that is not included, and which you consider a requirement, please tell us what it is and we can evaluate whether to add it.
Extension Type: 0x000A (supported_groups)
Extension Type: 0x000B (ec_point_formats)
Extension Type: 0x000D (signature_algorithms)
Extension Type: 0x0016 (encrypt_then_mac)
Extension Type: 0x0017 (extended_master_secret)At the moment we don’t have plans to add support for AVP. It’s an interesting use-case but a rather niche one.
Could you try adding this to the node.cfg file?
DisplayAgentExtraOptions “-alteventapi 1”
Locate the node.cfg file, edit it by adding the above line, then save. Restart the server.