02.04.2013 Views

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Problems and Solutions<br />

Contents Glossary Index Troubleshooting<br />

Problem: Accessing <strong>Sentinel</strong> <strong>Hardware</strong> Key on a different<br />

network subnet<br />

You want to access a <strong>Sentinel</strong> <strong>Hardware</strong> Key on a different network subnet.<br />

Solution:<br />

Create a configuration file and place it in the same directory as the executable<br />

file. In the configuration file, under the ContactServer section, enter the<br />

IP Address of the server computer.<br />

Note: There is a sample configuration file at the location, \Configuration<br />

File Template.<br />

Problem: Ethernet Port for <strong>Sentinel</strong> <strong>Keys</strong> Server<br />

You want to know which Ethernet Port is used for <strong>Sentinel</strong> <strong>Keys</strong> Server.<br />

Solution:<br />

UDP port 7001. In case UDP port 7001 is blocked, open the port in the<br />

advanced option of the IP firewall.<br />

Note: This applies to networked implementation of security only.<br />

Problem: Monitoring <strong>Sentinel</strong> <strong>Hardware</strong> <strong>Keys</strong> licenses<br />

in Use<br />

You want to monitor <strong>Sentinel</strong> <strong>Hardware</strong> <strong>Keys</strong> licenses that are in use on the<br />

key server.<br />

Solution:<br />

You can do the same by connecting to http://localhost:7002, or http://<br />

IP_Address:7002<br />

<strong>Sentinel</strong> <strong>Hardware</strong> <strong>Keys</strong> Developer’s <strong>Guide</strong> 247

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!