Skip to content

Commit 5cfb02b

Browse files
committed
refresh
1 parent f43e3ef commit 5cfb02b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/global-secure-access/how-to-create-remote-networks.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ author: kenwith
55
ms.author: kenwith
66
manager: amycolannino
77
ms.topic: how-to
8-
ms.date: 08/21/2023
8+
ms.date: 08/30/2023
99
ms.service: network-access
10-
ms.custom:
10+
1111
---
1212
# How to create a remote network
1313

@@ -195,8 +195,8 @@ There are a few things to consider and verify when creating remote networks. You
195195
- **Port forwarding**: In some situations, the ISP router can also be a network address translation (NAT) device. A NAT converts the private IP addresses of home devices to a public internet-routable device.
196196
- Generally, a NAT device changes both the IP address and the port. This port changing is the root of the problem.
197197
- For IPsec tunnels to work, Global Secure Access uses port 500. This port is where IKE negotiation happens.
198-
- If the ISP router changes this port to something else, Global Secure Access cannot identify this traffic and negotiation fails.
199-
- As a result, phase 1 of IKE negotiation fails and the tunnel is not established.
198+
- If the ISP router changes this port to something else, Global Secure Access can't identify this traffic and negotiation fails.
199+
- As a result, phase 1 of IKE negotiation fails and the tunnel isn't established.
200200
- To remediate this failure, complete the port forwarding on your device, which tells the ISP router to not change the port and forward it as-is.
201201
202202
[!INCLUDE [Public preview important note](./includes/public-preview-important-note.md)]

0 commit comments

Comments
 (0)