Fortinet black logo

SPA with a FortiGate SD-WAN Deployment Guide

Testing private access connectivity to FortiGate hub network from remote users

Copy Link
Copy Doc ID 8c54df13-c519-11ee-8c42-fa163e15d75b:958418
Download PDF

Testing private access connectivity to FortiGate hub network from remote users

You can verify access to the FortiGate hub network from FortiSASE users, namely FortiClient users connected to FortiSASE in endpoint mode using ping.

From a FortiClient user connected to FortiSASE, use ping within a Windows Command Prompt to verify access to a host behind the FortiGate hub internal network. The example pings 10.50.101.50, which is on an internal network. The following shows sample output:

C:\>ping 10.50.101.50

Pinging 10.50.101.50 with 32 bytes of data:

Reply from 10.50.101.50: bytes=32 time=80ms TTL=62

Reply from 10.50.101.50: bytes=32 time=80ms TTL=62

Reply from 10.50.101.50: bytes=32 time=80ms TTL=62

Reply from 10.50.101.50: bytes=32 time=84ms TTL=62

Testing private access connectivity to FortiGate hub network from remote users

You can verify access to the FortiGate hub network from FortiSASE users, namely FortiClient users connected to FortiSASE in endpoint mode using ping.

From a FortiClient user connected to FortiSASE, use ping within a Windows Command Prompt to verify access to a host behind the FortiGate hub internal network. The example pings 10.50.101.50, which is on an internal network. The following shows sample output:

C:\>ping 10.50.101.50

Pinging 10.50.101.50 with 32 bytes of data:

Reply from 10.50.101.50: bytes=32 time=80ms TTL=62

Reply from 10.50.101.50: bytes=32 time=80ms TTL=62

Reply from 10.50.101.50: bytes=32 time=80ms TTL=62

Reply from 10.50.101.50: bytes=32 time=84ms TTL=62