Troubleshoot IPSec with these tips. Takeaway:
Running IPSec to secure your network’s communication traffic provides a very strong layer of defense to your network. However, it’s important that you test these policies before deploying them and verify that they’re running properly. In this edition of Security Solutions, Mike Mullins offers some troubleshooting tips for when you run into trouble.
Securing your organization’s LAN and WAN traffic from prying eyes is an ongoing struggle. In the past, I’ve written about securing that traffic using IPSec policies. If you followed my recommendations, then good for you!
But what if you’ve been experiencing problems with your IPSec implementation? We can usually trace most IPSec problems to difficulties during the Internet Key Exchange (IKE) phase of authentication.
Computers go through a process in which they authenticate each other’s identity and form a security association. This identity authentication occurs via a preshared key, a digital certificate, or Kerberos (the default for Windows Server 2003).
However, before you begin troubleshooting the authentication process, let’s start at the beginning. First, make sure IPSec is running.













