Virtual Dongle

From CometWiki

Comet Security Server Virtual Dongle Installation

The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it:

• A signed EULA must be on file with Signature Systems that includes the conditions of using a virtual dongle. You'll find the current End User License Agreement.pdf here: [1]

• You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed.
• The Comet Security Server must have a reliable internet connection. If you use Internet Security Software you'll need to set it up to allow 2-way traffic with dongle.signature.net (to port 80) and signature.net (to port 8080). Be aware that your use of a proxy server may interfere with this communication. Also we have had customers with problems when SonicWall was doing content filtering. It may need to be disabled.
• The Comet Security Server must be running as a service and have administrator privileges.
• A Virtual Dongle may be associated with one and only one computer. Once installed you may not move it to another computer.

If you are replacing an existing USB or parallel dongle:

• Install Server Products vsn 18 or higher on your server and make sure all is well using the existing dongle.
• Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release.
• Stop the Comet Services then remove the old dongle.
• Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.
• Return the old dongle to Signature Systems so that the permanent certificate can be issued.

If you are installing a new system:

• Make sure your internet connection is working on the server where the Comet Services will be installed.
• If you haven't already done so, we recommend you install the Microsoft Redistributables Package. Some of the .NET framework files are used by the Security Server. You can download vcredist_x86.exe here [2]
• Create the Comet Services folder.
• Put the DRB.txt file into that folder.
• Install Server Products vsn 18 or higher on your server. When it asks for dongle type, choose USB. This is because the Security Server will attempt to find a USB dongle first and it needs the drivers to be able to do that. When it asks if you want to restart Windows, say "No". Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.

Notes: The DRB.txt file is a single-use file for installing and registering your virtual dongle. It is unique for each dongle installed. Once the installation has been registered successfully with our server the DRB.txt file expires and cannot be reused. This file is different from the Comet License Certificate file. Virtual dongles use a license file just like USB or parallel port dongles. The license file will be updated each time your subscription is renewed or new products are purchased.