                       LAN WorkGroup v4.1
                  LAN WorkGroup Release Document
                          SWUPDATE.TXT

Copyright (c) 1993 Novell, Inc.   All Rights Reserved.

THIS WORK IS SUBJECT TO U.S. AND INTERNATIONAL COPYRIGHT LAWS AND
TREATIES.NO PART OF THIS WORK MAY BE USED, PRACTICED, PERFORMED,
COPIED, DISTRIBUTED, REVISED, MODIFIED, TRANSLATED, ABRIDGED,
CONDENSED, EXPANDED, COLLECTED, COMPILED, LINKED, RECAST,
TRANSFORMED, OR ADAPTED WITHOUT THE PRIOR WRITTEN CONSENT OF
NOVELL, INC.  ANY USE OR EXPLOITATION OF THIS WORK WITHOUT
AUTHORIZATION COULD SUBJECT THE PERPETRATOR TO CRIMINAL AND CIVIL
LIABILITY.

This file documents software problems that have been noticed or
that changes have been made since publication of the LAN WorkGroup
manual set.  This release document includes the following sections:

     BOOTPCHK UTILITY
     BOOTP FORWARDING AND LAN WORKPLACE FOR MACINTOSH
     BOOTPD
     BOOTPFD
     HOST PRESENTER
     LWPCON UTILITY
     REMOTE SHELL APPLICATION
     SERVING FTP APPLICATION
     SLIP_PPP DRIVER
     SNMP UTILITY
     TELAPI, TSU, AND PROCOMM PLUS
     TNVT220 UTILITY
     WGSETUP UTILITY
     RELATED README FILES

Please use the search features of your text editor to jump directly
to a section of interest.

===================================================================

BOOTPCHK UTILITY:
~~~~~~~~~~~~~~~~

The BOOTPCHK utility is executed from a client workstation and is
used to check the BOOTP server's ability to respond to requests and
to display the configuration information returned to a client
workstation.

The BOOTPCHK utility can do the following:

     Display a client's connection information returned from the
     BOOTP server. If more than one BOOTP server responds, BOOTPCHK
     displays each response in the order received.

     Display the total number of BOOTP return packets that were
     examined.

     Display each BOOTP server that is currently accessible by the
     client and list the IP address for each server.

     Display any BOOTP packet conflict information, if the returned
     configuration packets from different servers are dissimilar.

BOOTPCHK determines which BOOTP servers are running and sends out
BOOTP request packets to each server.  It sends out two packets to
each BOOTP server by default.  BOOTPCHK then examines the packets
it receives back, displays the parameter settings received in each
response packet, and compares the information to detect conflicts.

BOOTPCHK is a DOS command-line utility that you can run as follows:

    C:\> BOOTPCHK <Enter>

You can specify the number of packets BOOTPCHK sends to each BOOTP
server by including the -Pn command-line option.  For example, use
the following command to send four request packets to each server:

    C:\> BOOTPCHK -P4 <Enter>

By default BOOTPCHK waits 2 seconds to receive the reply packets.
If your network is complex, you might want to increase the amount
of time BOOTPCHK waits using the -Tn command-line option.  The n
parameter is the number of seconds, from 1 through 60 inclusive.
For example, use the following command to wait 5 seconds to receive
the reply packets:

    C:\> BOOTPCHK -T5 <Enter>

You can also specify the type of network for which you want to
check BOOTP responses, as follows:

     -NT specifies a token ring network.

     -NA specifies an ARCnet network.

     -NE specifies an Ethernet network.

If you do not include the -N option, an Ethernet network is
assumed.  For example, the network for workstation fredpc has only
one BOOTP server.  Workstation fredpc runs BOOTPCHK at his client
workstation and receives the response shown below.

IP Address = 122.44.9.7                   IP Net Mask = 255.255.0.0
Default Gateway = 122.44.3.97             Bootp Server = 122.44.6.1
Domain Server Address = 122.44.6.57 122.44.3.6
Hostname = fredpc                         Domain Name = acme.com
-------------------------------------------------------------------
IP Address = 122.44.9.7                   IP Net Mask = 255.255.0.0
Default Gateway = 122.44.3.97             Bootp Server = 122.44.6.1
Domain Server Address = 122.44.6.57 122.44.3.6
Hostname = fredpc                         Domain Name = acme.com

