Forum Replies Created
-
Posts
-
Unforunately, whatever image you pasted didn’t upload so we can’t see what settings you can’t toggle. Please use the attachment utility to include any screenshots in your follow-up. (i.e no pasting of images). Thanks.
We’re glad you appreciate the improvements we made to the desktop shared/not shared functionality. Also remember that if the computer is your own and you need to access it remotely, you can still connect even when the desktop is not shared provided that your user is also the owner of the remote desktop. Even if you explicitly disabled it in the server UI.
Hi, please tell us:
1) does the NoMachine Player just close or does it show an error? If so, please attach a screenshot.
2) just so we have a full picture, the version of NoMachine on the server side and the OS on the server side as well.
Logs would also be useful from both sides. Please see the instructions here and send to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!
Thanks for your feedback.
It’s good that guests always need the explicit approval of the desktop owner
And remember that as desktop owner, you can disconnect guests at any time from the system tray selecting ‘Disconnect’ of a specific user or all user. Happy nomachining!
By PIP I suppose you mean “public” IP address? If so, then, it can be that your router doesn’t support UPnP. Or that our UPnP doesn’t support your router :-). Anyway this shouldn’t affect your ability to connect, even from the outside.
Please check my response to a similar post here: https://forums.nomachine.com/topic/are-my-settings-for-connecting-over-the-internet-ok#post-39243
Maybe you didn’t already see our online tutorial which is specifically for users connecting over the Internet.
https://www.nomachine.com/getting-started-with-nomachine#internet
You can also find a variety of other useful tutorials in our support section here:
Can you send us the output of ask of the ‘xrandr’ command on the server whilst reproducing the problem?
Hello,
to be able to connect from outside your LAN, you need to use the public IP address of the computer you want to access. Please check the following articles if you have not already done so:
How to connect over the Internet (enable UPnP to automatically configure port mapping)
https://kb.nomachine.com/AR10T01175How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR04S01122You can also check your External IP, for example, on whatismyip.com.
If this doesn’t help, please send a screenshot of the message you are receiving.
NoMachine 8.2.3 has been released and contains the official fix. Thanks everyone for testing the patch and providing their feedback 🙂
Ah ok so you’ve configured your Windows PC to not use a password for remote connections by changing a system policy key, like explained here: https://superuser.com/questions/106917/remote-desktop-without-a-password.
and outlined here:
How to connect to Windows with NoMachine and an empty password
https://kb.nomachine.com/AR05L00802Thanks for the feedback. Indeed, desktop sharing is one of the features of version 8 that we gave considerable thought. Being able to share your desktop with others on the fly needs to be under your control at all times. The input priority mechanisms in NoMachine that you mention mean that you always have control if someone is connecting to your desktop.
It’s not possible to remote into the computer without system credentials (not without explicitly changing your Windows settings). Please check this follow-up in a similar topic: https://forums.nomachine.com/topic/how-do-i-create-a-user-name-and-password-for-remote-control#post-37002
Hi, logs show that it’s an issue that we have also reproduced in our labs and are currently working on. For the moment, the only workaround available is to disable Wayland and use x.org.
The issue appears to be on the server side. To understand what’s happening, we need to see the logs. Please submit the server logs following the instructions here https://kb.nomachine.com/DT07S00243 and sending them to forum[at]nomachine[dot].com.
Hi, can you send us the NoMachine logs from both sides?
For detailed instructions, check this document: https://kb.nomachine.com/DT07S00243
You can also enable debug level 7 from within the server settings (on the Windows 10) if you are using verison 8. Once you’ve reproduced the error, send everything to forum[at]nomachine[dot]com, making sure to use the title of the topic as the subject of your email. Thanks!
Hi,
do you the latest version installed on both client and server? By “community” I assume you mean NoMachine Free Edition.
What Linux distro is installed on the server? Is it with Wayland? If so, please see the following article which contains suggestions and tips for Wayland desktops running in VMs:
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://kb.nomachine.com/AR04R01083Some further tips are also available here: https://kb.nomachine.com/AR02P00969