Branch office VPN won't stay up. Driving me nuts!!

[chris360]

Here's is the full scenario. I have a T1 internet connection in Manila where I have a Watchguard Firebox X Core 1250e. That is behind a Cisco 1800 series router. The reason for that is because I was unable to hook up my Firebox directly to the modem since the modem only has a V.35 connection. The Cisco has V.35, and I plug in the Firebox via ethernet. I'm trying to connect a Branch Office VPN to another Firebox in the US. I can establish it, but it won't stay up. The internet connection through the Firebox in Manila stays up, but not the VPN. When its up I can ping PC's in the US office, I can open shared folders, and open the company intranet, all through the VPN, but everytime I try to open a Terminal Server session to a server in the US, the VPN goes down. It will make the connection to the Terminal Server, but somewhere in between the login and loading the profile, it freezes. When that happens I see that packets are sending, but not receiving (remember, I'm on the Manila side). I can't ping or connect in any way at that point. If I wait about 30 minutes the VPN comes back up again and the story repeats itself.

The whole point of the VPN is for users in Manila to us terminal services off a server in the US office.

I've tried just about anything I can think of. I'm stuck and I can't go back home to the states until I figure this out. If anyone has any ideas what so ever, please, lay them on me.

Thanks!

 

[pankajchawla]

Trying set the lifetime or key expiration time to either 0 or disable the key expiration feature in phase two properties.

If possible post the logs from traffic monitor when the tunnel goes down and comes up.


Pankaj