Press any key to continue...

If the BOOTPCHK response fits entirely on one screen, BOOTPCHK
displays all of the information at once and does not pause for a
keypress.

The response shows that two BOOTP response packets were received
from the server in response to the two request packets sent by
BOOTPCHK.  The BOOTPCHK display includes the following information
(the corresponding LWGCON term is shown in parentheses, if
different):

     IP Address
     IP Net Mask (Subnetwork mask)
     Default Gateway (Router)
     BOOTP Server
     Domain Server Address (Primary, Secondary, and Tertiary DNS
     name servers)
     Hostname (Workstation name)
     Domain Name

When user Fred presses a key on workstation fredpc in response to
the display, BOOTPCHK compares the two responses.  If no conflicts
are found, information similar to the following is displayed.

     2 BOOTP packets have been examined.
     The following BOOTP servers are currently running:

                     122.44.9.5

     ===> No conflicting BOOTP packets have been found.

     C:\>

If conflicts are found, information similar to the following is
displayed.  In this example, the network for workstation fredpc now
has a second BOOTP server, and an attempt has been made to set up
BOOTP forwarding.

The following conflicting BOOTP packets have been found.

packet 1:
    IP Address = 122.44.9.7       ===>Bootp Server = 122.44.9.5
    Default Gateway = 122.44.3.97     IP Net Mask = 255.255.0.0
===>Domain Server Address = 122.44.6.57 122.44.3.6
    Hostname = fredpc                   Domain Name = acme.com

packet 2:
    IP Address = 122.44.9.7        ===>Bootp Server = 122.44.36.2
    Default Gateway = 122.44.3.974     IP Net Mask = 255.255.0.0
===>Domain Server Address = 122.44.36.1
    Hostname = fredpc                  Domain Name = acme.com

The Bootp Server field displays the IP address of the BOOTP server
that sent the response packet.

The arrows ( ===> ) indicate where a conflict was detected.  In
this example, the conflict is between the two BOOTP servers' DNS
server addresses.  Packet 1 returned 122.44.6.57 and 122.44.3.6,
but Packet 2 returned 122.44.36.1.  From this information, the
workgroup administrator can determine what LWGCON changes are
necessary to which BOOTP table.

BOOTPCHK can detect conflicts in only one pair of response packets
at a time.  If your network has more than two BOOTP servers, and
conflicts are found, run BOOTPCHK again after correcting the
conflicts to determine whether other BOOTP servers are also
returning conflicting information.  When BOOTPCHK replies that no
conflicts have been found, the responses of all currently operating
BOOTP servers are properly synchronized for the client.

===================================================================

BOOTP FORWARDING AND LAN WORKPLACE FOR MACINTOSH:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

LAN WorkGroup provides BOOTP and BOOTP forwarding services for LAN
WorkPlace for Macintosh under the following conditions:

     If your Macintosh client is configured to use the Novell
     TCP/IP transport provided with LAN WorkPlace for Macintosh and
     you are using BOOTP forwarding, BOOTP requests can be
     forwarded to a maximum of five successive BOOTP forwarders.
     That is, any BOOTP broadcast request originating on one IP
     subnet can be forwarded through up to five other subnetworks
     (or five hops) before reaching a BOOTP server.

     If your Macintosh client is configured to use the Macintosh
     TCP/IP transport provided with LAN WorkPlace for Macintosh and
     you are using BOOTP forwarding, BOOTP requests can be
     forwarded to a maximum of two successive BOOTP forwarders.
     That is, any BOOTP broadcast request originating on one IP
     subnet can be forwarded through up to two other subnetworks
     (or two hops) before reaching a BOOTP server.

For details on configuring Macintosh clients to use BOOTP, refer to
Appendix A of the LAN WorkPlace for Macintosh User's Guide.

===================================================================

BOOTPD:
~~~~~~

BOOTPD is an NLM that runs on the workgroup server.  It responds to
BOOTP requests from client workstations for their TCP/IP
configuration information.  Client workstations send BOOTP request
packets when WGTCPIP.EXE or TCPIP.EXE is run using a NET.CFG file
that does not include an ip_address setting in the Protocol TCPIP
section of the workstation's NET.CFG file.

