Forum Replies Created
Meanwhile, I made some tests with VirtualHere on my Windows machine, and looks like, I can forward a device from the Windows to Mac (when Mac is a client), and from the Mac to Windows forwarding do not work.
That’s probably because VirtualHere leaves some registered resources after it’s uninstallation. I’m investigating this issue.
Can you confirm that behavior (one direction forwarding) on your side?
1. In the file log/nxusbd.log I see a couple of more lines comparing with your previous log. It’ most probably appeared before you were able to delete that kext. But to be sure, could you please delete this file and try to reproduce it few more times?
2. I assume we have a similar problem on the Windows side.
Could you please check this registry key on Windows:
Do you see there something like DCV_USB_HUB_FILTER ? Or it’s the only nxusbf here?
I have found an issue with your Mac logs. It’s definitely about conflicting software KEXT loaded the same time as NM’s KEXTs are loaded.
To be sure it’s a VirtualHere, I just installed it on our test Mac and were able to reproduce the same behavior and logs at our lab.
Just run this command at your Mac’s terminal
kextstat | grep usb | grep -v “apple”
And if you see here anything but NoMcahine’s KEXTs – that might be a problem.
Even after manual stopping of VirtualHere and machine restart I still had VirtualHere’s driver loaded into the system:
0xffffff7f853f0000 0x4000 0x4000 com.virtualhere.vhusbd (2.3.1) 520E80E7-44CE-3AFF-949D-291C7E817174 <59 6 5 3 1>
So even having it installed, but not running may be a reason for issues (constant and not).
The worst thing is that if you remove VirtualHere from Applications its driver will still remain in the system even after a restart of the machine.
So to completely remove it you need to run the following commands in the terminal with admin rights:
sudo kextunload -b com.virtualhere.vhusbd
sudo /Applications/VirtualHereServer.app/Contents/MacOS/vhusbdosx -b uninstall
sudo /Applications/VirtualHereServer.app/Contents/MacOS/vhusbdosx -u
sudo rm -rf /Applications/VirtualHereServer.app/
sudo rm -rf /Library/Extensions/vhhcd.kext
After restart com.virtualhere.vhusbd were not loaded anymore, and NoMachine forwarding worked again.
1. Can you please check do you have any conflicting software from those list AR04Q01027 installed on any machine?
2. Or maybe any other heave software that consumes huge resources of CPU and/or network?
3. Can you please check the network ping time, is it constantly below 20ms and there are no spikes upper than 200ms?
It will always be after being disconnected for a while, ill come back to it not working anymore.
Have you tried to restart both machines and try again? Does it work?
5. What type of device you are forwarding?
6. If it will appear, you can collect logs and pass them to us. Collect them with an open session (with failed device forwarding). To collect logs from both sides use these articles: AR10K00697 and DT10O00163
Could you please tell us more details:
1. What machine (Win on Mac) is under a private VPN?
2. You connect with SSH or NM protocol?
3. Is the protocol’s corresponding port (22 for SSH and 4000 for NM), or maybe some custom, open in your VPN network?
4. Is that always reproducible (USB forwarding does not work) if you are connected through a VPN?October 12, 2020 at 15:17 in reply to: Cannot redirect USB to AWS Windows Server 2019 USB #29904
Sorry for belated reply.
No, as mentioned it will be released “one after next” release, so it’s not included in the current 6.12.3 version. I will prepare for you a 6.12.3 version with the mentioned patch this week and provide it to you.September 25, 2020 at 14:06 in reply to: Cannot redirect USB to AWS Windows Server 2019 USB #29624
Hi Steve, Mike,
I can confirm that this issue is fixed and will be released one release after the next (current release is 6.11.2). If you need a patched package with the fix, please don’t hesitate to ask and we will provide it before the official release.September 16, 2020 at 16:52 in reply to: Cannot redirect USB to AWS Windows Server 2019 USB #29498
Hi Mike, yes, that’s a reason. So for now we try to make it work even if Universal Serial Bus Controllers drivers are missing.
Have you accepted NoMachine USB drivers (kexts) installation in the security settings of OS?
As well as, do you see both local and remote USB devices in the USB forwarding panel?September 11, 2020 at 12:58 in reply to: Cannot redirect USB to AWS Windows Server 2019 USB #29443
Thanks for the provided info. I can confirm that we reproduced your issues on the same type of VM. Currently, we are focused on it’s fixing. I will share an update on the progress on this topic.September 10, 2020 at 08:25 in reply to: Cannot redirect USB to AWS Windows Server 2019 USB #29415
I was able to reproduce this issue on AWS EC2 machines and can confirm that USB device forwarding does not work on it.
The reason is that in that type of machine Universal Serial Bus Controllers drivers are missing on the Device Manager. Usually, that happens on VM because of USB functionality is disabled in VM’s settings. For now, we are trying to find a solution for that.
Could you please share some info about what type of VM you use on AWS? And as well as attach a screenshot of Devices Manager?
Do you see the local and remote devices on the USB devices forwarding tab?
Can you please attach a screen with that tab?
That means that on your client machine NoMachine USB forwarding module is not correctly installed or it’s disabled.
Can you please send us NM logs as described in AR10K00697
And a screenshot of the Devices Manager, with a list of all devices on the machine.
Do you see on that panel any other USB device? Please pay attention to the article “What to do if USB support is disabled on Linux with NoMachine 6 or later installed”( AR12J00658) and check if nxusb.ko is compiled on your Linux machine?
Screenshot from the devices panel will also be helpful for the investigation.
I wasn’t able to reproduce the same issue on my Debian machine, and most probably it’s caused by some issue with user rights.
Can you please check the few following things?
1. Does this directory exists?
This folder should have the following rights drwxr-xr-x
2. Does it contains “/usr/NX/var/run/nxusb/lock” file?
If the directory exists but there is no “lock” file, please try to create it manually and set the following rights: rw-rw-r–