Forum Replies Created
-
Posts
-
@andro, Manjaro is Arch-based if I am not mistaken. Although running NoMachine on Arch isn’t officially supported, we are investigating multiple issues regarding this particular distro (you can search the forums if you like). We’ll update the appropriate topics with our findings.
Regarding Kubuntu, it’s headless, so this may be of interest to you.
How to solve black screen on headless machines
https://www.nomachine.com/AR03P00973First let me clarify that NoMachine does not support connecting TO Android. The NoMachine for Android app is for connecting from Android tablets to a computer which has NoMachine installed. Steps to connect should be: 1) install on PC, note down IP addresses as per getting started guide; 2) install app on Android tablet; 3) create connection on Android tablet to connect to PC mentioned in steps 1 and 2.
Connecting to localhost essentially means connecting to yourself (so client and server are the same computer), i.e you install NM on a computer and insert its IP address for LAN that appears in Welcome screen (like you did) in the connection creation procedure. It’s a good test to see if NoMachine installed ok and is working. In your case, something is wrong with the authentication procedure.
Apologies for not including the link from our knowledge base. If you try to connect from Android to this Windows PC and you still get the same authentication issue, we will need to see the logs from the Windows host. Large attachments aren’t accepted here so any log files can be sent directly to forum[at]nomachine[dot]com making sure you insert the title of your topic in the subject. Instructions for logs are here:
The logs didn’t include the client logs.
If you have an antivirus installed, disable it temporarily and try starting NoMachine player again.Sorry, maybe I wasn’t clear. What is the macOS version where you have installed the NoMachine software?
Explaining why a session was suddenly closed requires a proper investigation based on logs and a backtrace.
You haven’t said what distro and version it is (I’m assuming Linux on the server), what the user was doing when the session suddenly closed, what the user was connecting from and so on. Is this connecting to a free NoMachine installation or a Terminal Server?
Logs can be found by following these instructions.
https://www.nomachine.com/AR10K00697This is not our login – it’s a system login. So for example you need to look at the Xubuntu manual on how to set auto-login.
Did you follow these instructions?
NoMachine’s own default settings should be suitable for the majority of environments in order to obtain optimal performance. Forcing specific settings for fine-tuning of the performance and display quality usually requires a proper investigation first. Changing node.cfg and server.cfg settings risks introducing unexpected behaviour and I think the NoMachine Support Team is able to suggest the most suitable configuration for these special cases if you are trying to set up your own commercial environment.
Associated reading:
The ProxyExtraOptions and DisplayServerExtraOptions keys in the node configuration file
https://www.nomachine.com/AR02N00877The server.cfg and node.cfg files explained
https://www.nomachine.com/AR02N00877You can also search these forums to see in what specific cases these keys have been modified.
It’s slightly more complicated 🙂
There are a number of issues with NoMachine on Arch-based distros which we have currently queued up for investigation. We will update this topic soon.
NoMachine work perfectly on all of them when on any other based distro (Debian, redhat,etc..) or Windows.
Debian, Red Hat, Fedora, Ubuntu, Suse are those distros we officially support so NoMachine must work out-of-the box 🙂 To be honest, Arch is not in the list of officially supported distros. There are so many Linux distributions and desktop variations for any possible Linux distribution that, even if we were willing to support them all, it would be an impossible task.