The BOOTPD server requires a properly configured and loaded
PKERNEL.NLM.  PKERNEL is configured automatically during the server
installation.

The BOOTPD server is loaded either manually from the workgroup
server's command line or automatically (when the server is
activated) from the server's AUTOEXEC.NCF file.

When BOOTPD is loaded, it reads the contents of the BOOTPTAB file
and stores this information in memory.  BOOTPD checks the BOOTPTAB
file each time it receives a BOOTP request packet from a client
workstation and rereads BOOTPTAB if the file contents have changed
since it was last read.


BOOTPD Command-Line Options:
***************************

When you run BOOTPD, you can include any of the following command-
line options to enable optional features:

     Enabling BOOTP forwarding (-F<address> option)

     Activating BOOTPD transaction logging (-V option)

     Deactivating BOOTPD logging (-Q option)

You can include these options in the NFSSTART.NCF file to load
BOOTPD automatically when you start your server.  The NFSSTART.NCF
file is created by the server installation program.


Enabling BOOTP Forwarding
=========================

To enable forwarding of client workstation BOOTP request packets to
another BOOTP server, include the -F<address> option.  This option
instructs BOOTPD to forward any BOOTP requests that its BOOTPTAB
file is not configured to handle to the BOOTP server specified by
address.

Use this option if you want BOOTPD to service certain requests and
forward other requests to another BOOTP server.  For example, you
might want a particular workgroup server running BOOTPD to respond
to BOOTP requests from one subnetwork but send requests from other
subnetworks to a different workgroup server.

If you want to forward all BOOTP request packets to a different
server, you can use the simpler BOOTPFD server.  Refer to the LAN
WorkGroup Installation and Configuration Guide for additional
information about BOOTP forwarding.

The server to which requests are forwarded can be up to five hops
(network links) away from the forwarding server.  The address
parameter is the IP address of the server to which requests are
forwarded, in dotted decimal notation.


Activating BOOTPD Transaction Logging
=====================================

Whenever a client workstation request is received and forwarded to
another BOOTP server, BOOTPD displays the response on the monitor
screen before forwarding it to the workstation.  This display can
be useful to determine whether the BOOTP system is configured
correctly.

For example, the BOOTP server for workstation janepc might be
configured to forward requests to another BOOTP server, 122.44.9.5.
When the workstation is restarted, the reply from BOOTP server
122.44.9.5 is displayed on the BOOTPD monitor screen.

Below is an example of the BOOTPD monitor display.

IP Address = 122.44.9.12                  IP Net Mask = 255.255.0.0
Default Gateway = 122.44.3.97             Bootp Server = 122.44.6.1
Domain Server Address = 122.44.6.57 122.44.3.6
Hostname = janepc                         Domain Name = acme.com

The display includes only the information that is configured in the
BOOTP table by LWGCON.  If the label for the entry is the full
domain name for the workstation, the domain name is displayed as
well as the hostname.


Deactivating BOOTPD Logging
===========================

The -Q option runs BOOTPD is quiet mode.  It deactivates BOOTPD
logging.


Activating Debugging Mode
=========================

The -D option activates debugging mode and displays and logs
engineering level information.


Unloading BOOTPD:
****************

To unload the BOOTP server, use the following command line from the
NetWare prompt:

     : UNLOAD BOOTPD <Enter>

===================================================================

BOOTPFD:
~~~~~~~

The BOOTPFD NLM forwards all requests from client workstations for
their TCP/IP configuration information to a centralized server
running the BOOTPD NLM.

BOOTPFD is an NLM that runs on NetWare v3.11 or greater.

Centralizing your TCP/IP configuration information on a single
BOOTP server lets you set up a database of information that only
has to be updated at one location.

The BOOTPFD server does not require the PKERNEL NLM.  Copying the
BOOTPFD.NLM file and running it on other NetWare servers is
permitted under your LAN WorkGroup license.

The BOOTPFD NLM is loaded either manually from the NetWare server's
command line or automatically (when the server is activated) from
the server's AUTOEXEC.NCF file. These procedures are the same as
for BOOTPD.

