Forum Replies Created
-
Posts
-
Hi, you have two choices basically. You can either uninstall and remove all traces of the product and reinstall or you can write to our sales team and ask for an extension 🙂
One thing though, you say you were evaluating Terminal Server but are interested in purchasing Enterprise Terminal Server. These are two separate products. The former is for a single server set-up; the latter offers multi-node support, so you would need to add on Terminal Server Nodes in order to create your load-balanced set-up.
Hi,
we have just recently made some changes to our roadmap which affect the FR that you linked. Please check it again and proceed to the new link that is provided in the dismissed FR. It is definitely planned and its current target is version 7.
Please check that you have the screen recording permissions set like in the screenshot.
Attachments:
Update: images received from user.
Attachments:
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.
