Skip to content

Commit 1809aa2

Browse files
authored
Merge pull request #195227 from carlost-MSFT/patch-23
Update vpn-gateway-troubleshoot-site-to-site-cannot-connect.md
2 parents caa321b + fc77fc5 commit 1809aa2

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/vpn-gateway/vpn-gateway-troubleshoot-site-to-site-cannot-connect.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,9 @@ If the Internet-facing IP address of the VPN device is included in the **Local n
9191

9292
`https://<YourVirtualNetworkGatewayIP>:8081/healthprobe`
9393

94+
> [!NOTE]
95+
> For Active/Acive Gateways use the following to check the second public IP: https://<YourVirtualNetworkGatewayIP2>:8083/healthprobe
96+
9497
2. Click through the certificate warning.
9598
3. If you receive a response, the VPN gateway is considered healthy. If you don't receive a response, the gateway might not be healthy or an NSG on the gateway subnet is causing the problem. The following text is a sample response:
9699

@@ -106,4 +109,4 @@ The perfect forward secrecy feature can cause disconnection problems. If the VPN
106109
## Next steps
107110

108111
- [Configure a site-to-site connection to a virtual network](./tutorial-site-to-site-portal.md)
109-
- [Configure an IPsec/IKE policy for site-to-site VPN connections](vpn-gateway-ipsecikepolicy-rm-powershell.md)
112+
- [Configure an IPsec/IKE policy for site-to-site VPN connections](vpn-gateway-ipsecikepolicy-rm-powershell.md)

0 commit comments

Comments
 (0)