Is it possible to connect a Windows 7 or higher device to the UTM's IPsec VPN via the built-in Windows client? I've successfully managed to get this to work with L2TP but not IPsec on its own. I've setup a X.509 based IPsec VPN.
The Sophos VPN client will connect fine, however when connecting via a windows built-in client I get:
2016:08:09-17:18:21 office-2 pluto[8029]: packet from 172.16.3.30:500: received Vendor ID payload [MS NT5 ISAKMPOAKLEY 00000008]
2016:08:09-17:18:21 office-2 pluto[8029]: packet from 172.16.3.30:500: received Vendor ID payload [RFC 3947]
2016:08:09-17:18:21 office-2 pluto[8029]: packet from 172.16.3.30:500: ignoring Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n]
2016:08:09-17:18:21 office-2 pluto[8029]: packet from 172.16.3.30:500: ignoring Vendor ID payload [FRAGMENTATION]
2016:08:09-17:18:21 office-2 pluto[8029]: packet from 172.16.3.30:500: ignoring Vendor ID payload [MS-Negotiation Discovery Capable]
2016:08:09-17:18:21 office-2 pluto[8029]: packet from 172.16.3.30:500: ignoring Vendor ID payload [Vid-Initial-Contact]
2016:08:09-17:18:21 office-2 pluto[8029]: packet from 172.16.3.30:500: ignoring Vendor ID payload [IKE CGA version 1]
2016:08:09-17:18:21 office-2 pluto[8029]: packet from 172.16.3.30:500: initial Main Mode message received on xx.xx.xx.xx:500 but no connection has been authorized with policy=PUBKEY
Does anyone have any suggestions on what I can check? I'd prefer to use the Windows client if possible as it's easy to control rollout via GPO.
Thanks,
Matt.
This thread was automatically locked due to age.