Forum Replies Created
-
Posts
-
I will answer for points 5 and 6
Point 5)
Also I do not fully understand this article:
That Trouble Report is nothing to do with manual port-forwarding on the router. It’s referring to the GWPort box in the server GUI Services panel which is not being flagged correctly. In this panel the port that NoMachine server has automatically chosen to allow connections to the computer over the Internet is printed. See our Server Guide, specifically section 2, (see the guide here: https://www.nomachine.com/DT10O00155#2.1.)
Point 6)
And I also don’t understand the concept behind this post:
https://forums.nomachine.com/topic/problem-mapping-gateway-port#post-18936
The topic you mention is also not your case. In that particular topic, the user was having issues with changing the port in the Services panel of the server GUI, mentioned in point 5. That user wanted to change the port of a particular computer to his preference. The message returned was “Failed to map the port on the Gateway” in his case.
NoMachine works like this. NoMachine tries to use UPnP to carry out port-forwarding on its own. When NoMachine starts, it automatically selects and maps certain ports to prepare for outside access. If you want, you can change the port (GWPort) to something more memorable to allow connections from the outside (see the same guide mentioned above). This is the port which shows up in the Welcome Panel when opening NoMachine on the server.
On some occasions, NoMachine can’t enable UPnP on its own for whatever reason, and it’s necessary to intervene manually on the router. In this case, you change nothing in the UI of NoMachine and any intervention is only done on your router according to the instructions for port-forwarding of your specific router.
As for point 1) I’d just like to add that when a user doesn’t specify the actual version in numbers, it’s standard practice that we ask just to make sure. The community edition you refer to I imagine is the free version and that you downloaded it from our website.
I reviewed this previous post with a similar problem:
https://forums.nomachine.com/topic/failed-to-map-the-port-on-d-link#post-24387
We test NoMachine in a multitude of set-ups with multiple types of routers as well, but we can’t for obvious reasons test with every router available on the market. This particular user had a problem with an old D-link router which was proving difficult to configure. Replacing it solved the connectivity issues.
Any attachments can be sent to forum[at]nomachine[dot]com. If they are large files, or too many, attaching can sometimes fail. Make sure you include the title of your topic in the subject. Thanks!
You should check how you have configured your system’s settings screen lock. See example attached.
Then, if changing that doesn’t help, you will need to provide more details. On both sides, assuming you have the free version of NoMachine installed on the Windows and Linux hosts, open NoMachine, go to Settings -> Server Preferences -> Updates. What’s the version printed there?
https://www.nomachine.com/DT10O00155#2.6.
We will need to know the desktop environment on the Linux host, plus the actual distribution and version (maybe CentOS?).
Attachments:
Use of the free version is for non-commercial use. If you’re not using the game server for financial profit, it would not be considered commercial use.
Maybe your router does not support UPnP – this is why UPnP doesn’t show up. You could try port forwarding. We looked for an article in English for that specific router on how to enable port forwarding correctly but couldn’t find a good one. Perhaps you are able to find one in French?
Thanks for letting us know. You could have also changed:
/usr/bin/xdg-open /home/acer/Documents/NoMachine/Exodus_ZT.nxsto:
/usr/NX/bin/nxplayer --session /home/acer/Documents/NoMachine/Exodus_ZT.nxsHI Kurt, we received the logs. Apologies for not specifying that the logs are meant to be from the Enterprise Desktop host. We’ll provide some feedback soon.
Agent logs are missing. We would need the whole content of the ‘var/log’ dir of the server host.
Please check for core files. If found, you should follow the instructions here:
https://www.nomachine.com/AR09L00810If there is no core file but you can find a crash report in the ‘/var/crash’ dir, you can use the instructions provided in this forum post:
https://forums.nomachine.com/topic/error-is-108-connection-reset-by-peer#post-24472Hi Kurt, what we need is the full set of logs, not just the crash report 🙂
Follow those instructions that Mth provided and then send the whole file to forum[at]nomachine[dot]com.
Hi! NoMachine software is free for non-commercial use. If you are using the software at work, or in a commercial environment, you are required to acquire to buy one of our Enterprise products. NoMachine doesn’t try to guess or find out whether you are using the software in a commercial-related activity, but, as the license states, if you are using our software in your business, you are required to have a commercial license.
If you use NoMachine for work or in a commercial-related activity, or you want more than one user to connect at the same time to the physical desktop, you should buy a NoMachine Enterprise Desktop product. Or the product that best matches your usage needs.
Hi, you are referring to version 5 when Cloud Server could be used in a ‘server-to-node’ set-up. With the release of version 6 we changed the focus to ‘server-to-server’ and Cloud Server became a federation server.
In the past few months we have been adding improvements to Cloud Server, one of which is the soon to be released feature (probably next week) of being able to see whether other users are connected. It will eliminate your students’ frustration, I’m sure.
Displaying the number of users connected to the child servers
https://www.nomachine.com/FR03R03953is there a way of hiding any servers that don’t have any connections available?
Not at the moment, but in a successive release (I can’t say which right now), this other feature is planned:
Giving the possibility to exclude an Enterprise Desktop from the Cloud Server architecture
https://www.nomachine.com/FR04R03976This will also be of interest to you I believe.
Did you already follow the instructions in the both the tutorial and the installation/configuration guide?
https://www.nomachine.com/getting-started-with-web-based-access and
When the connecting to the physical desktop, the supported resolutions are those of the remote graphics card as listed in the System settings on the server. I.e., the session resolution on the client cannot be higher than the maximum resolution supported by the remote graphics card.
More information is here:
Resize and scaling options for NoMachine client version 4 or later
https://www.nomachine.com/AR02M00835But did you actually run the commands I mentioned in my reply here? https://forums.nomachine.com/topic/trying-to-sort-out-enterprise-setup#post-26946
1. Run commands changing nxaudio permissions (if you didn’t do it earlier).
sudo chmod -R 755 /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext
sudo chown -R root:wheel /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext2. Run command
sudo kextutil -v 4 /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext
and paste/attach the output to the reply
3. After that check if kext nxaudio is loaded (via kextutil in 2.) using command:
kextstat | grep nxau
