Forum Replies Created
-
Posts
-
To ehammer99, enable debug for the affected NoMachine server host, reboot the computer, restart the server if it’s still disabled, reproduce the error, collect the logs:
https://www.nomachine.com/DT11R00182#2
To maykro, inspect events in Operational log under Applications and Services Logs\Microsoft\Windows\CodeIntegrity and look for potential issues with lsass process. Export the event and send to us for further analysis.
Hi, so to connect to your remote Windows 7 computer you need to use the account credentials of that computer – by account credentials I mean username and password that you normally use when switching on the computer.
As the article states you need a password, the “password cannot be empty.” Logging in remotely without having set a password is forbidden by Windows’ own policies. The reason for this is explained here:
https://forums.nomachine.com/topic/access-windows-pc-that-doesnt-have-password
How to connect to Windows with NoMachine 4 or later and an empty password
https://www.nomachine.com/AR05L00802We were able to reproduce the issue, so thanks for reporting.
Edit: the Trouble Report for this bug is here: https://knowledgebase.nomachine.com/TR03S10143. You can sign up to receive notification of the fix using the link above.
Hi,
did you enable port-forwarding on the router to which Computer 2 is attached? See here:
How to connect over the internet to NoMachine behind a NAT router
https://www.nomachine.com/AR10R01099You could try the tips suggested here:
https://forums.nomachine.com/topic/errors-trying-to-install-ubuntu-1804-using-wget#post-29994
and here:
https://forums.nomachine.com/topic/my-successful-story-in-setting-up-nvidia-driver-on-aws#post-27729
Hi Gatos,
very strange…..can you send us the player side logs (follow the instructions here: https://www.nomachine.com/DT11R00181#2) and then send them to forum[at]nomachine[dot]com.
After you’ve done that, could you then try disabling UDP? Do you still encounter the same the same behaviour?
Can you tell us what distribution and version you have installed on the NoMachine server? What’s the desktop environmen? What version of NoMachine? What product have you installed – the free version, Workstation? What’s the client OS and version?
Setting the automatic disconnection of the NoMachine user after a certain time of inactivity would mitigate the problem of users forgetting to log off and leaving the session open.
To enable this feature, edit /usr/NX/etc/node.cfg and set an appropriate value (in seconds) for this key:
DisplayAgentExtraOptions “-timeout s”
For example, to disconnect the user after 10 minutes of inactivity, set:
DisplayAgentExtraOptions “-timeout 600”
Hi, we have a Trouble Report currently open for Wayland:
Grabbing the keyboard doesn’t work when Wayland is enabled
https://www.nomachine.com/TR10P08952Can you check that Wayland is disabled/enabled?
echo $XDG_SESSION_TYPEuncomment or set:
WaylandEnable=falsein the:/etc/gdm3/custom.confand reboot. Does this help?
Hi, a new article has been inserted. Thank you for pointing out that the current article needed updating.
For version 6.10 onwards, you should use this: https://www.nomachine.com/AR03S01112. Let us know if you’re still having issues.