ISA Server VPN Remote Wizard - "Bad Data" error

I'm going through the steps here:

http://www.tacteam.net/isaserverorg/isabokit/5isadc/5isadc.htm

to set up a VPN connection for a remote office.  When I get to step 6 and run the Remote VPN Wizard, I can't import the file that I created on the Local VPN Wizard.

The error is:

"An error occurred during reading of the configuration file: Bad Data"

I've copied the original file a few times, onto different disks, but always get the same error.  I've also tried creating a different configuration file by re-doing the Local VPN wizard, again with no joy.

Any idea what is causing this ?

At the moment I'm testing this with machines in adjacent rooms . When I do it for real I will be halfway across the world, so I'd like to be able to get it working smoothly !
LVL 17
aflockhartAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
sirk_aConnect With a Mentor Commented:
I had the same problem when one of the machines was a Windows 2000 machine (main office) and the branch office was Windows 2003.

I never did get the Remote VPN Wizard to work on the 2003 machine, so I went ahead and manually added what was needed.

First, make sure you have installed ISA SP 2 onto both machines.

To manually reproduce what the Local VPN Wizard did:

1) Create the IP packet filters (2 for PPTP, 2 for L2TP). Look at the filters on the Local VPN and reproduce them on the Remote VPN
2) Create a new network interface in RRAS. Open up RRAS, expand your server, right click on network interface: new demand-dial interface. After walking through the wizard it will create a new user account to connect to the other VPN server, and setup a static route for you. When you ran the Local Wizard it created a new user account for you (probably called main_branch) with a secure password. You will need to reset this password so that you know what it is, and use it during this step.

After I completed these steps I was able to connect the VPN connection from the branch office to the main office.

If you have any further questions or need more details on the 2 steps then let me know.

0
 
aflockhartAuthor Commented:
Ended up manually recreating the link and it worked fine.

Still no idea what causes the original failure though !
0
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.