Question : Problem: MS 2003 Server VPN setup

First thanks for reading my post. I have very limited experience with
VPN's so any help is appreciated. I need to setup a VPN for 6 people
(remote sales people) to be able to map a drive and use an MS Access
DB. The topology is as follows (Home office): Broadband modem(16Mbps) ->Linksys
wireless Router -> MS server 2003 standard. Would anyone be able to
point me in the right direction?

A little more info for you:

Server has one Nic
Would like to utilize MS VPN (since cost is an issue)
We have a static IP on the broadband gateway
Linksys wireless Router configured with the static IP and is serving
as the DHCP server.
people are connecting to the router on the LAN for internet access

What do I do on the router?
What is the best way to setup the server for VPN?
I have a ton more question but this would be a great start for me.
Thanks again for your time

Answer : Problem: MS 2003 Server VPN setup

I have posted the instructions for setting up the server, router, and client for the Windows VPN below, however I have to agree with arnold, though VPNs can be very useful, one place they should not be used is to access a database. There is a lot of communications required between the database and client and the slower speed results in extremely poor performance, and very often data corruption.

With larger databases such as Oracle and SQL it is possible to write a front end application that communicates with the database over a VPN, but I have never seen this doe with a basic Access databases. Terminal Services is your best bet.

The basic server and client configurations can be found at the following sites with good detail:
-Server 2003 configuration:
http://www.lan-2-wan.com/vpns-RRAS-1nic.htm
-Windows XP client configuration:
http://www.lan-2-wan.com/vpns-XP-Client.htm
-You will also have to configure the router to forward the VPN traffic to the server. This is done by enabling on your router VPN or PPTP pass-through, and also forwarding port 1723 traffic to the server's IP. For details as to how to configure the port forwarding, click on the link for your router (assuming it is present) on the following page:
http://www.portforward.com/english/applications/port_forwarding/PPTP/PPTPindex.htm
-The users that are connecting to the VPN need to have allow access enabled under the dial-in tab of their profile in active directory
-The only other thing to remember is the subnet you use at the remote office needs to be different than the server end. For example if you are using 192.168.1.x at the office, the remote should be something like 192.168.2.x

-Once this is configured you can then use services similar to how you would on the local network. You will not be able to browse the network unless you have a WINS server installed. Also depending on your network configuration you may have problems connecting to devices by name, though this can usually be configured.. Using the IP address is less problematic such as \\192.168.1.111\SharenName.
-Nome resolution can be dealt with in many ways. See:
http://msmvps.com/blogs/robwill/archive/2008/05/10/vpn-client-name-resolution.aspx
However, the best method is to add the DNS suffix to the remote users VPN client configuration as described in the link above.