I've just downloaded the latest version (4.4) and installed on 3 computers specifically to test "force disconnect" feature.
I have 2 clients and 1 server. I've shared the USB device, configured "Allow clients to connect even if occupied...". Rebooted the server (just in case).
Then I connected manually from the client 1. Success. Connected. Then I tried to connect from client 2. Fail. It says that the device is occupied by client 1.
Tried this both from UI and command line. Same (command line reports error 2404) Also tried without "Allow ...". Same thing.
My question is what I'm doing wrong? Where is the "force disconnect"?
Could you please tell what operating systems you have on the client machine and on the server and if it's x32 or x64. Also I need to know what kind of USB device you have.
Please find the new version in the PM, install it and do the following experiment:
Share the device, disable "allow..." feature and connect the device from client#1. Now disconnect it from the client#1 (release it) and connect it using client#2. Check if you can do it. While doing it you need to be sure that nobody works with the device (read/write from it).
Server - Win XP Sp2 Eng x86 Client 1 - Win 2k3 R2 Sp2 Eng x86 Client 2 - Win 2k3 R2 Sp2 Eng x86
(All 3 installed on VMWare 7)
Devices - Aladdin eToken Pro 32K (v 4.2B) Logitech USB Headset Microsoft Intellimouse
Regarding the version you gave me: 1) The scenario you described does not involve any "force disconnect". You asked me to "connect, then disconnect, then connect from another PC" with "allow force disconnect" = off
This scenario does work since v1.0 However, I tried, it also works on 4.5.
2) Now, the most interesting Force disconnect DOES WORK on 4.5!!! of course with "allow force disconnect" = on Connect from client 1, then connect from client 2. Client 1 is being successfully disconnected.
In other words, 4.4 doesn't do "FD" while 4.5 does IN THE SAME CONDITIONS. Does it bring any light on this issue?
Regarding the version you gave me: 1) The scenario you described does not involve any "force disconnect". You asked me to "connect, then disconnect, then connect from another PC" with "allow force disconnect" = off
This scenario does work since v1.0 However, I tried, it also works on 4.5.
This was the plan, thanks for doing the test. We just wanted to be sure that client#2 could connect the device at all.