Installation, Configuration and Setup

Latest Version Info


NAT32 Version 2 is installed by running the Installer. This installer makes only minimal changes to your system and does not install the device driver.

If needed, the device driver is installed by executing the driver install command from within NAT32. Full details are here.


In some cases, NAT32 configuration can be done automatically by running the program config.exe. This command-line utility will generate the needed nat32.ini and ifn.ini files for a SoftAP configuration. Other configurations will be added in future builds. Details can be found in the file: config.txt.


NAT32 configuration is carried out once the device driver is running, and consists of two distinct procedures: Interface Selection and Interface Configuration.

Interface Selection

The Interface Selection dialog shows a list of all network adapters known to Windows on your machine. Some of those adapters may not actually be installed at the time and will be displayed in red. Select each adapter you would like NAT32 to use and then click an Adapter Type radio button.
Note that you should only click the One-way button if the adapter connects to a true one-way cable modem or to a Satellite device.
If you decide to use NAT32 in the presence of Windows ICS, click the ICS checkbox. Be sure to read the extended help pages on this topic before you do this.

Interface Configuration

An Interface Configuration dialog box will appear for each selected adapter. NAT32 auto-configuration will usually select the correct settings. Be sure to read the help page before you change any of the suggested settings.

Please click here for more NAT32 Configuration Details.

Uninstalling NAT32

If you need to completely uninstall NAT32, first uninstall the device driver by executing the driver uninstall command in the NAT32 Console. Then uninstall the NAT32 application in the usual fashion.

The device driver can also be uninstalled by viewing the Properties of any Network Adapter, selecting the WinPkFilter driver and then clicking Uninstall.

Configuration Files

The list of selected interfaces is in file nat32.ini, along with the connectivity type indicators.
Interface settings are in the files ifn1.ini, ifn2.ini and so on for each configured interface.
The initial Console window size (cols:rows), show state (H=hide, N=normal, F=full-screen) and browser embedding (E) are specified in file console.ini.
The Console screen buffer size (cols:rows) is specified in file screen.ini.

Script Files

startup.txt executed when NAT32 starts, specifies default settings
user.txt executed after startup.txt completes
exit.txt executed when NAT32 terminates
dialup.txt executed before dialing takes place (user-defined)
hangup.txt executed before a hangup takes place (user-defined)
connect.txt executed after a connection has been dialed
disconnect.txt executed after a connection is terminated
change.txt executed after an IP address change has occurred
url.txt loaded when a Web window is selected
dhcpd.ini The DHCP Server initialization file (user-defined)
dhcp.tcl A Tcl script that is executed whenever the DHCP Server performs an action
Script files can contain any NAT32 command, including names of files containing NAT32 commands, Tcl scripts and even Windows commands.

File readme.txt contains a list of changes in each build. If a new WinPkFilter driver is available, the build information will indicate this, and you must install the new version before you run that build.

File url.txt contains URLs that are displayed in a Web window's combobox prior to the Typed URLs fetched from the Registry.

You may need to modify file startup.txt, but note that custom settings should be placed in a file called ComputerName.txt, which will be executed by user.txt when startup.txt completes. File ComputerName.txt is not overwritten when you install a new build of NAT32, whereas file user.txt may well be.