Commands are not being executed when they are created.
Summary When creating and sending new key files to client devices, or sending new or changed profiles from the SES console, the commands for these tasks remain stuck in "Active" status for for a long period of time, and normally will only move to Sent and Executed statuses when the client device(s) initiate(s) the communication to the server on their scheduled "check in" basis. Cause This typically happens because UDP network traffic on port 3700 is blocked by a client side firewall rule, and as a result the SES Server is unable to send a UDP packet to the client device(s) to trigger them into an out-of-band call-in to the server. Solution This can be fixed by creating a Firewall rule on the Client Devices that permits UDP traffic on port 3700. The port can be opened by creating a policy on the local client, or by adding this to a Group Policy on the Domain Controller. Please see Article Number 000001071 - 'On what Communications Ports do SecureDoc Clients and the SES Server communicate with each other?' within our knowledge base for more information on ports used by the SecureDoc Enterprise Server. |
Custom Fields
|