NoMachine works out of the box with default settings which fit most of our users’ scenarios.Setting up a Linux desktop hosted on Azure Getting started with your Azure instance 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). i) Publishing your computer on any network for unattended access, and not protecting with a password is not recommended. I’ll reiterate what I wrote in previous replies. You keep mentioning “without a password”. I think here you mean the code that you have to insert when prompted. “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)” 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. Our upcoming feature, NoMachine Network, will eliminate the need for knowing the IP address. With NoMachine you need to know the IP address in order to connect. Then by logging in to their service, you then connect to the remote computer. 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. “It seems NoMachine works very differently than the other remote dektop programs i use.” More about this is in the Feature Request here: This new feature is not suitable for unattended desktops. A guest connecting will still require the approval of the desktop owner, which must authorize the client (based on its IP) to connect. 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. Remember that when the desktop owner is different from the connecting user, he/she is always required to authorize the incoming request for connection. Passwords must be set in the Windows accounts for you to get access. They will both then be able to connect via NoMachine and will see the same physical desktop. To avoid one user being logged out by the other, the two users must each have their own account on the Windows host. I’m just guessing this is what is happening since you’ve not actually made this clear. 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.
0 kommentar(er)
