Forum Replies Created
-
Posts
-
Hi, I’m not sure whether you’re asking about the labels or why you are seeing two connection icons. So I’ll try to be comprehensive in my answer 🙂
The pipe icon (located through local discovery) represents computers which are found on the same LAN. You can turn this off if you don’t want your server machines to advertize themselves on the LAN. See more about this here:
https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network
You can also turn off LAN computers from being shown in your local Player if you want as well, this is also explained in the above tutorial. It has a label (in the edit panel) which explains what it is: “Located through local discovery service”.
The other icon (!M) represents an nxs file, i.e a connection you created manually. It shows when you create a connection to that computer using the “Add” button or if you input the IP address in the ‘Search’ field. This connection file can also be from previous installations as it is stored in the .nx/cache folder.
Regular nxs connections can be used to connect to any NoMachine server whether it’s on a LAN or over the Internet. The labels you see are not dynamic. They don’t change on the basis of whether you have enabled port-forwarding or not. They are used to distinguish the difference between the types of connection: one for local discovery hosts, the other for direct connections (which for the majority of users that we have had feedback from “over the internet” clarifies the difference between the two).
Can you reattach your image? (don’t paste it in)
Hi, the package for macOS is what you need across all your Macs. The package is suitable for all mac ARM and Intel-based architectures. Can you first check that permissions have been enabled correctly on the M1? Go to System Settings > Privacy > Accessibility and then “+” and add NoMachine. If it’s already there, remove and add it again (see this article https://kb.nomachine.com/AR11Q01061).
There are no limits on how many outgoing NoMachine connections you start. What counts is the number of incoming connections. Let’s look at an example. You have installed the free version on the computer you want to connect from and you’ve also installed the free version on the computer you want to access (the “server”). The number of connections you can start is unlimited. On the server side, one incoming connection will be possible. If you install Enterprise Desktop on the server machine, unlimited incoming connections will be possible.
Please also take a look at the following article:
What is the difference between NoMachine Free Edition and NoMachine Enterprise Desktop?
https://www.nomachine.com/AR07L00808Ah so it was related to permissions not being correctly set for NoMachine during installation. Thanks for letting us know.
If you’re trying to close the window on the remote machine, you could try enabling “grab the keyboard” from the connection menu (https://kb.nomachine.com/DT06S00218#3. ) or setting it in advance in the Player settings (https://kb.nomachine.com/DT07S00236#2.1). You can also toggle this setting using the keyboard shortcut with Ctrl Alt(Option) K for macOS.
Hi,
a useful guide to follow for connecting to machines on the same LAN is here https://www.nomachine.com/getting-started-with-nomachine. To connect from a device to your Mac using its local IP address, both those devices must be on the same LAN.
But let’s check that everything is configured correctly. On the Mac, open NoMachine > Server Settings > Ports, and make sure that the “Advertise this computer on the local network” box is enabled. In Server Status is the server showing as ‘running’?
How are you connecting? Are you creating the connection manually or are you using an MDNS connection? By MDNS I’m referring to the computer icon with a little pipe that appears when you open the app on one of your mobile devices (scroll to the bottom of this guide for an example of what it looks like, thttps://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network).
Could you firewall be blocking ports that NoMachine uses?
Logs files weren’t attached, but you can send them to us at forum[at]nomachine[dot]com and we can go over them.
Can you tell us what product you install on the server side. Connecting through the browser is only supported in Enterprise products, for example you could try with Enterprise Desktop on the computer you want to connect to. It won’t be possible to connect with your browser if you are trying to connect to a server where you have installed the free version.
Are you able to connect from a client using the Player i.e not from the browser?
Hi adam, I’ve checked that link to the bug report, am I right in understanding that there will be a fix in the Godot application for this issue you reported?
Headless set ups are supported, but there are some considerations to take into account as mentioned in the article I linked. If you disconnect or turn off the monitor, this can cause your GPU to stop producing an image which can result in a black or white screen because there is nothing for NoMachine to capture. This is caused by, in your case, the AMD video card and not NoMachine not working properly.
It should be ok client side. Check the list of trouble reports here for current known issues regarding Wayland.
https://kb.nomachine.com/trouble-reports?s=waylandis the move to the new Intel APIs still coming in the next release?
Yes, it is.
Hi, the extraction location is not important, as
--subscriptionsetinstalls the license in our etc folder 😉Hi, from the logs you sent we confirm that you are encountering two issues, both already known, initially reported on different distributions. The main capture method nor the fallback work correctly.
Capture of the Wayland desktop by EGL doesn’t work with KDE Plasma 6
https://kb.nomachine.com/TR05V11141Attaching to the physical desktop could fail on Rocky Linux 8 with Wayland
https://kb.nomachine.com/TR03U10784Until the fixes are released for those Trouble Reports, you can try disabling Wayland and use X.Org instead, or try with an alternative desktop environment.
If the monitor on the Win11 machine (server) is on, it connects fine. If the monitor on the Win11 machine is off, it fails.
In the logs that you sent us we see that every capture method fails when you have the monitor off. The best workaround, if you don’t want to keep the monitor on, is to try with a dummy HDMI dongle.
Related article is this: https://kb.nomachine.com/AR05S01124
New logs were clean. So I come back to my original question. Is the NoMachine server you are connecting to headless (i.e without a monitor) or maybe there is a monitor but is turned off? If it is turned off, turn it on and try again.
This article handles what to do if the Linux machine is headless
https://kb.nomachine.com/AR03P00973