Please do not respond with only the following quote:
"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)." (http://blogs.technet.com/b/rrasblog/archive/2009/08/12/troubleshooting-common-vpn-related-errors.aspx)
The connection worked for some time, then after a weekend it could no longer connect. This is a second Virtual Network that has done the same. So far the only workaround we have found is to create another Virtual Network, and then recreate all deployments that used the old network.
To me this seems like a serious bug. I really hope this is fixed before General Availability of Point-to-Site.
The error is "Error 0x800704D4: The Network connection was aborted by the local system." The error happens on any machine trying to connect to the network.
Both https://<gateway IP address>/sra_{BA195980-CD49-458b-9E23-C84EE0ADCD75}/ andhttps://azuregateway-<VPN connection address>-0.cloudapp.net/sra_{BA195980-CD49-458b-9E23-C84EE0ADCD75}/ work (blank page with IE10, with certificate warning when using IP address).
Also it's possible to access other pages and other VPN connections on the computers. So this does not seem like a hostname resolution failure.
So the worst problem is over. Now we are just hoping that this doesn't happen with a third network. Last time Microsoft support just pointed me toward these forums. Is there some way to at least get this to the Azure team as a bug report?