Sentinel Key Troubleshooting

Troubleshooting Steps

Prior to commencing any of the below steps, please navigate to our sentinel error code guide, located here, as your issue may be related to a specific issue with the key itself.

Scenario One:

On the Framework server, in some cases there may have been an override of the windows firewall rules that are in place to allow broadcasting of the sentinel key across the network. These are the 'sentinel...' rules defined under the inbound rules. This is typically displayed as a sentinel error 601 - no active key available on the network.

In some cases, these may be incorrectly set to the wrong profile (i.e. private instead of domain). Without the domain network profile active, the key will not be shown/available on the client workstations. This may have also been incorrectly disabled, if so, enabling this rule again should allow traffic back to the key machine.

The following is to be done on the server that is hosting the sentinel key. Note: this should only be undertaken by your IT resource.

• Open run and type wf.msc, hit ok or press enter

• On the left hand side, select into 'inbound rules'

• You will need to look for two components of the rule, firstly, what profiles is it set against, and what is the current status of the rule. As aforementioned, a disabled rule will result in an inability for client machines to communicate back to the key.

• If the rules are disabled, then proceed to enable these rules on the applicable profile. Your systems administrator should be able to determine which profile applies to your organisation.

E.g. Domain network, rule enabled only on applicable profile, all rules enabled.