Forum Replies Created
-
Posts
-
Hi, please check 2.3. Troubleshooting of the following article How to connect over the internet to NoMachine behind a NAT router https://kb.nomachine.com/AR04S01122.
When we release NoMachine Network, the external IP address (in order to connect over the Internet) won’t be required. Please also take a look at my response for the following topic https://forum.nomachine.com/topic/nomachine-unable-to-connect-to-windows-machine-over-internet#post-46677.
Hello, when the NoMachine (server) computer is behind a NAT router or a firewall, NoMachine tries to use the UPnP or NAT-PMP protocol depending on what is supported by the router. This is to retrieve the public or external IP of the host machine where it’s installed and configure the router to allow a NoMachine client to connect from outside of the private network (port mapping). This port mapping service can work efficiently only when it’s enabled in the server configuration (check that this is the case) and that the router supports UPnP or NAT-PMP and can also accept commands for automatic port forwarding. In some cases port-forwarding must be manually configured.
There is an article with instructions on how to connect to NoMachine when the server is behind a NAT router or a firewall https://www.nomachine.com/AR04S01122. Please check this and follow the steps. It also explains how to enable port-mapping.
In the upcoming version major NoMachine 9, which is not that far off, we will release NoMachine Network. This will permit you to connect to your remote computer without having to do any of the above. You can see more about this here: https://www.nomachine.com/network.
Hi Ade, thanks for letting us know and good to know that everything is working correctly now. If you need help again, let us know here or start a new topic 🙂
Hi,
the steps work for us in our environment.
Please tell us:
– on which machine you generated the key
– which openssh version is installed there
– the exact command you used to generate that key
Last thing to check on the server side (I understand from what you write that you are connecting to a Windows machine) is whether the .nx/config/authorized.crt file is correctly named, has the correct permissions (needs to be readable for All) and that the key is added correctly.
By the way, I noticed you are using an earlier version of the NoMachine player (7.13). Although we maintain compatibility, please consider updating your software to keep the versions aligned 😉
Hi, logs don’t show anything strange.
Please take a look at the article about headless machines and follow the tips there:
Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973If you are using Wayland, take a look here:
Notes for connections to Linux physical desktops running Wayland
https://kb.nomachine.com/AR02P00969If you continue to have problems, we can take a look at the logs of the server machine with debug enabled. Follow the instructions here for those https://kb.nomachine.com/DT07S00243 and send them to forum[at]nomachine[dot]com using the title of the topic as the subject of your email.
Hi, if the custom script terminates before the time-out and exits with a non-zero code, in that case NoMachine reports an error. If the script finishes with exit code 0 before timeout, then the session is started. If the timeout is reached and the script has still not finished, the script is killed and NoMachine reports an error. What is happening in your case? Can you provide some more details about your script and what you are trying to achieve? Do you need your script to have finished running before the start of the session? Or can it maybe run in the background whilst the session still starts?
The time out for custom scripts is a value (30 secs) which is currently not configurable but we can evaluate the possibility to make it configurable. What would you like to achieve with your script that needs longer?
Here is the Trouble Report link so that you can track the issue.
https://kb.nomachine.com/TR01V11052Hi,
can you tell us the Linux distro that is installed on the Rock Pi? What desktop environment is it? Steps to reproduce?
You mention “login acceptance”, does that mean User 1 accepts the request to connect from User 2? What NoMachine product is running on the Rock device? The free version or the Enterprise Desktop?
Could you submit those logs to us via email? Send to forum[at]nomachine[dot]com. Thanks!
Can you send the zip file to forum[at]nomachine[dot]com please? Use the title of this topic as the subject of your email 🙂
Hi to both of you
we are aware of a similar issue. Logs from affected servers we have checked show the wrong behaviour is triggered someway by Wayland, our developers are looking for a possible solution, but in the meantime the suggested workaround is to disable Wayland.
If disabling Wayland has no effect, please submit logs from the Ubuntu server side. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Just checked them on the fly. The agent logs are missing 🙁
Can you reproduce and resubmit? From a terminal,
$ sudo /etc/NX/nxserver --debug --enable all(in case you disabled debug already)
$ sudo /etc/NX/nxserver --debug --collectSome feedback about this – in checking the latest image of Raspberry Pi OSarmv7 (Bookworm), there is a 64-bit kernel. This is why uname -m command shows aarch64. However, the libraries in Bookwork are for armv7 and that’s why you need to install a package for armv7. So the folks at Raspberry will probably need to fix this in a later update.
On normal systems or older Raspberry devices we block the installation, like here:
sudo dpkg -i /tmp/nomachine_8.10.1_1_arm64.deb
dpkg: error processing archive /tmp/nomachine_8.10.1_1_arm64.deb (–install):
package architecture (arm64) does not match system (armhf)
Errors were encountered while processing: /tmp/nomachine_8.10.1_1_arm64.debIf you are running Wayland, please use X.org instead. There is a Trouble Report already open which you can track using this link:
Wayland doesn’t work on Raspberry boards
https://kb.nomachine.com/TR10U11031