- This topic has 4 replies, 2 voices, and was last updated 2 years, 10 months ago by
.
-
Posts
-
When I try to log onto my MacPro6,1, which is MacOS 10.14.7, and has all available updates for that version of MacOS and has NM version 7.7.4, I enter my credentials to NM, click through the display options, and it shows me the login screen for the Mac, but at that point NM won’t display the mouse pointer, and won’t take any input from my keyboard, preventing me from actually logging in.
My local client is Win10 also running NM version 7.7.4. but my colleague gets the same results when he tries to login from his Macbook, also running NM version 7.7.4.
Server logs attached. I made a connection attempt just before 11AM. Also, I was mistaken about the mouse pointer – I can see it move over the login screen, but I can’t click in anywhere.
Hi.
I can see it move over the login screen, but I can’t click in anywhere.
Do you mean that you can see the cursor moving on the actual MacBook’s display, when looking at it locally?
Can you try to disable and re-enable privacy permissions for ‘NoMachine’ and ‘nxnode’ in Security & Privacy -> Accessibility.
Does the issue persist if you reboot the MacBook?
1. I can move the cursor (aka “mouse pointer”) around the screen, but it’s the pointer from my local machine.
I can’t change the keyboard focus from the username field, to the password field by clicking for example, and typing on the keyboard does nothing.2. I don’t have physical access (at least not yet) to the target MacPRO, so I don’t know any command-line way to disable/enable the privacy permissions, although I agree that could be the problem. When I updated to NM 7.7.4 on the target (server) system, I did a command-line installation so I didn’t get to see any pop-ups about “NM needs access to this or that”, I just got returned a successful installation message:
sh-3.2# NXMOUNTDIR=$(echo
hdiutil mount /Users/ladmin/Desktop/nomachine_7.7.4_1.dmg | tail -1 | awk '{$1=$2=""; print $0}'| xargs -0 echo)
sh-3.2# installer -pkg “${NXMOUNTDIR}/NoMachine.pkg” -target /
installer: Package name is NoMachine
installer: Installing at base path /
installer: The install was successful.
sh-3.2#3. I can and have rebooted the target MacPRO after doing command line updates, etc. If you’re referring to my colleague’s local client MacBook, I will have him reboot that and try again.
From what you say in point 2, it’s very likely a problem with permissions, so I’m afraid you have to access physically that Mac Pro and grant them. Here you can find some further hint: https://knowledgebase.nomachine.com/AR09S01139. In some cases, after a OS update, it might be necessary to remove (uncheck) the permissions and grant again.
This topic was marked as solved, you can't post.