Forum Replies Created
-
Posts
-
I suggest you to sign up to the Trouble Report using the ‘notify me’ which you can find if you follow the link I pasted earlier.
EDIT: the TR above was solved with the release of version 7.0.208.
NoMachine will connect you to the monitor which is physically available on the server. It cannot connect you to a virtual display running on Windows in the background (only our Linux products support that feature).
The only way I’ve been able to get it to work is to disable authorization for remote connections on the VM’s NM Service which then allows the instructor to connect with the VM using NoMachine.
If you make the instructor a trusted user, he/she will be able to connect without needing desktop authorization. Students connecting with a secondary account(s) can then connect in view-only mode. Please see the guide for more information here:
https://www.nomachine.com/DT02O00125&dn=enterprise%20desktop#10.3
Remember to re-enable the “authorization required” that you have disabled.
What desktop environment is it? It looks similar to this Wayland-related issue found on Arch:
Just to clarify, you are connecting from Android to Windows or are you connecting to the localhost? On reading again what you originally wrote this is not clear.
Anyway, to be able to understand why you are not able to log in to the Windows host because of “wrong password” we need to see the logs from the Windows computer. Please see here for details on what to send us, you can attach the file to an email and send directly to forum[at]nomachine[dot]com. Thank you!
You’ll find the answer to your question in the section “The build number” of the following article 🙂
NoMachine packages naming convention and usage
https://www.nomachine.com/AR11O00949We’ve managed to reproduce it and opened a Trouble Report. Please sign up to receive notification of the fix at the following link:
NoMachine server cannot detect Wayland local display on Arch Linux
https://www.nomachine.com/TR10R09881Because UPnP doesn’t support the double NAT scenario, you would need to enable port-forwarding on both routers. You should contact whoever is in charge of the other router and ask if this is possible.
Thank you for not naming the other product although it would have been removed during the moderation process anyway 🙂
Is it possible to change the port NoMachine uses? The router he uses is the one supplied by his ISP; it’s worked OK so far but when I tried to set up port forwarding it just gives me a list of applications but wouldn’t allow me to manually set port numbers.
First make sure that UPnP is set in server.cfg, see this article to know how to do this:
https://www.nomachine.com/AR11L00827You can change the port 4000 that NoMachine uses, but read this article first to make sure you don’t use a port that’s in use by another component.
https://www.nomachine.com/AR11L00823Is it possible to have NoMachine reject login attempts based on IP address? I have a static IP and so does he, plus it means he can’t ask me to help him when I’m away from my PC. I know how I would do that with SSH, but I don’t know if there is a different way to do that with your software, or if I would restrict it all with some sort of firewall arrangement.
I’m not sure if you are saying that you are not able to connect without approval or if you simply want to allow only connections from a specific device. You can set NoMachine to accept only connections from a specific IP address in the SSL authentication configuration, it’s for advanced users 🙂
How to enable SSL client authentication for connections by NX protocol
https://www.nomachine.com/AR10M00866It can be that your router doesn’t support UPnP. Or that our UPnP doesn’t support your router :-). This shouldn’t affect your ability to connect, even from the outside. Many routers that don’t support the query for the external IP still accept the commands required to enable port forwarding.
Some tips are available here:
How to connect to NoMachine when the server is behind a NAT router or a firewall
https://www.nomachine.com/AR11L00827The alternative is to wait for the upcoming functionality of NoMachine Network:
Airport Extreme doesn’t allow me to put an external IP in the port mapping, it just restricts me to the 10.0.1.x
You don’t need to enter the external IP.
Quoting from the instructions at the link provided, you enter the IP address (the local IP as Kroy specified) that you are forwarding ports to in the Private Address box.
All NoMachine products use the same cipher suite and it’s still ECDHE-RSA-AES128-GCM-SHA256. It cannot be modified.
I reach the user name and password field. ……Which password is being requested? How do I get past this?
To access any computer using NoMachine, you need the usual password and username of the account credentials for that machine (i.e the username of your profile on the Windows computer). Windows policies mean a local system account is limited to use an empty password to console logon only. If you don’t want a password to be requested over a remote desktop connection, you must configure your Windows to open the appropriate policy.
References:
No empty passwords are allowed (see this article for more information about that:
https://www.nomachine.com/AR05L00802)To understand why that is happening, we would need to see logs from that Ubuntu server host.
https://www.nomachine.com/DT10O00162
Please submit them to forum[at]nomachine[dot]com.