Do not attempt to run both BOOTPD and BOOTPFD simultaneously on the
same NetWare server.

Refer to the LAN WorkGroup Installation and Configuration Guide for
additional information about BOOTPFD.


BOOTPFD Command-Line Options:
****************************

The BOOTPFD NLM has the following command-line parameters; the
first is required, the others are optional:

     Directing BOOTP forwarding (-F<address> parameter)

     Activating quiet mode; suppressing logging to the log file (-Q
     option)
     
     Activating verbose mode (-V option)
     
You can include these options in the AUTOEXEC.NCF or the
NFSSTART.NCF file to load BOOTPFD automatically when you start your
server.


Directing BOOTP Forwarding
==========================

The BOOTPFD server does not respond to BOOTP request packets.  It
must forward all TCP/IP configuration request packets to a
centralized BOOTP server.  To direct the forwarding of client
workstation BOOTP request packets to a BOOTP server, you specify
the IP address of the centralized BOOTP server using the -
F<address> parameter.  This parameter instructs BOOTPFD to forward
the BOOTP requests it receives to the BOOTP server specified by
address.

The server to which requests are forwarded can be up to five hops
(network links) away from the forwarding server.  The address
parameter is the IP address of the server to which requests are
forwarded, in dotted decimal notation.


Displaying the BOOTPFD Screen
=============================

Whenever a client workstation request is received and forwarded to
the centralized BOOTP server, BOOTPFD displays the response on the
monitor screen before forwarding it to the workstation, and writes
it to the SYS:ETC\BOOTP.LOG file (or alternately to the BOOTP.BAK
file if the BOOTP.LOG file is full) in the same directory.  It also
logs the replies before sending them to the workstation.

Below is an example of the BOOTPFD monitor display.

04/14/93 08:19:38
   Sending reply to <00001b1e62f3> as <130.57.226.103>.
04/14/93 08:19:45
   Receiving request from <00001b1e62f3> on subnet <130.57.224.0>.

The display includes only the information that is configured in the
BOOTP table on the centralized BOOTP server.  If the label for the
entry is the full domain name for the workstation, the domain name
is displayed as well as the hostname.


Deactivating BOOTPFD Logging
============================

The -Q option runs BOOTPFD is quiet mode.  It deactivates BOOTPFD
logging.


Unloading BOOTPFD:
*****************

To unload the BOOTPFD server, use the following command line from
the NetWare prompt:

     : UNLOAD BOOTPFD <Enter>

===================================================================

Host Presenter:
~~~~~~~~~~~~~~

When you click the Host Presenter icon and open the Windows File
Properties menu item of the File Menu, the default Program Item
Properties dialog box appears.

From this dialog box, you can enter any of the following options in
the Command Line text box:

  /profile filename.php
  /host hostid
  /termtype termid

For example:

  /profile xconsole.php
  /host ca
  /termtype vt220

You can enter a Shortcut Key sequence by selecting the Shortcut Key
text box and entering a valid Windows sequence (for example, <Ctrl-
Shift-H>).

===================================================================

LWPCON UTILITY:
~~~~~~~~~~~~~~

The controlCommunity parameter in the Protocol SNMP section of the
NET.CFG file is shown in the NETCFG.TXT file in the <vol>:NET
directory. This parameter is designed to provide write permission
to LWPCON clients with the same community setting when attaching to
a LAN WorkGroup client workstation (remote host) running the SNMP
agent.

In the current release, attempts to change editable entries in a
remote host's Address Translation Table fail, regardless of how the
controlCommunity parameter is set.

Refer to the LAN WorkPlace for DOS Administrator's Guide for more
information about LWPCON and the SNMP agent.

===================================================================

REMOTE SHELL APPLICATION:
~~~~~~~~~~~~~~~~~~~~~~~~

If you have a short username (six characters or fewer), the Remote
Shell application does not read the username correctly from the DOS
environment.

This is not a problem as long as you specify a UserName value in
the [Remote Shell] section of the LWP.INI or LWP_GLBL.INI file.
For example:

  [Remote Shell]

    UserName=Ada

Refer to the LAN WorkPlace for DOS Administrator's Guide for
additional information about configuring Remote Shell.

===================================================================

