The NDIS3PKT Device Driver

NAME

The NDIS3PKT Device Driver.

NAT32 uses a special version of Dan Lanciani's NDIS3PKT Device Driver for direct network I/O. This driver works with all Ethernet Adapters, Token Ring Adapters (but not emulated TR as used on some ATM networks), and with Dial-Up Networking Adapters. Note that on all Windows platforms prior to Windows 2000, the Dial-Up Networking Connections must have IP Header Compression turned off.

Be sure that Windows TCP/IP is correctly configured for all networking adapters before attempting to install NDIS3PKT. You should be able to ping all your private machines and most Internet adresses from a Windows Console. If any machines can't be reached, please consult a local expert before continuing.

Installing NDIS3PKT

Open the Network Connections folder.

Right-click on any Local Area Connection and then select Properties

Click Install...

To uninstall the driver, simply select it and then click Uninstall.
Note that uninstalling the driver from any adapter will completely remove it from the system. A reboot is required to complete the procedure.

Select Protocol and then click Add...

Click Have Disk...

Browse to your NAT32 directory and then click OK.

Select the NDIS3PKT Driver and then click OK.

 

Then reboot Windows to start the driver.

 

Note that you must reboot at this point, even if Windows does not ask you to.

 

This is because the NDIS3PKT Driver can only be started at Boot Time.

 

Now run NAT32 as described here and it will auto-configure.

The NDIS3PKT driver should have no effect whatsoever on the normal operation of your network. However, some users have reported problems after installing NDIS3PKT on their systems. Such problems are due to one or more of the folllowing:

• Your Windows system may have latent configuration errors. These often show up as yellow icons in Control Panel, System, Device Manager. You must correct all indicated problems before continuing.

 
• Be sure you have installed only known-good Network Adapter device drivers. The drivers on your Windows CD will almost certainly be out of date, so check the vendor's web site for upgrades.

 
• Some Firewalls and other Internet Connection Sharing software install device drivers that are not fully Microsoft NDIS3 compatible. NDIS3PKT will probably not work until such drivers have been uninstalled.

If your TCP apps are consistently reporting Connection reset by peer errors, then run the Control Panel Network applet, double-click each Adapter in turn, and view the adapter bindings. Ensure that NDIS3PKT is bound to all adapters.

The NDIS3PKT Driver does not work with ATM adapters which emulate Token Ring. As ATM technology was never widely used for private LANs, this problem will not affect most users.

nat32