Forum Replies Created
-
Posts
-
Hi,
Can you please connect to macOS VM, go to USB devices forwarding tab, wait until local and remote devices will be loaded and after run the following command in the cmd and send its output.
sudo kextstat | grep nx
Could you please clarify, what kind of Hotplug you trying to use?
In general, if a device is listed in NoMachine’s USB devices forwarding tab it should be possible to forward it.
Hi,
Could you please check if you have enabled extensions loading on your macOS machine?
https://knowledgebase.nomachine.com/AR01P00962
Also, could you please send logs from Raspbery PI? And check if nxusb.ko is well compiled on it?
Based on your logs, I don’t see any issues with the USB forwarding module on the Windows machine.
To be 100% sure, could you please
1) send us a screen from Devices Manager
2) send a value of
“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}”
registry key. To find it out, open Windows registry: Menu start -> run -> regedit; find the mentioned registry key in the tree on the left; find UPPERFILTERS variable on the right side and send it’s value.
Also if all your VM’s are on the same VM host, I would suggest checking if their USB drivers are enabled and supported by VM by itself. The same type of logs from VM Windows machine could be helpful.
Such behavior could have a place if any of the conflicting software is installed on the Windows machine How to handle possible conflicts between NoMachine USB module and third party drivers
Hi,
Once you are connected to the remote macOS do you see there both local and remote USB devices?
Also, did you have checked this article about allowing NoMachine’s USB devices forwarding drivers to be loaded on macOS? https://knowledgebase.nomachine.com/AR01P00962
Hi,
Indeed, USB drivers seem not to be loaded.
To see them in the General tab first is required to trigger their loading. For. that you can do two things:
1. Open the General tab (as on the screenshot) and after connect via NoMachine to that machine and go to USB devices forwarding panel.
or
2. Run the following line in the terminal.
sudo kextload /Library/Application\ Support/NoMachine/Extensions/nxusbvhci_11.0.kext/
also please paste the output from that command to this topic.
Hi,
Can you please run this command to load the driver?
sudo kextload /Library/Application\ Support/NoMachine/Extensions/nxusbvhci_11.0.kext/
If there are no errors after launching the command, please run this one and check if the driver is loaded
sudo kextstat | grep nx
Hi, you have to open just one port 4000 (if a connection is via NX protocol). Opening 5041 port is not required.
Have you tried to forward a simple USB device like USB flash drive or mouse to the same instance? Is it forwarded well?
Hi,
After plenty of tests, I can confirm that in the case of iPhone forwarding from Windows to macOS 11.4, the forwarded device shows up in the NoMachine with a green dot, but it does not show up on the remote macOS.
Just only difference in our case and in your tests is that if after the restart, forward a simple USB device (mouse, USB disk) it is forwarded and shows up on the remote macOS. Worth noticing, if forward USB disk after iPhone forwarding, USB disk will also appear with a green dot, but will not appear on the remote macOS.
The Trouble Report https://knowledgebase.nomachine.com/TR07S10310 for the issue with iPhone forwarding has been created. Please use that link to monitor its status.
Would it be possible to share, what service was used as a host for virtual macOS?
Hi, can you please check, if when connecting from a MacOS to a Windows machine, does your screen looks like in the attached file (Local USB devices are not visible)? If you connect from Windows to Mac., will you see remote Mac’s USB devices in the USB devices window (look at the screenshot).
Attachments:
Hi,
Thank you for providing so detailed feedback and logs.
We made some internal tests based on your logs report and will come back to you on Monday.
Hi,
That means that no device has been forwarded to the target machine. Most probably it’s caused by not loaded kext drivers that are required to forward USB devices.
Please run this command when you have forwarded the device and see a green dot and send the output.
sudo kextstat | grep nx
