We have a Point-to-Site VPN connection between an on-premise server and Azure.
The connection worked for several days, then suddenly stopped working on Saturday 08th June. After that, connections to the Virtual Network have failed with the error:
"The network connection was aborted by the local system.
(Error 0x800704d4) For customized troubleshooting information for this connection, click Help."
- Connections to other Virtual Networks with Point-to-Site VPN work from our network.
- I have tried downloading a new VPN Client installation package from Azure portal, didn't work with that either
- The connection to the problematic Virtual Network also fails with the same error message if the VPN connection is installed on an Azure instance (not one in the problematic Virtual Network), so this doesn't seem to be related to our firewall settings. I tried
also with the new VPN Client package, without making other configuration changes. Connecting to another Virtual Network from the instance worked.
We managed to create another Virtual Network, create staging deployment using that network, install new VPN connections on the on-premise servers, and then switch the staging to production. This means that the immediate situation is over.
However, we would like to know what has caused this and how we can avoid this error in the future. The problematic network is still unreachable.
I found the following page with a proposed solution for the error, but I couldn't get it to work:
http://blogs.technet.com/b/rrasblog/archive/2009/08/12/troubleshooting-common-vpn-related-errors.aspx
The same solution was proposed on the Virtual Network forum:
http://social.msdn.microsoft.com/Forums/en-US/wavirtualmachinesvirtualnetwork/thread/38d67091-a789-480d-b065-83c8365d7b80
"Possible Solution: Check your proxy settings inside the Internet explorer. If the settings are correct, please ensure you are able to access other web sites (e.g.www.microsoft.com) using the browser. If that also works through, try accessing the URI which SSTP uses internally i.e.https://vpn_server_name/sra_{BA195980-CD49-458b-9E23-C84EE0ADCD75}/ - please replace vpn_server_name with actual VPN server name. If you see error “the website cannot
be found” inside your browser, that validates the hostname resolution failure. If you know the IP address of VPN server, try connecting with that. Else contact your network administrator (who is responsible for managing the web proxy – most probably your ISP)
– giving them the details of the problem (i.e. hostname resolution is failing for that particular hostname)."
I tried the following addresses:
https://<gateway IP address>/sra_{BA195980-CD49-458b-9E23-C84EE0ADCD75}/
Certificate problems (name doesn't match), then empty page (IE10)
Certificate problems (name doesn't match), then "The server requested a login authentication method that is not supported." (Opera 12.15). Probably Opera doesn't support certificate selection for the login.
https://azuregateway-<VPN connection address>-0.cloudapp.net/sra_{BA195980-CD49-458b-9E23-C84EE0ADCD75}/
Empty page (IE10)
Incomplete certificate chain, then "The server requested a login authentication method that is not supported." (Opera 12.15).
So it seems that this isn't a hostname resolution failure either.