Fortinet FortiGate 1U Quick Start Manual page 38

6. Verify the DNS configurations of the FortiGate unit and the PCs on the
internal network.
Check for DNS errors by pinging or using traceroute to connect to a domain name; for
example:
ping www.fortinet.com
ping: cannot resolve www.fre.com: Unknown host
If the name cannot be resolved, the FortiGate unit or PC cannot connect to a DNS server
and you should confirm the DNS server IP addresses are present and correct.
7. Verify the security policy configuration.
Go to Policy > Policy > Policy and verify that an internal -> wan1 security policy has been
added and check the Session column to ensure that traffic has been processed.
8. Verify the static routing configuration.
Go to System > Network > Routing Table and verify that the default route is correct.
9. Disable web filtering.
A web filtering security policy may block access to the website that you are attempting to
connect to. This could happen because the configuration of the default web filter profile is
blocking access to the site.
It is also possible that FortiGuard Web Filtering has produced a rating error for the website,
causing the web filter profile to block access. A rating error could occur for a number of
reasons, including not being able to access FortiGuard. To fix this problem, go to Security
Profiles > Web Filter > Profile and, in the default profile, enable Allow Websites When
a Rating Error Occurs.
10. Verify that you can connect to the gateway provided by your ISP.
Try pinging the default gateway IP address from a PC on the internal network.
11. Confirm that the FortiGate unit can connect to the FortiGuard network.
Once registered, the FortiGate unit obtains antivirus and application control and other
updates from the FortiGuard network. Once the FortiGate unit is on your network, you
should confirm that it can reach the FortiGuard network. The FortiGate unit must be able
to connect to the network from its management IP address. If the following tests provide
18 The FortiGate Cookbook 5.0.