Forum Replies Created
-
Posts
-
To Doug, we’re analyzing all the information you sent us and will come back to you soon.
To MasterOfus, your issue could be a different issue and so we will need the full set of logs from the Mac server. Check here for details: https://kb.nomachine.com/DT07S00244 and submit to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email.
To raleighr3, the logs from your Mac server would also be useful as per my request to MasterOfus. Thanks everyone.
On versions of macOS prior to Catalina, NoMachine installs without having to manually set permissions in the Accessibility section of the OS. You can read more about this here, but it should not affect you because you are running High Sierra.
https://kb.nomachine.com/AR11Q01061
The fact that you can start a connection is proof that NoMachine is installed correctly on at least one of the Macs đ
So, to connect, in your Add panel, you must put the IP address of the Mac (the NoMachine server) you want to reach. This is obtained by checking what NoMachine prints in the Server status panel for that machine. If the two computers are on the same network, perhaps on your home network(?), you should use the IP address that generally starts with 192.xx, like in the example in our Getting Started Guide, Fig. 2 https://www.nomachine.com/getting-started-with-nomachine.
The error you are receiving generally appears when you are connecting over the Internet (so the two computers are not on the same LAN). If that’s the case, you need to enable UPnP to allow NoMachine to automatically configure port-mapping. It might also be necessary to enable port-forwarding on your router. Please consult this article and follow the instructions there: https://kb.nomachine.com/AR04S01122.
Iâm using the current consumer Linux products, but this has happened to me under Windows as well.
Do you mean that you can also reproduce it when connecting to Windows ? Or are you always connecting to Linux hosts and you reproduce it regardless of what OS you are connecting from?
If the server side is always Linux, do you have Wayland or X.org running there?
Hi, NoMachine uses a system user that is already created on the server side (System username and password). While it is common on Windows not to set a password, one must be set if someone wants to use NoMachine. This is due to Windows policies. A local system account is limited to using an empty password to console logon only.
You can find more about this subject in the following article : https://knowledgebase.nomachine.com/AR05L00802
“Due to Windows policies, a local system account is limited to using an empty password to console logon only. This is a security setting within the Windows OS and determines whether local accounts that are not password protected can be used to log on from locations other than the physical computer console. If enabled, local accounts that are not password protected will only be able to log on at the computer’s keyboard. This implies that connecting by NoMachine with an account having a blank password is not possible unless you configure your Windows to open the appropriate policy.”
NoMachine offers the possibility to connect without a username and password in Guest Desktop Sharing mode. This requires a user to be present on the computer you are connecting to because the connection must be authorised. I’m not sure if this is of interest to you, but you can read more about it here: https://www.nomachine.com/guest-desktop-sharing.
Yes, NoMachine installs correctly and works out-of-the-box on macOS 10.13. Are you using the latest version? It is not necessary to have to manually enable/set permissions on earlier versions of macOS.
If you have installed and not been able to connect or are seeing an error of some sort, please provide steps to reproduce and possibly a screenshot of what you are seeing. Thanks!
get output audio working by disabling autospawn in my local pulseaudio.conf
Good. Sorry for not mentioning that last time. This is what we also suggested in other topics, for example in
https://forums.nomachine.com/topic/message-cannot-find-the-default-environment-please-contact-your-system-administrator-on-latest-slackwareWith regards to the microphone, by default microphone is always disabled, so users connected to the desktop can forward their own microphone to the session by activating it from the NoMachine menu panel inside the session. Click on the right upper corner of the session window or press Ctrl+Alt+0 to open the menu.
Choose âMic inâ icon button and click âEnable micâ. Sections 6.1 and 7 (Fig 18 and 19) in the following guide:
https://kb.nomachine.com/DT09T00266#7
Now users are able to use default microphone from the client machine in the session. To swap input device just click on âChange settingsâ and choose other device in the âMicrophone inputâ section.
To use input device from server machine in the session â users need only to play sound from microphone by using some application like system voice recorder.
Does this help?
We have reproduced this same behaviour and will be opening a Trouble Report. When you are in session with enabled caps lock and then disable caps lock and move to another window (for example move from notepad to terminal ) caps lock will be locked.
A temporary workaround can be clicking outside of session and then proceed with disabling caps lock.
nxmac, we got your email with the set of missing logs and will update this topic soon. Thanks for your patience đ
p.s we don’t need logs for the other topic, please check that topic to see a possible workaround that worked for us.
I’m not sure what the problem is that you have with the software you’ve installed. It seems to me that your license has expired and for this reason you can only install up to a certain version of v6 updates. The same rule applies to v7 updates installed on top of v6 software. i.e it’s not possible to install updates of any release on top of software which has an expired subscription.
For version 6, once your subscription expired, updates were no longer possible and the software continued to run as expired software. So, if you had a subscription, let’s say purchased on December 21st, 2018 and it expired on December 21st, 2019, you would have been able to install updates which were released before your expiry. So, in this particular example, the maintenance of v6 which was 6.9.2 (Dec 17th, 2019) could have been installed. Any maintenance update which we released after the license expiry date of December 21st 2019 could not have been installed, but the software would continue to let you connect.
This model changed in version 7.
Pasting from the article in our KB:
Why renewing your NoMachine Server license is important
https://kb.nomachine.com/AR03D00365Starting from version 7, it is necessary for subscriptions to be renewed in order to continue to use the software, and keep your NoMachine server(s) in a functional state. When your subscription period has expired, the software will stop working and connections will no longer be possible.
This applies to v7 licenses and later, and also v5/v6 licenses activated in v7 software.
Hi,
to be able to connect a computer which is not on your same LAN, you need to use the public IP address of the computer you want to access. Please check the following articles if you have not already done so:
How to connect over the Internet (enable UPnP to automatically configure port mapping)
https://kb.nomachine.com/AR10T01175How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR04S01122The External IP of the computer you want to access can be checked by its owner on whatismyip.com and then communicated to you.
If this doesnât help, please send a screenshot of the error message you are receiving when you connect to the other person’s PC.
We don’t see many differences in your environment settings between the two. You could try editing /usr/NX/etc/node.cfg on the server side:
DefaultDesktopCommand "env XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share /usr/bin/startxfce4"and connect again to your “headless” machine (on the server first stop X server and then
sudo /etc/NX/nxserver --restartand then connect)If the problem is still there, tell us what distro is and how you installed xfce.
Hi, you mention “take back control”. If your question is related to a sharing desktop scenario with another user and you find yourself in the situation that you want to disconnect any user which is connected to your computer, go to !M in the system tray and select to disconnect a specific user or all users. You can read more about this here:
https://kb.nomachine.com/DT07S00239#5.1
Additionally, something to consider about NoMachine in desktop sharing scenarios is that by default it gives priority to keyboard and input events from the local user logged-in to the remote computer over input generated by a user connected remotely via NoMachine. This adds a further security level to desktop sharing, so that the input (mouse and keyboard) of the remote user connected by NoMachine will be effective only after the local user doesnât produce any input for a certain period. When the NoMachine user gains control over keyboard and mouse, the local user can stop him/her at any moment by simply moving the mouse or typing something.
Does this answer your question?
About the topics from a while back for Linux set-ups, they are rather outdated now and were closed because the users didn’t get back to us đ
is it possible to implement this feature?
This is exactly what we are evaluating đ
Edited 17/4/2023: we will be adding the possibility to specify multiple IP addresses for the NXdListenAddress key.
NXdListenAddress is working only for single IP and not multiple entries. The correct syntax to use is NXdListenAddress âipaddressâ as indicated in the cfg templates, using without “” can create issues on some systems. Did you restart nxserver after changing that NXdListenAddress?
We confirm that NXdListenAddress will be correctly shown in the MDNS broadcasts, but NXdListenAddress does not show correct information in the Server Settings/ Status panel. This will need further investigation.