Forum Replies Created
-
Posts
-
Are you connecting with Chrome? There is a known issue specific to the Chrome browser which can monitor using this link: https://kb.nomachine.com/TR07T10566
Could you try connecting with an alternative browser and tell us if you still see the spinning wheel?
There is a bug that we are fixing in the soon-to-be-released maintenance. Keep your eyes peeled. This will fix the Rosetta 2 requirement that you are seeing on macOS ARM machines.
The output you show indicates that NoMachine Free Edition for Linux (debian) was not uninstalled correctly using the recommended way, which is by using
dpkg --purge. You probably just removed /usr/NX/ before uninstalling.To be able to install a new NoMachine package, you should also remove /etc/NX/ and /var/NX/ and try again from scratch.
With the release of version 8, a new option in the client connection file (.nxs) allows to enable/disable the update of the local clipboard when a text is selected inside the NoMachine session. This option is named “Disable updating clipboard on mouse selection” and accepts value “true” or “false” which is the default.
This setting applies to connections from Window and macOS to Linux (physical desktop, virtual desktop and custom sessions).
Hi,
just to clarify that this message “Running NoMachine sessions over a SSH connection is not supported on this server. Do you want to switch your connection to using the NX protocol?” occurs when you are trying to connect to the desktop where you have installed the NoMachine Free Edition via an SSH session, when the free edition does not support SSH.
If I understand correctly, you can connect to the localhost on your Windows machine. This means everything is working. But you cannot connect to the localhost on your Ubuntu machine. The IP address would appear to be not correct. Can you try by just inserting the term “localhost” in the hostname field of the connection configuration?
A connection timeout has occurred while trying to connect to ‘192.168.1.103’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.
This message generally appears when you are trying to connect from the internet and your computer is behind a NAT or if the firewall is blocking the connection in, but it’s strange that your firewall would be blocking connections from the same machine. The logs of the server machine would be useful. Please follow the instructions here and send them to forum[at]nomachine[dot]com, https://kb.nomachine.com/DT11R00182, making sure to use the title of this topic as the subject of your email. Thanks!
Balloon messages, which are used to notify (e.g someone has connected/disconnected) as well as prompt the desktop user to accept a specific function (e.g accept an incoming connection), are a central security feature of NoMachine software. Whilst in version 7 it is possible to disable all balloon messages using the appropriate key in node.cfg, in version 8 the disabling of all balloon messages is no longer possible.
In v8 we have maintained the possibility to show/not show the !M service icon in the system tray (like it is in version 7) but notification messages will still be displayed since they are independent from the !M icon.
Please take a look at the topic here: https://forums.nomachine.com/topic/no-connection-with-nordvpn
Maybe you could raise the DHCP lease time, so machines added to the network will keep the same IP for longer time? That way you won’t need to change it often in the connection settings.
are those mac addresses?
no, those are server UUID’s generated when NoMachine is installed
Edit: The release of NoMachine Network will resolve the question of now knowing the IP address of your remote computer (especially in the case of dynamic IP addresses).
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.