Draytek 2830 to Microsoft ISA 2004 Server LAN to LAN VPN Setup


We are currently trying to configure a LAN to LAN VPN connection for a client of ours using a Draytek 2830 router at the remote site and a Microsoft ISA 2004 server at the head office side.

Currently the ISA server is acting as the gateway for the main office and has a public IP address setup on it's WAN network interface.

We were looking for some help and guidance on setting this up, if anyone has achieved this before then I would be interested to know the steps they've taken.  We have tried setting it up based on what we think we should be doing but without any real step by step guide to follow we're struggling even to get the VPN link established.
Who is Participating?
pyranetukAuthor Commented:
Haven't really found a resolve to this issue as such but managed to work around the issue with our client by using router to router setup.
IPSec is the best way I've found.  It should be straight forward, I've created a few.  There are a few guides about it:

Draytek has some guides about different VPNs accross different platforms:
pyranetukAuthor Commented:
Thanks. We have actually found and followed that first guide without success.

It never seems to get past Phase 1.

Struggling to understand some of the settings on the ISA server too as to what it means for some parts.
WEBINAR: 10 Easy Ways to Lose a Password

Join us on June 27th at 8 am PDT to learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees. We'll cover the importance of multi-factor authentication and how these solutions can better protect your business!

You may want to try PPTP  just to get it working 1st, but I think there is little or no encryption with that, so I'd only use it to test!

Here's an old bookmark if it helps, plenty of ISA VPN info:
It should help you understand the ISA settings.  They Draytek is fairly simple in comparision!
Keith AlabasterEnterprise ArchitectCommented:
Turn it round please. What are the issues you are actually seeing. How have you configured the ISA - I assume it is a two-nic, domain joined implementation?

Before you change anything - have you run the ISA best practice analyser to check the basics?
Which part of the ISA terminology are you having difficulty with?

pyranetukAuthor Commented:
OK, thanks for everyone's feedback so far and sorry about the delay on coming back to this.

We have now managed to get the VPN connection established between the Draytek router and the ISA server now. The issue appeared to be the network address for Local Network setup on the ISA server. After we changed this so it correctly had the subnet in place the VPN established.

We now have a different issue though, in that the VPN connection only seems to allow traffic through it for about 15 minutes before we can no longer ping either side.

I have uploaded a couple of log files from the Draytek which were requested by their support in case anyone knows enough about them to determine what is going on. If anyone could give me any indication on how to get some logging info from ISA server then I can produce logs from there also.

On the log files attached all external IP addresses have been changed to random ones.

Would appreciate any suggestions as to how to best diagnose this problem.

For info we have already changed the IKE lifetimes down to 900 for Phase 1 and 600 for Phase 2. This impacted slightly in that the VPN would then occasionally drop out for 1 ping every 6 minutes or so.

Looking for a solution to have a stable VPN connection, I'm sure someone has got VPN working successfully between ISA server and Draytek routers in the past.
pyranetukAuthor Commented:
Keith, to answer your questions. Yes it is a 2 NIC Domain joined implementation.

One network card has an external IP address connected through a Cisco router which is connected to a 25MB leased line.

The other NIC is the LAN interface on the local subnet.

As mentioned, the VPN now establishes however traffic stops working after between 5 - 15 minutes.

There is also (possibly unrelated) another issue whereby we cannot ping a couple of server IP addresses from the remote site to the head office, even though you can ping them in the head office. There is no other firewall on the servers which we cannot ping.
pyranetukAuthor Commented:
Also, when we start having issues with traffic no longer going over the VPN we get these messages in Syslog on the Draytek:

 2013-02-15 15:08:04       connection: 81bc1ea0 is dial-out and NOT for dynamic client; in_index=0, out_index=-1. U can try to reduce phase1 lifetime...
 2013-02-15 15:08:04       Responding to Main Mode from
 2013-02-15 15:07:56       connection: 81bc1ea0 is dial-out and NOT for dynamic client; in_index=0, out_index=-1. U can try to reduce phase1 lifetime...
 2013-02-15 15:07:56       Responding to Main Mode from
 2013-02-15 15:07:53       sent QI2, IPsec SA established with In/Out Index: 0/-1
 2013-02-15 15:07:53       Client L2L remote network setting is

However as mentioned previously, we cannot set the key lifetime any lower as it's already at the lowest supported.
pyranetukAuthor Commented:
We had to work around the solution by implementing router-router setup.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.