#NOMACHINE PASSWORD AUTHENTICATION PRO#

Since it worked with a new user without a Microsoft account, the problem appears to be related to using the Microsoft Outlook user ID. Connection to nx.diamond.ac.uk Open this new connection - use this. Both Computers use the same Outlook account and password as their user ID. Its necessary to set a password for entering by remote. Use password authentication and dont use a proxy Give a name to the new connection, e.g. The problem is that now I will have to set up email and all of my other program accounts all over again. I set up a new administrator account on the laptop and tried to RDP in with the credentials from that account and was able to connect as a different user. I am able to connect in the reverse direction with no problem. I thought I had perhaps forgotten my password, so I carefully reset it and I get the same result. When I try to logon to the laptop with RDC, I get a 'logon failed' error message. At the time of creation of the add-on there wasnt any way to directly specify the username and password when starting NoMachine. Thus, host-specific definitions should be at the beginning of the configuration file, and defaults at the end.

system-wide file Any configuration value is only changed the first time it is set. The laptop is Windows Hello PIN and fingerprint secured. What this means is you can share the contents of an NXS file with multiple RDM users without requiring them to have the same NXS file in the same path as specified in the entry. Configuration data is parsed as follows: 1.

#NOMACHINE PASSWORD AUTHENTICATION PRO#

I have a new Win10 Pro laptop that I want to connect to via RDP from a Win10 Pro Desktop.

Nomachine password authentication