Reference Manual

HOW TO access a Microsoft VPN server running on a machine behind NAT32.

• Enter the following commands or add them to your user.txt file:

  ppmap add tcp 1723 192.168.0.2 1723

  The address 192.168.0.2 stands for the IP address of the private machine running the VPN server.
  Port 1723 is the standard Microsoft VPN Server port.

  gmap add 192.168.0.2 137.92.11.80

  The address 137.92.11.80 stands for the IP address of the VPN client.

• The VPN client on the Internet should connect to NAT32's registered IP address.

• Be sure that passwords and permissions have been set up correctly on both client and server.

• Be sure that no VPN Server is running on the NAT32 machine itself.

• To delete the mappings when no longer required, enter the following commands:

  ppmap delete tcp 1723

  gmap delete 192.168.0.2 137.92.11.80

  Note that when the VPN client disconnects, the TCP connection remains in the FINWAIT1 state for about 10 secs. Subsequent connection attempts will fail during this period.

• If the IP address of the VPN client is not known a priori, an Action Mapping Table entry such as the following can be used to add and delete the gmap entry dynamically:

  amap add 1723 "gmap add 192.168.0.2 $SRCIP" "gmap delete 192.168.0.2 $SRCIP"

• The Action Mapping Table entry can be deleted as follows:

  amap delete 1723

• The entire procedure can also be performed by running the vpns script from the command line or via the Application Mappings dialog:

  script/vpns 192.168.0.2 1723

  script/vpns off 1723

SEE ALSO

amap, gmap, ppmap, startup