1. nat32v6.zip Driver
2. TWOIP.TXT File Contents

TWOIP.TXT Driver File Contents (nat32v6.zip)

NAT32: Connecting Private LANS to the Internet                    
----------------------------------------------

(C) 1999 A.C.T. Software

***** ALL RIGHTS RESERVED *****

----------------------------- TECHNICAL NOTE --------------------------------

******  This information applies to the Windows 95/98 platform only.  *******

How to add a second IP address via the registry
-----------------------------------------------

The Microsoft Windows 95/98 Control Panel Network applet does not allow a 
second TCP/IP stack to be added to an Ethernet Adapter once the Dial-Up 
Networking Adapter has been installed.

The easiest way to solve this problem is to uninstall DUN, add the required
TCP/IP stack and then reinstall DUN.

This Technical Note describes an alternative method which allows a second IP
address and Mask to be added to any Adapter via the Registry.  

1. Run the program regedit.exe

2. Open the Key HKLM\System\CurrentControlSet\Services\Class\NetTrans\

3. You will see several Subkeys like:

        0000
        0001
        0002
        
4. Select each Key in turn until you find the Key with an IPAddress Value
   which matches the IP Address of the Adapter to which you wish to add
   the second IP address.
   
5. Double-Click that Value and an "Edit String" dialog box will be presented.
   Add the second IP address, separating it from the first IP address with
   a comma. No embedded spaces are allowed. Click OK.
   
6. Now double-click the IPMask value, and add a second IPMask, using a comma 
   as the separator. Click OK.
   
7. Close RegEdit and reboot Windows.

Points to note
--------------

NETBIOS cannot use the second IP address, so be sure the first IP Address is
always the address you want NETBIOS to use.

NAT32 details
-------------

After NAT32 has been configured, subsequent runs fail when a second IP 
address has been added in this fashion. 

To correct this problem, simply use Notepad (or any other text editor) to 
generate the file netcfg.tmp in your NAT32 directory. The content of this 
file is not important, just the fact that it exists is sufficient to correct
the problem.

Note that one side-effect is that NAT32 will *not* detect DHCP address
changes on subsequent restarts.

If NAT32 is to be used in SERVER mode, be sure you check the ipmap command
in the server file. Per default, it maps on IFN 2, but depending on the 
order in which you specified the IP addresses in the Registry, you may need
to map IFN 3.
             
This Technical Note applies only to NAT32 Build 1045 or higher.

-----------------------------------------------------------------------------