Some Cable Modem or ADSL users may wish to use NAT32E with Adapters which have no Microsoft TCP/IP installed. Such configurations are appropriate when total security of the NAT32 machine must be guaranteed.
NAT32 Configuration:
Be sure you are running the current build of NAT32E.
Configure the machine for normal Microsoft TCP/IP operation and for Dial-Up Networking operation. A DUN Adapter must be present, even though NAT32 won't be using it.Points to Note:Be sure a valid DNS Address is configured
Be sure that Windows can reach the Internet over the Cable Modem or DSL adapter, and that all private machines are reachable. Use ping to test reachability.
Then configure NAT32 in the usual fashion.
Be sure that the monitor checkbox is not set in the Interface Configuration dialog box for the Primary Interface.
Once you have tested the configuration and verified that NAT32 is working correctly, run Control Panel Network and edit the Properties, Bindings of each Adapter.
Uncheck the TCP/IP checkbox for each Adapter NAT32 is using.
Reboot Windows and then start NAT32 via its Desktop Shortcut.
In this mode, NAT32 has no WinSock access, so TCL scripts that use Sockets (e.g. HTTPD) won't work.SEE ALSO
Commands such as wns won't work either, because they too require WinSock access.
The Interface Monitoring feature will not work, because it is also dependent on Winsock
.
If the Internet-connected Adapter is DHCP configured, be sure to add a dhcpc command to your startup file.
If your ISP changes IP addresses frequently, you may need to start cron too.
cron dhcpc