Reference Manual

nat32.exe - the NAT32 Executable

nat32 [nifs]

NAT32.EXE is the executable file for the NAT32 application. The application may be installed on your system using the program setup.exe, which may prompt you to install the NDIS3PKT driver.

Argument nifs specifies how many [1..16] Network Interfaces are to be used. For each Interface requested, NAT32 will open a configuration file called netcfgx, where x is in the range [1..16]. If the specified configuration file does not exist, NAT32 displays a Network Configuration Dialog Box to obtain the needed configuration information.

If argument nifs is 0, NAT32 will use Winsock networking only; no NDIS3PKT Interfaces will be started and the Demo Version runs without time limits.

NAT32 supports Ethernet Interfaces, Token Ring Interfaces (but not emulated TR Interfaces) and Dial-Up Networking Interfaces. An interface can be running in its native mode or a special mode such as PPPoE or VPN mode. Note that only Microsoft VPN interfaces are supported. Other VPNs may or may not work, depending on how accurately the vendor's VPN device driver conforms to the Microsoft NDIS layer specifications.

If no arguments are specified, the program presents the NAT32 Configuration dialog box.

This dialog allows the user to check Windows TCP/IP settings, dial connections, and execute pings to test the reachability of hosts on the Internet and on the private LAN. If any tests fail, clicking Help will show several tips on how to solve the problem.

Before you continue, it is essential that the Windows TCP/IP protocol has been correctly configured on all adapters, that at least one valid DNS Server address has been specified (click Help to check this), and that all hardware components (cables, switches, hubs etc) are working correctly. If you are running a software firewall, be sure it is not blocking NAT32 traffic.

When all adapters are functioning correctly, clicking Continue will display the Interface Selection dialog.

You should now select each interface you would like NAT32 to use, and specify its Connection Type by clicking the appropriate radio button.

If Dial-Up Networking adapters are to be used, be sure the desired connections are established at this time. If need be, click the Dialer button to dial a connection, then click Refresh to update the display. The Autodial checkbox controls the Master Autodial switch and should normally be turned on. This will not necessarily make NAT32 autodial a connection, as interface-specifc autodial options will be specified later.

On platforms which support Windows ICS, the Windows ICS checkbox should be off, unless you wish to run NAT32 in the presence of ICS. Click here for a description of some of the known problems with all versions of Windows ICS, and 9X ICS, 2000 ICS or XP ICS for further configuration details.

On Windows XP and Server 2003 platforms, the Windows ICF checkbox should be on. For Windows XP SP2 platforms, be sure the Authorize NAT32 checkbox is on so that the Windows Firewall allows NAT32's Winsock traffic. Note that the Windows Firewall does not block NDIS3PKT traffic, so NAT32 will be able to forward such traffic irrespective of Windows Firewall settings. But note that most other firewalls do block NAT32's NDIS3PKT traffic, so you should consult the vendor's documentation for details on how to allow all traffic from the NAT32 Application.

The example shows two selected adapters: a private LAN Adapter and an Internet-connected Dial-Up Networking Adapter.

Some adapters may be displayed in red. Those adapters either do not exist at present (but were once present in the system), or they are unconnected USB adapters, or they have been disabled by the user, or their cable is disconnected.

The Create Shortcuts checkbox specifies whether or not the Run  and Configure  shortucts are to be created on the current Desktop.

Clicking Continue will display an Interface Configuration dialog box for the first selected adapter:

In the above example, the SURECOM Adapter details are shown. It is a LAN Adapter (as distinct from a Dial-Up Adapter) and has been configured under Windows to use the fixed, private IP address 172.16.4.2.
NAT32 will use the IP address 172.16.4.100 on this adapter, and your other computers can reach the NAT32 Router via that address. The adapter is the Main Private Adapter, as distinct from the other private adapters which may be present. It is not operating in PPPoE mode.

The settings shown by NAT32 will generally be correct, and you should only modify them after you have clicked Help and carefully studied the displayed Help information.

Clicking Continue will display the Interface Configuration dialog box for the second selected adapter:

In the above example, the Dial-Up Adapter details are shown. Because its IP address details will vary from connection to connection, NAT32 will store 0.0.0.0 IP, Mask and Gateway values in the associated netcfg2 file.

The adapter is the Main Internet Adapter and NAT32 will share the adapter's current Windows IP address. NAT32 will also Monitor the adapter for address changes, and dial the specified connection as needed, but only if the Master Autodial switch is on. Route selection by Source Address is off, because the Source Route entry is 0.0.0.0.

The connection is not a PPPoE connection, but if it were, be sure an MTU of 1492 bytes has been configured.

Once configuration is complete, NAT32 executes the file startup in the current directory. When execution of startup is complete, NAT32 terminates. Note that file startup typically contains a shell command which creates a NAT32 shell in a specified window. When that shell exits, NAT32 processes the onexit file and terminates.

While NAT32 is running, an icon  is displayed in the System Tray. Left-clicking that icon displays the Console Window. This is your main means of interaction with the NAT32 application and a powerful UNIX-like command interpreter is available in that window for your enjoyment.

Alternatively, right-clicking the System Tray icon  will display the Quick Dialog Box:

The Quick dialog appears in the lower right-hand corner of the Desktop and contains toolbar icons and a settings listbox. The icons have the same meaning and functionality as those in the Console. The list box contains a concise display of important NAT32 settings, and any list box entry can be double-clicked to open a dialog box in which the relevant settings can be modified or tested. A single click closes the selected dialog box. A throughput bar shows the current throughput of each Internet interface.

Only one invocation of NAT32.EXE is allowed at a time. The supplied program stop.exe can be used to terminate the NAT32 application or service if no other means exist. Never use the Windows Task Manager to terminate any running application, unless you subsequently reboot the system.

NAT32 will not close any established Dial-Up connections on exit, unless a hangup or dunsrv command is specified in the file onexit.

The NAT32 home page is http://www.nat32.com/index.htm. Please check this page regularly for the latest news and product updates.

dunsrv exit hide ipcfg ndis3pkt netcfg register shell service startup termin