Kerio Control VPN Client Error: 'TinyDB RPC Client received status packet (error, err: 167)'

Overview

Customers report that the debug logs for the installed Kerio Control VPN Client on Windows show the following errors:

[16/Oct/2019 11:18:14] {vpnRpc} TinyDB RPC Client: Connect called.
[16/Oct/2019 11:18:14] {vpnRpc} TinyDB RPC Client received status packet (connecting, err: 0).
[16/Oct/2019 11:18:14] {vpnRpc} TinyDB RPC Client received status packet (checking certificate, err: 0).
[16/Oct/2019 11:18:14] {vpnRpc} TinyDB RPC Client: GetServerCertificate called.
[16/Oct/2019 11:18:14] {vpnRpc} TinyDB RPC Client: AcceptCertificate called.
[16/Oct/2019 11:18:27] {vpnRpc} TinyDB RPC Client received status packet (error, err: 167).

Additionally, the VPN debug logs on the Kerio Control server-side show the following errors:

[16/Oct/2019 11:18:27] {engine} VpnFSM: GetStatus().
[16/Oct/2019 11:18:27] {engine} Callback StatusChanged called from libVpn(error 167).
[16/Oct/2019 11:18:27] {engine} VpnFSM: Saving and sending status to Engine (error).

This article shares the resolution of this issue. 

Root Cause

Third-Party software installed on the Windows-based computer is blocking UDP (User Datagram Protocol) traffic.

Process

Follow these steps to resolve this issue:

1. Log in to your Windows instance as an administrator.
2. Open the command prompt.
3. Run the following command to reset system's Winsock Catalog: netsh winsock reset
   
   
   
   
4. Restart the computer to complete the reset.
5. Run the Network Monitor Tool to determine any general network issues.
6. Confirm if the customer has any third-party software (for example, an antivirus such as Dr. Web, Kaspersky, Sophos, Avast, etc.) installed that might be blocking the network traffic. If yes, then advise the customer to disable it.
7. (Optional) If the third-party application cannot be disabled due to company/infrastructure policy, advise the customer to configure the Windows Native VPN Client as an alternate.