I am currently evaluating USB over Network, which is a quite impressing software, easy to install and get working. However, I am facing a problem remoting my RNDIS device. On the server side I have no driver installed for the device, on the client side I installed the drivers. When the device appears on the client side, the related network device is visible in device manager, but no Ethernet interface is created and therefor no IP communication is possible with the remote device. Do you have any ideas, what I am doing wrong?
Thank you for your support
Eberhard Kümmel
IP Logged
Sergey_Jarovski FabulaTech Forum Moderator
FabulaTech Forum God
Gender: Posts: 559
Re: Remoting of RNDIS devices Reply #1 on: Mar 31st, 2021, 8:37am
Thanks for the quick reply. The device works as expected when connected directly at the client side. The network adapter appears in device manage and a configured Ethernet interface is visible (ipconfig command in shell). When device is connected to server side, the network adapter appears but showing an error that Microsoft NDIS driver can not be loaded. Since the Ethernet adapter is also not getting configured, no IP communication of any kind is possible with the RNDIS device located behind the server PC.
Setup NDIS Device (Linux) ---- USB ----- Server PC (WIN10 64) -------- IP Network ------- Client PC (WIN10 64)
Sorry, what do you mean with a console session? The two PCs are normal Windows 10 computers where I have full admin access. No remoting like Citrix or Microsoft RDP is used.
Last Edit: Mar 31st, 2021, 9:28am by ekuemmel
IP Logged
Sergey_Jarovski FabulaTech Forum Moderator
FabulaTech Forum God
Gender: Posts: 559
Re: Remoting of RNDIS devices Reply #3 on: Mar 31st, 2021, 3:35pm
1) Regarding console session. Open Task Manager on your Windows 10 PC, click on Users, right click and add a new column Session, you'll see your session type there.
2) Run the following tests.
Test 1 1) Download our USB Monitor Pro here: http://fabulatech.com/usb-monitor-pro-download.html 2) Install and launch it on the USB over Network (client) PC (File -> Start New Session -> Monitoring of a hot-plugged USB device -> OK) 3) Plug your usb device to the USB over Network (client) PC 4) Minimize USB Monitor Pro and work with your usb device for some time 5) Unplug your usb device 6) Restore USB Monitor Pro and Save the log#1.
Test 2 1) Plug your usb device to the USB over Network (server) PC and share it using USB over Network (server) GUI/CLI 2) Launch USB Monitor Pro on the USB over Network (client) PC (File -> Start New Session -> Monitoring of a hot-plugged USB device -> OK) 3) Connect your usb device on the client side using USB over Network (client) GUI/CLI 4) Minimize USB Monitor Pro and work with your usb device for some time 5) disconnect your usb device via USB over Network (client) GUI 6) Restore USB Monitor Pro and Save the log#2.
Zip these logs, upload to any free file hosting Internet service, send a link to download to me (support@fabulatech.com) thought email message.
The problem has been solved. After getting a small file with eight registry entries from FabulaTech support dedicated for the client side, my RNDIS device could be operated perfectly from remote. Thanks a lot to the fast and competent support.
Thanks for sharing. That registry configuration solved the windows to windows issue. We can reach the RNDIS device from other windows PC and connection is never broken.
On the other hand, we want to achieve this on Linux (server) and Windows (client) condition. So we have tried the server app on our Linux PC and could not manage to run the server process. When we call "sudo /opt/ftusbnet/sbin/ftusbnetd", the returning says "libssl not found". However when we look at the "/usr/lib" directory, we can see the libssl.so.1.0.2 file. Also, we can establish secure connection between other network devices.
How can we overcome this issue?
Thank you.
IP Logged
Sergey_Jarovski FabulaTech Forum Moderator
FabulaTech Forum God
Gender: Posts: 559
Re: Remoting of RNDIS devices Reply #9 on: Aug 9th, 2022, 11:29am
We have managed to work server on Linux. We missed the info on your tutorials about "configuration file copy process". After copying that file under "/etc" directory, server daemon started and we linked the two PC.
Home
Search
Members
Login
Register
Reply
Notify of replies
Print
Author
Quote
Modify
IP Logged
Posts: 559
