Forum Replies Created
-
Posts
-
Just a quick update on this. We’ve been unable to reproduce the behaviour reported in this topic despite our continuous efforts. We will continue to investigate and will update the topic with our findings. I am going to close this topic in the meantime.
It doesn’t seem to be an input problem related to NoMachine given that input devices are functional with all other applications during the NoMachine session. There is a possibility that the issue is with rendering. Can you try disabling “Use acceleration for display processing” in the Performance panel of the remote computer’s setting? (I assume the server is Windows).
Regarding the audio problem. We don’t officially support Gentoo, but since we try and test with as many flavours as possible, we also tested with Gentoo. We happen to have a Gentoo server with SDDM-KDE configured and NoMachine installs and works out of the box. Additionally, audio works without extra manual configuration.
bobnx, NoMachine works out-of-the-box with a huge number of stock distros, including Xubuntu. The problem is related to the specific combination of graphics card and drivers as Fra81 said. So there’s not much we can do.
NX always worked previously
We were not able to reproduce this problem, you could go back to using the earlier version of Xubuntu. Or with this comment are you referring to our legacy product NX Free Edition (up to 3.5) maybe? The functionality of that product is available in the NoMachine Workstation product.
We’ve opened a Trouble Report:
https://knowledgebase.nomachine.com/TR04S10222Please follow the link and select “notify me” at the side of the Trouble Report to receive notification of the fix.
Thanks!“It seems NoMachine works very differently than the other remote dektop programs i use.”
Not really no. The only difference is that other programs you might be referring to get you to log in using an account which you’ve created on their server. Then by logging in to their service, you then connect to the remote computer. With NoMachine you need to know the IP address in order to connect. Our upcoming feature, NoMachine Network, will eliminate the need for knowing the IP address. You will create an account on our Network server, and once signed in to the Network service, it will connect you to your remote PC you’ve already added to the Network service. More about NoMachine Network is here: https://knowledgebase.nomachine.com/FR07J02731
“the server program creates a password i have to add to the controller program to access, or just remembers the connection even without a password)”
I think here you mean the code that you have to insert when prompted. You keep mentioning “without a password”. I’ll reiterate what I wrote in previous replies. i) Publishing your computer on any network for unattended access, and not protecting with a password is not recommended. ii) The upcoming Guest Desktop Sharing feature will allow guests to connect without a password, but the computer must be attended so that the incoming connection can be authorized (i.e the person in front of the desktop or the user already connected to the desktop must accept the request to connect from the incoming guest).
NoMachine works out of the box with default settings which fit most of our users’ scenarios. In the majority of cases it’s not necessary to configure additional authentication methods, but for those who are more tech-savvy and want to drill down in the many methods we support, including in the free version, there is plenty of documentation explaining what these methods do:
Integrating NoMachine with Various Authentication Methods
https://knowledgebase.nomachine.com/DT11R00187Using two-factor authentication on Linux with NoMachine
https://knowledgebase.nomachine.com/AR12L00828If you to our knowledge base and search with the keyword authentication, you will find other methods in more detail:
https://knowledgebase.nomachine.com/articles?s=Authentication
Thanks for checking us out anyway!
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/AR05L00802