Reference Manual
HOW TO reconfigure NAT32:
NAT32 may need to be reconfigured in the following cases:
You have changed Network settings or added Network Adapters
-
Click Start/Programs/NAT32/Configure to start a NAT32 Configuration
Run and then proceed as described here.
-
Be sure that the current version of the
NDIS3PKT Driver is installed and running, and that
it is bound to all adapters you want NAT32 to use. Note that the driver can
only be started at boot time, so be sure to reboot Windows after you install
the driver.
-
If you are using Dial-Up Networking on Windows 9X or NT4, be sure that
IP Header Compression is off for all connections you want NAT32
to use.
-
For details of diagnostic configuration commands, click
here.
Client machines no longer have Internet access
-
Check the DNS settings on the client machines. Be sure that only known-good
DNS server addresses have been specified, or that NAT32's private IP address
is specified. That address is shown in the Quick dialog box and in the
bottom-left corner of the NAT32 Console window.
-
Check the Gateway setting on the client machines. Be sure that NAT32's
private IP address is the only gateway specified.
-
If you configured the client machines via NAT32's DHCP server, check the
client's IP address. If it is something like 169.254.x.x, then DHCP
configuration must have failed, and you should run winipcfg.exe
(9X platforms) or ipconfig /renew to reconfigure the interface.
If problems persist, check your hardware and cabling. Further details can be
found here.
- If you can ping the Internet but not open Web pages, check your Browser
settings. Be sure the browser has the correct Proxy settings if your
ISP requires the use of a Proxy. Note that NAT32 should never be used
as the Web Proxy, as NAT32 is an IP Router, not a Proxy Server.
- If you can only send short emails, or if Web pages load only partially,
check your MTU settings. In nearly all cases, the client machines (and the
NAT32 Interface to which they connect) should have an MTU of 1500 bytes, even
if the Internet adapter on the NAT32 machine is actually using a smaller MTU.
SEE ALSO
config dhcpd IP Autoconfiguration netcfg ns ping setd setns