Forum Replies Created
-
Posts
-
So. you don’t want to force the log out – could it be that there are two users connecting to the same computer with the same username? If user A connects with the same account name as user B, and user B is already logged in, user B will be logged out by user A. I’m just guessing this is what is happening since you’ve not actually made this clear. To avoid one user being logged out by the other, the two users must each have their own account on the Windows host. They will both then be able to connect via NoMachine and will see the same physical desktop. Passwords must be set in the Windows accounts for you to get access.
Remember that when the desktop owner is different from the connecting user, he/she is always required to authorize the incoming request for connection.
In version 8, a new feature called Guest Desktop Sharing will be implemented which will eliminate the need for creating a second account for another user who wishes to connect whilst you are on the desktop. A guest connecting will still require the approval of the desktop owner, which must authorize the client (based on its IP) to connect. This new feature is not suitable for unattended desktops.
More about this is in the Feature Request here: https://knowledgebase.nomachine.com/FR01S04059
As we said, connecting to the remote desktop without a password in Windows is not possible for security reasons (in Windows OS).
Regarding the “force log out from the server”, you can achieve this by using the custom scripts functionality which is a feature of Enterprise Desktop. Please consult the guide:
12.3. Forcing a System Logout Upon Session Disconnection
https://knowledgebase.nomachine.com/DT10R00171I also suggest you take a look at 12. Connections to the Remote Desktop and Collaborative Sessions in general which explains the default behaviour of NoMachine when connecting to the physical desktop.
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?