Windows VPN clients and VPN servers provide a large set of troubleshooting tools for diagnosing and gathering information about remote access VPN connections. VPN
The most common problems with remote access VPN connections are the inability to establish a successful connection and the inability to reach locations beyond the VPN server. Make sure to follow the processes and steps in this chapter closely— they are the same troubleshooting steps the Windows product team uses to test the Windows operating system, so you should be able to get all the issues worked out quickly and easily.
In Chapter 11, “Troubleshooting Remote Access VPN Connections,” we went through the
“Divide and conquer.”
To isolate the problem, rule out
“This troubleshooting stuff really works!” Don’t get discouraged. Keep plugging away if you are having problems, and make sure you work with all the tools available.
As stated in Chapter 11, the Microsoft Windows Server 2003 family provides the following tools to troubleshoot VPN connections:
Transmission Control Protocol/Internet Protocol (TCP/IP) troubleshooting tools
Authentication and account logging
Internet Authentication Services (IAS) event logging
Point-to-Point Protocol (PPP) logging
We did an
One new tool you need to be aware of for site-to-site connections is the Unreachability Reason facility, which you can use to investigate a site-to-site VPN connection problem. When a
To view the unreachability reason tool
From the console tree in the Routing And Remote Access snap-in, click Network Interfaces.
In the details pane, right-click the demand-dial interface, and then click Unreachability Reason.