Forum / NoMachine for Mac / Entering login keychain password
- This topic has 4 replies, 2 voices, and was last updated 7 years ago by npn.
April 29, 2016 at 08:40 #11092
I have a Mac mini (Late 2014) running OSX 10.11.2, and recently figured out an issue that has been bugging me for a while. When ever I get prompted to enter my login keychain password (for example to allow some app to access a password in my keychain), no matter what I type and then hit enter, or allow, it never seemed to work. I thought that maybe I had some how forgotten the password, but I was actually able to change it and then change it back to the original.
I got the idea to try entering the password directly on the mac, rather than via NoMachine, and it worked! I confirmed this several times to make sure I was not doing something wrong. As a simple experiment, all I have to do is open the keychain app, go to any password in my login keychain, right click on it and select copy “copy password to clipboard”. If I do this directly on the mac, and enter my password it works, but if I do it via NoMachine it does not.
Has anyone else seen this behavior, and or know a workaround?
My connection is using server version 5.0.47 with player 5.1.24 (both from Windows 10 and Ubuntu 14.04 (inside a vm on windows 10)
I will have to figure out how to update the Mac server version.
JohnApril 29, 2016 at 13:27 #11111kroyContributor
Are you trying to connect via NX protocol? Which nxserver product do you have – is it free? Can you paste here what is in the nxerror.log (it’s in “/Library/Application Support/NoMachine/var/log/” directory)?
We couldn’t reproduce the problem on 5.0.47 server. Do you have any special symbols (non latin characters etc.) in username or password?
This also might be of help to you:
Setting up key-based authentication with NX protocol.
(By the way, if possible you should update to the latest NoMachine version.)May 2, 2016 at 08:17 #11125
Yes I am using the NX protocol, and yes it’s the free version, just using it to connect to my Mac from Windows and Linux in another room.
The nxerror.log file is pretty long (seems like it has entries going back to my initial install), attached below is the part from were I installed the updated version of the server, let me know if you think more would be useful.
My password does include an _ and some numbers, but I had tried with a simpler keystore password, and that did not seem to make a difference.
I will try to setup the key based authentication when I get a chance (later this evening or in the morning).
Thanks for looking into this!
Updated to 5.1.24 at: Thu Apr 28 21:26:54 2016
Info: Handler started with pid 7534 on Thu Apr 28 21:28:00 2016.
Info: Handling connection from 172.16.1.104 port 51639 on Thu Apr 28 21:28:00 2016.
Info: Connection from 172.16.1.104 port 51639 closed on Thu Apr 28 21:28:01 2016.
Info: Handler with pid 7534 terminated on Thu Apr 28 21:28:01 2016.
Info: Handler started with pid 7568 on Thu Apr 28 21:29:47 2016.
Info: Handling connection from 172.16.1.118 port 54165 on Thu Apr 28 21:29:47 2016.
Info: Connection from 172.16.1.118 port 54165 closed on Thu Apr 28 21:29:49 2016.
Info: Handler with pid 7568 terminated on Thu Apr 28 21:29:49 2016.
293 4627 21:33:09 601.224 NXSessionIsActive: WARNING! Failed to copy console user name.
293 4627 21:33:09 620.673 NXAppleDesktopOwner: WARNING! Cannot obtain name based on dynamic store.
418 4627 21:33:18 837.614 NXSessionIsActive: WARNING! Failed to copy console user name.
418 4627 21:33:18 838.104 NXAppleDesktopOwner: WARNING! Cannot obtain name based on dynamic store.
263 4627 21:45:28 976.351 NXSessionIsActive: WARNING! Failed to copy console user name.
263 4627 21:45:28 993.234 NXAppleDesktopOwner: WARNING! Cannot obtain name based on dynamic store.
Info: Handler started with pid 811 on Thu Apr 28 21:49:51 2016.
Info: Handling connection from 172.16.1.104 port 51794 on Thu Apr 28 21:49:51 2016.
Info: Connection from 172.16.1.104 port 51794 closed on Thu Apr 28 21:50:01 2016.
Info: Handler with pid 811 terminated on Thu Apr 28 21:50:01 2016.
Info: Handler started with pid 1096 on Thu Apr 28 21:58:21 2016.
Info: Handling connection from 172.16.1.118 port 54189 on Thu Apr 28 21:58:21 2016.
Info: Connection from 172.16.1.118 port 54189 closed on Thu Apr 28 21:58:23 2016.
Info: Handler with pid 1096 terminated on Thu Apr 28 21:58:23 2016.May 2, 2016 at 11:29 #11143kroyContributor
Please upgrade NoMachine on Mac to 5.1.24 and add extra options in the node configuration file (/Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg) to DisplayServerExtraOptions do not confuse with DisplayAgentExtraOptions).
Then uncomment DisplayServerExtraOptions key and change value to “-oldeventapi 0” or just add following line on the bottom node.cfg file.
DisplayServerExtraOptions “-oldeventapi 0”
Let us know if it helps.May 3, 2016 at 08:24 #11151
I had updated the mac server to 5.1.24 the other day and that did not seem to help but adding:
DisplayServerExtraOptions “-oldeventapi 0”
Seems to have worked.
This topic was marked as solved, you can't post.