VPN
.
Client: Windows 7 Pro
.
Host: Windows Server R2 Essentials
.
We set up VPN access to the host on a single client workstation after some playing around with the ports on the router. Was able to set up Server shares and access files etc.
.
Set up a second client and could not establish a VPN connection.
.
To verify that the VPN was working properly, we removed the VPN from the workstation that was working and rebuilt it.
.
Unfortunately we could not get the VPN to work again.
.
Remote Web Access, however, is working fine from all the workstations to the Server with no problems. Same certificate that we are using for the VPN.
.
With the workstation that had VPN working before:
.
VPN errors at the client end:
.
Running the ”Windows Server Essentials Connector Configuration Wizard” resulted in “Cannot get information from **.***.***.172. Please contact your server administrator”
Setting up a network connection:
.
“Connection failed with error 800. The remote connection was not made because the attempted VPN tunnels failed...
“The remote device or resource won't accept the connection Detected”
.
From the ClientDeployment.log
.
[8804] 160613.100137.5575: ClientSetup: Making web request: https://**.***.***.172//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1[8804] 160613.100137.7275: ClientSetup: Failed to download Setup.cab from server:
System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation
procedure.
.
At the Server End
.
Error 2016/06/13 8:06:07 Schannel 36888 None
.
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.
.
Error 2016/06/13 7:18:17 Schannel 36887 None
.
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 46.
.
Warning 2016/06/11 16:11:32 RasSstp 18 None
.
The Secure Socket Tunneling Protocol service either could not read the SHA256 certificate hash from the registry or the data is invalid. To be valid, the SHA256 certificate hash must be of type REG_BINARY and 32 bytes in length.
SSTP might not be able to retrieve the value from the registry due to some other system failure. The detailed error message is provided below. SSTP connections will not be accepted on this server. Correct the problem and try again.
.
Error 2016/06/11 16:11:32 RasSstp 24 None
.
The certificates bound to the HTTPS listener for IPv4 and IPv6 do not match. For SSTP connections, certificates should be configured for 0.0.0.0:Port for IPv4, and [::]:Port for IPv6. The port is the listener port configured to
be used with SSTP. The default listener port is 443.
.
From what I can see, it appears that the certificate is OK for Remote Web Access but not for the VPN.
.
Any ideas on how to fix, would be sincerely appreciated.
.
Thanks - Al