SERVING FTP APPLICATION:
~~~~~~~~~~~~~~~~~~~~~~~

When using the Access Restrictions option of Serving FTP, the
following security precautions are recommended:

     Enter your own username and password in the Restrict Access
     dialog box to satisfy the minimum requirement of the feature.

     Enter any other username without a password to provide
     restricted (guest) access to your workstation. By using the
     Change Home Directory menu item from the Options menu you can
     define the access directory for the guest.

If you provide password-protected access to other users, they gain
complete access to your workstation and all of its file systems. If
you grant these rights, Novell recommends that you do so with
caution. Refer to the LAN WorkPlace for DOS User's Guide or the LAN
WorkPlace for DOS Administrator's Guide for more information.

===================================================================

SLIP_PPP DRIVER:
~~~~~~~~~~~~~~~

SLIP_PPP.COM is an ODI driver for the SLIP and PPP serial-line
protocols. All serial ports (COMn: ports) on IBM-compatible PCs
(workstations) are based on Universal Asynchronous
Receiver/Transmitters (UARTs). Some UARTs, such as the 8250 and
16450, operate one byte at a time. This requires the workstation
CPU to stop other operations to read each byte before it is lost.
This is not a problem when you use the DOS utilities. You may
experience problems, however, with the Windows applications at baud
rates above 2400.

If your workstation has an 8250 or 16450 UART, Novell recommends
that you use the DOS utilities (for example, FTP or RCP for file
transfer) rather than the Windows applications (Rapid Filer, for
example).

The 16550A UART is a more efficient chip because it processes up to
16 bytes of data at a time. This prevents the loss of data and
provides faster response time. Windows applications, such as Rapid
Filer, should run reliably across the SLIP_PPP driver if your
workstation has a 16550A UART. (The 16550A generally performs
better than the earlier 16550.)

NOTE: You can run the Microsoft Windows v3.1 diagnostic utility,
      MSD.EXE, to identify the UART chip your serial ports are
      using. You must exit Windows to run this utility.

The following table summarizes these UART chip and data transfer
recommendations.

UART Chips for the SLIP_PPP Driver
-------------------------------------------------------------------
UART Chip      Data Transfer        Data Transfer
               Using DOS Utilities  Using Windows Applications
-------------------------------------------------------------------
8250, 16450    All baud rates       Less than or equal to 2400 baud

16550, 16550A  All baud rates       All baud rates
-------------------------------------------------------------------

You may need to install an additional serial expansion board in
your workstation or purchase a modem that includes the 16550 or
16550A chip to optimize the performance of Windows applications
over the SLIP_PPP driver.

The SLIP_PPP driver supports PAP (Password Authentication Protocol)
authentication for uppercase login names and uppercase passwords
only. Even if the user specifies lowercase letters, the SLIP_PPP
driver converts them to uppercase during authentication
negotiation.

The following table provides client NET.CFG configuration settings
for various methods of dialing from a SLIP/PPP client to a SLIP/PPP
router, dialup-service, or server-workstation. If the remote host
requires the dial-in client to provide name and password for login,
before bringing up the SLIP/PPP connection, use the second, third,
or fourth configurations from the following table.

SLIP_PPP Configuration Scenarios
-------------------------------------------------------------------
Configuration Scenario               direct Setting    open Setting

Using SLIP_PPP.COM with
autodial using the dial setting            No          Active

Using SLIP_PPP.COM and DIALUP              Yes         Passive

Using a third-party dialer when
the SLIP_PPP driver is loaded
after the connection is set up             Yes         Active

Using a third-party dialer when
the SLIP_PPP driver is loaded
before the connection is set up            Yes         Passive

Using a direct back-to-back
connection (NULL modem) and the
SLIP_PPP driver                            Yes         Active
-------------------------------------------------------------------

If the open setting is passive during the loading of the SLIP_PPP
driver, and if the server side did not initiate configuration
negotiation, the user must initiate SLIP/PPP negotiation using the
SLIP_PPP command with the S option. Refer to the LAN WorkPlace for
DOS Administrator's Guide for more details about SLIP_PPP
configuration.

===================================================================

SNMP UTILITY:
~~~~~~~~~~~~

Loading and Unloading:
*********************

