Forum Replies Created
-
Posts
-
It could be this known issue
Black screen occurs when rebooting macOS 11 (Big Sur) or when making logout
https://knowledgebase.nomachine.com/TR08S10335I would try the workaround provided. If that doesn’t help, you should contact the support team via your customer area if you have a valid subscription.
Hmm, we’re not able to reproduce so far. Try disabling ‘Use acceleration for displaying’ in Server settings -> Performance (on the computer you want to connect to). Does it make any difference?
If not, would you be available to try debug version and then submit logs to us? We’ll send you instructions.
Hi, I’m assuming you’ve installed the latest version both sides and that you are connecting to a free NoMachine installation, or have you installed one of our other products there? What’s the desktop environment installed there?
If you tell us the theme you’re using, we’ll try and reproduce the cursor-to-caret issue again. As for point 2, we have not been able to reproduce, but we’ll try again. Point 3, we have two upcoming features which might be what you are looking for:
Guest Desktop Sharing – https://knowledgebase.nomachine.com/FR01S04059
NoMachine Network – https://knowledgebase.nomachine.com/FR09S04214I immediately bump into the username and password issue
With this do you mean that your users don’t want to use their system username and password? To connect using NoMachine you need a valid system account on the remote computer you want to access. The user names can be a local account or a LDAP account or an AD account. I suggest you take a look at the Enterprise Desktop and check the guide, section 10:
https://knowledgebase.nomachine.com/DT10R00171#10
You can also find further info about usernames here:
Point 1) Are you using the default Windows theme for the cursors? You can check this in Settings -> Personalization -> Themes ? Do you have the same problem with the cursor when you attach a monitor to the server (not sure if you can check that or not).
Point 2) This has been reported by many Windows users and it’s not dependant on NoMachine in that case.
I’d check to see if there any updates for your Windows OS.
Regarding point 3, I understand you want to use a password to log in to the desktop when connecting via NoMachine. It’s not possible to log in with NoMachine without a password unless you have configured your Windows to open the appropriate policy. (see here: https://knowledgebase.nomachine.com/AR05L00802). Editing the NoMachine setting in this case won’t bypass the policy that has already been configured on the remote Windows host, so please check what has been set with regards to this policy.
I also suggest you take a look at this article with regards to username formats which are supported:
Username formats supported to log-in to NoMachine by password authentication
https://knowledgebase.nomachine.com/AR03S01118Have you enabled ‘Grab the keyboard input’ in the Player?
If you are referring to this problem in 2019 which has since been fixed https://forums.nomachine.com/topic/apple-key-combinations-like-cmdspace-i-e-spotlight-do-not-work, you should make sure you are using the latest version of NoMachine on both client and server sides.
If you are using the latest version of NoMachine, provide the steps to reproduce the problem, clarifying what macOS versions you are using.
Thanks for this detailed information. The patch helps with the display sleep issue but not with when the computer actually goes into stand-by. We’ll continue with our investigation.
Sounds like this Trouble Report here. It seems to be affecting Big Sur only.
That FR has not been implemented yet.
Feature Requests that are released in a software update have the label “implemented” label and the version it was released in.
Hi, can you show me exactly where NoMachine is showing the wrong hostname? Attach the screenshots to your reply.