Forum Replies Created
-
Posts
-
I suggest you update to the latest version and then try and reproduce the problem again. If it occurs, open a new topic and submit the information that we requested above.
The correct article to look at is:
How to set up key based authentication with NX protocol
https://www.nomachine.com/AR02L00785@ajburch, check your inbox 🙂
Hi, we are unable to reproduce this issue.
Can you send us the logs from the Linux server host and the Windows client? You will need to follow the instructions here for the two machines.
The NoMachine setup accepts /verysilent or /silent options.
Instructions are available here:
How to install NoMachine on Windows in silent or verysilent mode
https://www.nomachine.com/AR07K00682Once the installation has completed, and make sure you reboot when prompted, you can proceed to disable the printers and other services. This can be done via the NoMachine server UI. For more information about this, please see here:
https://www.nomachine.com/DT10O00155#2.3.If you prefer not to disable it via the UI, you can do it manually. There is a separate document explaining how to proceed with that:
Enabling and disabling the NoMachine device sharing services manually
https://www.nomachine.com/DT10O00151#12Just an FYI, for Catalina users we have an article which might be useful:
How to use NoMachine v. 6.8.2 or later on macOS Catalina
https://www.nomachine.com/AR11Q01061If the user on the other end has Enterprise Desktop installed you will be able to access as a guest user (they will still need to authorize you). This is available as evaluation software if you are interested in trying it out.
https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Desktop
https://www.nomachine.com/download-enterprise#NoMachine-Enterprise-DesktopIf you don’t want to explore that route, NoMachine Network will be useful to you. This is coming soon. More about this feature is available here: https://www.nomachine.com/FR07J02731
@otakuxtom, are you using the patched version we made available? I have sent the email again so you can download it.
Any logs can be sent to forum[at]nomachine[dot]com. Thanks!
To be able to connect to a remote computer using NoMachine, you must have a user account on that computer. If the computer is not yours, the person in charge of that computer must create a system account for you and provide you with the credentials (username and password). Once NoMachine is installed, you use those credentials to access the remote desktop. This might be useful: https://www.nomachine.com/getting-started-with-nomachine
The local user can control what level of control is possible and what notifications they prefer to receive by setting the appropriate security settings. This document indicates the default settings: https://www.nomachine.com/DT10O00154&dn=quick%20guide#3.2.
Glad to hear that the latest update fixes the issue. We’ll close this topic soon. If you need to report any unusual behaviour, please open a new topic (to avoid confusion between versions and issues reported herein) Thanks 🙂
See the FAQ here:
How do I share my desktop with another user if I have the free version installed?
https://www.nomachine.com/AR10K00703There is a little or nothing we can do for your case and NoMachine Network will solve the problem when it comes out – it’s in its final stages.
Your mobile internet modem gets a private IP address (non-routable) which is assigned by your ISP to a public IP. ISP routers don’t permit UPnP operations, NoMachine cannot therefore open a port in the router and detect the public IP.
@ggarcia, can you try uninstalling NoMachine and reinstalling the latest update from scratch?