Forum Replies Created
-
Posts
-
Yes, it is because only one connection is allowed to the remote computer where you have the Free Edition installed. Try the Enterprise Desktop (evaluation is for 30 days). You can also contact our sales team which will be able to answer any questions about pricing (possible volume discounts as well) and also our licensing model, extending the evaluation period etc.
You can compare the Free Edition and ED here:
Differences between NoMachine Enterprise Desktop and the free to download NoMachine package
https://kb.nomachine.com/AR07L00808and here:
In our case, we also found that
DefaultDesktopCommand "env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus /usr/bin/startplasma-x11"should be enough to start virtual sessions on Arch/manjaro with KDE Plasma.
Hi, we merged your two topics to create one 🙂
The error message you show indicates that the router on the side you are connecting to is not allowing incoming connections. You should follow the instructions here:
How to connect over the internet to another computer with NoMachine
https://kb.nomachine.com/AR10R01099When NoMachine Network, a new functionality we are developing, becomes available, this will mean that you don’t need to know the IP address of your target computer nor enable special access on your router.
The NoMachine software by default fetches our repositories every two days but updates are never installed automatically.
To disable the automatic check or change the update frequency, please refer to instructions at:
https://www.nomachine.com/AR05M00847.
You can also take a look at the following document:
What you need to know about automatic updates
https://kb.nomachine.com/DT11R00184Hi,
NoMachine server, and its corresponding license, is installed once on the machine which is running the desktop you want to access. In your case, a subscription license for Enterprise Desktop gives you access to the physical display on that host. If there are multi-monitors attached to that remote desktop (server-side), NoMachine will detect this in your remote desktop session and let you switch between the monitors. See here for more information:
https://www.nomachine.com/switching-the-view-between-multi-monitors-during-a-remote-desktop-session
If you prefer to start separate connections (so 3 in your example) to that desktop, they will all be connected to the same physical desktop, but as separate sessions each one will be able to view a different monitor.
I already tried ConnectPolicy autocreate=1,autoconnect=1,automigrate=0,desktop=0,dialog=0 on a Windows system, but still when I remote in, it disconnects the first connected session.
This key is for NoMachine virtual desktop sessions when connecting to NoMachine Terminal Server Products, so you should ignore this key. Have you already tried the evaluation ED or have you installed the free edition? Installing the Free Edition on the remote computer you want to access allows one connection. And so if you try to connect a second session, the first one will close.
If we create a virtual desktop such as with the workstation for Linux, can we define multiple virtual screens/monitors and display them through NX.
Yes. Workstation, like all of the products from the Terminal Server family, lets you run multiple instances of a Linux desktop on the same server. NoMachine terminal server products for Linux will also treat multi-monitors on the client as separate monitors in virtual desktop sessions. This means that when the user chooses to span the NoMachine player window across all client-side monitors, remote applications will see the same layout of monitors and can be maximized to a single monitor. See more about this here:
How multi-monitors on client side work when connected to a remote desktop
https://kb.nomachine.com/AR06S01131If you have multi-monitors on the server-side and connect with NoMachine to the physical desktop (whether it’s a VM or physical hardware), it’s not currently possible to have each of those monitors display to an individual screen on the client side. It’s planned, but we can’t give you a specific version of when this will be available.
Maybe the low resolution the headless physical display had was the cause of the KDE problems. Glad to know you’ve solved your issues anyway. Although I’m not quite sure if you’ve resolved the “black screen” or “missing kde taskbar” 🙂
Currently the client follows the selected DPI when painting on screen. In the future we are consider implementing an option to ignore the DPI. But this is still being evaluated.
Hi, this is related to the GPU’s capabilities.
Please consult this article from our online knowledge base:
How to solve ‘stuck resolution’ problems on headless machines
https://kb.nomachine.com/AR05S01127“In some cases users can get only a small screen resolution without the possibility to change it (‘stuck resolution’). This depends on the GPU which makes available only one resolution when the monitor is not present.
A common solution is to adopt a fake display dongle (also called ‘dummy dongle’) inserted in the video card port to simulate the presence of a screen and force the system to take full advantage of the GPU as if a real monitor is connected.”
I’m not sure what you mean by “Opening the settings on the headless windows machine also doesn’t really work because when I scroll to the desired setting only the scrollbar moves and everything else stays still.” A recording of the NoMachine session would be useful to illustrate the problem perhaps.
Hi,
we’ve just updated an article that will help with configuring your Fedora NoMachine server in an AD domain using the NX protocol.
Connecting with NX protocol to a NoMachine server on Linux in an Active Directory domain
https://kb.nomachine.com/AR12P01007mcjev, thanks for letting us know.
If you happen to switch back to Wayland and only if you want to, enable the logs on the server side and send them to us so we can check. This would help us understand what’s going on.
See this article for instructions: https://www.nomachine.com/DT11R00182