Dears, I would like to add some more information regarding this problem. I am one of the person that use these 10 VM together with UoN, with the problems that kyriakoylis has describe before.
Tonight we have also an other incident but not during the period that servers stay "inactive" but "active". What we have notice ? In pc with UoN (Server) the FabulaTech service it was stoped. We try to start again but the service can not start, and for that reason we restart the pc. After the restarting everything is normal again. Event viewer dos not help us a lot as no message from fabula service appear. The next time i will also send the event viewer files. Thank you for your help, Best Regards to everyone Kyriakos
We have do as told the following actions * Uninstalled the client version 4.3 from the 10 clients (virtual machines) * Installation of the new client version 4.4 (link you sent by mail) * Use a completely new hardware as server with 12 native usb ports (no hubs) * OS on the server is Windows XP Sp3 Professional * Installed the 4.4 Server edition * Connect and share one by one all 10 dongle keys (8 of them same) on Uon server * Share them * Connect each one on each virtual machine
All this infrastructure worked about 20 hours and then the virtual machines stopped responing (dongles disconnected!!) The server 4.4 list of shares was all RED and this situation recovered ONLY with a restart.
As you can see the solution is not stable!
What we can do about this? We cant have issues like this on our production and a solution must be given.
Is there any logs we can upload to you for investigation?
Hello, we have also this problem with two HASP Dongles. Now, we instaled the newest Windows UoN server version 4.5.3, but it is still the same! We can't share just one Dongle. Either both are shared or nothing. We need to share just one Dongle. Do you have a solution without Linux yet?
Dear Ypser Unfortunately dongle devices have no serial numbers. It means that these devices can not be uniquely identified in the system. Windows system identifies all of them by Vendor ID and Product ID (USB\VID_04B9&PID_0300 - which is the same for each device) thats why any action you are applying to the one device is applied to every other device with the same VID&PID(sharig, giving nicknames, enablingh auto-sharing etc.)
As for the devices that have serial number - you can give them nicknames or share separately.
As a workaround of this Windows system limitation we are going to add a special port sharing technology in the version 4.6 of USB over Network. This technology will resolve the issue you have.
Home
Search
Members
Login
Register
Reply
Notify of replies
Print
Author
Quote
Modify
IP Logged
Posts: 136