- This topic has 9 replies, 2 voices, and was last updated 9 months, 1 week ago by
.
-
Posts
-
I am trying to log into my Macbook Pro using NM free version 8.11.3. Upon connection I am presented with MacOS login screen. When I enter my login password, some of the characters are being deleted as if there is someone at the remote machine pressing the backspace key as I am entering the password. I have verified that is not happening as the Macbook in question is in the same room. This happens no matter which version of the client I use (i.e. Windows, Android app, etc). Can anyone explain why this might be happening?
Hi, how strange. Can you tell us the exact version of macOS you’re connecting to? Do you have any applications open or running in the background on the macOS when you try to connect?
I take it this is the latest version of NoMachine on both sides, client and server? Logs from both sides could be useful, taken when you can reproduce the problem. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, yes it is the latest NoMachine version for everything. The MacOS version is Sonoma 14.4. I also discovered another issue when connecting to the host that if the machine is currently unlocked, the screen will flicker between a black screen and flashing. I have sent the logs as requested for both client and server.
Hi, the server-side logs were clean. And the logs from the client-side were actually logs from the server component of the Windows machine you are connecting from.
Are you able to try connecting from a different device? Does the same behaviour occur?
To get logs from the client side of the session, see “Fourth Step: Collect Client Side Logs” of the document I posted last time.
The following instructions have to be done to the user’s device.
Inside the NoMachine session, open the menu panel by ctrl+alt+0 or click on the page peel at the top right corner of the window. Open ‘Connection’ and click on ‘Take the logs’ button on the left and choose where to save logs. A copy of the session directory is created to store logs and named as session name plus date. Compress it to create the log archive to be sent to Support Team.
On Windows the .nx folder is hidden. To find it, write the following in the address bar or the file browser:
%USERPROFILE%\.nx
Or you ca navigate through the computer folder till the user’s home and digit .nx in the navigation toolbar to reach it. Its path can be similar to: C:/Users/nomachine/.nx
Yes, as stated on OP, I have tried multiple machines and devices running Windows 11, Android, iOS, and MacOS to connect to the host in question. The behavior is always the same. I have sent client logs from the Windows 11 machine connecting to the server. Is there a way to show a screen capture? What would be the best way to show this?
A recording would be useful. You can even do it using NoMachine’s built-in screen recorder. You can open it from the !M system try icon on the Mac. It stays on top whilst you record. On the server activate the Accessibility Keyboard by pressing the Cmd + Option + F5 keys to open Accessibility Shortcuts. Enable Accessibility Keyboard from the list, and the keyboard will open. This will help us to see what keys are being pressed when you log in. Go to your Windows computer or whichever client-side OS you want to reproduce the problem and log in. Stop the recording on the macOS. Send us the nxr file which you generated.
So I went ahead and did the screen recording.. but it would appear that MacOS does not whow which keys are being pressed on the logon screen, probably due to security… I will send anyway.
You have us head scratching 😀
Are you using Control+Command+Q to activate lock screen (we see in the first recording, with NoMachine, that the Q button is being held down)?
If you press the Q button, as if you were trying to release it, does that change anything?
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.