Forum Replies Created
-
Posts
-
So its been 4 days since my last post, and I have not been able to get USB forwarding to work even once since then. I don’t know what fluke took place to let it work that one time, but I haven’t been able to use it since.
I should also add for clarity. That I did have it working yesterday, once, for several hours. I don’t know how or why, or what happened to allow it to work, but it did. But when I needed to disconnect briefly, and reconnect it has not worked again since, not even after a reboot of macOS.
ok. I have attached a new log folder with a fresh copy of nxusbd.log I tried to connect a USB device several times before zipping the log files. I also rebooted before trying.
The Windows registry key has 2 entries;
UsbDk
nxusbfI can also confirm, and the logs will likely confirm, that I CAN forward a remote device to my Mac, but I cannot forward a device from the Mac to Windows. So yes, I am seeing the same one direction forwarding. For added info, the device I forwarded from the Windows machine (host) to the Macbook (client) was an “Elecom Trackball”.
Ok, I finally got the kext to stop loading on boot. However the USB passthrough is still not working.
I have attached a new set of logs, as well as the terminal output of;
kextstat | grep usb | grep -v “apple”
No matter what I do I cannot get com.virtualhere.vhusbd (2.3.1) to stop loading. I even went as far as to go into the extension folders manually in finder and deleted vhusb.kext and on reboot it still loads.
Is there any update on this situation? Im not sure what to do from here. The USB passthrough is the main reason I use nomachine.
For the last couple of days I’ve been having to carry around an old android tablet running virtualhere with an OTG cable in order to get anything done.
1. Can you please check do you have any conflicting software from those list AR04Q01027 installed on any machine?
I do have Virtualhere installed on both machines, but it is not running at the same time. I have had virtualhere installed along side NoMachine for years and never had a problem. I also recently tried uninstalling Virtualhere and it made no difference.
2. Or maybe any other heave software that consumes huge resources of CPU and/or network?
CPU: on the client side no, on the host side I am running Solidworks, but cpu useage is still not very high, and Solidworks isnt open when I am trying to connect.
NET: Nothing running that would consume much at all.
3. Can you please check the network ping time, is it constantly below 20ms and there are no spikes upper than 200ms?
Ping times between the 2 locations was consistently under 20ms, average was 17, with a single spike up to 22.
4. Have you tried to restart both machines and try again? Does it work?
Trouble shooting step number 1, turn it off and back on again. Yes I have tried rebooting both machines.
5. What type of device you are forwarding?
It is a 3D Connexion Space Mouse Wireless.
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
I believe I captured the logs correctly. I have attached them, in 2 separate ZIP files.
Ok, I stand corrected. It doesn’t seem to be a VPN issue, that just seemed to have been a coincidence.
I managed to get it to work yesterday through the VPN for hours, and now im on the local network and cant get it to connect.
Is there perhaps a log somewhere so I can see if there are any error messages or something?
1. What machine (Win on Mac) is under a private VPN?
The Windows 10 Machine is behind the VPN, and the MacBook Pro is the Client PC.
2. You connect with SSH or NM protocol?
The connection is using NX on the default port 4000.
3. Is the protocol’s corresponding port (22 for SSH and 4000 for NM), or maybe some custom, open in your VPN network?
Port 4000 is open through the VPN.
4. Is that always reproducible (USB forwarding does not work) if you are connected through a VPN?
It appears to be yes. the last 2 times I was on the VPN it did not work, yet now that I’m home (no VPN) its working just fine.