Forum Replies Created
-
AuthorPosts
-
klapas1ParticipantHi.
On which exact machine are the devices listed, and on which are they not? Or do both machines fail to list the devices?
Are the devices showing up on the list, but simply cannot be forwarded?
How does the reverse connection behave (when connecting from Mac to Windows)?
Did this work on any previous version? If so, since which version did it stop working?
Did this happen after an update? If so, after which specific update?Have you tried completely reinstalling NoMachine on the machine where forwarding isn’t working? Have you tried forwarding to a different machine?
Please send us the session logs from the player.
Regarding your comment:
“Audio and Mic work (although I have to re-enable/unmute it each connection… is
there another option for this to default enabled?)”We are aware of this issue and are currently working on a fix.
klapas1ParticipantHi,
Thank you for the update. Given that the nx user exists both locally and in the domain, the best course of action is to uninstall NoMachine from the domain controller.
1. Uninstall NoMachine from the domain controller.
2. Verify that the nx user account has been removed from the domain using commands that I sent you before.
3. Install NoMachine locally on your target servers instead.This ensures that the application is running on the appropriate machines without impacting your domain services.
Regards,
Klaudiusz
klapas1ParticipantHi,
Is it possible that NoMachine was installed on a domain controller?
If so, you can check whether the user nx exists using the following commands:net user "nx" /domain – checks if the user exists in the domain
net user "nx" – checks if the user exists locally or in the domainIf the nx user is part of the domain, please install NoMachine locally on the target servers instead of the domain controller.
Additionally, please refer to the article regarding known issues with NoMachine in Active Directory domain environments.
https://kb.nomachine.com/AR04O00925Regards,
Klaudiusz
klapas1ParticipantHi.
A fix for this issue will be included in the next released version. In the meantime, please try the workaround described below.
Regards,
Klaudiusz
-
AuthorPosts
