Before you can solve a problem, you need to understand it. Often this step can be the longest in this process. Before starting to troubleshoot a problem, answer these questions:
- Where and when did the problem occur?
- Has it ever worked before?
- Where does the problem lie?
- Is it a connectivity issue? Can your FortiMail unit communicate with your network and the Internet? Is there connection to a DNS server?
- Is there more than one thing not working?
- Is it partly working? If so, what parts are working?
- Can the problem be reproduced at will or is it intermittent?
- Are the servers covered by the policy working? Has a policy been disabled?
- Is your system overloaded?
- What has changed?
- After determining the scope of the problem and isolating it, what servers does if affect?
If the unit never worked properly, you may not want to spend time troubleshooting something that could well be defective.
Be specific. Do not assume the problem being experienced is the actual problem. First determine if the FortiMail unit's problem lies elsewhere before starting to troubleshoot the unit.
Make a list.
Make a list.
An intermittent problem can be difficult to troubleshoot due to the difficulty reproducing the issue.
Check the status of the protected servers.
View the System Resource on the dashboard.
Do not assume that nothing has changed in the network. Use the FortiMail event log to see if something changed in the configuration. If something did change, see what the effect is when you roll back the change.
Once the problem is defined, you can search for a solution and then create a troubleshooting plan to solve it.