Hi! I have an Safenet Sentinel HASP key for one of my two main work programs and a Rainbow Ultra Pro for the other. Sorry, I can't say which programs, my boss would probably kill me if he knew I was messing around with this... Anyway I'm getting tired of dragging the dongles around (I keep forgetting them in town when I'm going to the country house and vice versa), so I wanted to put them both into my home server and use VPN to access them. I downloaded the trial version, and the problem is that I can't get the Safenet thing to work.
The full name in the USB Over Network system is "HASP HL 3.25 - AKS", and the full name in Windows is three parts: "SafeNet Inc. HASP Key", SafeNet Inc. Sentinel HASP Key" and SafeNet Inc. USB Key". All three show up in windows when the key is connected over the network, but still the work program can't see it. I tried in a a roundabout way, by connecting them to a VMWare VM on the workstation, and then using the USB To Network to get the data back to the physical workstation, and that worked. But connecting it to another computer, physical or not, isn't working at all. Any idea what this can be?
And what if you try installing both Server and Client onto the same machine, share the device with Server and connect with Client, then try to use the dongle? Will the software see the key in this case?
Yeah, using 127.0.0.1 it works. When the client's connected I can use the program I need to, and when I disconnect the dongle from client, it refuses to start. So there is obviously a connection.
You can check LAN connection as well and if it works then the only reason it doesn't work over VPN is speed. It seems the SafeNet key requires quick responses and VPN cannot provide enough speed for this.
1) If you install Server and Client onto the same machine it works ok 2) If you share the device to/from the VM from/to the local machine it works ok 3) It does not work over LAN
What OSes do you use on your local machine, VM and another machines from the LAN? Have you tried connection over the LAN using the same OSes with 1) or 2)?
Your three points are correct. The client is a Windows 7, or a virtual Windows XP. As server I have tried both a physical Server 2003, a virtual XP on that server and another physical Windows 7 computer.
Well, I waited until I came to the cabin/country house, installed the trial on my home server and I am now using the Rainbow Ultra Pro dongle (the one that worked on the home LAN as well) through VPN from my country house to my home. If only I could get that other HASPL key to work, I'd buy the program. But half way there unfortuantely doesn't help me all that much.
To answer your one and a half month old question: Yes. I have tried everything, and it seems like any configuration where the USB dongle isn't physically connected to the computer I want to use it on (no matter if it's connected to a VM or the actual computer, and no matter if I'm using the USB over Network from the physical computer to the VM or vice versa) I just cant get it to work. Have you had other dongles that has behaved like that before?
Unfortunately not. When the dongle isn't connected physically to the computer it goes over to the secondary (old) method of licencing, which is hard drive ID (the deepest one that doesn't change with reformats and stuff). Seems like the program is in some way able to sense if the dongle is physically connected or not.
Please contact our support dept at support@fabulatech.com And include: - a brief instruction of the problem - some screenshots from server and client side. - The system information of both PC's where USB over Network (Server and Client) is installed. To get system information file you need to do the following: Start -> Programs -> Accessories -> System Tools -> System Information File -> Save. - The USB over Network log files. Please look for the logs in %systemroot%\system32 folder (or if your PC is x64 then in %systemroot%\syswow64). The log file names should be: ftusbsrv.log - for USB over Network Server ftusbsrvc.log - for USB over Network Client
Our support manager will contact you to proceed with resolving this issue,