Possible connection errors

When you’re trying to connect to a computer with DeviceLock Service, DeviceLock Enterprise Server or DeviceLock Content Security Server you may receive some of these errors:

•(1722) The RPC server is unavailable - You’re trying to connect to a computer that either does not exist (the wrong name or IP address) or is not accessible. Make sure that the computer name you’ve specified is correct. Try to ping this computer by its name and IP address and connect to it using any standard Windows administrative tool (such as Computer Management, Services and so on). Make sure that this computer is working under a DeviceLock-compatible OS.

Also, it is possible that a firewall is blocking access to this computer. You would need to configure your firewall to allow some ports needed for DeviceLock. You could also instruct DeviceLock to use the fixed TCP port, making it easier to configure a firewall. By default, DeviceLock Service, DeviceLock Enterprise Server and DeviceLock Content Security Server are using 9132, 9133 and 9134 ports thereafter. Also, please note that DeviceLock Service automatically adds itself to the exception list of Windows Firewall.

•(1753) There are no more endpoints available from the endpoint mapper - You’re trying to connect to a computer where DeviceLock Service, DeviceLock Enterprise Server or DeviceLock Content Security Server is not accessible. First of all, make sure that DeviceLock Service, DeviceLock Enterprise Server or DeviceLock Content Security Server is installed and started on the remote computer.

It is possible that this computer was just started and Windows is still initializing its services. The Remote Procedure Call (RPC) service may not be running yet.

It is also possible that the firewall is blocking access to DeviceLock Service, DeviceLock Enterprise Server or DeviceLock Content Security Server (see error description 1722 above). For instructions on configuring the firewall to support Remote Procedure Call, see Microsoft’s article at docs.microsoft.com/windows/security/threat-protection/windows-firewall/create-inbound-rules-to-support-rpc.

More on troubleshooting Remote Procedure Call errors see in Microsoft’s article at docs.microsoft.com/windows/client-management/troubleshoot-tcpip-rpc-errors.

•(5) Access is denied - You don’t have enough privileges on the remote computer. Make sure that DeviceLock Management Console is trying to connect to the remote computer under a user with local administrator privileges on that computer.

You may also need to run DeviceLock Management Console under a different user that can authenticate on the remote computer as a local admin.

•(7045) You must have administrative privileges to perform this operation - You don’t have sufficient privileges to access DeviceLock Service, DeviceLock Enterprise Server or DeviceLock Content Security Server because the user is not in the list of DeviceLock Administrators. Make sure that DeviceLock Management Console is trying to connect to the remote computer under the user that is in the list of DeviceLock Administrators on that computer.