Forum Replies Created
-
Posts
-
Have you checked this article?
How to connect to NoMachine when the server is behind a NAT router or a firewall
https://knowledgebase.nomachine.com/AR11L00827You posted a link to a PDF which was removed, but googling I see that it has a section on how to enable port-forwarding. Please follow the instructions for doing that as well.
There’s no need to change the gateway port
“Authentication failed, please try again” – this indicates that you are reaching the Windows host but that the username and/or password are incorrect. Are you 100% sure that you are using the right credentials of a system account on the Windows PC?
What version and product of NoMachine do you have installed on the server side? Ctrl-Alt-0 (zero) activates the NoMachine session menu (or you can use the page peel). See this guide for more information on Display settings that Tor mentioned:
https://www.nomachine.com/DT10R00167 (sections #2.1 and #5)
Almost every time it is getting timed out and sometimes it gets connected.
Strange. That sometimes you can connect and sometimes you can’t can indicate a problem with the network and not with NoMachine.
1) When trying to connect, if you are seeing “Error ‘Operation timed out'”, this indicates that NoMachine on the remote computer is not reachable.
When this occurs you should verify the status of NoMachine server.
You can do that from a terminal using an account with administrative privileges is needed:
sudo /etc/NX/nxserver –status
Output should be similar to:
$ sudo /etc/NX/nxserver –status
Password:
NX> 111 New connections to NoMachine server are enabled.
NX> 162 Enabled service: nxserver.
NX> 162 Enabled service: nxnode.
NX> 162 Enabled service: nxd.2) However, then there is this in the logs “A connection timeout has occurred while trying to connect to ‘skanoj-jumpbox.dlpxdc.co’ 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.'”
NoMachine connections use by default NX protocol and port 4000. Port 4000 must be free so check that it is not being used by other applications maybe?
It’s strange because you mentioned that your other Windows computer installed fine.
There’s not much we can do as it seems the default profile of your Windows host prevents our installation from creating user nx (without it NoMachine cannot function), and the only way to check whether your profile is corrupt in some way is by creating a new one and trying to install NoMachine in that.
Hi brigman, indeed relaying the location and compass data from the client-side device to the server would require minimal effort. I agree that this could be a useful feature to have, so we’ll definitely evaluate doing this. Do you just need it because the navigation program you are using happens to be on the server?
Hi all, thanks for your feedback.
We understand that this can be problematic. If you think about it the problem was also there in the past, where connecting to the same machine from 5 different places would mean having to create 5 individual nxs files.
The current mechanism does actually make perfect sense for a user that connects to multiple computers from the office, where you presume that there is a proxy in place, or from home via their ASDL to computers anywhere in the world by simply toggling on and off in the Player settings. This is how browsers work as well.
How to use automatic proxy settings with NoMachine
https://knowledgebase.nomachine.com/AR05S01129How to configure proxy settings manually with NoMachine
https://knowledgebase.nomachine.com/AR05S01130We placed considerable importance on the automatic/manual configuration of the proxy either based on the configuration of the operating system or the LAN. We imagined that this “automatic proxy configuration” would work and resolve the question in most settings. (By the way, please tell us if you tried it and if it worked).
We can evaluate whether to give the possibility to choose the most appropriate proxy setting at the start of the session. That said, please, check that the automatic configuration of the proxy on your network is usable, it’s a standard in all OS and all network configurations via the DHCP protocol.
Willie108, the same thread shows the correct link to use, just a few rows down 🙂
https://forums.nomachine.com/topic/my-successful-story-in-setting-up-nvidia-driver-on-aws#post-28650
Does that work for you?
We’ve inserted an article which can be useful for other users in similar situations:
How to install NoMachine packages when RPM security policies are elevated
https://knowledgebase.nomachine.com/AR05S01128Maybe an entry in DefaultDesktopCommand was no longer valid for your sysem after you executed the system update?
Anyway, Thanks for letting us know. A clean reinstallation fixed it, so that’s the important thing.
In that same guide you can find how to re-enable it via CLI in the server.cfg file, it’s in section 10.
Override user's setting to disable 'Accept connection' If the user disabled 'Accept connections' from the !M monitor menu of the Enterprise Desktop, it's still possible to re-enable it via command line. nxserver --useredit USERNAME --screensharing yesNoMachine packages for Linux are, at the moment, not signed. This is to prevent warnings when the user doesn’t have
the installed publisher certificate.You can install the NoMachine package, even if unsigned, on Fedora 33 by means of the ‘rpm -i’ command as per the instructions in the download page of the NoMachine web site.
Hi,
Is it possible to update NoMachine without terminating sessions?
No. You will be disconnected because updating requires the stop of all NoMachine services which will be restarted once the update has been completed. You will then be able to reconnect.
Please refer to this article for more details:
How to remotely update NoMachine
https://knowledgebase.nomachine.com/AR05S01123If I don’t update the NoMachine is there any issue with the existing sessions?
Whereas we always recommend users keep the NoMachine software updated to the latest version which means the latest bug fixes have been installed, including important security updates, if the software is working well for you, you aren’t forced to install the latest version.
We were hoping sooner than later. Development on the next update for mobile is in parallel with our next major, which is now v8. We know it’s long overdue, we are working flat out to make sure it fixes what we promised it will fix 😉