Currently set in Aggressive mode. 1 side has keep alives every 60 seconds
Main Topics
Browse All TopicsScenario: 2 sites 1 Domain
Main office:
Watchguard Firebox X Edge
MS Small Business Server 2003 w/ Exchange
30-40 windows XP professional clients
T1
192.168.2.x subnet
Remote office:
Fortigate 60
10-20 windows XP professional clients
DSL
192.168.3.x subnet
There is a site-to-site VPN setup between the two firewall devices. Remote office workers access shared folders and e-mail over the VPN tunnel. VPN tunnel has been shutting down every couple weeks. I've been able to solve this by logging into each VPN device and refreshing the IPsec keys and/or resetting the remote office firewall. Once the tunnel is active connectivity returns to normal. The settings are DH5, Sha-1, 3DES-CBC pre-shared key. key exprires every 24 hours.
Any ideas why the tunnel would break intermittently? Today was the most recent occurence of this event and I've been able to get the tunnel backup with a reboot on the Fortigate60 at the remote site. But now remote office clients cannot access shared files or network drives. Tunnel status is showing as active on both devices
Also the Watchguard at the main site will intermittently freeze every few weeks, requiring a reboot. There's no common interval. Sometimes it will be up for 6 weeks some times 4 or 5 days.
I've heard that malware can cause buffer overflows and wierd gateway problems. I've been logging events on the watchguard to verify my suspician but haven't seen anything conclusive yet.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
IPSec tunnels can drop for the following reasons:
The SA's can be mismatched (even though the tunnel has been up for months) i.e
some IPSec tunnel access-lists if not exactly matched by subnet and networks can caused dropped tunnels (using a network name for one subnet and using the actual subnet ip on the other peer can cause this)
mismatch in keepalive values
ISAKMP Lifetime (you see this in syslogs with error messages stating rekeying attempts)
I would only change the MTU's as a last resort, if nothing else seems to work. MTU changes usually are a result of router issues, or when the following happens with applications thru an IPSec tunnel:
MTU's become issues when hosts have trouble with certain apps, ie. exchange server and graphics programs which have large data packets which exceed the mtu's of the firewall. When ESP headers are added to the data packets, the packets often exceed the mtu of the firewall with the DF (don't fragment bit) cleared, and the packets don't get fragmented. These type of issues will involve changing the mtu of the firewalls as well as the MSS (maximum segment size) of the packets
Make sure order of transform sets on both piers are identical as well as the sets themselves being identical.
syntax of Phase 1 (ISAKMP) on both peers
NatExempt access lists must be identical as well as the syntax (always use the command line over the gui to verify this)
Verify routing tables also - if you cannot ping hosts, then there is a problem with
routes and or natexempt lists.
tunnel seems to be working currently. Although users in the remote office cannot access anything on the main office network. no pings, no outlook, no rdp. I'll double check the NAT entries. But these have not changed. Why would the be working (intermittently) for 6-9 months and then stop working. DHCP isn't enabled for the external interfaces on either device. and the local and remote subnets are specified correctly on both devices.
The only thing that changed over the weekend was a scheduled downtime to rearrange some power cords and UPS connections. No software was altered. The tunnel status is Active.
do a clear xlate in global mode after hours - to clear all the NAT translation slots. In some cases, you can try removing and re-applying the crypto maps.
Again, I have seen instances of tunnels functioning flawlessly for months and then just drop. Had some drop on me this week at a location -- it turned out I had to reapply the access-lists in both nat exempt and acl's. I used the numerical ip notation on the opposing peer, which had a network object group syntax mapping to the allowed networks. placing the numerical ips back in the config brought the tunnel back up
something to try at least
Business Accounts
Answer for Membership
by: ccpjcPosted on 2009-10-19 at 13:45:14ID: 25608849
I don't have experience with these firewalls, but usually VPN's are somewhat the same
I'm going to assume that you have static IP's assigned on each side, if not there's one thing to look at
Are the VPN's set to Main mode or an Aggressive mode?
Do you have a keep alive option on the firewalls, perhaps somewhere in the advanced, if so, enable it only on one side of the sites not both
play with the expiring of the pre-shared key
Change the MTU settings on the firewalls from 1500 to 1404, seems to work good with a lot
Ensure that both sides of the VPN tunnels have the same settings, sha-1, 3des, etc...