Forum Replies Created
-
Posts
-
Hi,
Docker containers are intentionally built to isolate the host and container. Therefore, using the NoMachine to forward a device from/to an instance running in a docker container will not be possible.
You could try connecting from your Client NoMachine to your remote Host Nomachine (installed on the host, not inside the container), forwarding a USB device, and then starting the docker container with a USB device passthrough (need to explicitly pass devices through). This might work.
Hi,
I’ve tried forwarding the Android device internally, and it worked as expected. It’s common to have issues with popup windows, and I would recommend connecting Android directly and allowing access to the popups a few times in a row. And then try forwarding with an unlocked main screen. Additionally please send us your session logs when you try to forward the devices? You can find them in .nx directory that is in your home directory on Mac
Hi, could you try restarting both machines and forwarding a simple device like a USB Flash Drive or mouse/keyboard?
Also, have you tried forwarding in a vice-versa direction? Is it working?
Hi,
It is a known issue on NoMachine 8.10.1 for macOS 14 (on Intel processors only) and the fix will be available in the next release.
For now, to fix the issue you could run this command in macOS terminal.
sudo sed -i '' "s/== 12./== 14./g" /Applications/NoMachine.app/Contents/Frameworks/scripts/restricted/nxusb.shHi,
Have you tried forwarding the Smart Card as a USB device? To do that, you could go to Devices -> Connect USB Device, and then select SMC reader for the local devices list and click connect.
That will disconnect the SMC reader from local devices and will connect it to the remote server, as it’s physically connected to it.
Hi,
perhaps the issue is because of the missing /usr/lib/modules/<kernel>/build/include/generated/autoconf.h file. Could you please check if the file is there? If not please do the following steps:
1. Uninstall NoMachine.
2. Uninstall all linux-headers by running this command:
pacman -Rs linux-headers
3. Install linux-headers by running this command:
pacman -S linux-headers
4. Check if the file /usr/lib/modules/<kernel>/build/include/generated/autoconf.h is present.
5. Install NoMachine.
Hi,
The issue is that the driver required for the USB forwarding feature wasn’t installed, as it failed with the 183 code.
The recommendation here would be:
1. Uninstall NoMachine
2. Make sure that none of the software from this list is installed. If any of them is installed, please uninstall it.
3. Restart the machine twice.
4. Install NoMachine and see if drivers are installed without error.
Thank you for the response.
The fact that other devices work indicates that the issue is USB device-specific and more info will be needed to proceed. Few questions:
1. Have you tried directly connecting the tablet to the remote machine? Does it work well in that case?
2. You mentioned “Huion Kamvas 22 plus pen tablet display” and Wacom tablets. None of them work?
3. What is the Wacom tablet model? Is it also with a display?
Hi Robert,
Could you please help me localize the issue? If you forward another USB device, i.e., a flash drive or keyboard, can you use it on the remote machine?
I’m trying to understand if the issue is Wacom device-specific or if the USB forwarding doesn’t work on your devices.
Hi,
NoMachine session, by default, allows a pointing device to be used on both sides at the same time. For that, there is no need to forward a USB device manually. But in that mode, the pressure sensitivity isn’t supported.
If you forward a USB device via NoMachine -> Devices -> Connect a USB device, then your USB device will be “disconnected” from your local machine and “connected” to the remote machine. So it won’t be available on your local machine anymore, but on the remote machine, it should work as it’s physically connected to it. Have you tried this option? Was your device available on the remote machine?
Hi,
When the TR is fixed, inputs will be automatically captured and forwarded to the remote device without a need to forward the keyboard/mouse as a USB device.
The issue with the blue screen doesn’t seem to be caused by NoMachine USB forwarding, hovewer you can send us the Memory dump, and we can investigate it.
The system restart should fix the issue with the device being forwarded but unavailable on the remote machine.
Hi, what’s the ping time between your machine and the remote macOS?
If it’s more than 30ms, that will cause delays between the remote macOS machine and your phone and will result in being the phone connected, but not operational.
Did I get it right that your client machine (the one with Win 22H2) is freezing only when you connect to one specific remote machine with a multiple-display setup?
Assuming that you don’t use USB passthrough on that machine, you can try to use a different display setting and see if that works.
The test I described above could be performed for some short period (i.e., a day) to ensure that it’s not because of USB passthrough. After the test is done, you can enable USB forwarding back.
Hi,
You0re right. As you “forwarded” your mouse and kb to the remote machine (server machine), you won’t be able to use it on your client machine (the one you are connected from).
So to use this workaround, you will need a second set of KB and a mouse.
Hi,
There is a way to check for sure if NoMachine is a reason for this issue or not. For that, you need to unregister the “NoMachine USB Hub Filter”.
Steps to do:
1. Open Windows registry: Menu Start -> run -> regedit
2. Find the following registry key in the tree on the left:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\36fc9e60-c465-11cf-8056-444553540000
3. Find the UPPERFILTERS variable on the right side. Edit UPPERFILTERS variable and remove “nxusbf”.
4. Reboot the Windows machine.
5. Check UPPERFILTERS, to make sure that “nxusbf” is not registered. USB devises forwarding won’t work anymore.
6. Wait to check if the freezing occurs.