Fortinet 5.0 Patch 6

Fortinet 645 FortiWeb 5.0 Patch 6 Administration Guide

3. Enter the command:

execute ping <destination_ipv4>

where <destination_ipv4> is the IP address of the device that you want to verify that the

appliance can connect to, such as 192.168.1.1.

If the appliance can reach the host via ICMP, output similar to the following appears:

PING 192.168.1.1 (192.168.1.1): 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=253 time=6.5 ms

64 bytes from 192.168.1.1: icmp_seq=1 ttl=253 time=7.4 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=253 time=6.0 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=253 time=5.5 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=253 time=7.3 ms

--- 192.168.1.1 ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max = 5.5/6.5/7.4 ms

If the appliance cannot reach the host via ICMP, output similar to the following appears:

PING 10.0.0.1 (10.0.0.1): 56 data bytes

Timeout ...

--- 10.0.0.1 ping statistics ---

5 packets transmitted, 0 packets received, 100% packet loss

“100% packet loss” and “Timeout” indicates that the host is not reachable.

For more information, see the FortiWeb CLI Reference.

To ping a device from a Microsoft Windows computer

1. Click the Start (Windows logo) menu to open it.

If the host is running Windows XP, instead, go to Start > Run...

2. Type cmd then press Enter.

The Windows command line appears.

To verify that routing is bidirectionally symmetric, you should also ping the appliance. See “To

enable ping and traceroute responses from FortiWeb” on page 642 and “To ping a device from

a Microsoft Windows computer” on page 645 or “To ping a device from a Linux or Mac OS X

computer” on page 646.