chinese_simplified english italian
Home arrow VPN-X Tech Info arrow Advanced Configuration arrow Configuring VPN-X server as NAT server on Windows

Configuring VPN-X server as NAT server on Windows

Tuesday, 01 March 2011

Windows 2003, Mac OS X , FreeBSD and Linux supports acting as a NAT server. Unfortunately Windows XP does not support this method.

If you are using Windows 2003, please follow these steps:

  • Stop Windows Firewall/Internet Connection Sharing (ICS), and disable it.

    vpnx_advanced_2

  • Control Panel-> Administrative Tools-> Routing and Remote Access
    Open the configuration window like this.

    vpnx_advanced_3

  • Configure Routing and Remote Access

    vpnx_advanced_4


    Select Next and Select network address translation (NAT), then Next again.

    vpnx_advanced_5


    Keep in mind, the VPN-X virtual device is a virtual Network interface connection (NIC), but you can deal with it just like a real NIC.

    Choose the real NIC to be the public interface to the Internet. Windows will use the VPN-X NIC to be the private connection automatically.

    vpnx_advanced_6

    vpnx_advanced_8

    vpnx_advanced_9

    Next, finish the Windows NAT configuration. You can disable the NAT firewall or write an exception rule to make your NAT work properly. Note: The NAT firewall is not the same thing as Windows built-in general ICS firewall.


    The client does not know how to access the remote LAN through the VPN server, so you should add a route configuration for clients, and click “Apply”

    vpnx_advanced_10

    Add a route rule on “Client Route Table” for your VPN clients.

    network: 192.168.1.0
    netmask: 255.255.255.0
    gateway: 192.168.240.1
    metric: 20


    if you want to surf internet with server side IP, you should add route rule like this:

    network: 0.0.0.0
    netmask: 0.0.0.0
    gateway: 192.168.240.1
    metric: 1


    Don't forget to click "Apply". After change route setting, you’d better tell your clients to restart VPN-X client to make sure the new route rule is working.


Test your NAT server from VPN-X client

Run VPN-X client.
Assumed your VPN-X server public/Internet IP is 61.173.25.162

  • For SSL VPN:

    VPN Server host: 61.173.25.162
    VPN Server port: 25443
    protocol: TCP(SSL/TLS)
    user name and password

  • For P2P VPN:
    VPN Server host: 61.173.25.162
    VPN Server port: 25000
    protocol:  UDP
    user name and password


  • After your VPN-X clients logon VPN-X server, they will access your remote LAN easily.

    ping 192.168.240.1
    ping 192.168.1.1
Last Updated Friday, 11 March 2011
All rights reserved.
Copyright (C) 2006-2014 BirdsSoft - Web by Amigamerlin