Signature check at the Sophos IPsec Client fails

  • Article ID: 115823
  • Updated: 14 Feb 2014

Issue

The signature check at the Sophos IPsec Client fails.

Known to apply to the following Sophos product(s) and version(s)


Sophos IPSec Client 9.2

Operating systems
Sophos IPsec Client V10

Cause

The problem is caused by importing new configfile/certificate into the Sophos Ipsec Client.

What To Do

  • If you see a Log-Output like this example:
2007:03:06-09:46:46 (none) pluto[3578]: "D_REF_NJLHlwWdMn_1"[5] 192.168.4.80 #44: Signature check (on swurth1@sophos.com) failed (wrong key?); tried *AwEAAedwQ
2007:03:06-09:46:46 (none) pluto[3578]: "D_REF_NJLHlwWdMn_1"[5] 192.168.4.80 #44: sending encrypted notification INVALID_KEY_INFORMATION to 192.168.4.80:500 
    • Restart both Windows NCP-Services, or the entire PC

  • If the certificate and config do not match
    • download and import a fresh profile/certificate into the Sophos Ipsec Client, from the UserPortal

 
If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent

Comments