If you load SNMP from a DOS window, make sure to unload it using
the SNMP -U command before closing the DOS window.

If you load SNMP from the DOS prompt before starting Windows, do
not unload it from a DOS window.

If you load and unload SNMP from the DOS prompt, no additional
action is necessary.


Tabs in the NET.CFG File:
************************

The Protocol SNMP section of the NET.CFG file, shown in Figure 3-8
of the LAN WorkPlace for DOS Administrator's Guide, does not accept
tab characters before parameter settings (tab and space characters
are normally allowed in the NET.CFG file).

If you use tabs before the parameters in the Protocol SNMP section,
SNMP uses the default values for those parameters.

===================================================================

TELAPI, TSU, AND PROCOMM PLUS:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

When running TELAPI, TSU, and DataStorm's Procomm Plus Network v2.0
software, use the BAPI interface. Do not use the Int 14H interface.

===================================================================

TNVT220 UTILITY:
~~~~~~~~~~~~~~~

The bottom line of the TNVT220 setup screens (just above the
TNVT220 status line) currently reads:

  Press numeric Enter or + key to take this action ...

If you have problems with your keyboard mapping (for example, your
keyboard does not have a numeric <Enter> key), you must make
appropriate changes in your EXTMAP.TXT mapping file (or current
mapping file for your workstation). For example:

  Plus = NULL;      Enter = Num Plus;

After you update your mapping file, you must run the KEY220 utility
as described in the LAN WorkPlace for DOS Administrator's Guide.

If you have an enhanced keyboard, the numeric <Enter> key works but
the numeric <+> key does not. The numeric <+> key is intended for
the AT and XT keyboards; these keyboards do not have a numeric
<Enter> key.

===================================================================

WGSETUP UTILITY:
~~~~~~~~~~~~~~~

WGSETUP does not copy required font files correctly onto the LAN
WorkGroup server when installing with shared Windows.  When running
WGSETUP on a workstation that is using a network based shared
installation of Windows, the fonts are listed in the Control Panel
Font dialog box, but the files are not in the Windows directory.

The LAN WorkGroup administrator must copy the .FON files from the
<vol>:NET\WINDOWS\SYSTEM directory to the shared directory for
Windows.  Each workstation user must then run Control Panel to Add
the appropriate font file (for example, NOV_VGA) to the workstation
configuration.  In the Control Panel --> Font --> Add --> Add fonts
dialog box, make sure each user selects the .FON file from the
shared Windows directory and UNCHECKs the Copy Fonts to Windows
Directory check box.


WGSETUP Logging:
***************

The WGSETUP program creates a logfile for WGSETUP in the
<vol>:NET\BIN directory on the server during server setup.
Whenever a user attempts to run WGSETUP, the user's login name and
information about the results of the user's attempt are recorded in
this logfile.  This logfile is named WGSETUP.LOG.

Below are examples of the entry types from the WGSETUP log file.

  12-15-92 09:17:46 Setting up, joyce, using configuration, joyce
  12-15-92 09:25:33 joyce was successfully set up.
  01-18-93 13:23:05 shirley set up failed. Unknown configuration.
  01-20-93 08:10:55 fred set up failed. Entry is locked.

Only the SUPERVISOR has the trustee rights necessary to view the
WGSETUP.LOG file. Client workstation users do not have filescan
trustee rights and do not see WGSETUP.LOG if they list the
<vol>:NET\BIN directory.

===================================================================

RELATED README FILES:
~~~~~~~~~~~~~~~~~~~~~

For additional information, see the following text files:

  DOCUPDTE.TXT (for information about documentation updates)
  LWGLWP.TXT (for information on running LAN WorkPlace and LAN
  WorkGroup on the same workstation)
  NFSV12B.TXT (for upgrade information on NetWare NFS v1.20B)
  NETCFG.TXT (for information about the NET.CFG file)
  README.TXT (for information installation and configuration)
     
All of these files are located on the first installation diskette
and copied to the <vol>:NET directory.  The README.TXT file is also
copied to the SYS:ETC\INSTALL directory as LWG.TXT.  If the
information in the printed manuals, online help, or in the text
files does not answer your questions, contact your Novell-
authorized reseller for assistance.

