Win 10 1903 ate my VPN

[markwilfan]

There I was boasting about how amazing Win 10 1903 was the other day for us in the What cool things have you done today thread... Until I upgraded my laptop to 1903. Now our AlwaysOn VPN will not connect. I have even reimaged my laptop today thinking it may be some kind of certificate that has borked. Nope, still not connecting.

 

Here is the error... all works fine on 1809 and below so not thinking it is a serverside issue

 

An IPsec main mode negotiation failed.


Local Endpoint:
Principal Name:		external url for our VPN
Network Address:	external ip for our VPN
Keying Module Port:	4500

Local Certificate:
SHA Thumbprint:	0b373f293b7e5bf045353967aec9571db87e0588
Issuing CA:		CA my school
Root CA:		CN=CA my school

Remote Endpoint:
Principal Name:		-
Network Address:	
Keying Module Port:	4500

Remote Certificate:
SHA thumbprint:		- my home IP
Issuing CA:		-
Root CA:		-

Additional Information:
Keying Module Name:	IKEv2
Authentication Method:	Certificate
Role:			Responder
Impersonation State:	Not enabled
Main Mode Filter ID:	240147

Failure Information:
Failure Point:		Local computer
Failure Reason:		Negotiation timed out

State:			EAP payload sent
Initiator Cookie:		e5160a5cccce04bf
Responder Cookie:	5e15736aa8cbc8fd

 

Anybody else having "issues" with their VPN and 1903? Found this

so one would assume it's an undocumented feature