• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1290
  • Last Modified:

Linksys BEFVP41 Setup

Have two offices that currently connect using terminal services from the remote office to the main office. Both have a dynamic IP address at each end, although the IP address for the two Linksys routers is always the same. Looks like this:

Main Office:
Remote Office:

The Remote Office (Win 2000 Pro machine behind a Linksys router(non VPN type))logs onto a Win 2000 server via Terminal Services. Everything works great.

The router at the main office was giving some trouble so it was replaced with a Linksys BEFVP41 VPN Router. Got it all set up and terminal services still works from the remote office to the main office. Decided to try and set up a VPN but can't seem to get it to work. Followed all the tutorials I could find on the web and in the instruction manual but can't make a VPN connection. Here are the VPN settings from the Main Office new VPN router:

   Tunnel 1: SSMaintenance
This Tunnel: Enable
Tunnel Name: SSMaintenance

Local Secure Group:   Subnet      IP:                      'This is the end where the WAN IP is

Remote Secure Group:   Subnet    IP:

Remote Security Gateway:      ANY (This gateway accepts request from any IP address!)

Encryption:    DES is selected
Authentication:      MD5 is selected

Key Management:   Auto. (IKE) is selected
      PFS (Perfect Forward Secrecy) checkbox is selected

Pre-Shared Key:  this is about a 10 digit alpha-numeric string
Key Lifetime: 3600 Sec.

Status: Disconnected

The Remote Office doesn't have a VPN router. Using Windows 2000 as the client to connect to the VPN router at the main office. Appendix C in the manual had a step by step for configuring the IPSec between a Windows 2000 and a Linksys Cable/DSL VPN Router. I followed all the directions exactly, including entering the WAN IP address of each end in the correct places.

My question, finally, is that I'm not sure what to put in for the "Remote Secure Group" and the "Remote Secure Gateway" values on the VPN router, can anyone explain what these are? Also, to make a VPN from the client do I have to specify a domain name or can I just use the Username and Password to logon to the private network that sits at the Main Office behind the VPN Router?
  • 2
1 Solution
Here is a simple workaround for the time being:

Open up port 3389 on your external interface of your main office router and redirect it internally to your internal server via NAT.  Furthermore, Lock Down this redirection by making sure that only the external interface ip of your remote office router can connect to port 3389 on the external interface of your main office router.  This is done so that no one can connect and try to remotely access your machine located within your main office.  Being that you have static IP's on both sides, you don't worry about having to change IP's in your configuration, etc.

Good Luck,

cshoreyAuthor Commented:
Sounds like a good plane for now, thanks.
Glad to help.  Take care...

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now