Forum Replies Created
-
Posts
-
Hi McVitas, we’ve prepared a new package for debugging. I am going to send you the link via email like last time. Please check your inbox.
m8johnson, the logs you submitted were not complete. Let’s try again with the automatic procedure. Please see here:
https://knowledgebase.nomachine.com/DT11R00182#2
Enable (with
sudo /etc/NX/nxserver --debug --enable all), reproduce the problem, gather up the logs. They can be submitted to forum forum[at]nomachine[dot]com if they are too big to attach here.We would like to check the .nx folder permissions. You should submit this information (2 screenshots) via email to us because there could be sensitive information included:
– Open Windows explorer (file browser window)
– Type %USERPROFILE% in the URL bar
– Open View menu and check “Hidden items” box
– Right click the folder “.nx” and select Properties
– Get a screenshot of the Security tab
– Enter “.nx” folder and do the same for the folder “config”When you enter the .nx folder what is the path visible in the file browser?
Thank you.
Hi, this should not be happening.
Can you take a look at the list of processes while that dialog is open?
– Open the Window’s Task Manager
– Right click the list of columns and check the item “Command line”
– Look for every application named “NoMachine Tray Monitor”
– Write down the list of arguments visible in the column “Command line” and tell us here (or submit a screenshot if you prefer).Also, confirm the Windows version and that you have installed NoMachine 7.9.2. Thanks!
Hi Zardoc, I’ve just sent you a link to the patched nxclient binary. Please check your inbox and follow the instructions 🙂
To JimmyBlue, you are running Linux and it would be better in a separate topic to not confuse NoMachine macOS users.
You can either open a separate topic or since you have Enterprise Desktop installed, and you are also probably entitled to support as part of your subscription, you can open a support ticket from your customer area. Our team will be happy to help.
Look at https://forums.nomachine.com/topic/unable-to-connect-over-wireguard-tunnel#post-34517.
If you’ve tried with ngrok like in the other topic and it didn’t work, NoMachine Network will be useful to you when it is released (version 9) https://www.nomachine.com/FR07J02731. This will remove the need to know your computer’s IP address in order to connect and will also remove the need for port-forwarding on the router.
Hi, we never received logs back. Can you update to the latest version and tell us if you are encountering the same problem?
You will get screen mirroring, so you see on the monitor the same things you see on the tablet, including the screen form factor (in this case in a square format).
This is more of a commercial/marketing related question that we are unable to answer here. I have passed this on to our build team who will evaluate, together with the marketing team, whether this is something that is commercially viable.
What version of NoMachine have you installed on either side?
It’s not clear whether are you connecting from the Mac to Windows or to the Mac from Windows? (you said Windows is the server and mac is the client, but then you write that you have no mouse control when connecting to the mac 🙂 )
This is happening not because you installed NoMachine but because Rocky Linux’s system security setting (by default) forbid the user to refresh the software repositories and install updates when you’re logged in from remote. What’s needed is the appropriate polkit rule. Check how to add it using the article here:
System requests for authentication to refresh system repositories
https://knowledgebase.nomachine.com/AR03T01156Hi,
port-forwarding is done on the router and you have to follow the instruction according to your router.
Can you check that EnableUPnP in the server.cfg on the Raspberry is uncommented and set to NX (without #)?
EnableUPnP NX
Just so I know that you’ve check the right side, did you check the IP address of the Raspberry by going to the whatismyip website from the Raspberry?
There was another user in a similar position and he used ngrok which avoids the port-forwarding. Take a look here: https://forums.nomachine.com/topic/use-nomachine-together-with-ngrok-for-accessing-remote-access-on-jetson