NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  Client32 TCPIP.NLM version 1.10D
README FOR:  TCP32D.EXE

NOVELL PRODUCTS and VERSIONS:
TCPIP - Client32 for DOS/Windows 2.1
TCPIP-CLNT (LWP 5.0)-NW410

ABSTRACT:

Current release of TCPIP.NLM for Client32 (Dos/Win31).  Resolves many issues
and adds more robust DHCP functionality.  Also included are the current
Winsock.dll and Wlibsock.dll.



 -----------------------------------------------------------------
 DISCLAIMER
 THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.  NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.  HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
 -----------------------------------------------------------------


ISSUE: 

Problems resolved with this release of TCPIP

  PING would stop working.  Resources are now made available without using an
alloc.

  Resolved a problem with doing an FTP file transfer to a fast client (ie
200MHZ Pentium) using client32.  If the file you where dong a get on was larger
that the TCP_RCV_WINDOWSZ the application would stop.  This had to do with SEND
returning EWOULDBLOCK and posting a message either to WINSOCK.DLL or directly
to WSOCK32.DLL (for ipx gateway client, Win95).  A new WINSOCK.DLL is included
to resolve this.  For the ipx/ip gateway client a new SPX_SKTS.NLM is provided
 also.

  Added a new confgiuration function for NET.CFG related to cahing DHCP
information on the client32.  DHCPCACHEIP=NO can be added to the tcp protocol
section to ignore caching when loading TCPIP.NLM.

  Resolved a problem with DHCP packet retransmission interval being to fast.
The client32 TCPIP.NLM now complies with RFC 1541section 4.1 in retransmitting
DHCP packets at the intervals specified in the RFC.

  Resolved a problem of the client not updating the router information it has
when recieving a DHCP ack packet that contains new or changed router
information.

  Problems resolved with this version of Wlibsock.dll :

  Resolved problem of not being able to do a DNS resolution using IPResolver of
an alias name that begins with a numeric character.

  Resolved issues regarding sequential DNS queries :
  The RESOLV.CFG now supports up to 8 name servers.  When a name resolution is
started, the TCP/IP protocol stack currently queries all 8 servers at the same
time.  Users may want to change this so that the name servers are queried
sequentially.  The following enhanced commands may be placed anywhere within
RESOLV.CFG.

        Syntax: SEARCH DNS HOSTS SEQUENTIAL
  This example searches the DNS first, then the HOSTS file, and search the DNS
servers sequentially.

        Syntax: SEARCH DNS
  This searches DNS only and makes concurrent queries to the DNS servers.

        Syntax: SEARCH HOSTS
  This example searches the \NET\TCP\HOSTS file only.

        Syntax: SEARCH HOSTS DNS SEQUENTIAL
  This example searches the HOSTS file first, then the DNS servers
sequentially.  Using Ping under DOS, both the hosts file and DNS servers are
queried.  If the answer is found in the HOSTS file, that is returned to the
application.  Queries are still sent to the DNS servers.  Using IPResolver in
windows (or any other windows based application that does DNS resolution), if
the answer is in the hosts file no queries will be sent to the DNS servers.

        Syntax: SEARCH DNS HOSTS
  This is the default behavior, unless overridden.

  Problems resolved in previous verisons of TCPIP.NLM that are included in this
release.

    There is no current utility for the Client 32 (DOS/WIN31) workstation that
can display the users IP address, MAC address, hostname, DHCP address, lease
time, etc.  TCPMON.EXE is released with version 1.10C of TCPIP.NLM.  TCP/IP and
DHCP information can be displayed with this utility.  TCPMON.EXE will only work
with TCPIP.NLM version 1.10C or higher and must be run from windows.  Limited
support will be provided on this utility.

    To display DHCP information, run TCPMON.EXE, choose the IP/ARP tab, Click
the address button and then double click on your IP address.

    Added functionality : When the Client32 (DOS/WIN31) is using DHCP to get
its IP address, and the connection to the DHCP server has been lost, the client
is unable to maintain its TCPIP address and network connections if the
workstation has been rebooted.  The DHCP information is now cached to disk and
retrieved at bootup time.  A rebind request is sent out with the broadcast. 
This allows the
   workstation to maintian a TCPIP connection even though the DHCP server is
not working.  This information can be viewed with tcpmon.exe and is stored in
the file DHCPXXX.001.  Deleting this file will cause the Client32 to do a new
DHCP Discover when the workstation is rebooted.

    The win 3.x install places the load command for tcpip.nlm right after the
load command for the token ring lan driver CNTR2000.LAN in STARTNET.BAT.  On 4
meg token rings, the tcipip.nlm does not load, complaining that it cannot bind
to the lan driver.  But if you wait for a few seconds (say, insert a pause
between the lan driver load and the stack load), everything works fine.  This
problem with not working the resume/suspend information correctly is now
resolved.

    Unable to connect to the IPX/IP GateWay Server over the Remote Access
Dial-in via Client 32.  Resolved in version 1.10C or above of TCPIP.NLM.

    Added Functionality to allow for RCB routine's getmyipaddress, setipinfo,
and getipinfo.

    Resolved problem with not displaying IP address when binding to second
network interface through DHCP.  This only happens when there are two lan
boards. While loading tcpip.nlm the first network interface is able to get its
configured IP address correctly, but the second network interface tries to get
its IP address through DHCP which fails to display the IP address. The rest of
the information such as IP Network Mask and Default Router show correctly.

    TCP/IP-32 now supports designation of the client hostname in the BOOTP or
DHCP request.  The 16-bit stack (TCP16) supports this by using the current
NetWare user connection as the hostname.  This release provides a NET.CFG
controlled designation of the client-side hostname.
    The new syntax for designating the client-side hostname is:

          Protocol TCPIP
                  HOSTNAME john_doe

    When assinging IP address using DHCP from a NT Server - Entering windows
causes lose of DNS and Router information.  This release provides a new
TCPIP.NLM that no longer causes DNS and router information to be lost when
entering windows.

    This release has helped certain occurances of the Black Screen of Death
when exiting windows to dos and then re-entering windows and you are getting
your IP address using DHCP from an NT Server.


Self-Extracting File Name: TCP32D.EXE

Files Included     Size     Date      Time

..\
      TCP32D.TXT     (This file)
     INSTALL.BAT            1846         2-12-97      5:36:58 pm
    NOVGWP16.EXE           92160          1-8-97      7:51:46 pm
        PING.EXE           54664          1-9-97      7:37:46 pm
    SPX_SKTS.NLM           41918         1-16-97     10:01:38 pm
       TCPIP.MSG            4582         1-27-97     10:10:26 pm
       TCPIP.NLM          215222         1-27-97     10:10:34 pm
      TCPMON.EXE          344392         1-27-97     10:10:36 pm
     WINSOCK.DLL           81408          2-5-97      3:18:50 am
    WLIBSOCK.DLL           46268          2-4-97     12:39:48 am


Installation Instructions:

Extract the files by executing TCP32D.EXE in a directory other that the one
that contains you current TCPIP.NLM.  If your TCPIP.NLM is in the default
"c:\novell\client32" directory simlpy type install from the directory that has
the extracted files.  If your TCPIP and Client files are not in the default
directory, type install followed by the directory your TCPIP and Client files
are in (ie "install c:\other\dir").

  A total of 8 files will be copied.

 The files NOVGW16.EXE and SPX_SKTS.NLM have been provided for those customers
running the IPX/IP Gateway client.


 -----------------------------------------------------------------
 Any trademarks referenced in this document are the property of their
respective owners.  Consult your product manuals for complete trademark
information.
 -----------------------------------------------------------------

