You can also open the Policy Manager, and go to the Setup menu, and choose Logging, then the Diagnostic Log Level button. Look for red "deny" messages, they will give you a clue why the traffic is denied. If you are using PPTP or SSL for the connections, those policies do live in the normal rule sets.įor troubleshooting, connect a client and setup a continuous ping to a server (ping -t server_ip) and then open Firebox System Manager and go to the Traffic Monitor tab, to see the logs of what is happening. When you open the Policy Manager, at the top of the rules is another tab for IPSEC MUVPN rules. There is a catch with "MUVPN with IPSEC" because the policies which control it do not live in with the normal firewall policies. Watchguards support three kinds of mobile VPN - PPTP, IPSEC and SSL.
We've looked at the settings on the Mobile VPN client, but nothing seems like a probable cause. Plus, some people can successfully connect to network drives through the VPN.Ĭan someone please suggest some steps to help troubleshoot? We've checked the policies on our Watchguard box, and they seem fine. But we also made other changes at the time that might have thrown something off, although we feel like we've checked them all. We've since switched back and the problem persists, so that doesn't seem to have been it (which makes sense). Last week, we temporarily switched one of our Comcast modems to our backup DSL modem because the Comcast was accidentally shut off by Comcast, and the problem seemed to start around then. The problem is, when they try to map drives, or even ping the IP address of a server on our network, it fails.
That is, their status in the the VPN client says "Connected" and they have the correct IP address listed as the VPN Endpoint. We use Watchguard Mobile VPN (we have a Watchguard Firebox firewall) and the users are able to connect. We're having any issue in which some of our employess can no longer connect to our network drives when out of the office.
0 kommentar(er)
