Forum Replies Created
-
Posts
-
If you can send us logs when it does happen, this would be useful.
Edit: the topic is now closed. If it happens again, please start a new topic.
Hi, the player logs were not included. Are you sure you ticked the box “Don’t delete logs files on exit’ as outlined here? – https://www.nomachine.com/DT10O00163#2
Provided that checkbox is ticked, logs will be saved on the connecting client of the affected session.
We’ve also released version 7 since this topic started, so it would be wise to update to that on both the client and server and try and reproduce.
Daniel, sorry for the delay in replying. If you have NoMachine free installed on the remote Linux computer, this shouldn’t be possible. It’s strange that we don’t detect physical session. First, can I ask you to update to the latest version (v7)?
Can you also confirm the following:
– are you using Wayland? If so, can you try with x.org instead?
– is this a virtual machine, if so is it virtualbox or something else?
– can you show me the output of
nxserver --historyAlso, logs of the affected session (from the server host) would be useful. (see https://www.nomachine.com/DT11R00182) and submit to forum[at]nomachine[dot]com.
Answer: I don’t understand. Do you mean I have to set up another Port Forwarding for UDP?
Yes, like also suggested here: https://forums.nomachine.com/topic/access-multiple-desktops-via-internet#post-23829
If it still doesn’t work, what you need is the upcoming NoMachine Network feature which will make intervention on the router unnecessary. Sign up to receive a notification of its implementation by following this link: https://www.nomachine.com/FR07J02731.
It could be possibly related to this TR (https://www.nomachine.com/TR11R09917) which was recently fixed in the first version 7 software update, so please update NoMachine and report back. If it continues, please show us a screenshot(s) of what you see when clicking on the !M icon of the remote Linux computer and select ‘Download a file from the server’.
Please update to the latest version of NoMachine and if you still have issues, please open a new topic and attach the screenshot of the permissions in Security/Privacy. Thanks!
The patch was included in version 7.0.208. Please make sure you’ve updated to that version or later. Thanks!
What message are you seeing when connecting via NoMachine? Did you follow the instructions here?
How to connect over the internet to NoMachine behind a NAT router
https://www.nomachine.com/AR10R01099What you attached appears to be ok, except you should also select a rule for UDP (as outlined in the article) just to make sure.
Maybe you should look at this trouble-shooting page https://openmyip.com/Dlink-DIR-850L-router-setup. It also gives possible reasons for port-forwarding not working.
Topic closed as user also posted to this topic addressing the same issue https://forums.nomachine.com/topic/problems-with-nomachine-on-windows-10
Hi, please see the topic which has already dealt with this topic: https://forums.nomachine.com/topic/cant-quick-access-remote-pcs-from-systray-context-menu-in-7-0-x.
The logs would need to include debug level. We checked on the fly and didn’t have any problems installing and running sessions from a Linux Cinnamon 20. If this is your first installation, I suggest to completely uninstall, remove all nx dirs
rm -rf /usr/NX .nxand install again. If that doesn’t help, submit the logs of a failed session once you have enabled debug on the server side and gathered the logs. See this article for instructions: https://www.nomachine.com/DT11R00182. Send them to forum[at]nomachine[dot]com making sure to reference the title of your topic. Thanks!
You can disable it in the server configuration key:
#
# Specify the network interface where the NX service will be bound.
# Populate the field with an IP address or a domain name.
#
#NXdListenAddress “”For example:
NXdListenAddress 10.1.5.1
Hi, are you using the latest version of the software on both server and client? Can you confirm the version of the Windows PC you are connecting to?
The connection logs can be sent directly to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
We’ve reproduced the problem and opened a Trouble Report which you can track using the following link: