Skip to content

Commit a2e0c3d

Browse files
Merge pull request #228858 from stegag/patch-41
Update vpn-gateway-troubleshoot-site-to-site-cannot-connect.md
2 parents ad174cb + 7afda7f commit a2e0c3d

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,10 @@ If the Internet-facing IP address of the VPN device is included in the **Local n
100100
<string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">Primary Instance: GatewayTenantWorker_IN_1 GatewayTenantVersion: 14.7.24.6</string>
101101
```
102102

103+
> [!Note]
104+
> Basic SKU VPN gateways do not reply to health probe.
105+
> They are not recommended for [production workloads](https://learn.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpn-gateway-settings#workloads).
106+
103107
### Step 8. Check whether the on-premises VPN device has the perfect forward secrecy feature enabled
104108

105109
The perfect forward secrecy feature can cause disconnection problems. If the VPN device has perfect forward secrecy enabled, disable the feature. Then update the VPN gateway IPsec policy.

0 commit comments

Comments
 (0)