najprosciej zainstaluj sobie jakies proxy ktory udostepni ci necik dla drugiego kompa a wtedy admin moze sobie ustawiac co chce a i tak bedzie ci wszystko dzialalo ponizej masz programiki
& lt; none & gt;
[reflected]
:137
:138
:139
NAT32 Remote Console
NAT32 Remote Console
Please choose a Browser: & nbsp; & nbsp; & nbsp; [ Internet
Explorer ] [ Other ]
pcAnywhere
NAT32 Reference Manual
HOW TO manage machines behind NAT32 with SYMANTEC pcAnywhere:
Be sure you are running Build 2068 (or later) of NAT32+ or Build 1125 (or
later) of NAT32.
Start pcAnywhere in Host Mode on the private machines you intend to manage
from the Internet.
pcAnywhere listens on TCP/UDP Ports 5631 and 5632. The ports are fixed
and can only be altered by modifying the Registry.
The required Permanent Port Mappings can be installed by running the command:
& nbsp; & nbsp; & nbsp; pcany 172.16.2.2
The above command makes the private machine 172.16.2.2 visible
to the Internet at the pcAnywhere Ports.
You can enter the needed pcany command either at the NAT32 Console
or remotely via the NAT32 HTTPDI daemon.
Now start pcAnywhere on the remote machine.
Click the Remote Control icon and then right-click the Network Icon and
select Settings.
Select the radio button: Network host PC to control or IP address
and enter the DNS Name or the IP address of the NAT32 box in the edit control
to the right of the radio button. In the above example, you would enter:
137.92.11.80
Now double click the NETWORK icon to connect to the NAT32 machine.
The pcAnywhere Remote Control program will then attempt to contact machine
137.92.11.80 at TCP/UDP Ports 5631 and 5632.
Again, these ports are fixed and can only be altered by modifying the Registry.
Because you previously mapped those ports to private machine 172.16.2.2,
NAT32 will pass the traffic to that machine.
A few seconds later you will see the Desktop of the 172.16.2.2 machine
appear on your screen.
To manage a different private machine, simply point your Netscape Browser
or Java Applet Viewer at 137.92.11.80.
Enter a new pcany command to switch the mapping to the desired
machine.
Be sure to close the previous Remote Session first, and always use a
strong password .
SEE ALSO
httpd
[HOWTO INDEX] [HOME]
Help Pages
NAT32 Reference Manual
Local Help Page Index
NAT32.COM Reference Manual
in WinHelp format
NAT32.COM Help Page
Index
NAT32.COM HowTo Index
NAT32 Console
Asheron's Call setup
NAT32 Reference Manual
HOW TO set up Asheron's Call (thanks to David Bell)
Configure Asheron's Call as follows:
In the startup screen for Asheron's Call (AC) click the Settings
button. In the Settings Panel , for the Port Setting To Use ,
select the Specific Port checkbox and then fill in the text box
with a specific port number. & nbsp; Whatever port number you choose, you
then need to configure NAT32 for the same port number. & nbsp; For each instance
of AC, you will need to select a different specific port number and add
mappings to NAT32 for those port numbers. & nbsp; I suggest using port number
9010 for a single instance and incrementing the port number by 10 for each
additional instance.
For example:
Host-1/Game-1 & nbsp; (IP address 192.168.0.1) uses & nbsp; port 9010
Host-2/Game-2 & nbsp; (IP address 192.168.0.2) uses & nbsp; port 9020
Host-3/Game-3 & nbsp; (IP address 192.168.0.3) uses & nbsp; port 9030
The mapping commands for NAT32 are then:
# AC Game-1 on Host-1 (IP addr 192.168.0.1)
umap add 9010 1
ppmap add udp 9010 192.168.0.1 9010
# AC Game-2 on Host-2 (IP addr 192.168.0.2)
umap add 9020 1
ppmap add udp 9020 192.168.0.2 9020
# AC Game-3 on Host-3 (IP addr 192.168.0.3)
umap add 9030 1
ppmap add udp 9030 192.168.0.3 9030
The above commands could be executed by the following TCL script, which
can be invoked from the NAT32 Console or from within the file startup .
#!tcl
#
# AC Mappings
#
if {$argc != 2} {
& nbsp; & nbsp; & nbsp; error {Usage: ac IPaddress|off port}
}
set addr [lindex $argv 0]
set port [lindex $argv 1]
if {$addr == " off " } {
& nbsp; & nbsp; & nbsp; exec " umap delete $port "
& nbsp; & nbsp; & nbsp; exec " ppmap delete udp $port "
} else {
& nbsp; & nbsp; & nbsp; exec " umap add $port 1 "
& nbsp; & nbsp; & nbsp; exec " ppmap add udp $port $addr $port "
}
The TCL help Page documents
the special features of the NAT32 implementation of TCL.
SEE ALSO
ppmap tcl
umap
[HOWTO INDEX] [HOME]
Tcl Scripts
NAT32 Reference Manual
HOW TO write simple TCL scripts to add Permanent Port Mappings:
NAT32 Permanent Port Mappings are documented here .
The following TCL scripts serve as examples for using TCL to write scripts
which can be invoked from the NAT32 Console or from within the file startup .
Example 1: QuickTime 4
#!tcl
#
# Quicktime 4 mappings
#
if {$argc == 0} {
& nbsp; & nbsp; & nbsp; error {Usage: qt4 IPaddress|off}
}
set addr [lindex $argv 0]
if {$addr == " off " } {
& nbsp; & nbsp; & nbsp; exec " ppmap delete udp 6970:6999 "
} else {
& nbsp; & nbsp; & nbsp; exec " ppmap add udp 6970:6999 $addr 6970:6999 "
}
Example 2: REAL AUDIO
#!tcl
#
# Real Player mappings
#
if {$argc == 0} {
& nbsp; & nbsp; & nbsp; error {Usage: real IPaddress|off}
}
set addr [lindex $argv 0]
if {$addr == " off " } {
& nbsp; & nbsp; & nbsp; exec " ppmap delete udp 6970:7170 "
} else {
& nbsp; & nbsp; & nbsp; exec " ppmap add udp 6970:7170 $addr 6970:7170 "
}
Example 3: Battle Net
#!tcl
#
# Battle Net mappings
#
if {$argc == 0} {
& nbsp; & nbsp; & nbsp; error {Usage: battle IPaddress|off}
}
set addr [lindex $argv 0]
if {$addr == " off " } {
& nbsp; & nbsp; & nbsp; exec " ppmap delete udp 6112 "
& nbsp; & nbsp; & nbsp; exec " umap delete 6112 "
} else {
& nbsp; & nbsp; & nbsp; exec " ppmap add udp 6112 $addr 6112 "
& nbsp; & nbsp; & nbsp; exec " umap add 6112 1 "
}
Example 4: DialPad
#!tcl
#
# DialPad mappings
#
if {$argc == 0} {
& nbsp; & nbsp; & nbsp; error {Usage: dialpad IPaddress|off}
}
set addr [lindex $argv 0]
if {$addr == " off " } {
& nbsp; & nbsp; & nbsp; exec " ppmap delete udp 51200:51201 "
& nbsp; & nbsp; & nbsp; exec " ppmap delete tcp 51210 "
} else {
& nbsp; & nbsp; & nbsp; exec " ppmap add udp 51200:51201 $addr 51200:51201 "
& nbsp; & nbsp; & nbsp; exec " ppmap add tcp 51210 $addr 51210 "
}
The TCL help Page documents
the special features of the NAT32 implementation of TCL.
SEE ALSO
ppmap tcl
[HOWTO INDEX]
[HOME]
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.
-----------------------------------------------------------------------------
Net2Phone Setup
NAT32 Reference Manual
HOW TO set up Net2Phone
Net2Phone uses three ports (two UDP ports and one TCP port) to establish
a line of communication between the PC and the & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Net2Phone Switch.
One UDP port is used to establish the initial connection to the server;
the second UDP port is used to pass voice packets. The TCP port is used
for control to make sure the connection between the PC and the Net2Phone
server remains open.
Net2Phone establishes the first connection using port UDP port 6801.
This port must remain open for the duration of the call. The other UDP
port does normally not need to be specified. Net2Phone uses anything in
the range 1 - 30000. However, when Net2Phone is running on a machine behind
NAT32, the actual port number used must be known.
Fortunately, the Net2Phone client software can be configured so that
specific port numbers are used. You do this as follows:
1.1 & nbsp; & nbsp; & nbsp; & nbsp; Run the Net2Phone software.
1.2 & nbsp; & nbsp; & nbsp; & nbsp; Click Menu/Preferences/Network
1.3 & nbsp; & nbsp; & nbsp; & nbsp; Select Client and enter a UDP port such
as 3000.
1.4 & nbsp; & nbsp; & nbsp; & nbsp; Click OK to save the changes.
In the NAT32 Console, run the n2p Tcl script as follows:
& nbsp; & nbsp; & nbsp; n2p 172.16.2.20 3000
The above command will assign Net2Phone access to the specified private
machine using the specified UDP port number.
To reverse the mappings, enter the command:
& nbsp; & nbsp; & nbsp; n2p off 3000
To assign Net2Phone access to a particular machine automatically, simply
add the needed command to file startup .
The n2p Tcl Script is as follows:
#!tcl
#
# Net2Phone mappings
#
if {$argc != 2} {
& nbsp; & nbsp; & nbsp; error {Usage: n2p IPaddress|off Port}
}
set addr [lindex $argv 0]
set port [lindex $argv 1]
if {$addr == " off " } {
& nbsp; & nbsp; & nbsp; exec " umap delete $port "
& nbsp; & nbsp; & nbsp; exec " ppmap delete udp $port "
} else {
& nbsp; & nbsp; & nbsp; exec " umap add 6801 1 "
& nbsp; & nbsp; & nbsp; exec " ppmap add udp $port $addr $port "
}
The TCL help Page documents the special features
of the NAT32 implementation of TCL.
SEE ALSO
ppmap tcl umap
[HOWTO INDEX] [HOME]
ICS Configuration
NAT32 Reference
Manual
HOW TO configure NAT32 in the presence of Windows Internet Connection
Sharing.
The NAT32 Interface Selection dialog box lists all Network adapters
known to Windows. When an adapter has an X in front of its name, NAT32
has detected a problem with it and displays a red
warning message in the Adapter Details field. Such adapters
should normally not be selected for use by NAT32.
& nbsp;
On a system with Windows Internet Connection
Sharing installed, the NAT32 Interface Selection dialog box
will detect all ICS adapters and flag them as problem devices.
The Dial-Up Adapter in this example had been configured under Windows
to act as the ICS Internet interface. This will have caused Windows to
bind a special device driver to that adapter in order to provide the ICS
functionality. Unfortunately, that device driver is incompatible with NAT32's
NDIS3PKT driver and so NAT32 marks that adapter as Disabled
by Windows ICS . This presents a problem if you would like to use
NAT32 to share that adapter.
The Internet Connection Sharing adapter has also been added by Windows
ICS, and it is also flagged as a problem device. Fortunately, this adapter
does not interfer with NAT32, so you can safely ignore it.
But if you do wish to use NAT32 to share the Dial-Up Adapter,
the following solutions can be applied. & nbsp;
Method 1: Uninstall Windows ICS via Control Panel , Add/Remove
Programs ,
Windows Setup .
This has the disadvantage that all your ICS Port Mappings in the Registry
at
& nbsp; & nbsp; & nbsp; HKLM\System\CurrentControlSet\Services\ICSharing\Mappings
may be unavailable if you ever decide to use ICS again. But it is by
far the simplest solution to the problem. After you have uninstalled ICS,
reboot the machine and then reconfigure NAT32.
& nbsp;
Method
2: Leave ICS installed, but you run icssetup.exe
to select a NULL adapter as the Internet ICS Interface.
This is done by selecting the blank entry in the first combo box. Alternatively,
you could select any adapter you know you don't need, such as a USB adapter
which is not connected to the system. In the case of RASPPPoE configurations,
you could even select the LAN adapter which is connected to the ADSL modem,
because that adapter is not actually used by Windows for TCP/IP, the RASPPPoE
adapter is used instead.
Then click OK and Windows will request a reboot. Then start NAT32 again
and you will then be able to configure it to use the desired adapter as
the shared interface to the Internet.
& nbsp;
& nbsp;
Tips
To turn off the Windows DHCP Server , run the NAT32 command wdhcpd
off and then reboot Windows.
To turn off Windows ICS , run the NAT32 command ics off
and then reboot Windows.
To turn off Windows IP Forwarding , run the NAT32 command winrt
off and then reboot Windows.
[Home]
NAT32E: Connecting Private LANS to the Internet Build 1054
----------------------------------------------- ----------
(C) 2003 NAT Software ** NAT32 Enhanced Version 1.6 **
***** ALL RIGHTS RESERVED *****
Redistribution of this software without the prior written permission of the
author is strictly prohibited.
Version 1.6 WINDOWS 95/98/NT/2000/XP 21. April, 2003
-----------------------------------------------------------------------------
NAT32E is a versatile Software Router which allows all computers on one or
more private LANs to share one or more Internet connections.
With appropriate configuration, NAT32E will bind to the following devices:
Windows WAN devices: Modems, ISDN, ADSL, PPPoE, Microsoft VPN
Windows LAN devices: Ethernet, Token Ring (but not emulated TR)
Hybrid Devices: One-way cable modems, Satellite devices (DirecPC)
NAT32E fully supports the Windows DUN/RAS Server, allowing dial-in access to
machines which connect to the Internet via some other Network Interface with
a registered IP address.
Administrators can remotely configure and interrogate NAT32E using a Java-
enabled WEB Browser. A NAT32 password must be specified and Internet access
to the NAT32E HTTP server is blocked per default.
NAT32E is an IP Router, NOT a Proxy Server. Time-consuming reconfiguration
of network applications is not required. All applications on your private
LAN have address-mapped UDP, TCP and ICMP access to the Internet.
NAT32E Version 1.6 supports " connection aggregation " , a technique used for
distributing Internet traffic over two or more modems (or other types of
connections). The technique should not be confused with " modem bonding " or
" multilink " , which requires ISP support and is usually only available for
ISDN services.
Connection aggregation is particularly useful in cases where two or more
Dial-Up Networking connections are available and router traffic is to be
spread (more or less) evenly over multiple connections. The feature is also
useful for DSL or Cable Modem users requiring a backup Internet connection.
If the high-speed connection fails, the DUN Connection can be easily enabled
for emergency use.
Installation
------------
The NAT32E archive can be unzipped into any desired directory, the example
below assumes the directory C:\NAT32E.
You should then run the setup program setup.exe. This program makes NO major
modifications to your system. In particular, no Windows DLLs or Drivers are
overwritten or modified, and your networking configuration is not altered
in any way. Only minor registry modifications are made. Only one file is
copied: nat32.inf to your Windows INF directory.
Before Running NAT32E:
----------------------
This version *requires* Internet Explorer 4 (or later). Even if you are a
Netscape or Opera user, you must install IE, even if you uninstall it again
afterwards. The IE uninstall procedure leaves all the needed DLL's on your
system.
WINDOWS 95 users should install the Microsoft DUN 1.2 (or later) upgrade
before running NAT32E. This upgrade is an absolute must (even for Cable
Modem users) because it contains the latest VIP.386 and TCP/IP upgrades,
as well as vastly improved Dial-Up Networking support. The upgrade is
available for free download from www.microsoft.com.
IMPORTANT
---------
You must turn off IP Header Compression for all DUN Connections you
plan to use with NAT32 (95/98/NT4 platforms only). If you ran setup,
this will have been done for you, but any connnections you add later
will need to have IP Header Compression turned off manually.
Installing NDIS3PKT
-------------------
NAT32E uses a special version of Dan Lanciani's NDIS3PKT driver. DO NOT
ATTEMPT to run NAT32E with any version of NDIS3PKT other than the one
contained in this distribution.
1. Start the Control Panel Network Applet and click Add then Protocol.
Under Windows 2000/XP, open Control Panel, Network and Dial-up
Connections, and then right-click any Local Area Connection. Then click
Install and select Protocol, Add.
2. Click the " Have Disk " button and specify the directory into which you
unzipped NAT32E as the source directory.
3. Select the required .inf file:
Windows 9X: NDIS3PKT.INF
Windows NT: OEMSETUP.INF
Windows 2K: NDIS3P2K.INF
Windows XP: NDIS3P2K.INF
4. Click OK.
5. REBOOT WINDOWS, even if a reboot is not requested. Note that the NDIS3PKT
driver can only bind to adapters which Windows enables at boot time.
If you have disabled an adapter, reenable it and then reboot Windows so
that NDIS3PKT can bind to it.
Running NAT32E
--------------
The first time NAT32E is run, it examines the existing network configuration
and generates several configuration files in the directory from which it was
started. Click the Notepad Toolbar Icon for more details.
IMPORTANT
---------
For NAT32E autoconfiguration to work correctly, you MUST have at
least one private LAN adapter which has been assigned a FIXED IP
address. That address should be private, but it needn't be.
A Dialog Box will be presented listing all Network Interfaces available on
your system, and you should then select the Interfaces you would like NAT32E
to use. One of those Interfaces (the one which connects to the Internet)
should be designated as the Primary Shared Interface, all others must have
the Primary and Shared checkboxes unchecked.
A yellow shortcut will be added to your Desktop, and you should use that
shortcut whenever you subsequently wish to run NAT32E with the selected
interfaces. A grey shortcut is also added. It can be used to start a new
NAT32E configuration run.
IMPORTANT
---------
NAT32E can be run as a Service, but you MUST NOT start it as
a service until it has been correctly configured and you have
familiarized yourself with its operation.
NAT32E is documented in the Windows Help File: nat32e.hlp.
************************* HOW TO UNINSTALL NAT32E ***************************
* *
* Click Start/Programs/NAT32/Uninstall *
* *
* Uninstall leaves a few configuration files in your NAT32 directory, so *
* you should subsequently drag the NAT32 directory to the Reycle Bin. *
* *
* To uninstall NDIS3PKT, use Control Panel Network to remove the driver. *
* *
*****************************************************************************
NAT32E is SHAREWARE and will run for 60 minutes to allow you to evaluate its
features. NDIS3PKT has been modified to run with NAT32E only.
*****************************************************************************
* *
* Online Registration: see menu item Help/Register *
* *
* Bug Reports: bugs *
* @ *
* nat32. *
* com *
* *
* WEB Site: http://www.nat32.com *
* *
*****************************************************************************
What's New in this Release
--------------------------
DD.MM.YEAR
21.04.2003 BUILD 1054
Dhcpd modified.
20.04.2003 BUILD 1053
Command setw modified, new setw.htm man page posted.
FTP problem: some FTP servers don't originate connections at port 20.
Added a wild-card mechanism to fix this.
Problem with PASV mode transfers fixed.
NOTE
====
PASV mode may not work with non-UNIX compatible FTP servers.
Check your FTP Client for details of supported server types.
14.04.2003 BUILD 1052
Nif diagnostic string added. Used to show Autodial trigger.
WIN32 brush handle problem fixed.
Refresh button added to Interface Selection dialog.
DHCP server upgraded.
Command ukmap added. See http://www.nat32.com/nat32e/htm/ukmap.htm
for details. Ukmap can be used to map a range of port numbers to a
single port number on a private machine. Used for some games and
mapping scan traffic to honeypots.
Command icmap upgraded. Now allows any number of private machines
to ping and traceroute simultaneously.
22.03.2003 BUILD 1051
NAT32 now detects Windows 98SE/ME Internet Connection Sharing.
Click Help, More Help in the Interface Selection dialog to view a
detailed description of how NAT32 and ICS can coexist.
ICMP FNADF packets now forwarded correctly.
NAT32 Windows 2k/XP ICS detection added.
16.03.2003 BUILD 1050
*** NEW NDIS3PKT.386 ***
*** NEW NDIS3PKT.SYS ***
The new NDIS3PKT driver solves a MUX problem.
Umap error fixed.
Map_port now increments the new src port for each retransmitted
SYN. The old MUX entry is deleted. This feature can be turned on
and off using the setdf command. It should probably NOT be used
for Satellite links.
IP_IN no longer reschedules on receipt of a packet.
DHCPD now allows 10 sec for ARP to complete (was 5 sec).
Test for ICS (SharedAccess) service added.
Test for ICS on 98 platforms added.
MSTCP traffic monitoring added. Use command " mstcp ifn " to start
the monitor, " mstcp ifn kill " to stop the monitor.
Command " mstcp ifn block " will block all MSTCP traffic for the
specified interface.
Command " mstcp ifn allow " will allow all MSTCP traffic.
Note that only one interface at a time can be monitored in this
release.
Main Dialog now indicates disabled adapters.
Windows Account Name displayed.
01.03.2003 BUILD 1049
Mux problems solved temporarily.
New NDIS3PKT driver pending.
28.02.2003 BUILD 1048
For DUN Connections, throughput is now calculated as the max of
received and sent bytes per second.
Unused bytes in short packets set to 0.
Sendf again used in ip_in.
Hex trace now dumps entire packet.
Netstart now does a mux reset to clear the NDIS3PKT MUX table.
OnExit does too.
Pmdel now resets stalled TCP connections correctly.
Map_port and unmap_port modified.
Local traffic handling modified (ipgetp, ipproc, ipputp).
21.02.2003 BUILD 1047
DHCPD was adding PENDING ARP entries to NAT32 ARP cache.
Resulted in new machines not being reachable from NAT32 for
about 600 sec.
Arpdel command fixed. Was failing if unconfigured interfaces present.
Experimental: if a TCP SYN segment is retransmitted, change the
mapped source port. Some servers require this.
19.02.2003 BUILD 1046
IP_IN modified to not force packet deleivery when IP input queue is
full. IP input queue size increased to 100 packets.
Above measures increased throughput to 5.4 Mbps on 133 Pentiums.
Trace indicates if a packet was dropped because of full input queue.
Local TCP traffic had incorrect source address if more than one
gateway present.
Rttimer: DHCP address change code modified.
Bug on 9x platforms fixed: if multiple adapters with the same name
were present, the adapter exclusion mechanism failed. The exclude
file is no longer used.
Fixed the problem with local traffic and multiple default routes
DHCPD now allocates less memory.
Dhcpd command syntax changed.
IPPROC now uses NI_PRIMARY default route if no Interface Selection
algorithm specified.
Setis command syntax changed.
Console lockup bug fixed. New window created in a seperate thread.
Primary Interface semantics changed. The Primary Interface is now the
interface used to communicate with the Internet. In cases where 2 or
more such interfaces exist, the Primary interface will be used,
unless the setis command has been used to enable interface selection
by other means.
Quick Dialog box now shows the settings for the Primary interface.
Winio: ctrl-b problem fixed.
10.02.2003 BUILD 1045
Connection name, IP address and Interface number now logged in
rttimer function.
W2000 and XP: major problem with connection aggregation fixed.
DHCPD problem fixed: for two or more DUN connections, single adapter
mode was being set.
W2000 and XP: major problem with Interface Number in netin2k fixed.
Setis command modified to provide more details.
Connection name problem fixed for connections which come up while
NAT32 is running.
28.01.2003 BUILD 1044
Calls to ppp.log were colliding. Only " connect " and " disc " now write
to ppp.log.
For 2000 and XP platforms, the connection name is now displayed for
all connected NDISWANIP adapters.
Command 'setmap' now has following syntax:
setmap [ " connection " [off | primary]]
The command can be placed in the script file 'connect' and is used
to turn mappings for a WAN connection on or off. If 'primary' is
specified, the interface will become the Primary Interface.
21.01.2003 BUILD 1043
Command 'setmap IP [mask]' added. Turns on mappings for DUN
connections which have an IP address matching 'IP' after it has
been AND'ed with 'mask'. Use for Windows 2000 and XP only.
20.01.2003 BUILD 1042
Command 'setnsi [ifn]' added. Sets the NSERVERs to that of the
specified interface. Use for Windows 2000/XP only.
Bug in winio.c fixed (keyboard input during output was locking on
W2K and XP).
NifUpdate now also updates NSERVER if it is equal to 137.92.1.1.
Winute bug fixed: ni_private was not being set.
Command setsu clears all NSERVERs and then calls NifUpdate.
Setsu mechanism modified and tested.
Command 'setsu' prints the subunit table.
Command 'setsu subunit' turns on mappings for the specified
subunit, if the adapter is Internet connected.
06.01.2003 BUILD 1041 ***** EXPERIMENTAL *****
On W2K and XP platforms, this build detects DUN connections as they
come up but does _not_ turn on the various port mappings unless the
NDIS3PKT subunit numbers match or the connection is coming up for the
first time. For the case where the subunit of a connection has
changed, the mappings must be turned on via a new set subunit
command:
setsu subunit
where 'subunit' is the subunit number of the desired Primary (DUN)
Interface. The needed subunit number is displayed in the relevant
Interface Configuration dialog box.
The needed setsu command can be added to file 'connect'. A future
build will automate this procedure.
Command 'setsu subunit' searches for the established DUN connection
with the matching subunit number and then does the following:
1. Adds a default route
2. Turns on IP mapping
3. Turns on Port Mapping
4. Turns on ICMP Mapping
Command x_up now displays subunit and su_valid for each adapter.
20.12.2002 BUILD 1040
Registration bug fixed.
18.12.2002 BUILD 1039
Monitor bug fixed.
Bug in cat command fixed.
CURRPID modified in create function.
12.12.2002 BUILD 1038
All centered windows (and Trace) now have focus.
Setup Version 1.4 is now compatible with WinZip INSTALL.
Admin log problem fixed. Admin log file now opened in append mode.
30.11.2002 BUILD 1037
Redirection problem fixed in P32.C.
QuickDlg again displays a TaskBar button.
11.11.2002 BUILD 1036
95/98 platforms: stale DHCP values no longer returned by
GetDhcpDns95.
Password problem fixed.
TDI problem on NT/2000/XP platforms fixed.
No more double ping replies after a private machine has pinged.
DNS Help page fixed.
23.10.2002 BUILD 1035
Console window creation code modified.
22.10.2002 BUILD 1034
Netmeeting now works fully for outgoing connections to Internet.
Incoming connection support coming soon.
Quick command modified: throughput bar can be turned on/off as
needed.
Service behaviour modified:
1. Shutdown and logoff for NAT32 Service fixed.
2. No splash screen for NAT32 Service.
3. No Quick dialog for NAT32 Service at startup.
Note that on 98 platforms, NAT32 assumes it is running as a service
if a NAT32 value is present in the RunServices key.
12.10.2002 BUILD 1033
Hex dump mode in trace window added.
Console mode network trace removed.
DHCPD no longer pings 0.0.0.0.
10.10.2002 BUILD 1032
Permanent Port Mappings can now be made interface-specific.
04.10.2002 BUILD 1031
Minor changes only.
28.09.2002 BUILD 1030
Command added: setis [1|2]
The setis command sets the algorithm for choosing which of several
Internet-connected interfaces should be used for an outgoing TCP
connection. The value 1 sets the algorithm to choose the interface
which had the least amount of traffic over the last second.
The value 2 sets the algorithm to round-robin. This is the default.
Additional algorithms will be added in future builds.
Port Mapping now uses Critical Sections rather than Semaphores for
mutual exclusion.
Color change code modified.
RTTIMER bug fixed: no longer turns on IP mapping when a DUN server
connects.
DNS bug fixed. DNS port number is now fixed at 53.
DNS detection ignore servers that don't support recursion.
Console Window redraw bug fixed for NT platforms.
Dial-Up Networking dialog box modified: Properties button added.
Interface Configuration dialog box modified: DUN Server modem number
added (9X platforms only). This allows a particular DUN Server modem
to be specified for each DUN Server interface.
RAS not required if no PPP connections selected.
07.08.2002 BUILD 1029
Dial and Hangup mechanism modified.
WinInet Commands: ** Work for ONE connection only **
dial [ " connection name " ]
Dials " connection name " or the default connection
hangup [ " connection name " ]
Hangs up the specified connection or the default connection.
RAS Commands: ** Work for any number of connections **
rdial " connection name "
Dials the specified connection via RAS.
rhangup " connection name "
Hangs up the specified connection via RasHangUp.
Command " dun " lists details of all open connections.
The Toolbar Dial Icons refer only to the Windows Default Connection.
Use Config, Dial-Up Networking Settings, to dial or hangup
connections other than the Windows Default Connection, or click the
DUN list box entry in the Quick dialog.
03.08.2002 BUILD 1028
Console window now dimensions properly for non-standard font sizes.
Fixed PASV FTP problem when multiple connections are up.
Modified the Gateway dialog box to display all default routes.
31.07.2002 BUILD 1027
Fixed TCP problem when multiple Internet connections are up.
31.07.2002 BUILD 1026
Interface Configuration now supports an " auto " interface speed.
If a speed is specified, it overrides the speed reported by Windows.
This was needed because Windows reports 10 Mbps for DSL connections,
even though the actual service is usually much slower.
The Quick dialog now calculates the total number of bits received
each second on all Internet interfaces. It then displays that value
as a bar graph. Each bar represents 2, 4, 8, 16 ... bits.
29.07.2002 BUILD 1025
Splash screen now closed in thread: pmain
Registration check modified.
27.07.2002 BUILD 1024
Interface Selection dialog modified.
Interface Configuration dialog modified.
Speed variable added.
Active thread no longer displays anything on Status Bar.
Slowtime displays total received bits per second each second for all
Internet-connected interfaces.
26.07.2002 BUILD 1023
Admin Backup saved in registry.
Load balancing not done if a Source Route is specified on any
Internet-connected interface.
Mappings dialog box now shows all mappings.
25.07.2002 BUILD 1022
Load Balancing algorithm modified. Link speeds now included in
algorithm.
24.07.2002 BUILD 1021
Admin list box log added, backup to registry added.
23.07.2002 BUILD 1020
FTP bug fixed. Only passive mode was working.
19.07.2002 BUILD 1019
Connection Aggregation now works in unregistered mode.
19.07.2002 BUILD 1018
DNS mapping modified: src IP address of responses to mapped queries
set to the NAT32 private IP address of the interface.
08.07.2002 BUILD 1017
Minor changes only.
06.07.2002 BUILD 1016
Ndis3log command added. Usage: ndis3log [c|w]
No args: print contents of ndis3log buffer
Arg 'c': check log, copy output to buffer.
Arg 'w': check log, copy output to buffer, wait for further output
Ndis3log.exe fixed to not crash on 9X platforms.
Admin buf fixed: IP addresses saved incorrectly in Registry.
Admin display modified.
Admin now displays bytes received from Internet for a private
machine.
Admin default is now " enabled " .
Slowtimer now adjusts sleep time for processing delays.
04.07.2002 BUILD 1015
Admin saves details to registry each minute.
Setproms command added. Silent version of setprom.
03.07.2002 BUILD 1014
Umap port range bug fixed.
Dots no longer printed for each ICMP source quench sent.
23.06.2002 BUILD 1013
Not released.
20.06.2002 BUILD 1012
Bandwidth Limiting modified.
Umap command now accepts a Destination Port Range as its third
argument.
Active thread now actually sends a UDP packet through Winsock to
prevent Windows disconnection because of inactivity.
11.06.2002 BUILD 1011
ICMP code modified.
10.06.2002 BUILD 1010
Any number of Internet Interfaces and default routes supported.
Registered version balances Internet traffic over all Internet
interfaces. The best interface is the one over which the least
number of bytes arrived during the last second.
Wintrace now run as a thread when started from NAT32 menu.
TDI command -R arg added. Writes Windows Routing Table to TDI_Buffer.
Test command added. Prints the TDI_Buffer.
Command usr added. Automatically configures the Primary interface
for the 3Com U.S. Robotics Cable Modem VSP.
Command rtdump added. Dumps the NAT32 Routing Table, pointers and all.
Bandwidth Limiting for administered hosts added (experimental).
All dialog boxes (except Service Settings) now run in their own
threads.
Packet timestamps added.
01.06.2002 BUILD 1009
Interface Selection dialog redone.
Interface Configuration dialog changed.
31.05.2002 BUILD 1008
Log files are now appended to rather than created each time NAT32
starts.
Connection open and close logged to PPP.LOG.
29.05.2002 BUILD 1007
Interface selection on the basis of packets received during last
second.
Checkmtu bug fixed.
Interface metric bug fixed.
25.05.2002 BUILD 1006
UDP bug fixed: UDP connections with checksum failed.
DNS mapping: change destination address and then process as a
normal UDP packet.
14.05.2002 BUILD 1005
TCP bug fixed: local TCP connections failed.
13.05.2002 BUILD 1004
Packets destined for private networks for which NAT32 has no
network-specific route are now discarded in IPPROC, unless the
default gateway is a private IP address.
A provisional pmap entry is deleted if ipputp sends the packet on
a non-mapped interface.
08.05.2002 BUILD 1003
DNS changes not logged to nat32.log
New NDIS3PKT.386
30.04.2002 BUILD 1002
Port map deletion is now interface specific.
Configuration bug fixed: only changing a Primary Interface number
prompts for a confirmation.
Route selection mechanism modified. The pmap table is searched only
once.
24.04.2002 BUILD 1000
This is the initial Build and was generated from NAT32P Version 1.4
Build 4060. Please see README.TXT of that build for details.
NAT32E differs from NAT32P in that ALL mapping options are now
interface-specific.
In addition, multiple default routes are supported, each of which is
distinguished via an optional Source Address and Metric.
A Source Address is an IP Address (or Network Address) which can be
used to influence a routing decision. For example, if two default
routes exist, one which specifies a Source Network Address of
172.16.2.0, then only traffic from private machines on that network
will be sent to the Internet via that default route. All traffic from
other networks will be sent via the other default route.
A Routing Metric can be specified so that traffic from any private
machine can be routed via different default routes. The first
default route has a Metric of 15, the second a Metric of 14 and so
on. To use this feature, configure the preferred default route as
the Primary Interface, the next default route as Primary Backup 1
and so on.
Note that the Autodial mechanism (at present) works only for the
Primary Interface, not for any Primary Backup Interfaces. To dial
a Primary Backup Connection, use the Windows Dial-Up Networking
user interface to dial (or hangup) the second connection.
ICS Configuration 98SE/ME
NAT32 Reference
Manual
HOW TO configure NAT32 in the presence of Windows 98SE/ME Internet
Connection Sharing.
The NAT32 Interface Selection dialog box lists all Network adapters
known to Windows. When an adapter has an X in front of its name, NAT32
has detected a problem with it and displays a red
warning message in the Adapter Details field. Such adapters
should normally not be selected for use by NAT32.
& nbsp;
On a system with Windows Internet Connection
Sharing installed, the NAT32 Interface Selection dialog box
will detect all ICS adapters and flag them as problem devices.
The Dial-Up Adapter in this example had been configured under Windows
to act as the ICS Internet Adapter. This will have caused Windows to bind
a special device driver to that adapter in order to provide the ICS functionality.
Unfortunately, that device driver is incompatible with NAT32's NDIS3PKT
driver and so NAT32 marks that adapter as the Windows
ICS Internet Adapter . This presents a problem if you would like
to use NAT32 to share that adapter.
The second SURECOM adapter is this example has also been marked as disabled.
When you click that adapter, you will see the message Windows
ICS Private Adapter . It is safe to use that adapter as your private
LAN adapter (even though it has an X in front of it) if you take
further steps as outlined below.
The Internet Connection Sharing adapter has also been added by Windows
ICS, and it is also flagged as a problem device. Fortunately, this adapter
does not interfer with NAT32, so you can safely ignore it.
But if you do wish to use NAT32 to share the Dial-Up Adapter,
the following solutions can be applied. & nbsp;
Method 1: Uninstall Windows ICS via Control Panel , Add/Remove
Programs ,
Windows Setup .
This has the disadvantage that all your ICS Port Mappings in the Registry
at
& nbsp; & nbsp; & nbsp; HKLM\System\CurrentControlSet\Services\ICSharing\Mappings
may be unavailable if you ever decide to use ICS again. But it is by
far the simplest solution to the problem. After you have uninstalled ICS,
reboot the machine and then reconfigure NAT32.
& nbsp;
Method
2: Leave ICS installed, but you run icssetup.exe
or icsmgr.exe
to select a NULL adapter as the Internet ICS Interface.
This is done by selecting the blank entry in the first combo box. Alternatively,
you could select any adapter you know you don't need, such as a USB adapter
which is not connected to the system. In the case of RASPPPoE configurations,
you could even select the LAN adapter which is connected to the ADSL modem,
because that adapter is not actually used by Windows for TCP/IP, the RASPPPoE
adapter is used instead.
Then click OK and Windows will request a reboot. Then start NAT32 again
and you will then be able to configure it to use the desired adapter as
the shared interface to the Internet. & nbsp;
In this example, Windows ICS is using the second SURECOM adapter as
its private LAN adapter. It is marked with X by NAT32 but you can use it
as NAT32's private LAN adapter if you turn off the Windows ICS DHCP server
and IP Routing. The status commands shown below allow you to do this from
the NAT32 Console.
& nbsp;
& nbsp;
NAT32 ICS Status Commands
To turn off the Windows DHCP Server , run the NAT32 command wdhcpd
off and then reboot Windows.
To turn off Windows ICS , run the NAT32 command ics off
and then reboot Windows.
To turn off Windows IP Forwarding , run the NAT32 command winrt
off and then reboot Windows.
[Home]