Is there a way on the client side of USB over Network to fix the servid and devid when adding a usb device to the client?
The problem is I have to script the connect/disconnect to a usb device. This script has to migrate between computers and these scripts run automatically by some servers on these comptures. Having the device with the same servid and devid on all the clients would make things so much simpler.
Unfortunately USB over Network does not solve this issue. One of the possible solutions to it is to write a script for parsing output of USBCLNCmd.exe and select necessary servid and devid.
Unfortunately USB over Network does not solve this issue. One of the possible solutions to it is to write a script for parsing output of USBCLNCmd.exe and select necessary servid and devid.
I am not sure if this is the right place for feature request, but here goes...
Having one (or both) of the following would be a great addition to you otherwise excellent product: 1) Have the option to set the servid/devid on the client side. 2) Have the option to name the device on the server side and give the client the possibility to connect to the named device (independently of servid/devid).
Thanks for your feedback, your interest in our software is greatly appreciated.
Can you describe how you see the project in details? Our developer team is quite interested to know how to implement your offer.
Ideas for the first option (client side ); a. With GUI: Add devices normally and then i. Right click on the server -> Properties and from there assign the serverid. ii. Right click on the device -> Properties and from there assign the devid deviId and servId only need to unique within the scope of the client so id conflicts should be easy to manage. b. With command line: i. usbclncmd assigservid <host> [:<port>] <newservid> ii. usbclncmd add <newservid> <devid on server> <client side devid> iii. usbclncmd connect <newservid> <newdevid>
Ideas for the second option (server side ); a. With GUI: i. On the server, Right click on the device->Properties and from there give the device a name/alias. ii. On linux server, create an entry in the /etc/ftusbnet.conf that maps the hwid and port to a name/alias, e.g. [USB Disk] hwid=1234:5678:9abc share=true takeaway=true name=MyPublickUSBDisk iii. On the client command line A. usbclncmd add <servid> <devicenameonserver> <localalias> B. usbclncmd connect localalias or C. usbclncmd connect <servid> <devicenameonserver> iv. On the client GUI, connect normally. a. With command line, i. On the server, usbcmd assign <devid> <name> ii. On the client, usbclncmd connect <name>
These are just some quick thoughts, but basically since the servid/devid are scoped within the client it should be no big deal to be allowed to change the servid/devid on the client as long as servid/devid are unique for given client.
The second option basically does the same, but since it can not control the servid/devid on the client we have to go through name/alias concept. But here the server would push the alias to the clients which can decide to use that name or just to use the locally assigned servid/devid pair.
I hope that this is understandable since formatting is a little tricky in this forum system.
Thank you for your time, detailed and clear description. We appreciate it.
We have looked into your offer and here is our alternative proposal. What if the functionality of connect command is extended: usbclncmd connect <server_hostname> <device_unique_identifier>
where - hostname is string of IP or hostname of the server, exactly as you added (e.g. 10.0.0.100 or usbserver1.mycompany.com) - device_unique_identifier is a) VID: PID:REVISION:SERIAL (for USB devices with serial numbers) b) VID: PID:REVISION:USB_PORT (for USB devices with no serial number)
You will be able to obtain "device_unique_identifier" on Server side in device properties, or in command line (using additional option when enumerating USB devices for specified server).
Thank you for your time, detailed and clear description. We appreciate it.
We have looked into your offer and here is our alternative proposal. What if the functionality of connect command is extended: usbclncmd connect <server_hostname> <device_unique_identifier>
where - hostname is string of IP or hostname of the server, exactly as you added (e.g. 10.0.0.100 or usbserver1.mycompany.com) - device_unique_identifier is a) VID: PID:REVISION:SERIAL (for USB devices with serial numbers) b) VID: PID:REVISION:USB_PORT (for USB devices with no serial number)
You will be able to obtain "device_unique_identifier" on Server side in device properties, or in command line (using additional option when enumerating USB devices for specified server).
Let us know what you think.
Looks good. Would suit me even better than my own proposal
Home
Search
Members
Login
Register
Reply
Notify of replies
Print
Author
Quote
Modify
IP Logged
Posts: 182