Question : VPN access to a non-PDC W2K3 Server

I am trying to get VPN access to a server in a temporary installation which is connected to a GlobalspanVirata router. I think that the port forwarding is set up correctly on the router, i,e,

Port 1723 Incoming Accept Destination Address 192.168.7.22
and the same for 47 & 50

I am simply getting an error 800

Answer : VPN access to a non-PDC W2K3 Server

An 800 error is a basic no connection error, so it sounds like the two have not even begun handshaking. You may want to review the configuration outline below. Included is a link for setting the port forwarding on your router. This only addresses port forwarding of port 1723. You won't need 47 and 50, these are protocols, not ports. You do need protocol 47 (GRE) which is enabled on different routers in different ways. See below.

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 see:http://www.portforward.com/english/routers/port_forwarding/GlobespanVirata/GS8100/Point-to-Point_Tunneling_Protocol.htm
The VPN pass-through, or enabling GRE (protocol, not port, 47) is done is different ways on different routers. Some are automatic when you enable port forwarding, others have a "PPTP pass-through" or VPN pass-through" option, still others require specific commands. Without it you will usually get a 721 error.
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.