ShivaRemote Software Configuration Notes Contents

  ShivaRemote supports a wide variety of network software
  for DOS and Windows. Supported protocols are Novell IPX,
  TCP/IP, NetBEUI, and LLC. This document describes how to
  install and configure a number of network software
  packages.
  
  For help on a particular package, see its section title
  below. The following list describes all of the topics in
  this document, in the order in which they appear.
  
     FTP PC/TCP and OnNet
     IBM Network Software (LSP, DLR, etc.)
     Microsoft TCP/IP-32
     Microsoft Windows for Workgroups 3.11
     NetManage Chameleon
     Novell LAN Workplace
     Novell NetWare
     Wollongong PathWay
     WRQ TCP Connection
  
  For help on configuring software packages not listed, see
  one of the topics below:
     
     NDIS Configuration
     ODI Configuration
  
  
*********FTP Software's PC/TCP and OnNet*********
  
  This section describes how to configure and use FTP's
  PC/TCP and OnNet products with ShivaRemote. For help on a
  specific product, see its topic in this section.
  
     PC/TCP
  
     OnNet
  
  FTP Software, Inc.         Technical Support
  2 High Street              Phone: (508) 685-3600
  North Andover, MA 01845    BBS:   (508) 659-6240
  Phone:(508) 685-4000       FTP:   ftp.ftp.com
  
  
FTP PC/TCP
  This section describes how to install, configure, and use
  FTP's PC/TCP with ShivaRemote.
  
  1.0  Introduction
  2.0  Installing PC/TCP Software
  3.0  Configuring PC/TCP (ODI)
       3.1   Files Needed for ODI
       3.2   NET.CFG File Change
       3.3   Loading PC/TCP (ODI)
  4.0  Configuring PC/TCP (NDIS)
       4.1   Files Needed for NDIS
       4.2   PROTOCOL.INI Configuration
       4.3   Loading PC/TCP (NDIS)
  5.0  Connecting in DOS
  6.0  Connecting in Windows
  7.0  Disconnecting
  8.0  Using PC/TCP with NetWare
  
  
  1.0  Introduction
  
  PC/TCP is FTP's older, DOS-based TCP/IP software. It has
  been replaced with OnNet. ShivaRemote supports PC/TCP
  version 2.2 and later. If you have an earlier version of
  PC/TCP, please contact FTP Software for upgrade
  information.
  
  PC/TCP cannot directly use an ODI or NDIS driver;
  instead, it uses the Packet Driver (PD) standard.
  However, utilities that allow PC/TCP to use an ODI or
  NDIS driver are included on the PC/TCP diskettes. These
  utilities, called shims, allow you to use PC/TCP with
  either the ShivaRemote ODI or NDIS driver.
  
  If you are using another NDIS-based network in addition
  to PC/TCP, then you should use the ShivaRemote NDIS
  driver also. In all other cases, the ShivaRemote ODI
  driver is recommended.
  
  
  2.0  Installing PC/TCP Software
  
  This section describes how to install PC/TCP for the
  first time. If you have already installed PC/TCP on your
  PC, skip ahead to section 3.0. For details on running the
  PC/TCP install program, refer to the PC/TCP
  documentation.
  
  Insert Disk 1 of the PC/TCP software in your floppy disk
  drive and run the PC/TCP install program:
  
     C:\> a:install
  
  Continue with the install program until the "Network
  Interface Card Driver Selection" window is displayed.
  From this menu, select option number 6, "Do not Install
  any now", and press the F10 key.
  
  When the "Generic Kernel Selection" window appears,
  select the first entry, "ETHDRV (Ethernet (DIX))" and
  press the F10 key. The Ethernet kernel is selected
  because both of the ShivaRemote dial-in drivers pretend
  to be Ethernet network card drivers.
  
  Before completing the install program, you must specify
  an IP address. In the "PC/TCP Kernel and Application
  Configuration" window, select "Basic Network
  Configuration".
  
  At the "IP-address" prompt, enter any IP address, such as
  "1.1.1.1". At the "subnet mask" prompt, enter any IP
  subnet mask, such as "255.0.0.0". It is not important
  what these values are; it matters only that values are
  entered, so that the install program can complete.
  
  When the PC/TCP install program is finished, verify that
  the IP address and subnet mask have been set. In the
  pctcp.ini file, check the interface section:
  
     [pctcp ifcust 0]
     ip-address = 1.1.1.1
     subnet-mask = 255.0.0.0
  
  
  3.0  Configuring PC/TCP (ODI)
      
  This section describes how to configure PC/TCP for use
  with the ShivaRemote ODI dial-in driver. If you want to
  use PC/TCP with NDIS, refer to section 4.0 below.
  
  
  3.1  Files Needed for ODI
  
  In order to use PC/TCP with ODI, you need the following
  files:
  
  lsl.com        ODI Link Support Layer
  dialodi.exe    ShivaRemote ODI dial-in driver
  odipkt.com     PC/TCP ODI shim
  ethdrv.exe     PC/TCP Ethernet kernel
  
  The first two files (lsl.com and dialodi.exe) are
  included on the [[ShivaRemote software diskette, and are
  installed by the ShivaRemote Setup program]].
  
  The last two files (odipkt.com and ethdrv.exe) are
  installed by the PC/TCP install program.
  
  
  3.2  NET.CFG File Change

  ODI drivers are configured by entries in the net.cfg
  file. In order to use PC/TCP and the ShivaRemote ODI
  driver, you must add the following entries to your
  net.cfg file:
  
     link support
      max stacks 9
  
  If you do not add these entries to your net.cfg file, the
  PC/TCP kernel will not be able to load.
  
  
  3.3  Loading PC/TCP (ODI)
  
  The PC/TCP ODI drivers are loaded from the DOS prompt (or
  in the autoexec.bat file). Load the drivers in the
  following order:
  
     C:\PCTCP> lsl
     C:\PCTCP> dialodi
     C:\PCTCP> odipkt
     C:\PCTCP> ethdrv
  
  When the odipkt.com driver is loaded, it should report
  that it is bound to "MLID DIALODI".
  When the ethdrv.exe driver is loaded, the last line of
  its display should state something similar to the
  following:
  
     The Resident Module occupies 78160 bytes of memory
  
  This indicates that the Ethernet kernel has been loaded
  successfully. If the kernel does not load successfully,
  the last line of its display will state:
  
     Couldn't start PC/TCP kernel! Exiting...
  
  If this message is displayed, it indicates that you have
  not configured your net.cfg file properly, as described
  in section 3.2 above.
  
  PC/TCP is now ready for dial-in. Skip to section 5.0
  below.
  
  
  4.0  Configuring PC/TCP (NDIS)
  
  This section describes how to configure PC/TCP for use
  with the ShivaRemote NDIS dial-in driver. If you want to
  use PC/TCP with ODI, refer to section 3.0 above.
  
  
  4.1  Files Needed for NDIS
  
  In order to use PC/TCP with NDIS, you need the following
  files:
  
   protman.dos     NDIS Protocol Manager
   protman.exe     NDIS Protocol Manager
   dis_pkt.gup     PC/TCP NDIS shim
   dialndis.exe    ShivaRemote NDIS dial-in driver
   netbind.com     NDIS Netbind utility
   ethdrv.exe      PC/TCP Ethernet kernel
   
  The dialndis.exe driver is included on the ShivaRemote
  software diskette, and is installed by the ShivaRemote
  Setup program.
  
  The PC/TCP Ethernet kernel (ethdrv.exe) and the NDIS shim
  (dis_pkt.gup) are installed by the PC/TCP install
  program.
  
  The remaining files (protman.dos, protman.exe, and
  netbind.exe) can be found on the PC/TCP diskette titled
  "Unsupported Network Software Disk A" in the a:\ndis
  subdirectory.
  
  
  4.2  PROTOCOL.INI Configuration
  
  NDIS drivers are configured by entries in the
  protocol.ini file. The protocol.ini file should have the
  following entries:
  
     [protman]
     DriverName=PROTMAN$
  
     [SDIALIN$]
     DriverName=SDIALIN$
  
     [PKTDRV]
     DriverName=PKTDRV$
     Bindings=SDIALIN$
     intvec=0x60
     chainvec=0x65
  
  For detailed information about the protocol.ini file,
  refer to the section on NDIS configuration.
  
  
  4.3  Loading PC/TCP (NDIS)
  
  The PC/TCP NDIS drivers are loaded in the config.sys file
  and the at DOS prompt (or in the autoexec.bat file).
  
  Put the following statements in the config.sys file:
  
     device=c:\pctcp\protman.dos /i:c:\pctcp
     device=c:\pctcp\dis_pkt.gup
     device=c:\shiva\dialndis.exe
  
  From the DOS prompt (or in the autoexec.bat file), run
  the following commands:
  
     C:\PCTCP> netbind
     C:\PCTCP> ethdrv
  
  The netbind.com driver binds the PC/TCP shim
  (dis_pkt.gup) to the ShivaRemote dial-in driver
  (dialndis.exe).
  
  When the ethdrv.exe driver is loaded, the last line of
  its display should state something similar to the
  following:
  
     The Resident Module occupies 78160 bytes of memory
  
  This indicates that the Ethernet kernel has been loaded
  successfully. If the kernel does not load successfully,
  the last line of its display will state:
  
     Couldn't start PC/TCP kernel! Exiting...
  
  If this message is displayed, it indicates that you have
  not configured your protocol.ini file properly, as
  described in section 4.2 above.
  
  
  5.0  Connecting in DOS
  
  To dial into a remote network in DOS, use the ShivaRemote
  Connect program for DOS and a ShivaRemote connection
  file:
  
     C:\NET> connect @filename
  
  The ShivaRemote connect program will report the IP
  address that has been assigned by the remote networking
  server. In this example, the IP address is
  140.248.208.151.
  
  Verify that PC/TCP has been updated with this address by
  running the PC/TCP inet.exe program:
  
     C:\PCTCP> inet stats
  
  The first lines of the display should look like the
  following:
  
  Interface     address           subnet mask
  ifcust0   140.248.208.151        255.0.0.0
  
  If the address does not match the address reported by the
  ShivaRemote Connect program, make sure that that the
  PC/TCP kernel (ethdrv.exe) is loaded before the dial-in
  connection is made.
  
  Once you are connected, you can use PC/TCP programs for
  DOS such as ping.exe, tn.exe, and ftp.exe.
  
  
  6.0  Connecting in Windows
  
  PC/TCP does not require that you connect in DOS. Instead,
  you can start Windows, then use the ShivaRemote Connect
  program for Windows. This allows you to use the Windows
  versions of the PC/TCP utilities.
  
  
  7.0  Disconnecting
  
  PC/TCP does not place any restrictions on when you can
  disconnect from the remote network. In DOS, just use the
  ShivaRemote Connect program:
  
     C:\SHIVA> connect /d
  
  In Windows, run the ShivaRemote Connect program for
  Windows, then select the Disconnect button.
  
  If you are using ODI, you can unload all the drivers:
  
     C:\PCTCP> inet unload
     C:\PCTCP> odipkt u
     C:\PCTCP> dialodi u
     C:\PCTCP> lsl u
  
  If you are using NDIS, you can unload the PC/TCP kernel
  with "inet unload", but the other NDIS drivers cannot be
  unloaded.
  
  
  8.0  Using PC/TCP with NetWare
  
  Since PC/TCP can use the ODI driver standard, it can be
  used in conjunction with Novell NetWare. Refer to the
  Configuring PC/TCP (ODI) section above for information on
  configuring PC/TCP to use ODI.
  
  Load the network drivers in the following order:
  
     C:\PCTCP> lsl
     C:\PCTCP> dialodi
     C:\PCTCP> odipkt
     C:\PCTCP> ethdrv
     C:\PCTCP> ipxodi
     C:\PCTCP> vlm
  
  For detailed information on configuring NetWare, refer to
  the Novell NetWare VLM section.
  
  
FTP OnNet
  
  This section describes how to install, configure, and use
  FTP's OnNet with ShivaRemote. OnNet is also known as
  PC/TCP 3.0.
  
  1.0  Introduction
       1.1   OnNet and Network Drivers
       1.2   VxD and DOS Kernels
       1.3   Obtaining Patches
       1.4   IP Address Updating
       1.5   DNS Address Updating
  2.0  Installing OnNet for Windows
       2.1   The Windows Setup Program
       2.2   Configuring OnNet (ODI)
       2.3   Configuring OnNet (NDIS)
  3.0  Installing OnNet for DOS
       3.1   The DOS Install Program
       3.2   Configuring OnNet (ODI)
       3.3   Configuring OnNet (NDIS)
  4.0  Connecting
       4.1   Connecting with the DOS Kernel
       4.2   Connecting with the Windows Kernel
  5.0  Disconnecting
  6.0  Using OnNet with NetWare
  
  
  1.0  Introduction
  
  OnNet is FTP's new TCP/IP for DOS and Windows. It
  replaces PC/TCP. ShivaRemote supports OnNet version 1.1
  and later.
  
  
  1.1  OnNet and Network Drivers
  
  OnNet cannot directly use an ODI or NDIS driver; instead,
  it uses the Packet Driver (PD) standard. However,
  utilities that allow OnNet to use an ODI or NDIS driver
  are included on the OnNet diskettes. These utilities,
  called shims, allow you to use OnNet with either the
  ShivaRemote ODI or NDIS driver.
  
  Instructions for installing and configuring both drivers
  are given below.
  
  
  1.2  VxD and DOS Kernels
  
  OnNet comes with two IP protocol implementations, called
  kernels: one for Windows and one for DOS.
  
  The Windows (VxD) kernel is preferred, since it runs in
  protected mode and thus occupies very little DOS memory.
  The VxD kernel supports both Windows and DOS programs (in
  a DOS box), but can only be used after Windows is
  started.
  
  If you do not run Windows, or need to use OnNet in DOS
  before Windows is started, you can use the OnNet DOS
  kernel. The DOS kernel runs in real mode, and thus
  occupies more DOS memory.
  
  For more information on the OnNet kernels, refer to the
  OnNet documentation.
  
  
  1.3  Obtaining Patches
  
  FTP Software has released two major versions of OnNet:
  1.1 and 1.2. For each version, FTP has also released
  patches that fix problems specific to ShivaRemote. This
  section describes how to obtain these patches.
  
  1. OnNet Version 1.1
  
     OnNet version 1.1 requires a patch to enable IP address
     updating (described below). If you do not obtain this
     patch, ShivaRemote will not be able to update the IP
     address used by OnNet.
  
     The problem lies in the 1.1 version of the vxdinit.exe
     program. Version 3.0 of this file that does not work,
     and has the following date and time stamp:
  
     VXDINIT EXE     27,118  06-30-94  12:00a
  
     If you have this version, you must update it by
     obtaining the 30init.exe file from FTP. This file is
     available on FTP Software's BBS at (508) 659-6240. Log
     into the BBS and enter the following command:
  
     d 30init.exe
  
     This file is also available on FTP Software's FTP
     server (ftp.ftp.com). Log into the FTP server as
     "anonymous", then enter the following commands:
  
     binary
     cd support/ftpsoft/onnet/v1.1/patches
     get 30init.exe
  
     Once you have obtained this file, run it at the DOS
     prompt to create the updated vxdinit.exe:
  
     C:\> 30init
  
     A new vxdinit.exe will be created with the following
     date and time stamp:
  
     VXDINIT EXE     52,128  08-29-94  9:15a
  
     Refer to section 4.0 below for instructions on
     verifying that the IP address has been updated.

  2. OnNet version 1.2

     OnNet version 1.2 requires patches to fix a number of
     problems, including problems with the ping.exe utility,
     DNS lookups, and duplicate IP address errors.
  
     These patches are included in a file called shiva.exe.
     This file is available on FTP Software's BBS at (508)
     659-6240. Log into the BBS and enter the following
     command:
  
     d shiva.exe
  
     This file is also available on FTP Software's FTP
     server (ftp.ftp.com). Log into the FTP server as
     "anonymous", then enter the following commands:
  
     binary
     cd support/ftpsoft/onnet/v1.2/patches
     get shiva.exe
  
     Once you have obtained this file, run it at the DOS
     prompt to create the updated files (be sure to include
     the "-sftp" option:
  
     C:\> shiva -sftp
  
     Several files will be created with the following date
     and time stamps:
  
     ETHDRV EXE     179,149  02-24-95 10:39a
     ODIPKT COM       7,404  02-24-95 11:42a
     VXDPCTCP 386   217,662  02-24-95  2:42p
     VXDINIT EXE     54,720  02-13-95 12:21p
  
     Make sure that these updated files are used.
  
  
  1.4  IP Address Updating
  
  You do not have to configure OnNet with the correct IP
  address that you will use for dial-in. Instead,
  ShivaRemote will automatically update the OnNet kernel
  with the IP address that was assigned by the remote
  networking server.
  
  Unfortunately, this feature does not work with the
  initial release (1.1) of OnNet due to a bug in the OnNet
  vxdinit.exe program. Make sure you have obtained the
  updated version of this file as described in section 1.3
  above.
  
  
  1.5  DNS Address Updating
  
  Under certain circumstances, ShivaRemote can update OnNet
  with the address of an appropriate Domain Name Server
  (DNS). In order for this feature to work, the following
  conditions must be met:
  
  1. You must be running ShivaRemote 3.5 or later.

  2. You must be dialing into a Shiva remote access server
     running firmware version 3.5 or later.

  3. The Shiva remote access server must either be
     configured with an appropriate DNS address, or be
     configured to obtain dial-in IP addresses through DHCP.

  If these conditions are met, ShivaRemote will update
  OnNet with the specified DNS address. Refer to section
  4.0 below for instructions on verifying that the DNS
  address has been updated.
  
  
  2.0  Installing OnNet for Windows
  
  This section describes how to install the OnNet Windows
  VxD kernel. If you will use OnNet for DOS, you should
  install the OnNet DOS kernel, as described in section 3.0
  below.
  
  This section describes how to install OnNet for the first
  time. If you have already installed OnNet on your PC,
  skip ahead to section 4.0. For details on running the
  OnNet install program, refer to the OnNet documentation.
  
  
  2.1  The Windows Setup Program
  
  This section describes how to install OnNet with the
  OnNet Windows Setup program. Although these instructions
  below refer to NDIS, they apply to both NDIS and ODI
  installations.
  
  1. Insert Disk 1 of the OnNet software in your floppy disk
     drive. From the Program Manager's menu, select
     File/Run, enter a:setup.exe, and select the OK button.
     At the Welcome display, select the Continue button.
  
  2. At the New Installation display, select Express setup
     and select the Continue button. Enter your serial
     number and authentication key and select the Continue
     button.
  
  3. When prompted for a network card to use, highlight the
     Other NDIS Driver or Updated Packet Driver entry and
     select the Continue button. When prompted for the
     location of the driver disk, enter the directory in
     which ShivaRemote installed (this is usually c:\shiva).
     Select the OK button.
  
  4. Highlight the ShivaRemote Dial-In Driver entry and
     select the Continue button.

     If a ShivaRemote Dial-In Driver entry does not appear,
     it indicates that ShivaRemote has not been installed
     properly. Please run the ShivaRemote Setup program.
  
  5. In the IP Configuration dialog box, enter values for IP
     Address, Subnet Mask, and Router(s):
  
     IP Address:   1.1.1.1
     Subnet Mask:  255.0.0.0
     Router(s):    1.1.1.1
  
     It does not matter what values you enter here; it only
     matters that something be entered. ShivaRemote will
     update this information when the dial-in connection is
     made. Select the Continue button.
  
  6. At the DNS Configuration dialog box, enter appropriate
     values and select the Continue button.
  
  7. The OnNet Setup program will then copy the needed files
     to your hard disk. Insert the OnNet diskettes as
     directed. When all files are copied, allow Setup to
     restart your computer.
  
  OnNet is now installed on your PC. Next, you must
  configure OnNet to use either the ShivaRemote ODI or NDIS
  driver. To configure OnNet for ODI, continue with section
  2.2. To configure OnNet for NDIS, continue with section
  2.3.
  

  2.2  Configuring OnNet (ODI)

  This section describes how to configure the OnNet VxD
  kernel for use with the ShivaRemote ODI dial-in driver.
  If you want to use OnNet with NDIS, refer to section 2.3
  below. Follow these steps:
  
  1. Obtain the following files:
     
     lsl.com        ODI Link Support Layer
     dialodi.exe    ShivaRemote ODI dial-in driver
     odipkt.com     OnNet ODI shim
     vxdinit.exe    OnNet VxD loader
  
     The first two files (lsl.com and dialodi.exe) are
     included on the ShivaRemote software diskette, and are
     installed by the ShivaRemote Setup program. The third
     file (odipkt.com) is located on the OnNet software Disk
     5. If you are using OnNet version 1.2, make sure you
     have obtained an updated version of this file as
     described in section 1.3 above.
  
     The last file (vxdinit.exe) is installed by the OnNet
     Setup program. As stated above, you must obtain an
     updated version of this file from FTP.
  
  2. ODI drivers are configured by entries in the net.cfg
     file. In order to use OnNet and the ShivaRemote ODI
     driver, you must add the following lines to your
     net.cfg file:
  
     link support
         max stacks 9
  
    If you do not add these entries to your net.cfg file,
     the OnNet kernel will report an error when Windows
     starts.
  
  3. Add the following entries to the pctcp.ini file, which
     is located in the OnNet directory:
  
     [pctcp ifcust 0]
     odi-pkts=8
     asynch-send=yes
  
  4. The OnNet ODI drivers are loaded from the DOS prompt
     (or in the autoexec.bat file). Load the drivers in the
     following order:
  
     C:\ONNET> lsl
     C:\ONNET> dialodi
     C:\ONNET> odipkt
     C:\ONNET> vxdinit
  
     When the odipkt.com driver is loaded, it should report
     that it is bound to "MLID DIALODI".
  
     Make sure that vxdinit.exe reports the following
     message:
  
     VXDINIT is successfully loaded.
  
  5. Start Windows and verify that OnNet initializes without
     any errors. If the following error message is
     displayed:
  
     PC/TCP Virtual Device
     VXDPCTCP InitComplete failed
     Press any key to continue
  
     This indicates that you have not modified your net.cfg
     file as described in step 2 above.


  2.3  Configuring OnNet (NDIS)

  This section describes how to configure the OnNet VxD
  kernel for use with the ShivaRemote NDIS driver. If you
  want to use OnNet with ODI, refer to section 2.2 above.
  Follow these steps:
  
  1. Obtain the following files:
  
     protman.dos    NDIS Protocol Manager
     protman.exe    NDIS Protocol Manager
     netbind.com    NDIS bind utility
     dis_pkt.gup    OnNet NDIS shim
     dialndis.exe   ShivaRemote NDIS dial-in driver
     vxdinit.exe    OnNet VxD loader
  
     The first three files (protman.dos, protman.exe, and
     netbind.com) are locatd on the OnNet software Disk 2.
     The fourth file (dis_pkt.gup) is located on the OnNet
     software Disk 5. The fifth file (dialndis.exe) is
     included on the ShivaRemote software diskette, and is
     installed by the ShivaRemote Setup program.
  
     The last file (vxdinit.exe) is installed by the OnNet
     Setup program. As stated above, you must obtain an
     updated version of this file from FTP.
  
  2. NDIS drivers are configured by entries in the
     protocol.ini file. The protocol.ini file should have
     the following entries:
  
     [protman]
     DriverName=PROTMAN$
  
     [SDIALIN$]
     DriverName=SDIALIN$
  
     [PKTDRV]
     DriverName=PKTDRV$
     Bindings=SDIALIN$
     intvec=0x60
     chainvec=0x65
  
  3. The OnNet NDIS drivers are loaded in the config.sys
     file and at the DOS prompt (or in the autoexec.bat
     file).
  
     Put the following statements in the config.sys file:
  
     device=c:\onnet\protman.dos /i:c:\onnet
     device=c:\onnet\dis_pkt.gup
     device=c:\shiva\dialndis.exe
  
     From the DOS prompt (or in the autoexec.bat file), run
     the following commands:
  
     C:\ONNET> netbind
     C:\ONNET> vxdinit
  
     Make sure that vxdinit.exe reports the following
     message:
  
     VXDINIT is successfully loaded.
  
  4. OnNet is now ready to use. Start Windows and proceed
     with section 4.0 below.
  
  
  3.0  Installing OnNet for DOS
  
  This section describes how to install the OnNet DOS
  kernel. If you will use OnNet for Windows only, you
  should install the OnNet Windows VxD kernel, as described
  in section 2.0 above.
  
  This section describes how to install OnNet for the first
  time. If you have already installed OnNet on your PC,
  skip ahead to section 4.0. For details on running the
  OnNet install program, refer to the OnNet documentation.
  
  
  3.1  The DOS Install Program
  
  This section describes how to install OnNet with the
  OnNet DOS Install program. Although these instructions
  below refer to NDIS, they apply to both NDIS and ODI
  installations.
  
  1. Insert Disk 1 of the OnNet software in your floppy disk
     drive. From the DOS prompt, enter the following
     command:
  
     C:\> a:install
  
     At the Welcome display, select the Continue button.
  
  2. At the New Installation display, select Express setup
     and select the Continue button. Enter your serial
     number and authentication key and select the Continue
     button.
  
  3. When prompted for a network card to use, highlight the
     Other NDIS Driver or Updated Packet Driver entry and
     select the Continue button. When prompted for the
     location of the driver disk, enter the directory in
     which ShivaRemote installed (this is usually c:\shiva).
     Select the OK button.
  
  4. Highlight the ShivaRemote Dial-In Driver entry and
     select the Continue button.

     If a ShivaRemote Dial-In Driver entry does not appear,
     it indicates that ShivaRemote has not been installed
     properly. Please run the ShivaRemote Setup program.
  
  5. In the IP Configuration dialog box, enter values for IP
     Address, Subnet Mask, and Router(s):
  
     IP Address:   1.1.1.1
     Subnet Mask:  255.0.0.0
     Router(s):    1.1.1.1
  
     It does not matter what values you enter here; it only
     matters that something be entered. ShivaRemote will
     update this information when the dial-in connection is
     made. Select the Continue button.
  
  6. At the DNS Configuration dialog box, enter appropriate
     values and select the Continue button.
  
  7. The OnNet Install program will then copy the needed
     files to your hard disk. Insert the OnNet diskettes as
     directed. When all files are copied, allow Install to
     restart your computer.
  
  OnNet is now installed on your PC. Next, you must
  configure OnNet to use either the ShivaRemote ODI or NDIS
  driver. To configure OnNet for ODI, continue with section
  3.2. To configure OnNet for NDIS, continue with section
  3.3.
  
  
  3.2  Configuring OnNet (ODI)
  
  This section describes how to configure the OnNet DOS
  kernel for use with the ShivaRemote ODI dial-in driver.
  If you want to use OnNet with NDIS, refer to section 3.3
  below. Follow these steps:
  
  1. Obtain the following files:
  
     lsl.com   ODI Link Support Layer
     dialodi.exe    ShivaRemote ODI dial-in driver
     odipkt.com     OnNet ODI shim
     ethdrv.exe     OnNet Ethernet DOS kernel
  
     The first two files (lsl.com and dialodi.exe) are
     included on the ShivaRemote software diskette, and are
     installed by the ShivaRemote Setup program. The third
     file (odipkt.com) is located on the OnNet software Disk
     5.
  
     The last file (ethdrv.exe) is installed by the OnNet
     Setup program.
  
  2. ODI drivers are configured by entries in the net.cfg
     file. In order to use OnNet and the ShivaRemote ODI
     driver, you must add the following lines to your
     net.cfg file:
  
      link support
          max stacks 9
  
     If you do not add these entries to your net.cfg file,
     the OnNet kernel will report an error when it is
     loaded.
  
  3. Add the following entries to the pctcp.ini file, which
     is located in the OnNet directory:
  
     [pctcp ifcust 0]
     odi-pkts=8
     asynch-send=yes
  
  4. The OnNet ODI drivers are loaded from the DOS prompt
     (or in the autoexec.bat file). Load the drivers in the
     following order:
  
     C:\ONNET> lsl
     C:\ONNET> dialodi
     C:\ONNET> odipkt
     C:\ONNET> ethdrv
  
     When the odipkt.com driver is loaded, it should report
     that it is bound to "MLID DIALODI".
  
     When the ethdrv.exe driver is loaded, the last line of
     its display should state something similar to the
     following:
  
       The Resident Module occupies 50.8K of conventional
       memory
  
     This indicates that the Ethernet kernel has been loaded
     successfully. If the kernel does not load successfully,
     the last line of its display will state:
  
       Couldn't start PC/TCP kernel! Exiting...
  
     If this message is displayed, it indicates that you
     have not configured your net.cfg file properly, as
     described in step 2 above.
  
  
  3.3  Configuring OnNet (NDIS)
  
  This section describes how to configure the OnNet DOS
  kernel for use with the ShivaRemote NDIS driver. If you
  want to use OnNet with ODI, refer to section 3.2 above.
  Follow these steps:

  1. Obtain the following files:
  
     protman.dos    NDIS Protocol Manager
     protman.exe    NDIS Protocol Manager
     netbind.com    NDIS bind utility
     dis_pkt.gup    OnNet NDIS shim
     dialndis.exe   ShivaRemote NDIS dial-in driver
     ethdrv.exe     OnNet Ethernet DOS kernel
  
     The first three files (protman.dos, protman.exe, and
     netbind.com) are locatd on the OnNet software Disk 2.
     The fourth file (dis_pkt.gup) is located on the OnNet
     software Disk 5. The fifth file (dialndis.exe) is
     included on the ShivaRemote software diskette, and is
     installed by the ShivaRemote Setup program.
  
     The last file (ethdrv.exe) is copied by the OnNet
     Install program.
  
  2. NDIS drivers are configured by entries in the
     protocol.ini file. The protocol.ini file should have
     the following entries:
  
     [protman]
     DriverName=PROTMAN$
  
     [SDIALIN$]
     DriverName=SDIALIN$
  
     [PKTDRV]
     DriverName=PKTDRV$
     Bindings=SDIALIN$
     intvec=0x60
     chainvec=0x65
  
  3. The OnNet NDIS drivers are loaded in the config.sys
     file and at the DOS prompt (or in the autoexec.bat
     file).
  
     Put the following statements in the config.sys file:
  
      device=c:\onnet\protman.dos /i:c:\onnet
      device=c:\onnet\dis_pkt.gup
      device=c:\shiva\dialndis.exe
  
     From the DOS prompt (or in the autoexec.bat file), run
     the following commands:
  
     C:\ONNET> netbind
     C:\ONNET> ethdrv
  
     When the ethdrv.exe driver is loaded, the last line of
     its display should state something similar to the
     following:
  
       The Resident Module occupies 50.8K of conventional
       memory
  
  
  4.0  Connecting
  
  It is very important that you connect to a remote network
  after all OnNet drivers have been loaded. If you connect
  before OnNet is loaded, ShivaRemote will not be able to
  update the IP address, and you will not be able to
  communicate with hosts on the remote network.
  
  
  4.1  Connecting with the DOS Kernel
  
  If you are using the DOS kernel and want to connect in
  DOS, be sure to run ShivaRemote Connect for DOS after you
  have loaded the OnNet DOS kernel:
  
     C:\ONNET> ethdrv
     C:\ONNET> connect @file
  
  Once you have connected, verify that ShivaRemote has
  updated the OnNet IP address. First, look at the
  ShivaRemote IP statistics by running the following
  command:
  
     C:\ONNET> connect /ip
  
  Towards the end of this display, your IP address is
  displayed at the IP address: prompt.
  Next, view the OnNet statistics by running the following
  command:
  
     C:\ONNET> inet stats
  
  The first lines of the display should be similar to the
  following:
  
     Interface     address
      ifcust0      140.248.208.151
  
  Make sure that the address reported here matches the
  address reported by ShivaRemote.
  
  If you meet the conditions described in section 1.4 above
  for DNS address updating, verify that the DNS address has
  been updated by running the following command:
  
     C:\ONNET> inet config
  
  Towards the end of this display, the DNS server address
  should be displayed at the Domain name server(s): prompt.
  If this address has not been set, review section 1.4
  above.
  
  
  4.2  Connecting with the Windows Kernel
  
  If you are using the Windows kernel, run ShivaRemote
  Connect for Windows at any time once Windows has started.
  
  Do not connect before Windows is started. If you connect
  before Windows is started, ShivaRemote will not be able
  to update the IP address.
  
  Once you have connected, verify that ShivaRemote has
  updated the OnNet IP address. First, look at the
  ShivaRemote IP statistics by selecting the
  Tools/Statistics... menu item and selecting IP from the
  drop-down list. Towards the end of this display, your IP
  address is displayed at the IP address: prompt.
  
  Next, view the OnNet statistics by double-clicking the
  Statistics icon in the Program Manager's PC/TCP WinApps
  3.0 group. Select the File/Open Text... menu item, select
  the Statistics entry, then select the OK button. In the
  System Information window, the IP address will be
  displayed at the Address prompt.
  
  Make sure that the address reported here matches the
  address reported by ShivaRemote. If it does not, please
  refer to section 1.3 above for information on
  vxdinit.exe.
  
  If you meet the conditions described in section 1.5 above
  for DNS address updating, you can also use this program
  to verify that the DNS address has been updated. Select
  the File/Open Text... menu item, select the Configuration
  entry, then select the OK button. The DNS address will be
  displayed at the Domain Name Server(s) window.
  
  If this address has not been set, review sections 1.3 and
  1.5 above.
  
  
  5.0  Disconnecting
  
  OnNet places no restrictions on when you can disconnect
  from the remote network. However, if you try to access
  hosts on the remote network after you have disconnected,
  you will experience a short delay.
  
  If you are using the ODI drivers, you can unload the
  drivers. If you are using the Windows (VxD) kernel, enter
  the following command:
  
     C:\ONNET> vxdinit u
  
  If you are using the DOS kernel, enter the following
  command:
  
     C:\ONNET> inet unload
  
  Once the kernel is removed, unload the other drivers in
  reverse order:
  
     C:\ONNET> odipkt u
     C:\ONNET> dialodi u
     C:\ONNET> lsl u
  
  
  6.0  Using OnNet with NetWare
  
  Since OnNet can use the ShivaRemote ODI driver, it can be
  used with NetWare. If you are running the OnNet DOS
  kernel, load the drivers in the following order:
  
  C:\ONNET> lsl
  C:\ONNET> dialodi
  C:\ONNET> odipkt
  C:\ONNET> ethdrv
  C:\ONNET> ipxodi
  C:\ONNET> vlm

  If you are running the OnNet Windows kernel, load the
  drivers in the following order:

  C:\ONNET> lsl
  C:\ONNET> dialodi
  C:\ONNET> odipkt
  C:\ONNET> vxdinit
  C:\ONNET> ipxodi
  C:\ONNET> vlm


*********IBM Network Software*********
  
  This section describes how to configure IBM network
  software for use with ShivaRemote. For detailed
  information on IBM network software, please refer to the
  IBM documentation.

  For help on a particular topic, see its topic in this
  section.
  
     LAN Support Program (LSP)
  
     DOS LAN Requestor (DLR)
  
     ODI-to-NDIS Converter (ODI2NDI)
  
  
IBM LAN Support Program (LSP)
  
  1.0  Introduction
  2.0  Installing LSP
       2.1  Setup for E0 and T0
       2.2  Setup for J0
  3.0  Configuring LSP
       3.1  Configuring the E0 and T0 Drivers
       3.2  Configuring the J0 Driver
  
  
  1.0  Introduction
  
  The IBM LAN Support Program (LSP) is the foundation of
  all IBM PC networking software. It implements the NetBEUI
  and LLC protocols, and provides the NetBIOS and LLC
  programming interfaces.
  
  ShivaRemote supports the LAN Support Program versions
  1.33 and later. If you have an earlier version of LSP,
  please upgrade it to 1.33.
  
  
  2.0  Installing LSP
  
  The easiest way to install LSP is to use its automatic
  installation aid (DXMAID). To run DXMAID, follow these
  steps:
  
  1. Run the ShivaRemote Setup program to install
     ShivaRemote on your PC.
  
  2. Insert the LSP disk in your floppy drive and run the
     DXMAID program at the DOS prompt:
  
     C:\> a:dxmaid
  
  3. When you are asked if you have an adapter diskette,
     answer Yes. When you are asked for the location of your
     adapter files, specify the ShivaRemote directory
     (usually c:\shiva). The ShivaRemote driver should show
     up in the list:
  
     ShivaRemote dial-in driver for NDIS (dialndis.exe)
  
     If this entry does not appear in the list, or if the
     DXMAID program reports an error, it may indicate that
     you have not installed ShivaRemote properly.
  
     The DXMAID program will copy the necessary files to your
     hard disk, then modify your config.sys, autoexec.bat,
     and protocol.ini files.
  
  
  2.1  Setup for E0 and T0
  
  If you are using both the NetBIOS and the LLC interface,
  the DXMAID program will put the following entries in your
  config.sys files:
  
     device=c:\lsp\protman.dos /i:c:\lsp
     device=c:\lsp\dxmA0mod.sys 001
     device=c:\lsp\dxmE0mod.sys ,20
     device=c:\lsp\dxmT0mod.sys O=N S=16 ST=16 C=16 ES=1 EST=1 N=18 CF=Y
  
  The following command will be added to your autoexec.bat
  file:
  
    c:\lsp\netbind
  
  A protocol.ini file will be created with the following
  entries:
  
    [PROTMAN_MOD]
    DriverName=PROTMAN$
  
    [DIALIN_MOD]
    DriverName=SDIALIN$
  
    [DXME0_NIF]
    DriverName=DXME0$
    Bindings=DIALIN_MOD
  
  
  2.2  Setup for J0
  
  If you are using only the NetBIOS interface, the DXMAID
  program will put the following entries in your config.sys
  files:
  
     device=c:\lsp\protman.dos /i:c:\lsp
     device=c:\lsp\dxmA0mod.sys 001
     device=c:\lsp\dxmJ0mod.sys
  
  The following command will be added to your autoexec.bat
  file:
  
    c:\lsp\netbind
  
  A protocol.ini file will be created with the following
  entries:
  
    [PROTMAN_MOD]
    DriverName=PROTMAN$
  
    [DIALIN_MOD]
    DriverName=SDIALIN$
  
    [DXMJ0_NIF]
    DriverName=DXMJ0$
    Bindings=DIALIN_MOD
  
  
  3.0  Configuring LSP
  
  Before the LAN Support Program can be used for dial-in,
  you must make several modifications to your configuration
  files. If you do not make these changes, dial-in will not
  function properly.
  
  
  3.1  Configuring the E0 and T0 Drivers
  
  This section describes the configuration changes needed
  for the E0 and T0 drivers. If you are running the J0
  driver, refer to section 3.2 below.
  
  The T0 and E0 drivers are loaded in the config.sys file.
  Make sure that the command line for the T0 driver
  includes the options specified below:
  
     device=c:\lsp\dxmT0mod.sys T1=10 T2=10 TI=10 MI=2 MO=2
  
  Please note that this is not a complete command line for
  the T0 driver; there are many other options that are set
  by the LSP installation aid. Make sure to add the options
  listed above to the existing command line.
  
  The T1, T2, and TI entries specify the protocol-retry
  timeouts. The default values for these timeouts are too
  short for dial-in; these values have been found to work
  well.
  
  The MI and MO entries limit the send and receive window
  sizes; if they are omitted, the window will grow too
  large. If this happens, the data in the window cannot be
  transmitted before the retry timeout occurs, and the
  connection will be lost.
  
  
  3.2  Configuring the J0 Driver
  
  This section describes the configuration changes needed
  for the J0 driver. If you are running the E0 and T0
  drivers, refer to section 3.1 above.
  
  The J0 driver is configured by a section in the
  protocol.ini file. This section is created by the LSP
  installation aid, and is usually called DXMJ0_MOD. Modify
  this section so that it contains these entries:
  
    [DXMJ0_MOD]
    T1=8000
    T2=2000
    TI=6000
    MaxIn=3
    MaxOut=3
    MaxTransmits=2
    MinTransmits=1
  
  The T1, T2, and TI entries specify the protocol-retry
  timeouts. The default values for these timeouts are too
  short for dial-in; these values have been found to work
  well.
  
  The MaxIn and MaxOut entries limit the send and receive
  window sizes; if they are omitted, the window will grow
  too large. If this happens, the data in the window cannot
  be transmitted before the retry timeout occurs, and the
  connection will be lost.
  
  The MaxTransmits and MinTransmits entries limit the
  number of transmit frames that the protocol will ask the
  dial-in driver to transmit at one time. This ensures that
  the dial-in driver will always have enough resources to
  transmit the frames.
  
  
IBM DOS LAN Requestor (DLR)
  
  1.0  Introduction
  2.0  Configuring DLR
  3.0  Using DLR
  
  
  1.0  Introduction
  
  The IBM DOS LAN Requestor (DLR) allows a PC to log into
  an IBM LAN Server and use its shared files and printers.
  
  
  2.0  Configuring DLR
  
  In order to use DLR, you must first install the IBM LAN
  Support Program (LSP). Pay particular attention to the
  configuration items specified in sections 3.1 and 3.2. If
  these configuration changes are not made, you will not be
  able to communicate reliably with the LAN Server.
  
  Next, you must modify the protocol.ini file in the
  \IBMCOM subdirectory of the LAN Server. Add the following
  entries to the NetBIOS section:
  
     [NETBEUI_NIF]
     T1=8000
     T2=2000
     TI=60000
     MaxIn=3
     MaxOut=3
     SideBand=0
     AdaptRate=0
  
  The T1, T2, and TI entries specify the protocol-retry
  timeouts. The default values for these timeouts are too
  short for dial-in; these values have been found to work
  well.
  
  The MaxIn and MaxOut entries limit the send and receive
  window sizes; if they are omitted, the window will grow
  too large. If this happens, the data in the window cannot
  be transmitted before the retry timeout occurs, and the
  connection will be lost.
  
  The SideBand and AdaptRate entries instruct the LAN
  Server not to dynamically adjust the send and receive
  window sizes.
  
  Finally, you must modify the ibmlan.ini file in the
  \IBMLAN subdirectory of the LAN Server. In the
  SRVHEURISTICS parameter, change bit 15 from a 0 to a 2.
  
  
  3.0  Using DLR
  
  The DLR software is usually initialized in the
  autoexec.bat file. Follow these rules:
  
  1. The netbind command must be run before the dial-in
     connection is made.
  
  2. The net start command can be run either before or after
     the dial-in connection is made. This command can take
     up to 30 seconds to execute, regardless whether it is
     run before or after the connection is made.
  
  3. The net logon command must be made after the dial-in
     connection is made.
  
  The autoexec.bat file should look like this:
  
    c:\lsp\netbind
    c:\shiva\connect @lanserv
    c:\dlr\net start
    c:\dlr\net logon
  
  
IBM ODI-to-NDIS Converter (ODI2NDI)
  
  1.0  Introduction
  2.0  Configuring ODI2NDI
       2.1  The CONFIG.SYS File
       2.2  The PROTOCOL.INI File
  3.0  Loading Drivers
  4.0  Using ODI2NDI
  
  
  1.0  Introduction
  
  IBM's ODI2NDI is a program that allows an NDIS protocol
  implementation to use an ODI network card driver. For
  example, suppose you want to use both the IBM LAN Support
  Program (LSP) and Novell NetWare at the same time. LSP is
  an NDIS protocol, and Novell IPX is an ODI protocol.
  
  The solution is to use the ShivaRemote NDIS dial-in
  driver (dialndis.exe) and ODI2NDI. LSP automatically
  knows how to use this driver, and with the help of
  ODI2NDI, Novell NetWare can use it also.
  
  This section gives instructions on installing and using
  ODI2NDI with IBM LSP and Novell NetWare.
  
  
  2.0  Configuring ODI2NDI
  
  This section assumes you are using the IBM LSP E0 and T0
  drivers.
  
  
  2.1  The CONFIG.SYS File
  
  The LAN Support Program drivers are be loaded in the
  config.sys file as always:
  
     device=c:\lsp\protman.dos /i:c:\lsp
     device=c:\shiva\dialndis.exe
     device=c:\lsp\dxmA0mod.sys 001
     device=c:\lsp\dxmE0mod.sys ,20
     device=c:\lsp\dxmT0mod.sys O=N S=16 ST=16 C=16 ES=1 EST=1 N=18 CF=Y
  
  
  2.2  The PROTOCOL.INI File
  
  The protocol.ini file should look like this:
  
     [PROTMAN_MOD]
     DriverName=PROTMAN$
  
     [DIALIN_MOD]
     DriverName=SDIALIN$
  
     [DXME0_NIF]
     DriverName=DXME0$
     Bindings=DIALIN_MOD
  
     [ODI2NDI_MOD]
     DriverName=ODI2NDI$
     Bindings=DIALIN_MOD
     Ethernet_802.3 = "yes"
     Token-Ring = "no"
     Token-Ring_SNAP = "no"
  
  The Ethernet_802.3="yes" entry instructs the ODI2NDI
  driver that it should use Ethernet framing. This is
  required, even when you are dialing into a Token-Ring
  network. The ShivaRemote dial-in driver always claims to
  be an Ethernet driver; if it connects to a Token-Ring
  remote networking server, the server will do the
  necessary translations.
  
  
  3.0  Loading Drivers
  
  The various drivers should be loaded in autoexec.bat in
  the following order:
  
    c:\nwclient\lsl
    c:\shiva\odi2ndi
    c:\lsp\netbind
    c:\nwclient\ipxodi
    c:\nwclient\vlm
  
  
  4.0  Using ODI2NDI
  
  When you use an ODI protocol with ODI2NDI, it should
  generally work the same way that it does with the
  ShivaRemote ODI driver (dialodi.exe). However, there are
  some exceptions.
  
  1. The NetWare VLMs will take longer to load when not
     connected
  
     When used with the ShivaRemote ODI driver, and when
     loaded before the dial-in connection is made, the
     NetWare VLMs will load without delay and immediately
     return to the DOS prompt. This is possible because of a
     special feature of the ODI driver standard that lets
     the VLMs know that the dial-in connection is not made,
     and that it shouldn't try to connect to a server.
  
     When the VLMs are used with ODI2NDI and the ShivaRemote
     NDIS driver, this special feature is not available.
     When the VLMs are loaded, they will attempt to connect
     to a NetWare server for up to 30 seconds before
     returning to the DOS prompt.
  
  2. LAN Workplace IP address update will not work
  
     When Novell LAN Workplace is used with the ShivaRemote
     ODI driver, ShivaRemote updates LAN Workplace with the
     IP address it obtained from the remote networking
     server. This feature will not work when LAN Workplace
     is used with ODI2NDI and the ShivaRemote NDIS driver.
 
 
*********Microsoft TCP/IP-32*********
  
  This section describes how to install and configure
  Microsoft TCP/IP-32 with ShivaRemote.
  
  1.0  Introduction
  2.0  Obtaining Microsoft TCP/IP-32
  3.0  Configuring Microsoft TCP/IP-32
       3.1   Installing the ShivaRemote Driver
       3.2   Adding the TCP/IP-32 Protocol
       3.3   Configuring TCP/IP-32
       3.4   TCP/IP-32 and IP Addresses
  4.0  Connecting
       4.1   Connecting with Dynamic IP Addressing
       4.2   Connecting with Static IP Addressing
       4.3   Domain Name Server Address Update
  5.0  Disconnecting
  6.0  Using TCP/IP-32 with NetWare
  

  1.0  Introduction
  
  Microsoft TCP/IP-32 is an implementation of the TCP/IP
  protocols for Windows for Workgroups version 3.11. It
  includes the following features:
  
  *  32-bit VxD implementation occupies no DOS memory
  *  Supports Winsock programs such as Mosaic and Eudora
  *  Supports WFW peer networking over TCP/IP
  *  Includes basic FTP and Telnet programs
  
  ShivaRemote can update the IP address used by TCP/IP-32.
  This means that you do not have to configure a specific
  IP address; when ShivaRemote connects to a remote
  network, it updates TCP/IP-32 with the IP address it was
  assigned.
  
  In addition, if you are dialing into a Shiva LanRover
  (version 3.5 or later), ShivaRemote can update the Domain
  Name Server (DNS) address.
  
  The sections below give instructions on installing and
  using TCP/IP-32 for applications such as FTP, telnet, and
  Winsock. If you will use TCP/IP-32 for networking
  services (to connect to Microsoft Windows for Workgroups,
  LAN Manager, and Windows NT file servers), please refer
  to the Windows for Workgroups 3.11 topic for detailed
  information.

  
  2.0  Obtaining Microsoft TCP/IP-32
  
  Since it was released after Windows for Workgroups 3.11,
  Microsoft TCP/IP-32 is not included on the WFW 3.11
  diskettes. Instead, it must be obtained from Microsoft.
  If you have already obtained TCP/IP-32, skip ahead to
  section 3.0.
  
  To obtain this software, you must have a connection to
  the Internet, and you must be able to connect to
  Microsoft's FTP server, ftp.microsoft.com. Follow these
  steps:
  
  1. At your FTP prompt, enter the following command to
     connect to the Microsoft FTP server:
  
     ftp> open ftp.microsoft.com
  
  2. When prompted for your user name, enter the following:
  
     anonymous
  
     When prompted for your password, enter your complete
     electronic mail ID:
  
     user@host.com
  
  3. Once you are logged into the Microsoft FTP server,
     download the TCP/IP-32 file by entering the following
     commands:
  
     ftp> cd peropsys/windows/public/tcpip
     ftp> binary
     ftp> get WFWT32.EXE
  
  4. When the download is complete, disconnect from the FTP
     server:
  
     ftp> close
  
     Then exit your FTP program.
  
  5. The file wfwt32.exe is a self-extracting archive file.
     Execute this program at the DOS prompt to extract the
     TCP/IP-32 files:
  
     C:\MSTCP32> wfwt32
  
     The TCP/IP-32 files will be placed in the current
     directory. When the Network Setup program asks for the
     location of these files, specify this directory.
  
     If the program reports errors while extracting files, or
     if the program hangs, it most likely indicates that you
     did not specify a binary transfer as described in step
     3 above. Get the file again, making sure to specify a
     binary transfer.

  
  3.0  Configuring Microsoft TCP/IP-32
  
  Microsoft TCP/IP-32 requires Windows for Workgroups
  version 3.11. If you have a different version of Windows,
  you must upgrade it to WFW 3.11 in order to use TCP/IP-
  32.

  
  3.1  Installing the ShivaRemote Driver
  
  First, follow these steps to install the ShivaRemote dial-
  in driver:
  
  1. Run the Network Setup program by double-clicking its
     icon in the Program Manager's Network group.
  
  2. Choose the Drivers... button to display the Network
     Drivers dialog box.
  
  3. Choose the Add Adapter... button to display the Add
     Network Adapter dialog box.
  
  4. Select Unlisted or Updated Network Adapter from the
     list of network adapters, and choose the OK button.
  
  5. When WFW asks for the location of the driver disk,
     specify the directory in which ShivaRemote has been
     installed (this is usually c:\shiva). Choose the OK
     button.
  
     Note: if you have the ShivaRemote software diskette, you
     can insert it in your floppy drive and specify the
     drive letter (such as A:). Choose the OK button.
  
  6. The entry "ShivaRemote Dial-In Driver" should appear in
     the Unlisted or Updated Network Adapter dialog box.
     Select this entry and choose the OK button.
  
     Note: if the ShivaRemote entry does not appear in this
     dialog box, it may be because you have already added
     the ShivaRemote driver. Check the main adapter list to
     see if this entry is already there. If it is there,
     select it and choose the OK button.
  
     You will return to the Network Drivers dialog box. The
     ShivaRemote driver will be listed, along with the
     default protocols:
  
     ShivaRemote Dial-In Driver
       IPX/SPX Compatible Transport with NetBIOS
       Microsoft NetBEUI
  
  7. As described in the Windows for Workgroups 3.11
     section, the Microsoft IPX/SPX protocol does not work
     with ShivaRemote; thus, the protocol must be removed.
     Select the "IPX/SPX Compatible Transport with NetBIOS"
     entry and choose the Remove button. The display should
     now look like this:
  
     ShivaRemote Dial-In Driver
       Microsoft NetBEUI

  
  3.2  Adding the TCP/IP-32 Protocol
  
  Once you have added the ShivaRemote dial-in driver, you
  can install the TCP/IP-32 protocol. Follow these steps:
  
  1. Run the Network Setup program by double-clicking its
     icon in the Program Manager's Network group.
  
  2. Choose the Drivers... button to display the Network
     Drivers dialog box.
  
  3. Highlight the ShivaRemote Dial-In Driver entry by
     clicking on it or by using the arrow keys. If
     ShivaRemote has not been installed as a network
     adapter, please refer to the instructions in section
     3.1 above before proceeding.
  
  4. Choose the Add Protocol... button to display the Add
     Network Protocol dialog box.
  
  5. Select Unlisted or Updated Protocol from the list of
     network protocols, and choose the OK button.
  
  6. When the Install Driver dialog box appears, enter the
     drive and directory where the TCP/IP-32 files are
     located, then choose the OK button. For example, if the
     files are on a floppy diskette, enter A: and choose the
     OK button.
  
  7. When the Unlisted or Updated Protocol dialog box
     appears, there should be an entry named Microsoft
     TCP/IP-32 3.11. Highlight this entry and choose the OK
     button. If Network Setup asks you if you want to
     replace any Microsoft TCP/IP-32 files already installed
     on your computer, answer Yes.
  
  8. When you are returned to the Network Drivers dialog
     box, the ShivaRemote entry should look like this:
  
     ShivaRemote Dial-In Driver
       Microsoft NetBEUI
       Microsoft TCP/IP-32 3.11
  
     If you wish to use only the TCP/IP protocol, highlight
     the Microsoft NetBEUI entry and choose the Remove
     button.
  
     Finally, choose the Close button to close the Network
     Drivers dialog box.
  
  9. When you are returned to the Network Setup dialog box,
     choose the OK button.

     If Network Setup asks you if you want to replace any
     Enhanced Protocol Manager files already installed on
     your computer, answer No. This prevents network setup
     from overwriting any files updated by the ShivaRemote
     Setup program.

  
  3.3  Configuring TCP/IP-32
  
  Next, you will be presented with the Microsoft TCP/IP
  Configuration dialog box. Follow these steps to configure
  TCP/IP:
  
  1. Do not check the Enable Automatic DHCP Configuration
     option. Configuring the ShivaRemote driver to obtain
     its configuration through DHCP will not work.
  
  2. At the IP Address: prompt, enter any IP address (for
     example, 1.1.1.1). It does not matter what this address
     is; it matters only that an address is entered. When
     the dial-in connection is made, ShivaRemote will update
     TCP/IP-32 with the appropriate IP address.
  
  3. The Subnet Mask: field will be updated automatically
     based on the IP address entered above. Do not change
     this value.
  
  4. At the Default Gateway: prompt, enter the same IP
     address entered at the IP Address: prompt above. When
     the dial-in connection is made, ShivaRemote will update
     TCP/IP-32 with the appropriate IP address value.
  
  5. Select the OK button. When Network Setup asks if you
     want to set the IP Address and Default Gateway values
     to the same address, answer Yes.
  
  When Network Setup is done modifying your configuration
  files, it will prompt you to restart your computer. Allow
  Network Setup to restart your computer so that these
  changes can take effect.

  
  3.4  TCP/IP-32 and IP Addresses
  
  As stated above, ShivaRemote can update the IP address
  used by TCP/IP-32 when a dial-in connection is made.
  Unfortunately, there is an unresolved problem with this
  address update feature. This section describes this
  problem.
  
  Microsoft TCP/IP-32 applications fall into two
  categories: IP services and networking services:
  
  IP Services
  
     IP services are standard TCP/IP applications such as
     ping, telnet, and FTP. In addition, Winsock-based
     applications such as Mosaic and Eudora are considered
     IP services.
     
  Networking Services
  
     Networking services are the ability to connect to a
     network file or print server, such as a Microsoft
     Windows NT or LAN Manager server.
     
  The ShivaRemote IP address update feature works with IP
  services. Unfortunately, due to a problem in WFW and
  TCP/IP-32, this feature does not work with networking
  services. Microsoft has acknowledged this problem, and
  has indicated that it will not be fixed.
  
  Thus, you have two options: you can use IP address
  updating with IP services, or you can use static IP
  addressing with networking services. Below are
  instructions for each option.
  
  1. Dynamic IP Address Updating
  
  If you will only use TCP/IP-32 for IP services, and will
  not use it to connect to network file servers, then you
  can use the IP address update feature of ShivaRemote.
  However, in order to do this, you must disable IP
  networking services.
  
  To do this, you need to edit your system.ini file. In the
  [386Enh] section, you will find a transport= entry:
  
    [386Enh]
    transport=vip.386,vdhcp.386,vtdi.386,vtcp.386,vnbt.386
  
  Remove vnbt.386 from this entry:
  
    [386Enh]
    transport=vip.386,vdhcp.386,vtdi.386,vtcp.386
  
  This disables NetBIOS over TCP/IP, which effectively
  disables networking services over TCP/IP-32. However, it
  leaves all other IP services intact.
  
  2. Static IP Addressing
  
  If you will use TCP/IP-32 for networking services, then
  you cannot use the IP address update feature of
  ShivaRemote. By default, ShivaRemote will update the IP
  address at connection time; thus, this feature must be
  explicitly disabled.
  
  To do this, add the following entry to the [Options]
  section of the sremote.ini file:
  
     [Options]
     UpdateIPAddress=No
  
  The sremote.ini file is in the Shiva directory, usually
  c:\shiva.
  
  Since you have disabled IP address updating, you must now
  configure the correct IP address for your dial-in
  connection. Ask your network administrator for the
  appropriate IP address. Run the Network Setup program and
  enter this address as described in section 4.2 above.

  
  4.0  Connecting
  
  Because TCP/IP-32 is Windows-based, you can connect using
  the ShivaRemote Connect program for Windows.
  
  Once you have connected to a remote network, you should
  verify that TCP/IP-32 is using the appropriate IP
  address.

  
  4.1  Connecting with Dynamic IP Addressing
  
  If you are using dynamic IP addressing (as described in
  section 3.4 above), verify that ShivaRemote has updated
  TCP/IP-32 with the new IP address.
  
  First, determine the address obtained by ShivaRemote by
  selecting the Tools/Statistics... menu item, and
  selecting IP from the drop-down list.
  
  Next, compare this to the address being used by TCP/IP-
  32. To do this, you must run the TCP/IP-32 ipconfig.exe
  program. Since this is a DOS program, it must be run at
  the DOS prompt:
  
    C:\WINDOWS> ipconfig
    Windows IP Configuration Version 1.0
    Ethernet adapter :
     IP Address. . . . . . . : 140.248.208.151
     Subnet Mask . . . . . . : 255.255.0.0
     Default Gateway . . . . : 140.248.208.151
  
  If the IP Address value displayed here does not match the
  one displayed by ShivaRemote, please check the
  configuration.

  
  4.2  Connecting with Static IP Addressing
  
  If you are using static IP addressing (as described in
  section 3.4 above), verify that ShivaRemote obtained the
  appropriate IP address.
  
  First, determine the address obtained by ShivaRemote by
  selecting the Tools/Statistics... menu item, and
  selecting IP from the drop-down list.
  
  Next, compare this to the address expected by TCP/IP-32
  by running the Network Setup program. If this address
  does not match the address reported by ShivaRemote,
  contact your network administrator.
  
  Next, compare this to the address being used by TCP/IP-
  32. To do this, you must run the TCP/IP-32 ipconfig.exe
  program. Since this is a DOS program, it must be run at
  the DOS prompt:
  
    C:\WINDOWS> ipconfig
    Windows IP Configuration Version 1.0
    Ethernet adapter :
     IP Address. . . . . . . : 140.248.208.151
     Subnet Mask . . . . . . : 255.255.0.0
    Default Gateway . . . . : 140.248.208.151
  
  Finally, check again to make sure that you have prevented
  ShivaRemote from updating the IP address used by TCP/IP-
  32 (as described in section 3.4 above). This is very
  important, since it is the mere act of updating the IP
  address, and not just updating with a different address,
  that prevents IP network services from functioning.

  
  4.3  Domain Name Server Address Update
  
  If you are dialing into a Shiva LanRover, ShivaRemote can
  update the Domain Name Server (DNS) address used by
  TCP/IP-32. In order for this feature to work, the
  following conditions must be met:
  
  1. You must be running ShivaRemote 3.5 or later.

  2. You must be dialing into a Shiva LanRover running
     firmware version 3.5 or later.

  3. The LanRover must either be configured with an
     appropriate DNS address, or be configured to obtain dial-
     in IP addresses through DHCP.

  Verify that ShivaRemote updates the DNS address by
  looking at the system.ini file in the Windows directory
  (usually c:\windows). Before you connect, the [DNS]
  section should have the following entry:
  
    [DNS]
    DNSServers=
  
  At connection time, ShivaRemote will update this section:
  
    [DNS]
    DNSServers=140.248.192.1
    SavedDNSServers=
  
  When you disconnect, ShivaRemote will revert to the
  original DNS settings:
  
    [DNS]
    DNSServers=
  
  If you have configured specific DNS server addresses with
  the Network Setup program, ShivaRemote will not delete
  them. Instead, it will insert the new DNS address at the
  front of the list:
  
    [DNS]
    DNSServers=140.248.192.1,192.80.57.1
    SavedDNSServers=192.80.57.1

  
  5.0  Disconnecting
  
  TCP/IP-32 allows you to disconnect from a remote network
  and reconnect at any time.
  However, since the IP address in use may change at
  connection time, it is important that no IP applications
  are running when the connection is made. An IP
  application that is running is not aware of the IP
  address change, and will lose communications with hosts
  on the remote network. If this happens, exit and then re-
  start the IP application.
  
  If you are using static IP addressing (as described in
  section 3.4 above), you can verify that ShivaRemote has
  cleared the IP address by running the ipconfig.exe
  program at the DOS prompt:
  
    C:\WINDOWS> ipconfig
    Windows IP Configuration Version 1.0
    Ethernet adapter :
     IP Address. . . . . . . : 0.0.0.0
     Subnet Mask . . . . . . : 0.0.0.0
     Default Gateway . . . . :

  
  6.0  Using TCP/IP-32 with NetWare
  
  Because Windows for Workgroups 3.11 and TCP/IP-32 can use
  the ShivaRemote ODI dial-in driver, they can be used with
  NetWare. Refer to section 3.1 above for instructions on
  installing the ShivaRemote ODI driver.
  
  Load the drivers in the following order:
  
    C:\> c:\nwclient\lsl
    C:\> c:\shiva\dialodi
    C:\> c:\windows\odihlp
    C:\> c:\nwclient\ipxodi
    C:\> c:\nwclient\vlm
    C:\> c:\windows\net start
  
  For more information on NetWare, refer to the Novell
  NetWare VLM section.
  
  
*********Windows for Workgroups 3.11*********
  
  This section describes how to install, configure, and use
  Microsoft Windows for Workgroups 3.11 with ShivaRemote
  dial-in.
  
  1.0  Introduction
  2.0  Networking Protocols
  3.0  Configuring WFW for NetBEUI
       3.1   Configuring ShivaRemote
       3.2   Updating the NetBEUI Protocol
       3.3   Configuring Other Network Servers
  4.0  Configuring WFW for TCP/IP
       4.1   Obtaining Microsoft TCP/IP-32
       4.2   Configuring TCP/IP-32
       4.3   TCP/IP-32 and IP Addresses
  5.0  Troubleshooting
       5.1   Windows for Workgroups Starts Slowly
       5.2   Cannot See Other Servers when Browsing
       5.3   Cannot Connect to Other Servers
       5.4   File Transfer Failures
       5.5   DHCP Error Message
  
  
  1.0  Introduction
  
  Windows for Workgroups (WFW) is a version of Microsoft
  Windows that includes peer-to-peer networking.
  ShivaRemote supports version 3.11 of Windows for
  Workgroups. If you are using an earlier version, you must
  upgrade it to version 3.11 to use ShivaRemote.
  
  ShivaRemote Version 3.5 supports the following features
  of WFW 3.11:
  
  *   WFW peer networking using the Microsoft NetBEUI and
      TCP/IP protocols
  *   Concurrent support of Novell NetWare and other TCP/IP
      software (Novell LAN Workplace, NetManage Chameleon,
      FTP PC/TCP, etc.)
  *   Dial-in using the ShivaRemote ODI or NDIS driver
  *   Concurrent dial-in and local (Ethernet or Token-Ring)
      network connections
  *   Dial-in connections from either DOS or Windows
  
  Each of these features is discussed in this section.
  

  2.0  Networking Protocols
  
  Windows for Workgroups 3.11 includes a number of
  different networking protocols for its peer networking
  services. All of the features of WFW 3.11 are available
  with each protocol. These protocols are:
  
  *  Microsoft NetBEUI
  *  IPX/SPX Compatible Transport
  *  IPX/SPX Compatible Transport with NetBIOS
  *  Microsoft TCP/IP-32
  
  The first three protocols are included with WFW 3.11. The
  last one, Microsoft TCP/IP-32, has recently been released
  by Microsoft as an add-on for WFW 3.11.For more
  information on configuring this protocol for use in dial-
  in connections, see Microsoft TCP/IP-32
  
  ShivaRemote 3.5 supports the NetBEUI and TCP/IP
  protocols. This topic describes how to install and
  configure these protocols, for use with ShivaRemote.
  
  Unfortunately, due to timing problems in Microsoft's
  protocol implementation, ShivaRemote does not support the
  Microsoft IPX/SPX protocol. If a protocol other than
  NetBEUI is required, Shiva recommends the Microsoft
  TCP/IP-32 protocol.
  
  Note: This does not mean that you cannot connect to
  NetWare servers when dialed in; you can do this by
  installing Novell NetWare and using Novell's IPX
  protocol. You simply cannot connect to WFW 3.11 servers
  using Microsoft's implementation of the IPX protocol.

  
  3.0  Configuring WFW for NetBEUI
  
  This section describes how to configure Windows for
  Workgroups 3.11 with the NetBEUI protocol. If you want to
  install the Microsoft TCP/IP-32 protocol, please follow
  the steps in this section, then proceed with section 4.0
  below.
  
  These instructions assume that you have already installed
  ShivaRemote and Windows for Workgroups 3.11. For
  information on installing ShivaRemote, see the
  ShivaRemote User's Quick Reference for the PC card. For
  information on installing WFW 3.11, refer to the Windows
  for Workgroups documentation.

  
  3.1  Configuring ShivaRemote
      
  To configure ShivaRemote for use with WFW 3.11, follow
  these steps:

  1. Run the Microsoft Windows for Workgroups Network Setup
     program by double-clicking its icon in the Program
     Manager's Network group.
  
  2. In the dialog box that appears, click the Drivers
     button to display the Network Drivers dialog box.
     
  3. Click the Add Adapter button to display the Add Network
     Adapter dialog box.
  
  4. Select Unlisted or Updated Network Adapter from the
     list of network adapters, then click OK.
  
  5. When WFW asks for the location of the driver disk,
     specify the directory in which ShivaRemote has been
     installed (this is usually c:\shiva). Choose the OK
     button.
  
     Note: if you have the ShivaRemote software diskette, you
     can insert it in your floppy drive and specify the
     drive letter (such as A:). Choose the OK button.
  
  6. The entry "ShivaRemote Dial-In Driver" should appear in
     the Unlisted or Updated Network Adapter dialog box.
     Select this entry and choose the OK button.
  
     Note: if the ShivaRemote entry does not appear in this
     dialog box, it may be because you have already added
     the ShivaRemote driver. Check the main adapter list to
     see if this entry is already there. If it is there,
     select it and choose the OK button.
  
     You will return to the Network Drivers dialog box. The
     ShivaRemote driver will be listed, along with the
     default protocols:
  
       ShivaRemote Dial-In Driver
        IPX/SPX Compatible Transport with NetBIOS
        Microsoft NetBEUI
  
  7. As stated in section 1.0 above, the Microsoft IPX/SPX
     protocol does not support ShivaRemote; thus, the
     protocol must be removed. Select the "IPX/SPX
     Compatible Transport with NetBIOS" entry and choose the
     Remove button. The display should now look like this:
  
       ShivaRemote Dial-In Driver
        Microsoft NetBEUI
  
  8. If the ShivaRemote Dial-In driver is the only adapter
     you will use, skip this step and continue with step 9.
  
     If you will also be using a local network adapter (such
     as an Ethernet or Token-Ring card), you must make sure
     that you do not use ShivaRemote to dial into the same
     network that this local card is attached to. Windows
     for Workgroups supports multiple network adapters, but
     only if they are connected to different networks.
  
     If your remote networking server is attached to the same
     network that your local network card is attached to,
     you must remove the other network adapter in order for
     dial-in to function. To do this, select the name of the
     other network adapter and choose the Remove button.
  
     Note: if you do not remove the other network adapter,
     ShivaRemote will display an error message when you
     connect. ShivaRemote will report that a NetBIOS name
     conflict was detected on the remote network, and your
     dial-in connection will be terminated.
  
  9. Determine which ShivaRemote dial-in driver you want to
     use: NDIS or ODI. All of the features of Windows for
     Workgroups are available with each driver. If you
     decide later to switch from one driver to another, you
     can run Network Setup to make the change.

     The driver you select depends on what remote network
     support you need in addition to Windows for Workgroups.
     When choosing the dial-in driver to use, follow these
     guidelines:
  
     If you use only Windows for Workgroups, select the NDIS
     driver. WFW was designed for use with NDIS drivers, and
     NDIS installation and configuration is automatic.
  

     If you use Novell NetWare with WFW, select the ODI
     driver. The NetWare IPX protocol requires an ODI
     driver. Some configuration changes must be made, and
     are described in section ?.? below.
  
     If you are using WFW with another network program,
     select the driver preferred by that network. For
     information on configuring other networks, refer to the
     ShivaRemote Dial-In Configuration Notes.
  
  10.Select the ShivaRemote Dial-In Driver entry and choose
     the Setup... button. At the Driver Type prompt, select
     either "Real Mode NDIS Driver" or "ODI Driver". You are
     returned to the Network Drivers dialog box where the
     driver type should be listed.

     For the NDIS driver:
  
       ShivaRemote Dial-In Driver [NDIS2]
  
     For the ODI driver:
  
       ShivaRemote Dial-In Driver [ODI/NDIS3]
  
  11.Choose the Close button to finish network driver
     setup. This returns you to the Network Setup dialog
     box. Choose the OK button to finish network setup as
     follows:
  
  *  If WFW needs files from the WFW diskettes, insert the
     diskettes as requested. If WFW asks if you want to
     update any files that already exist on your PC, answer
     No.
  
  *  If you selected the ODI driver, WFW may ask for the
     location of your net.cfg file. If you have already
     created a net.cfg file, type in its path and select the
     OK button. If you have not already created a net.cfg
     file, let WFW create one in the Windows directory
     (usually c:\windows).
  
  12.At this point Network Setup is finished. WFW will
     inform you of any configuration files it has changed,
     then ask if you want to restart your PC. Let WFW
     restart your PC so that the configuration changes can
     take effect.

  When your PC restarts, start WFW again by typing win at
  the DOS prompt.

  
  3.2  Updating the NetBEUI Protocol
  
  The NetBEUI protocol module that Microsoft ships with
  Windows for Workgroups 3.11 was designed for local
  networks such as Ethernet and Token-Ring. It does not
  support low-speed network connections such as ShivaRemote
  dial-in.
  
  Shiva has developed and tested a special version of
  NetBEUI that adds support for low-speed network
  connections. This updated module (netbeui.386) is
  included on the ShivaRemote software diskette.
  
  To update the NetBEUI module on your PC, follow these
  steps:
  
  1. Insert the ShivaRemote software diskette in your floppy
     drive. From the Program Manager or File Manager, choose
     the File/Run menu item and enter "a:setup.exe" to run
     the ShivaRemote Setup program.
  
  2. The ShivaRemote Setup dialog box is displayed:
  
     Make sure that the second checkbox is selected, and
     choose the OK button. Setup will update the needed WFW
     system files.
  
  3. When the Setup program is complete, it will prompt you
     to restart your PC. Let Setup restart your PC so that
     configuration changes can take effect.

  
  3.3  Configuring Other Network Servers
  
  Your dial-in PC is now configured and ready to use.
  However, before you can dial in and communicate with
  servers on a remote network, you must configure those
  servers for use with dial-in. ShivaRemote supports the
  following servers for dial-in:
  
  *  Windows for Workgroups 3.11
  *  OS/2 LAN Manager
  *  Windows NT 3.1 and 3.5
  
  Each server on the remote network must be configured in a
  particular manner. If you are able to connect to a remote
  server, but get errors when copying files to or from it,
  the problem may be that the server has not been properly
  configured. Following are instructions for configuring
  each type of server.
  
  Windows for Workgroups 3.11

     To communicate with Windows for Workgroups 3.11 servers
     on the remote network, you must update the NetBEUI
     protocol module on those servers. The updated
     netbeui.386 file is included on the ShivaRemote
     software diskette.
     
     The ShivaRemote Setup program can be used to update the
     NetBEUI module on WFW 3.11 servers. Refer to section
     3.2 above for instructions.
     
  OS/2 LAN Manager

     To communicate with an OS/2 LAN Manager server on the
     remote network, you need to update the server's
     protocol.ini file. Add the following entry to the
     [NetBEUI] section:
     
     [NETBEUI]
     T1=8000
     
     The name of the NetBEUI section may vary; consult your
     LAN Manager documentation for details. The T1 entry
     specifies the main NetBEUI timeout value; 8000
     specifies 8 seconds.
     
  Windows NT 3.1 and Windows NT 3.5

     Windows NT servers do not need to be updated in order
     to work with ShivaRemote dial-in.
     

  4.0  Configuring WFW for TCP/IP
  
  Microsoft TCP/IP-32 is a 32-bit implementation of the
  TCP/IP protocols for Windows for Workgroups 3.11. It
  includes the following features:
  
  *  32-bit VxD implementation occupies no DOS memory
  *  Supports Winsock programs such as Netscape and Eudora
  *  Supports WFW peer networking over TCP/IP
  *  Includes basic FTP and Telnet programs
  
  This section describes how to configure Windows for
  Workgroups 3.11 with the Microsoft TCP/IP-32 protocol. It
  assumes that you have already followed the instructions
  for configuring WFW given in section 3.0 above.
  
  For detailed information about this protocol, refer to
  the Microsoft TCP/IP-32 topic.

  
  4.1  Obtaining Microsoft TCP-IP/32
  
  Since it was released after Windows for Workgroups 3.11,
  Microsoft TCP/IP-32 is not included on the WFW 3.11
  diskettes. Instead, it must be obtained from Microsoft.
  If you have already obtained TCP/IP-32, skip ahead to
  section 4.2.
  
  To obtain this software, you must have a connection to
  the Internet, and you must be able to connect to
  Microsoft's FTP server, ftp.microsoft.com. Follow these
  steps:
  
  1. At your FTP prompt, enter the following command to
     connect to the Microsoft FTP server:
  
       ftp> open ftp.microsoft.com
  
  2. When prompted for your user name, enter the following:
  
       anonymous
  
     When prompted for your password, enter your complete
     electronic mail ID:
  
       user@host.com
  
  3. Once you are logged into the Microsoft FTP server,
     download the TCP/IP-32 file by entering the following
     commands:
  
       ftp> cd peropsys/windows/public/tcpip
       ftp> binary
       ftp> get WFWT32.EXE
  
  4. When the download is complete, disconnect from the FTP
     server:
  
       ftp> close
  
     Then exit your FTP program.
  
  5. The file wfwt32.exe is a self-extracting archive file.
     Execute this program at the DOS prompt to extract the
     TCP/IP-32 files:
  
       C:\MSTCP32> wfwt32
  
     The TCP/IP-32 files will be placed in the current
     directory. When the Network Setup program asks for the
     location of these files, specify this directory.
  
     If the program reports errors while extracting files,
     or if the program hangs, it most likely indicates that
     you did not specify a binary transfer as described in
     step 3 above. Get the file again, making sure to
     specify a binary transfer.

  
  4.2  Configuring TCP/IP-32
  
  This section describes how to configure Windows for
  Workgroups 3.11 with the Microsoft TCP/IP-32 protocol. It
  assumes that you have followed the instructions in
  section 3.0 above.
  
  1. Run the Network Setup program by double-clicking its
     icon in the Program Manager's Network group.
  
  2. Choose the Drivers... button to display the Network
     Drivers dialog box.
  
  3. Highlight the ShivaRemote Dial-In Driver entry by
     clicking on it or by using the arrow keys. If
     ShivaRemote has not been installed as a network
     adapter, please refer to the instructions in section
     3.1 above before proceeding.
  
  4. Choose the Add Protocol... button to display the Add
     Network Protocol dialog box.
  
  5. Select Unlisted or Updated Protocol from the list of
     network protocols, and choose the OK button.
  
  6. When the Install Driver dialog box appears, enter the
     drive and directory where the TCP/IP-32 files are
     located, then choose the OK button. For example, if the
     files are on a floppy diskette, enter A: and choose the
     OK button.
  
  7. When the Unlisted or Updated Protocol dialog box
     appears, there should be an entry named Microsoft
     TCP/IP-32 3.11. Highlight this entry and choose the OK
     button. If Network Setup asks you if you want to
     replace any Microsoft TCP/IP-32 files already installed
     on your computer, answer Yes.

  8. When you are returned to the Network Drivers dialog
     box, the ShivaRemote entry should look like this:
  
     ShivaRemote Dial-In Driver
       Microsoft NetBEUI
       Microsoft TCP/IP-32 3.11
     
     If you wish to use only the TCP/IP protocol, highlight
     the Microsoft NetBEUI entry and click the Remove
     button.
  
     Finally, click the Close button to close the Network
     Drivers dialog box.
  
  9. When you return to the Network Setup dialog box, click
     OK.
  
     If Network Setup asks you if you want to replace any
     Enhanced Protocol Manager files already installed on
     your computer, answer No. This prevents network setup
     from overwriting any files updated by the ShivaRemote
     Setup program.
  
  10.You will be presented with the Microsoft TCP/IP
     Configuration dialog box. Follow these steps to
     configure TCP/IP:

  *   Do not check the Enable Automatic DHCP Configuration
      option. Configuring the ShivaRemote driver to obtain
      its configuration through DHCP will not work.
  
  *   At the IP Address: prompt, enter a valid IP address.
      It does not matter what this address is; it matters
      only that a valid address is entered. When the dial-
      in connection is made, ShivaRemote will update TCP/IP-
      32 with the appropriate IP address.
  
  *   The Subnet Mask: field will be updated automatically
      based on the IP address entered above. Do not change
      this value.
  
  *   At the Default Gateway: prompt, enter the same IP
      address entered at the IP Address: prompt above. When
      the dial-in connection is made, ShivaRemote will
      update TCP/IP-32 with the appropriate IP address
      value.
  
     When these fields are filled in, select the OK button.
     When Network Setup asks if you want to set the IP
     Address and Default Gateway values to the same address,
     answer Yes.
  
  11.When Network Setup is done modifying your
     configuration files, it will prompt you to restart your
     computer. Allow Network Setup to restart your computer
     so that these changes can take effect.

  
  4.3  TCP/IP-32 and IP Addresses
  
  As stated above, ShivaRemote can update the IP address
  used by TCP/IP-32 when a dial-in connection is made.
  Unfortunately, there is an unresolved problem with this
  address update feature. This section describes this
  problem.
  
  Microsoft TCP/IP-32 applications fall into two
  categories: IP services and networking services:
  
  IP Services
  
     IP services are standard TCP/IP applications such as
     ping, telnet, and FTP. In addition, Winsock-based
     applications such as Mosaic and Eudora are considered
     IP services.
     
  Networking Services
  
     Networking services are the ability to connect to a
     network file or print server, such as a Microsoft
     Windows NT or LAN Manager server.
     
  The ShivaRemote IP address update feature works with IP
  services. Unfortunately, due to a problem in WFW and
  TCP/IP-32, this feature does not work with networking
  services. Microsoft has acknowledged this problem, and
  has indicated that it will not be fixed.
  
  Thus, you have two options: you can use IP address
  updating with IP services, or you can use static IP
  addressing with networking services. Below are
  instructions for each option.
  
  Dynamic IP Address Updating
  
     If you will only use TCP/IP-32 for IP services, and
     will not use it to connect to network file servers,
     then you can use the IP address update feature of
     ShivaRemote. However, in order to do this, you must
     disable IP networking services.
     
     To do this, you need to edit your system.ini file. In
     the [386Enh] section, you will find a transport= entry:
     
        [386Enh]
        transport=vip.386,vdhcp.386,vtdi.386,vtcp.386,vnbt.386
     
     Remove vnbt.386 from this entry:
     
        [386Enh]
        transport=vip.386,vdhcp.386,vtdi.386,vtcp.386
     
     This disables NetBIOS over TCP/IP, which effectively
     disables networking services over TCP/IP-32. However,
     it leaves all other IP services intact.
     
     Once you have disabled networking services, verify that
     ShivaRemote is updating the IP address at connection
     time. When ShivaRemote makes an IP connection, it
     reports the IP address that it has been assigned. For
     example:
     
        Note: Your IP address is 140.248.208.151
     
     To verify that TCP/IP-32 has been updated with this
     address, run the ipconfig.exe program. This is a DOS
     program, so it must be run in a DOS command window:
     
        C:\WINDOWS> ipconfig
        Windows IP Configuration Version 1.0
        Ethernet adapter :
         IP Address. . . . . . . : 140.248.208.151
         Subnet Mask . . . . . . : 255.255.0.0
         Default Gateway . . . . : 140.248.208.151
     
     You must verify two things:
     
     That the IP address reported by TCP/IP-32 is the same
     as the IP address reported by ShivaRemote at connection
     time (in this case, 140.248.208.151); and
     
     That this address is also reported by TCP/IP-32 as its
     Default Gateway
     When you disconnect from the remote network,
     ShivaRemote will clear the IP address. This prevents
     long delays when you are not connected to a remote
     network. After disconnection, verify that the IP
     address has been cleared:
     
        C:\WINDOWS> ipconfig
        Windows IP Configuration Version 1.0
        Ethernet adapter :
         IP Address. . . . . . . : 0.0.0.0
         Subnet Mask . . . . . . : 0.0.0.0
         Default Gateway . . . . :
     
     If this is not the case, it indicates that you have not
     properly installed ShivaRemote. Please run the
     ShivaRemote Setup program again.
     
  Static IP Addressing
  
     If you will use TCP/IP-32 for networking services, then
     you cannot use the IP address update feature of
     ShivaRemote. By default, ShivaRemote will update the IP
     address at connection time; thus, this feature must be
     explicitly disabled.
     
     To do this, add the following entry to the [Options]
     section of the sremote.ini file:
     
        [Options]
        UpdateIPAddress=No
     
     The sremote.ini file is in the Shiva directory, usually
     c:\shiva.
     
     Since you have disabled IP address updating, you must
     now configure the correct IP address for your dial-in
     connection. Ask your network administrator for the
     appropriate IP address. Run the Network Setup program
     and enter this address as described in section 4.2
     above.
     
     Next, verify that ShivaRemote does not change this
     address after the dial-in connection is made:
     
        C:\WINDOWS> ipconfig
        Windows IP Configuration Version 1.0
        Ethernet adapter :
         IP Address. . . . . . . : 140.248.208.151
         Subnet Mask . . . . . . : 255.255.0.0
         Default Gateway . . . . : 140.248.208.151
     
     Finally, verify that ShivaRemote does not clear the
     address after you disconnect from the remote network.
     Run ipconfig.exe again and verify that the IP address
     has not been changed to 0.0.0.0.

  
  5.0  Troubleshooting
  
  This section describes some problems that you may
  encounter while using ShivaRemote with Windows for
  Workgroups 3.11.

  
  5.1  Windows for Workgroups Starts Slowly
  
  When the ShivaRemote dial-in driver is installed, Windows
  for Workgroups should start up as quickly as it does when
  the driver is not installed. If Windows for Workgroups
  takes an inordinate amount of time to start up, your
  configuration may be incorrect.
  
  Specifically, make sure that all of the Windows for
  Workgroups files have been updated by the ShivaRemote
  Setup program. These files are netbeui.386, ndis2sup.386
  (for the NDIS driver), and msodisup.386 (for the ODI
  driver). Refer to section 3.2 above for details.

  
  5.2  Cannot See Other Servers when Browsing
  
  With the File Manager, you can search for WFW servers on
  the remote network by choosing the Disk/Connect Network
  Drive... menu selection. A list of workgroups and
  computers found on the remote network is displayed in the
  Show Shared Directories on: box. This is known as
  browsing.
  
  If no computers are displayed in this box, it may
  indicate a configuration problem. For dial-in browsing to
  function properly, you must be in a workgroup that has at
  least one other member on the remote network. If this is
  not the case, you must change your workgroup by running
  the Network item in the Control Panel.
  
  If browsing still does not work, try setting the
  following entry in your system.ini file:
  
    [network]
    MaintainServerList=No
  
  Note: regardless of whether browsing works, you should
  always be able to connect to a remote network by typing
  its name in the Path: field of the browse dialog. For
  example, to find a list of shares on the server named
  STRIPER, you would enter "\\striper" at this prompt, then
  select the OK button. If you cannot connect to remote
  servers in this manner, it may indicate a network
  problem.

  
  5.3  Cannot Connect to Other Servers
  
  If you are unable to connect to a server on a remote
  network, check the following potential problems:
  
  1. Make sure that you are dialed into a remote network. If
     you are not dialed into a remote network, Windows for
     Workgroups will report that "The selected server cannot
     be found on the network."
  
  2. Make sure that the appropriate protocol (NetBEUI and/or
     TCP/IP) is enabled in the ShivaRemote connection file.
     To check whether a protocol is active on a given dial-
     in connection, select the Tools/Statistics... menu item
     and check the display for the protocol.
  
  3. If you are using Microsoft TCP/IP-32, make sure that
     you are not also using ShivaRemote IP address updating.
     Refer to section 4.3 above for details.
     
  4. Make sure that you are using the updated NetBEUI
     module. Refer to section 3.2 above for details.


  5.4  File Transfer Failures
  
  When you copy files to or from a remote server that is
  configured properly, the transfers should succeed. If you
  get error messages from WFW, it may indicate a problem in
  your configuration.
  
  For example, when reading files from a remote server, you
  might see the message "Network drive does not exist," or
  "Extended error 53." When writing files to a remote
  server, you might see "Disk full." There are several
  possible causes of these errors:
  
  1. Check the ShivaRemote statistics by selecting the
     Tools/Statistics... menu item, then selecting Async
     from the drop-down list. If the Overrun errors: item is
     not 0, it indicates that your serial port is unable to
     keep up with the data coming from the modem. Try
     lowering the serial port speed with the Tools/Port
     Setup... menu selection.

  2. If you are using the NetBEUI protocol, make sure that
     the NetBEUI module on the remote file server has been
     updated. Refer to section 3.3 above for details.
  
  3. Make sure that you have removed the IPX/SPX Compatible
     Transport protocol. If you do not remove this protocol,
     then Windows for Workgroups 3.11 will use it for all
     file server connections. Since this protocol does not
     support low-speed connections such as ShivaRemote dial-
     in, all file transfers will fail. Refer to section 3.1
     above for details on removing this protocol.

  
  5.5  DHCP Error Message
  
  If Windows for Workgroups takes a long time to start, and
  then you get the following error message:
  
    Unable to get DHCP Address
  
  It indicates that your computer is configured to use the
  DHCP protocol to obtain its IP address. As described in
  section 4.2 above, the ShivaRemote dial-in driver should
  not be configured for DHCP.

  
*********NetManage Chameleon*********
  
  This section describes how to install, configure, and use
  NetManage Chameleon with ShivaRemote dial-in.
  
  1.0  Introduction
  2.0  Installing Chameleon (NDIS)
       2.1   Running Chameleon Custom
       2.2   Checking NDIS Configuration
  3.0  Installing Chameleon (ODI)
       3.1   Running Chameleon Custom
       3.2   Loading ODI Drivers
  4.0  Connecting
  5.0  Disconnecting
  6.0  Using Chameleon with NetWare
  7.0  Using Chameleon with a Shiva LanRover
       7.1   The BOOTP Protocol
       7.2   BOOTP with a LanRover
       7.3   Configuring Chameleon for BOOTP
       7.4   Using Chameleon with BOOTP
  
  
  NetManage, Inc.
  20823 Stevens Creek Blvd.
  Cupertino, CA 95014
  Phone: (408) 973-7171
  Fax: (408) 257-6405
  

  1.0  Introduction
  
  Chameleon is a NetManage's IP package for Windows.
  ShivaRemote supports two major versions of Chameleon:
  3.11 and 4.0. Chameleon 3.11 can use NDIS drivers only,
  while Chameleon 4.0 can use NDIS drivers or ODI drivers.
  
  Currently, ShivaRemote is not able to update the IP
  address used by Chameleon upon connection. If you are
  dialing into a Shiva LanRover, you can rely on the
  LanRover's BOOTP support; details are given in section
  7.0 below. If you are dialing into another remote
  networking server, you must configure an appropriate IP
  address, as described below. Ask your network
  administrator for the IP address you should use.
  
  The configuration information below assumes that you have
  run the Chameleon Setup program.

  
  2.0  Installing Chameleon (NDIS)
  
  Both supported versions of Chameleon (3.11 and 4.0) can
  use NDIS drivers. This section describes how to install
  and configure Chameleon for use with the ShivaRemote NDIS
  driver. If you want to use the ShivaRemote ODI driver,
  refer to section 3.0 below.
  

  2.1  Running Chameleon Custom
  
  The Chameleon Custom program is used to configure network
  card drivers and IP protocol settings. Run Custom, and
  select the Setup/Hardware... menu item. If this menu item
  is disabled, it indicates that you already have an ODI
  network card driver loaded; refer to section 3.0 below.
  
  In the Vendor: field, select (Other), and fill in the
  dialog as shown below, making sure to use all upper-case
  letters where SDIALIN$ is specified.
  
  Next, select the Setup/IP Address... menu item, and fill
  in the IP address you will use for dial-in (in the
  example below, 140.248.208.151).
  
  Finally, exit Custom and check the configuration files as
  described in the next section.
  

  2.2  Checking NDIS Configuration
  
  Next, confirm that Custom has properly configured your PC
  for dial-in. The following entries should be added to
  your config.sys file:
  
     device=c:\netmanag\protman.dos /i:c:\netmanag
     device=c:\netmanag\dialndis.exe
     device=c:\netmanag\netmanag.dos
  
  The Custom program copies the ShivaRemote NDIS driver
  (dialndis.exe) into the NetManage Chameleon directory
  (c:\netmanag in this example). In order to avoid
  configuration problems later, it is a good idea to edit
  config.sys so that it refers to the ShivaRemote
  directory:
  
     device=c:\shiva\dialndis.exe
  
  Your protocol.ini file should contain the following
  sections:
  
     [SDIALIN$]
     DriverName=SDIALIN$
  
     [NetManage]
     DriverName=NETMNG$
     Bindings=SDIALIN$
  
  Make sure that SDIALIN$ is always in upper-case letters.
  Finally, your autoexec.bat file should contain the
  following command:
  
     c:\netmanag\netbind.exe
  
  Once you have verified these configuration files, reboot
  your PC and restart Windows. You are now ready to use
  Chameleon, as described in section 4.0 below.
  

  3.0  Installing Chameleon (ODI)
  
  In order to use Chameleon with the ShivaRemote ODI
  driver, you must use Chameleon version 4.0. If you only
  have version 3.11 of Chameleon, you must use the
  ShivaRemote NDIS driver as described in section 2.0
  above.

  
  3.1  Running Chameleon Custom
  
  The Chameleon Custom program is used to configure network
  card drivers and IP protocol settings. By default, Custom
  will use an NDIS driver. In order to use an ODI driver,
  you must load the ODI driver before starting Windows and
  running Custom.
  
  At the DOS prompt, run the following commands:
  
     C:\SHIVA> lsl
     C:\SHIVA> dialodi
  
  These two drivers are included on the ShivaRemote
  software diskette, and are installed by the ShivaRemote
  Setup program.
  
  After these drivers are loaded, start Windows and run the
  Chameleon Custom program. Select the Setup menu and
  verify that the Hardware... option is disabled. If it is
  still enabled, it may indicate that you did not load the
  dialodi.exe before starting Windows, or that you are not
  running Chameleon version 4.0.
  
  Next, select the Setup/IP Address... menu item, and fill
  in the IP address you will use for dial-in. Ask your
  network administrator for the IP address you should
  enter; in the example below, 140.248.208.151 is used.
  
  Finally, exit Windows and load the ODI drivers as
  described below.
  

  3.2  Loading ODI Drivers
  
  The ODI drivers for Chameleon are loaded at the DOS
  prompt (or in the autoexec.bat file). Load the drivers in
  the following order:
  
     C:\NETMANAG> lsl
     C:\NETMANAG> dialodi
     C:\NETMANAG> nmodi
  
  The first two drivers (lsl.com and dialodi.exe) are found
  in the ShivaRemote directory. The last driver (nmodi.com)
  is found in the Chameleon directory.
  
  Once these drivers are loaded, you are ready to use
  Chameleon, as described in section 4.0 below.
  

  4.0  Connecting
  
  Before you dial into a remote network, make sure that you
  have configured the appropriate IP address as described
  in sections 2.1 and 3.1 above. This IP address is
  assigned by your network administrator. If you are
  dialing into a Shiva LanRover, refer to section 7.0
  below.
  
  Chameleon does not require a dial-in connection when
  Windows starts; thus, you can use the ShivaRemote Connect
  program for Windows. For information on using ShivaRemote
  Connect, refer to the ShivaRemote Online User's Guide.
  
  During the connection process, Connect will inform you of
  the IP address assigned to you by the remote networking
  server. Verify that this is the same address configured
  in Chameleon by running the Chameleon Custom program.

  
  5.0  Disconnecting
  
  You can disconnect from the remote network at any time by
  running the ShivaRemote Connect program for Windows and
  choosing the Disconnect button.
  
  It is a good idea to exit any Chameleon applications
  before you disconnect. If you disconnect before exiting
  an application, the application may attempt to
  communicate with the remote network. Since you are no
  longer connected to the remote network, it may take
  several minutes before the application gives up.
  
  
  6.0  Using Chameleon with NetWare
  
  Since Chameleon 4.0 can use an ODI driver, it can easily
  be used with NetWare. Follow the directions given in
  section 3.0 above for configuring Chameleon with ODI.
  
  Next, load the ODI drivers in the following order:
  
     C:\NETMANAG> lsl
     C:\NETMANAG> dialodi
     C:\NETMANAG> nmodi
     C:\NETMANAG> ipxodi
     C:\NETMANAG> vlm
  
  For further information on NetWare, refer to the Novell
  NetWare section.
  
  
  7.0  Using Chameleon with a Shiva LanRover
  
  The Shiva LanRover includes a feature that simplifies IP
  address configuration with Chameleon. If you dial into a
  Shiva LanRover, follow the directions in this section. If
  you dial into another remote networking server, please
  follow the directions above for IP address configuration.
  
  
  7.1  The BOOTP Protocol
  
  BOOTP is a protocol that allows a computer to obtain its
  IP address (and other IP configuration information) from
  a central server. This allows a network administrator to
  maintain a single configuration server for all computers
  on a network; each computer does not need specific
  configuration.
  
  When a computer is configured for the BOOTP protocol, it
  is not assigned an IP address. Instead, when it
  initializes it searches for a BOOTP server on the network
  that can configure it. The BOOTP server responds with the
  IP address that the computer should use. In addition, the
  BOOTP server can provide other information, such as the
  address of a DNS server and the address of a time server.
  
  
  7.2  BOOTP with a LanRover
  
  When a computer uses ShivaRemote to dial into a LanRover,
  it is assigned an IP address by the LanRover. This IP
  address assignment is independent of any BOOTP servers
  that might be running on the network. Thus, it is
  inappropriate for the dialed-in computer to request an
  address from a BOOTP server, since it has already been
  assigned an address by the LanRover.
  
  However, the LanRover will pretend to be a BOOTP server
  for the benefit of the dialed-in computer. When the
  computer sends a BOOTP request to the remote network, the
  LanRover will return a BOOTP response that contains the
  negotiated IP address (and whatever other options have
  been configured).
  
  This allows the dialed-in computer to be configured for
  BOOTP, which means that it does not have to be configured
  with a specific IP address.
  
  
  7.3  Configuring Chameleon for BOOTP
  
  To configure Chameleon for BOOTP, run the Chameleon
  Custom program and select the Setup/BOOTP... menu item.
  Check the Use BOOTP box and choose the OK button.
  
  
  7.4  Using Chameleon With BOOTP
  
  When Chameleon is configured for BOOTP, you must connect
  to a LanRover before you run any Chameleon applications.
  If you run an application before you connect, Chameleon
  will search for a BOOTP server, and will not find one. It
  will report the following error message:
  
    Waiting for BOOTP response.
  
  It is also a good idea to exit all Chameleon applications
  before you disconnect from the remote network.
  
  
*********Novell LAN Workplace*********
  
  LAN Workplace is Novell's IP package for DOS and Windows.
  This section describes how to use LAN Workplace with
  ShivaRemote dial-in.
  
  1.0  Installing LAN Workplace
  2.0  Configuring LAN Workplace
  3.0  Loading LAN Workplace
  4.0  Connecting
       4.1   Connecting in DOS
       4.2   Connecting in Windows
  5.0  Disconnecting
  6.0  Using LAN Workplace with NetWare
  
  
  1.0  Installing LAN Workplace
  
  For help installing LAN Workplace, see Novell's
  installation guide.
  
  
  2.0  Configuring LAN Workplace
  
  You do not have to configure LAN Workplace with the
  correct IP address that you will use for dial-in.
  Instead, ShivaRemote will automatically update the LAN
  Workplace TCP/IP driver with the IP address that was
  assigned by the remote networking server.
  
  However, in order to get LAN Workplace to load, you must
  configure it with a temporary IP address. This is done in
  the net.cfg file:
  
     Protocol TCPIP
      ip_address 140.248.208.151
  
  It does not matter what this address is. It matters only
  that an address be given, so that LAN Workplace will
  load. As stated above, ShivaRemote will inform LAN
  Workplace of the appropriate address at connection time.
  
  
  3.0  Loading LAN Workplace
  
  The LAN Workplace software must be loaded at the DOS
  prompt (or in the autoexec.bat file). Load the drivers in
  the following order:
  
     C:\NET> lsl
     C:\NET> dialodi
     C:\NET> tcpip
  
  When you load tcpip.exe, it should report its address
  settings and return to the DOS prompt immediately. If it
  does not return to the DOS prompt immediately, but
  instead reports "Waiting for BOOTP reply..." or "Waiting
  for RARP reply...", please check the IP address
  configuration as described in section 2.0 above.
  
  It is very important that the LAN Workplace TCP/IP driver
  (tcpip.exe) be loaded before you dial into a remote
  network. If you connect before tcpip.exe is loaded, then
  ShivaRemote will not be able to update the IP address.
  
  
  4.0  Connecting
  
  This section describes how to use LAN Workplace with a
  remote network.
  
  
  4.1  Connecting in DOS
  
  To dial into a remote network in DOS, use the ShivaRemote
  Connect program for DOS and a ShivaRemote connection
  file:
  
     C:\NET> connect @filename
  
  For more information about connecting to a remote
  network, refer to the ShivaRemote Online User's Guide.
  
  The ShivaRemote connect program will report the IP
  address that has been assigned by the remote networking
  server. Verify that LAN Workplace has been updated with
  this address by running the LAN Workplace Console
  program:
  
     C:\NET> lwpcon
  
  If the address reported here does not match the address
  reported by the ShivaRemote Connect program, make sure
  that the LAN Workplace driver (tcpip.exe) is loaded
  before the dial-in connection is made.
  
  Once you are connected, you can use LAN Workplace
  programs for DOS such as ping.exe, tnvt220.exe, and
  ftp.exe.
  
  
  4.2  Connecting in Windows
  
  LAN Workplace does not require that you connect in DOS.
  Instead, you can start Windows, then use the ShivaRemote
  Connect program for Windows. This allows you to use the
  Windows versions of the LAN Workplace utilities.
  
  
  5.0  Disconnecting
  
  LAN Workplace does not place any restrictions on when you
  can disconnect from the remote network. In DOS, just use
  the ShivaRemote Connect program:
  
     C:\SHIVA> connect /d
  
  In Windows, run the ShivaRemote Connect program for
  Windows, then select the Disconnect button.
  
  
  6.0  Using LAN Workplace with NetWare
  
  Since LAN Workplace and NetWare both use the ODI driver
  standard, both can be used with ShivaRemote dial-in.
  
  Load the network drivers in the following order:
  
     C:\NET> lsl
     C:\NET> dialodi
     C:\NET> tcpip
     C:\NET> ipxodi
     C:\NET> vlm
  
  For detailed information on configuring NetWare, refer to
  the Novell NetWare VLM section.
  
  
*********Novell NetWare*********
  
  ShivaRemote fully supports both types of NetWare client
  software: VLM (Virtual Loadable Module) and NETX.
  
  VLM is Novell's new client software for NetWare versions
  3.11 and later. VLM is strongly recommended for best dial-
  in performance.
  
  NETX is Novell's old client software for all versions of
  NetWare. Work on NETX has been discontinued by Novell,
  and Novell encourages all users to upgrade to VLM.
  
  For help on using either type of client software, see its
  topic in this section:
  
     VLM
  
     NETX
  
  
  Novell, Inc.
  122 East
  1700 South
  Provo, UT 84606
  Phone:  (801) 429-7000
          (800) 453-1267
  
  
Novell NetWare VLM
  
  This section describes how to install, configure, and use
  the NetWare Virtual Loadable Modules (VLMs) for use with
  dial-in.
  
  1.0  Introduction
  2.0  Obtaining the VLMs
  3.0  Installing the VLMs
  4.0  Installing Burst Mode Server Support
  5.0  Using the VLMs with DOS
       5.1   Loading the VLMs
       5.2   Dialing into a Remote Network
       5.3   Attaching to a NetWare Server
       5.4   Logging into a NetWare Server
       5.5   Disconnecting from the Remote NetWork
  6.0  Using the VLMs with Windows
       6.1   Loading the VLMs
       6.2   Starting Windows
       6.3   Dialing into a Remote Network
       6.4   Logging into a NetWare Server
       6.5   Mapping a Drive
       6.6   Using Remote Drives
       6.7   Disconnecting from a Remote Network
       6.8   Using the Automatic Reconnect Feature
       6.9   Using the VLMs with Windows for Workgroups 3.11
  7.0  Troubleshooting
  
  
  1.0  Introduction
  
  Virtual Loadable Modules (VLMs) are Novell's new client
  software. VLMs replace NETX, the old client software.
  Shiva will continue to support NETX, but strongly
  encourages users to upgrade to VLMs.
  
  ShivaRemote fully supports the use of VLMs, starting with
  the Novell NetWare Client release 1.2. Shiva has tested
  the VLMs to make sure they work as well as possible with
  our remote access solutions. Please read this document
  carefully before installing and using the VLMs.
  VLMs provide the following major benefits for ShivaRemote
  dial-in:
  
     Burst Mode Support. Novell's Burst Mode protocol is
     designed to improve file transfer speeds over slow
     links (such as modems). The protocol allows the PC to
     send more than one packet at a time without waiting for
     a response from the server.
     Testing shows that Burst Mode improves file transfer
     performance by 50% to 100% over NETX.
     
     Windows-Based Dial-In. With Novell's old client
     software, you had to make your dial-in connection
     before you loaded NETX, and thus before you started
     Windows. VLMs can be loaded without a dial-in
     connection.
     
     This allows you to make your dial-in connection from
     within Windows whenever you want to access data on a
     remote network, then disconnect when you are done.
     
     Extended Memory Support. VLMs can be loaded in extended
     memory, leaving more DOS memory for your applications.
     
  
  2.0  Obtaining the VLMs
  
  The current version of the VLMs are found in the NetWare
  DOS/Windows Client Kit version 1.2. A copy of the NetWare
  Client 1.2 is included with each remote access server
  purchased from Shiva Corporation.
  
  You can also find the latest version of the VLMs in the
  following ways:
  
  *   Purchase them from Novell. Contact Novell at (801)
      429-7000 or (800) 453-1267 for more information.
  *   Download them from Novell's forum on CompuServe. You
      can find Novell's forum by logging on to CompuServe
      and typing GO NETWIRE at any CompuServe prompt.
      (CompuServe Information Manager users can choose Go
      from the Services menu and enter NETWIRE in the
      dialog box that appears.)
  
  
  3.0  Installing the VLMs
  
  You use the NetWare Client Install program to install the
  VLMs on your computer. The steps for doing this are as
  follows:
  
  1. Install ShivaRemote as described in the ShivaRemote
     User's Quick Reference card.
  
  2. Exit Windows if it is currently running.
  
  3. Insert Disk 1 of the NetWare Client Kit 1.2 in your
     computer's disk drive and make that drive the current
     drive by typing "A:" (or "B:") and then Enter.
  
     The NetWare client Install program will not run unless
     the floppy drive is the current drive letter.
  
  4. Run the Install program by typing "install" and
     pressing Enter.
  
  5. In Step 1 of Install, specify the directory on your
     hard disk where the VLMs should be installed or accept
     the default directory c:\nwclient.
  
  6. If you have Microsoft Windows on your PC, in Step 3 of
     Install, select "Yes" and specify your Windows
     directory.
  
     The default directory is c:\windows. If you have
     installed Windows in a different directory, enter that
     directory name here.
  
  7. In the next step of the installation, press Enter to
     specify the network card you will use. An entry called
     "ShivaRemote Dial-In Driver" should appear in the list.
     If it does, skip ahead to Step 8 of these instructions.
  
     If the ShivaRemote driver does not appear in the list,
     select OTHER DRIVERS, which is the last entry on the
     list. When the Install program asks for the location of
     the Driver Disk, type in the full path of the
     ShivaRemote directory (usually c:\shiva).
  
     Note: if the Install program cannot find a necessary
     file, this may indicate that you have not installed
     ShivaRemote version 3.2 or later. In this case, run
     your most recent ShivaRemote Setup program.
  
  8. Select ShivaRemote Dial-In Driver from the list and
     press Enter. When Install asks you to specify the
     configuration for the driver, press the Esc key to
     continue. The ShivaRemote dial-in driver does not
     require any configuration.

  9. When you return to the main Install screen, highlight
     Step 6 and press the Enter key. Insert the appropriate
     NetWare Client disks as requested by Install.
  
     Note: the complete NetWare Client 1.2 consists of five
     disks, and the Install program will ask for them in
     order. The version of the NetWare Client 1.2 included
     with a Shiva remote access server has been placed on
     two disks. When the Install program asks for the
     NetWare Client disk #4, insert the second disk. All of
     the files originally found on the NetWare Client 1.2
     disk 4 are found on Shiva's VLM installation Disk 2.
  
     When installation is complete, press Enter to return to
     the DOS prompt.
  
  10.Specify a preferred NetWare server by editing the
     NET.CFG file that Install created in the NetWare Client
     directory (usually c:\nwclient). You can use any text
     editor to modify this file, including the DOS EDIT
     command.

     The NET.CFG file should look similar to the following:
  
        Link Driver DIALODI
  
        NetWare DOS Requester
            FIRST NETWORK DRIVE = F
            NETWARE PROTOCOL = NDS BIND
  
     Add an entry that specifies your preferred server:
  
        NetWare DOS Requester
            FIRST NETWORK DRIVE = F
            NETWARE PROTOCOL = NDS BIND
            preferred server = SERV1
  
     In addition, if you will dial into a Shiva remote
     access server, you should have your network
     administrator configure it so that you are connected to
     the preferred NetWare server first. To do this, your
     administrator must add the following entry to the
     [NetWare] section of the Shiva remote access server's
     configuration file:
  
       [NetWare]
       DefaultNearestServer=SERV1
  
     Have your administrator refer to the Shiva Net Manager
     documentation for instructions on manually adding an
     entry to the Shiva remote access server's configuration
     file.
  
  11.If you are using ONLY NetWare 4.01 and later at your
     site, skip this step.
  
     If you are using NetWare 3.x, you must modify NetWare
     Protocol entry in the NET.CFG file. This entry
     specifies the order in which the VLMs connect to
     NetWare servers. NDS is NetWare Directory Services,
     which is available only in NetWare 4.01. BIND is the
     NetWare Bindery, which is used by 3.x servers.
  
     Since NetWare 3.x does not support Directory Services,
     reverse the order of the entries on the NetWare
     Protocol line:
  
       NETWARE PROTOCOL = BIND NDS
  
     If you do not put BIND first, the VLMs will search
     first for NetWare 4.X servers. If you do not have any
     NetWare 4.X servers on your network, a delay of up to
     30 seconds occurs when you connect.
  
     The VLMs should now be installed and configured
     properly, and ready for use. The following sections
     discuss how to use the VLMs.
  
  
  4.0  Installing Burst Mode Server Support
  
  As stated above, the VLMs support the Novell Burst Mode
  protocol, which increases dial-in performance
  substantially. Burst Mode support must also be installed
  on any NetWare server that you will connect to.
  
  Burst Mode support is built into NetWare versions 3.12,
  4.01, and later. If you have only these versions
  installed, you can skip this section.
  
  If you have NetWare version 3.11 installed on your
  network, you must perform the following steps:
  
  1. Obtain the file pburst.nlm. This file is available in
     Novell's NetWire forum on CompuServe in the DOSUP9.EXE
     file.
  
  2. Copy the pburst.nlm file into the SYSTEM directory of
     your server's SYS volume. You might need to log into
     your NetWare server as SUPERVISOR in order to gain
     access to this directory.
  
  3. Add the following two lines to the end of your
     autoexec.ncf file:
  
        load PBURST
        set NCP Packet Signature Option = 0
  
     The first line loads the Burst Mode module. The second
     line disables the NCP Packet Signature security option.
  
  4. Finally, restart your NetWare server so that the above
     commands are executed. If you do not want to restart
     your server, you can instead type the above two
     commands at the NetWare server command prompt.
  
  
  5.0  Using the VLMs with DOS
  
  This section describes how to use the VLMs with DOS. If
  you are using the VLMs with Windows, read this section
  first, then proceed with the section below on Windows.
  
  
  5.1  Loading the VLMs
  
  Since the VLMs can be loaded without a dial-in network
  connection, you can load them in your AUTOEXEC.BAT file.
  The NetWare Client Install procedure described above
  creates a batch file called STARTNET.BAT. This file
  contains the following commands:
  
  SET NWLANGUAGE=ENGLISH
  C:\NWCLIENT\LSL
  :DRIVER1
  C:\NWCLIENT\DIALODI.EXE
  C:\NWCLIENT\IPXODI
  C:\NWCLIENT\VLM
  
  To load these files during AUTOEXEC.BAT, verify that the
  following command is in your AUTOEXEC.BAT file:
  
  @call c:\nwclient\startnet.bat
  
  The NetWare Client Install program may have added this
  line to AUTOEXEC.BAT already. If it did not, add it at
  the end of the file.
  
  When your PC starts, these commands are executed and the
  network drivers are loaded. These files should load and
  return to the DOS prompt immediately. If you experience
  any delays when VLM.EXE is being loaded, please refer to
  the troubleshooting section below.
  
  
  5.2  Dialing into a Remote Network (DOS)
  
  When you want to dial into a remote network, run the DOS
  version of the ShivaRemote Connect program. Before you
  connect, make sure that the IPX protocol is enabled in
  the connection file you are using (with the Options...
  button).
  
  
  5.3  Attaching to a NetWare Server (DOS)
  
  Before you log into a remote NetWare server, you must
  first "jump start" the connection process by attaching to
  a server.
  
  To do this, change the current drive letter to the first
  network drive specified in your NET.CFG file. This is
  usually the F: drive. At the DOS prompt, type "F:" and
  then Enter:
  
  C:\> f:
  
  When you press Enter, the VLMs will attempt to connect to
  a NetWare server on the remote network. This can take up
  to 20 or 30 seconds; if you think that it is taking too
  long, refer to the troubleshooting section below. When
  the VLMs are connected to a remote server, you are
  returned to the DOS prompt on the new drive:
  
     F:\>
  
  You will not receive any messages about which file server
  you have been attached to. To find out which server you
  have attached to, run the MAP.EXE utility.
  
  The connection process takes approximately 20 to 30
  seconds to attach to a NetWare server. This is because
  the VLMs are testing the speed of the network connection.
  During this process, a series of full-size Ethernet
  frames (1500 bytes each) are exchanged to determine the
  throughput of the connection. The results of this
  throughput test are used by NetWare to set appropriate
  retry timeouts.
  
  This 20-second penalty is incurred each time you log into
  a different remote file server. Thus, it is a good idea
  to set up a Preferred Server as described above.
  
  
  5.4 Logging into a NetWare Server (DOS)
  
  Once you have attached to a remote server, you can log
  into any NetWare server on the remote network. To do
  this, first change back to your local hard disk by typing
  "C:" and press Enter at the DOS prompt:
  
  F:\> c:
  
  You are then returned to the DOS prompt on the C: drive.
  You can then log into a NetWare file server as you always
  do. For example:
  
  C:\> login SERV2/GUEST
  
  Logging into a file server with VLMs should run exactly
  the same as it does when logging in with NETX. However,
  if you log into a server different than your Preferred
  Server, you must wait through another 20-second delay as
  the VLMs measure the performance of the connection.
  
  If the VLMs display error messages with error code 8901
  ("The following drive mapping operation could not be
  completed"), check that the LASTDRIVE parameter in your
  CONFIG.SYS file is set to Z.
  
  
  5.5  Disconnecting from the Remote Network (DOS)
  
  When you want to disconnect a remote network connection,
  you do not have to unload the network drivers. Instead,
  you can just hang up the connection with the ShivaRemote
  Connect program, for example:
  
  C:\> connect /d
  
  If you attempt to access a drive that was mapped to a
  remote network, you will receive an "Access Denied" error
  message. If you want to access this drive again, you need
  only reconnect to the remote network with the ShivaRemote
  Connect program.
  
  If you want to unload the VLM software, you must unload
  the drivers in the reverse order in which they were
  loaded:
  
  C:\> vlm u
  C:\> ipxodi u
  C:\> dialodi u
  C:\> lsl u
  
  
  6.0  Using the VLMs with Windows
  
  VLMs allow you to start Windows without a dial-in
  connection, then connect inside Windows when you need to
  access data on a remote network.
  
  
  6.1  Loading the VLMs
  
  The VLMs must be loaded before Windows starts. Make sure
  that the following command is in your AUTOEXEC.BAT file:
  
  @call c:\nwclient\netstart.bat
  
  For more information on loading the VLMs, refer to
  Section 5.1.above.
  
  
  6.2  Starting Windows
  
  Start Windows in the usual manner, by typing "win" and
  pressing Enter at the DOS prompt. Windows should start up
  normally with no additional delays. If you do experience
  unusual delays when starting Windows, refer to section
  7.0 below.
  
  
  6.3  Dialing into a Remote Network (Windows)
  
  When you want to dial into a remote network, run the
  ShivaRemote Connect program for Windows. The ShivaRemote
  Setup program creates an icon for the Connect program in
  the ShivaRemote program group. Before you attempt to
  connect, make sure that the IPX protocol is enabled in
  the connection file you are using by opening the
  Connection File Options dialog box.
  
  For a complete description of using ShivaRemote to dial
  in to a remote network using the NetWare VLMs, see
  Dialing Into Your Network Using IPX.
  
  
  6.4  Logging into a NetWare Server (Windows)
  
  To log into a NetWare server, run the Windows File
  Manager and select the Network Connections from the Disk
  menu. The first time you select this command after
  dialing in, it will take approximately 20 to 30 seconds
  for the NetWare dialog box to appear. Refer to Section
  5.3 for a discussion of this delay.
  
  If the Connect Network Drive dialog box provided by
  Windows for Workgroups appears, click the NetWare button.
  
  Once the NetWare Drive Connections dialog appears, click
  the NetWare Connections button or press Alt-C on your
  keyboard. The Resources window appears containing a list
  of NetWare servers on the remote network.
  
  To log into a remote server, highlight its name and
  choose the Login button. Again, if this is the first time
  that you have attached to this particular server since
  you dialed in, you will have to wait through another 20-
  second delay while the VLMs time the connection.
  
  When the NetWare Login dialog box appears, enter your
  user name and password for the NetWare server. You are
  now logged in to a remote NetWare server.
  
  
  6.5  Mapping a Drive (Windows)
  
  To map a drive letter to a remote server's volume, choose
  the Drive Connections button by clicking on it or by
  pressing the Alt-D key combination. The Resources window
  should contain a list of volumes available on the server
  you have logged into.
  
  In the Drives window on the left, highlight the drive
  letter that you want to map. In most cases you want to
  start mapping at the F: drive. Next, in the Resources
  window select the volume to be mapped. Finally, select
  the Map button to map the drive.
  
  When the drive has been mapped, the server volume name
  will appear next to the drive letter in the Drives window
  on the left.
  
  
  6.6  Using Remote Drives (Windows)
  
  When you are done mapping drives, choose the Exit button
  by clicking on it or by pressing the Alt-X key
  combination. You can now use the remote drives as you
  normally would.
  
  
  6.7  Disconnecting from a Remote Network (Windows)
  
  When you want to disconnect a remote network connection,
  use the ShivaRemote Connect program to hang up. You can
  also select the Quick Hang Up icon in the ShivaRemote
  program group.
  
  If you attempt to access a drive that was mapped to a
  remote network, you will eventually receive an "Access
  Denied" or "An error occurred reading drive F:" error
  message. If you want to access this drive again, you need
  only reconnect to the remote network with the ShivaRemote
  Connect program.
  
  
  6.8  Using the Automatic Reconnect Feature
  
  ShivaRemote versions 3.2 and later include a feature for
  use with the VLMs: automatic reconnection to NetWare
  servers. This feature works with the ShivaRemote Windows
  Connect program.
  
  To enable this feature, run the Windows Connect program,
  select the Options... button, and check the Restore
  NetWare connections when IPX is connected button.
  
  When you dial into a remote network with the IPX protocol
  enabled, ShivaRemote will use the NetWare User Tools
  program to do two things:
  
  1. Attach to a NetWare Server
  
     ShivaRemote will attach you to a NetWare file server on
     the remote network. If you have specified a preferred
     server (as described in section 3.0 above), you will be
     attached to that server.
  
     This feature us useful for applications that require a
     NetWare server connection. For example, Lotus Notes
     uses a NetWare server's bindery to find the names and
     network addresses of the available Notes servers. If
     you are not attached to a NetWare server, you will not
     be able to connect to any Notes servers.
  
     This attachment process can take approximately 15 seconds
     to complete. For details, refer to section 5.4 above.
  
  2. Restore Permanent Mapped Drives
  
     ShivaRemote will then restore any NetWare drive
     mappings that you have marked as permanent. When you
     map a drive with the NetWare drive connections dialog,
     you can mark it as permanent by selecting the Permanent
     button. For more information on permanent drive
     mappings, refer to the VLM documentation.
  
     While drive mappings are being restored, you will be
     prompted to log into the corresponding NetWare
     server(s). Enter the appropriate user name and password
     for each server.
  
  
  6.9  Using the VLMs with Windows for Workgroups 3.11
  
  Windows for Workgroups 3.11 (WFW) is a special version of
  Microsoft Windows that includes support for various
  networks, including NetWare. If you are running Windows
  for Workgroups, you must make some changes to your system
  files after you run the NetWare Client Install program.
  
  ShivaRemote supports the VLMs with Windows for Workgroups
  version 3.11. If you are running Windows for Workgroups
  version 3.1, please upgrade to WFW 3.11 before using the
  VLMs.
  
  When the NetWare Client Install program modifies your WFW
  system files, it sometimes overwrites some information
  that is required by WFW. Before you install the NetWare
  client, your SYSTEM.INI file will include the following
  entries:
  
  [boot]
  network.drv=wfwnet.drv

  [386Enh]
  network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386
  
  The files listed here are the WFW network support files.
  The NetWare Client Install program sometimes replaces
  these lines with the following:
  
  [boot]
  network.drv=netware.drv

  [386Enh]
  network=*vnetbios,*vwc,vnetsup.386,vredir.386,
     <continued> vserver.386, vipx.386, vnetware.386
  
  In order to use both the WFW network and NetWare, you
  must change your SYSTEM.INI file to match the following:
  
  [boot]
  network.drv=wfwnet.drv
  secondnet.drv=netware.drv
  
  [386Enh]
  network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386
  secondnet=vipx.386, vnetware.386
  
  With this configuration, support for both networks will
  be loaded. When you select Connect Network Drive from the
  File Manager's Disk menu, the Windows for Workgroups
  Connect Network Drive dialog box appears. To connect to
  NetWare servers, click the NetWare button in this dialog.
  

  7.0  Troubleshooting
  
  This section describes problems that are common when
  using the VLMs with ShivaRemote dial-in. If you
  experience problems with VLMs, please review the contents
  of this document carefully.
  Following are some common problems and their resolutions:
  
  VLM.EXE takes a long time to load before dialing in

     When you load the VLM.EXE file before you dial into a
     remote network, it should load immediately. If there is
     a noticeable delay when VLM.EXE is loading, make sure
     that you are not already dialed into a remote network.
     In addition, make sure that you are using the VLM.EXE
     file from the NetWare Client 1.2 diskettes. If you are
     using a previous version of the NetWare client, upgrade
     it to 1.2.
     
  It takes a long time to log into a remote NetWare server

     Once you are dialed into a remote network, you can log
     into servers on that network. The login process takes
     longer with VLMs than it did with NETX. However, if you
     notice a long delay, check the following:
     
     1) Remember that connecting to a remote server takes 20
     to 30 seconds, since the VLMs have to measure the
     performance of the network connection.
     
     2) Make sure that you have specified a preferred server
     in your NET.CFG file, and that your Shiva remote access
     server is configured with the same server. This is
     described in section 4.0 above
     
     3) Make sure that you are not running LOGIN.EXE from a
     remote network drive. This is a common problem with
     VLMs, since you must change to the F: drive to attach
     to a server. Make sure that you switch back to the C:
     drive before you run the LOGIN.EXE program, which is
     installed by the ShivaRemote Setup program.
     
  Map errors during login

     When you log into a remote server, you may see an error
     message similar to the following:
     
     The following drive mapping operation could not be
     completed:The error code was 8901
     
     If you receive an 8901 error message, it indicates that
     the LASTDRIVE entry in your CONFIG.SYS file is not set
     to Z:
     
     LASTDRIVE=Z
     
     Change this entry to Z, then restart your PC.
     
  Unable to copy files to/from a remote NetWare server

     Once you log into a remote NetWare server, you should
     be able to copy files to and from its volumes. If you
     see an "Abort, Retry, Fail?" prompt when copying a
     file, check the following:
     
     1) Make sure that you are using the VLM.EXE file from
     the NetWare Client version 1.2. The versions of VLM.EXE
     previous to 1.2 contain a bug that prevents file
     transfers from working over low-speed links.
     
     2) Make sure that your dial-in connection has not been
     lost. To do this in DOS, press the A key to abort, then
     type "connect /a" at the DOS prompt. To do this in
     Windows, run the ShivaRemote Connect program and check
     the status line.
     
  Windows for Workgroups functionality is lost

     If you are running Windows for Workgroups, but no
     longer have WFW functionality, it may be due to the
     NetWare Client Install program overwriting your WFW
     system files. Please refer to section 6.9 for more
     information.
     
  Black Screen of Death in Windows

     If you experience the so called Black Screen of Death
     in Windows, make sure that you are running the latest
     version of vipx.386 which is included on the NetWare
     Client 1.2 diskettes. This version of vipx.386 should
     clear up almost all Black Screen of Death problems. If
     this does not solve the problem, contact Novell for
     more information.
     
  Switching Between Local and Dial-In

     The instructions above describe how to install VLMs for
     use with ShivaRemote dial-in. Due to the limitations of
     Novell's IPX protocol, you cannot access both a local
     network (Ethernet/Token-Ring) and a remote network
     (with ShivaRemote) at the same time.
     
     However, you can easily switch between the two
     configurations. To reconfigure VLMs for a local
     network, first edit STARTNET.BAT so that it loads your
     local network ODI driver instead of the ShivaRemote
     driver. For example, if you have an NE2000 Ethernet
     card:
     
      SET NWLANGUAGE=ENGLISH
      C:\NWCLIENT\LSL
      :DRIVER1
      C:\NWCLIENT\NE2000
      C:\NWCLIENT\IPXODI
      C:\NWCLIENT\VLM
     
     You also must add an appropriate section to your
     NET.CFG file that contains the correct configuration
     information for that driver. For example:
     
      link driver NE2000
          int 3
          port 300
          frame ethernet_802.2
          protocol IPX e0 ethernet_802.2
     
  Miscellaneous Problems

     If you experience problems not mentioned in this
     section try forcing the VLMs to load in conventional
     memory. By default, the VLMs will load in extended or
     expanded memory.

     To force the VLMs to load in conventional memory, use
     the "/MC" option when loading VLM.EXE:
     
      SET NWLANGUAGE=ENGLISH
      C:\NWCLIENT\LSL
      :DRIVER1
      C:\NWCLIENT\DIALODI.EXE
      C:\NWCLIENT\IPXODI
      C:\NWCLIENT\VLM /MC
     
     
Novell NetWare NETX
  
  This section describes how to configure and use the old
  NetWare client software (NETX) for use with dial-in.
  
  1.0  Introduction
  2.0  Obtaining the NETX Software
  3.0  Installing the NETX Software
  4.0  Loading the NETX Software
  5.0  Logging into a NetWare Server
  6.0  Disconnecting
  7.0  Using NETX With Windows
  
  
  1.0  Introduction
  
  NETX is Novell's old client software for DOS and Windows.
  NETX has been replaced by Novell's new client software,
  Virtual Loadable Modules (VLMs). VLMs are preferred for
  best dial-in performance. In addition, Novell has
  discontinued work on NETX, and encourages all of its
  customers to upgrade to VLMs.
  
  This software is called NETX because its main module is a
  file named NETX.EXE. The 'x' refers to the fact that this
  module supports all versions of DOS. Previous versions of
  the NETX software only supported a single DOS version.
  For example, NET3.COM supported DOS version 3, and
  NET4.COM supported DOS version 4.
  
  
  2.0  Obtaining the NETX Software
  
  The NETX software uses Novell's ODI driver standard. You
  need six files to use NETX for dial-in:
  
   lsl.com       ODI Link Support Layer
   dialodi.exe   ShivaRemote ODI dial-in driver
   ipxodi.com    Novell IPX protocol
   netx.exe      Novell NETX shell
   guard.exe     ShivaRemote LaunchGuard
   login.exe     Login utility
  
  The ShivaRemote driver (DIALODI.EXE) and LaunchGuard
  program (GUARD.EXE) are included on the ShivaRemote
  software diskette, and are copied to your hard disk by
  the ShivaRemote Setup program. The other four files are
  included in all versions of Novell NetWare
  
  
  3.0  Installing the NETX Software
  
  Due to its simplicity, the NETX software does not have
  its own installation program. Instead, you must copy the
  files listed above into a directory on your hard disk. In
  the examples below, the c:\shiva directory is used.
  
  
  4.0  Loading the NETX Software
  
  You can load the NETX software from the DOS prompt.
  First, load the following drivers:
  
     C:\SHIVA> lsl
     C:\SHIVA> dialodi
     C:\SHIVA> ipxodi
     
  Next, connect to a remote network using ShivaRemote
  Connect for DOS. You must dial in before you run NETX.EXE
  due to a limitation of the NETX driver.
  
  When NETX.EXE is loaded, it searches for a NetWare server
  to attach to. If it cannot find one, it displays an error
  message and does not remain resident. If you load
  NETX.EXE before you have dialed into a remote network, it
  will not be able to attach to a server, and thus will not
  remain resident. To avoid this restriction, use Novell's
  new VLM software.
  
  To dial into a remote network, use the ShivaRemote
  Connect program for DOS and a ShivaRemote connection
  file:
  
     C:\SHIVA> connect @filename
     
  For more information about connecting to a remote
  network, refer to the online help for ShivaRemote Connect
  for DOS.
  
  Once you are connected to a remote network, you can
  continue to load the NETX software:
  
     C:\SHIVA> netx
     C:\SHIVA> guard
     
  When loaded, the NETX.EXE driver will attach to a NetWare
  server. The LaunchGuard program (GUARD.EXE) is a
  ShivaRemote utility that helps you avoid running an
  executable program from the NetWare server's volumes.
  
  
  5.0  Logging into a NetWare Server
  
  Once you are connected to a remote network, you can log
  into a NetWare server on that network by running the
  LOGIN.EXE program. Run this program the same way as you
  do on a local network, by specifying your server and/or
  user name on the command line:
  
     C:\> login server/user
     
  You will be prompted for your password (as usual), and
  your login script will be run (as usual). Any ATTACH and
  MAP commands that are in your login script will be run
  with no problem, since the LOGIN.EXE file will process
  them locally.
  
  However, if there are any external DOS commands in the
  script, the LaunchGuard utility will catch them and allow
  you to skip them. This is advised, since running an
  executable program from a remote file server can take
  several minutes.
  
  
  6.0  Disconnecting
  
  Before you disconnect from the remote network, you should
  unload the NETX.EXE driver:
  
     C:\SHIVA> guard u
     C:\SHIVA> netx u
     
  Next, disconnect from the network and unload the
  remaining software:
  
     C:\SHIVA> connect /d
     C:\SHIVA> ipxodi u
     C:\SHIVA> dialodi u
     C:\SHVIA> lsl u
  
  
  7.0  Using NETX With Windows
  
  There are severe restrictions on using NETX dial-in with
  Windows:
  
  You must dial in before starting Windows

     This is because the NETX.EXE driver will not remain
     resident unless it can attach to a NetWare server, and
     it cannot attach to a NetWare server unless you are
     dialed in.
     
  You must exit Windows before hanging up

     NETX was not designed to work in the Windows
     environment. When you disconnect while Windows is
     running, NETX cannot recover gracefully; instead, it
     prints a standard DOS "Abort, Retry, Ignore?" prompt on
     the screen and locks up Windows. Thus, you must exit
     Windows, then disconnect in DOS.
     
  Note that these restrictions do not apply to the VLM
  software. For this reason, we recommend that all Windows
  users install the VLMs instead of using NETX.
  
  
*********Wollongong PathWay*********
  
  This section describes how to install, configure, and use
  Wollongong PathWay.
  
  1.0  Introduction
  2.0  Installing PathWay (ODI)
       2.1  Running PathWay Runtime Setup (ODI)
       2.2  Loading PathWay Drivers (ODI)
  3.0  Installing PathWay (NDIS)
       3.1  Running PathWay Runtime Setup (NDIS)
       3.2  Loading PathWay Drivers (NDIS)
  4.0  Connecting
  5.0  Using PathWay
  
  
  1.0  Introduction
  
  PathWay is The Wollongong Group's TCP/IP protocol
  implementation for DOS and Windows. ShivaRemote supports
  PathWay Runtime version 2.0 or later.
  
  ShivaRemote can update the IP address used by PathWay.
  This means that you do not have to configure a specific
  IP address; when ShivaRemote connects to a remote
  network, it updates PathWay with the IP address it was
  assigned.
  
  PathWay supports both ODI and NDIS, so it can be used
  with either the ShivaRemote ODI driver or the ShivaRemote
  NDIS driver.
  
  
  2.0  Installing PathWay (ODI)
  
  This section describes how to install PathWay Runtime
  with the ShivaRemote ODI driver. To install PathWay with
  the ShivaRemote NDIS driver, refer to section 3.0 below.
  
  
  2.1  Running PathWay Runtime Setup (ODI)
  
  To install PathWay Runtime for ODI, follow these
  directions:
  
  1. Before you run the PathWay Setup program, you must load
     the ODI Link Support Layer and the ShivaRemote ODI
     driver from the DOS prompt:
  
     C:\> c:\shiva\lsl
     C:\> c:\shiva\dialodi
  
     In addition, the ODI configuration file net.cfg must
     exist in the same directory as the lsl.com file.
  
     If you do not load these drivers before running Setup,
     or if the net.cfg file does not exist, PathWay Runtime
     cannot be installed for ODI.
  
  2. Insert the PathWay Runtime Disk 1 in your floppy driver
     and run the pwsetup.exe program from the DOS prompt:
  
     C:\> a:pwsetup
  
     Press the Enter key to skip past the greeting messages.
  
  3. At the PathWay Setup Program display, select the
     Install/PathWay Runtime menu item. Specify the source
     directory (usually a:\) and the destination directory
     (the default is c:\pathway). Press Enter to continue.
  
  4. When prompted for the driver interface media, select
     Ethernet and press Enter.
  
  5. At the Ethernet Adapters display, select ODI Driver and
     press Enter. If Setup displays any error messages,
     please refer to step 1 above.
  
  6. At the Driver ODI and kernel configuration display,
     select the default interrupt values for pwconfig.exe
     (65) and the ODI driver (3). Press Enter to continue.
  
  7. At the PathWay Configuration Setup display, where you
     are asked if you want to use the BOOTP service, answer
     No. Press Enter to continue.
  
  8. At the Configuration Setup for Site Parameters display,
     enter an IP address at the IP Address: prompt. It does
     not matter what this address is; it matters only that
     an IP address (such as 1.1.1.1) be entered. When a
     connection is made to a remote network, ShivaRemote
     will update PathWay with the appropriate IP address.
  
     You should also enter a value (such as 1.1.1.1) at the
     Default gateway address: prompt. Enter appropriate
     values for the other entries, then press Enter to
     continue.
  
  9. Setup will copy the Pathway Runtime files to your hard
     disk. Insert the Runtime disks as requested.
  
  10.When Setup asks if it can modify your net.cfg and
     autoexec.bat files, answer Yes.
  
  11.When you are returned to the PathWay Setup main menu,
     select the Exit/Exit to DOS menu item.
  
  
  2.2  Loading PathWay Drivers (ODI)
  
  The PathWay drivers for ODI are loaded from the DOS
  prompt (or in the autoexec.bat file). Load the drivers in
  the following order:
  
    C:\> lsl
    C:\> dialodi
    C:\> pwconfig -N:65
    C:\> odi -I:3
    C:\> pwtcp
  
  PathWay Runtime is now installed and ready for use.
  Continue with section 4.0 below.
  
  
  3.0  Installing PathWay (NDIS)
  
  This section describes how to install PathWay Runtime
  with the ShivaRemote NDIS driver. To install PathWay with
  the ShivaRemote ODI driver, refer to section 2.0 above.
  
  
  3.1  Running PathWay Runtime Setup (NDIS)
  
  To install PathWay Runtime for NDIS,follow these
  directions:
  
  1. Before you run PathWay Setup, you must create a
     protocol.ini file that contains information about the
     ShivaRemote NDIS driver. This file should be created in
     the ShivaRemote directory (usually c:\shiva).
  
     This file should contain the following entries:
  
     [PROTMAN]
     DriverName=PROTMAN$
  
     [SDIALIN$]
     DriverName=SDIALIN$
  
     If you do not create this file with these entries,
     PathWay Setup will not be able to use the ShivaRemote
     NDIS driver.
  
  2. Next, you must create a copy of the ShivaRemote NDIS
     driver, dialndis.exe. This copy must be named
     sdialin.exe. Use the copy command at the DOS prompt:
  
     C:\SHIVA> copy dialndis.exe sdialin.exe
  
     The PathWay Setup program requires that the driver file
     name (sdialin.exe) be the same as the NDIS module name
     (SDIALIN$). If you do not create the sdialin.exe file,
     PathWay Setup will not be able to use the ShivaRemote
     NDIS driver.
  
  3. Insert the PathWay Runtime Disk 1 in your floppy driver
     and run the pwsetup.exe program from the DOS prompt:
  
     C:\> a:pwsetup
  
     Press the Enter key to skip past the greeting messages.
  
  4. At the PathWay Setup Program display, select the
     Install/PathWay Runtime menu item. Specify the source
     directory (usually a:\) and the destination directory
     (the default is c:\pathway). Press Enter to continue.
  
  5. When prompted for the driver interface media, select
     Ethernet and press Enter.
  
  6. At the Ethernet Adapters display, select NDIS Driver
     and press Enter.
  
  7. At the Driver NDIS and kernel configuration display,
     enter the directory in which you created a protocol.ini
     file as described in step 1 above (usually c:\shiva).
     When Setup asks which driver it should use, select
     DIALNDIS from the list.
  
     If Setup displays any error messages, please refer to
     the instructions given in steps 1 and 2 above.
  
  8. When prompted, specify the default interrupt values for
     PWCONFIG (65) and the NDIS device driver (3). Press
     Enter to continue.
  
  9. At the PathWay Configuration Setup display, where you
     are asked if you want to use the BOOTP service, answer
     No. Press Enter to continue.
  
  10.At the Configuration Setup for Site Parameters
     display, enter an IP address at the IP Address: prompt.
     It does not matter what this address is; it matters
     only that an IP address (such as 1.1.1.1) be entered.
     When a connection is made to a remote network,
     ShivaRemote will update PathWay with the appropriate IP
     address.
  
     You should also enter a value (such as 1.1.1.1) at the
     Default gateway address: prompt. Enter appropriate
     values for the other entries, then press Enter to
     continue.
  
  11.Setup will copy the Pathway Runtime files to your hard
     disk. Insert the Runtime disks as requested.
  
  12.When Setup asks if it can modify your config.sys and
     autoexec.bat files, answer Yes.
  
  13.When you are returned to the PathWay Setup main menu,
     select the Exit/Exit to DOS menu item.

  
  3.2  Loading PathWay Drivers (NDIS)
  
  The PathWay NDIS drivers are loaded in config.sys and
  autoexec.bat. The PathWay Setup program will add the
  following entries to config.sys:
  
    device=c:\pathway\protman.dos /i:c:\pathway\lanman
    device=c:\pathway\lanman\sdialin.exe
  
  Change the second line to refer to the original
  ShivaRemote NDIS driver:
  
    device=c:\shiva\dialndis.exe
  
  The PathWay Setup program also adds the following entries
  to the autoexec.bat file:
  
    pwconfig -N:65
    ndis -I:3 -d:2
    netbind
    pwtcp
  
  Make sure that the netbind program reports a successful
  binding. If it does not, please refer to section 3.2
  above.
  
  
  4.0  Connecting
  
  To connect to a remote network, you can use either the
  ShivaRemote Connect program for DOS or the ShivaRemote
  Connect program for Windows.
  
  When you are connected, verify that ShivaRemote has
  updated the IP address used by PathWay. First, check the
  address obtained by ShivaRemote by selecting the
  ShivaRemote Connect program's Tools/Statistics... menu
  item, then selecting IP from the drop-down list.
  
  Next, compare this address to the address used by
  PathWay. In DOS, run the stat.exe program, then press 4
  to view IP group stats. The first line of this display
  reports the IP address:
  
    140.248.208.151 is the IP address of interface 1.
  
  In Windows, run the winstat.exe program. the IP address
  is reported on the third line of the display.
  
  
  5.0  Using PathWay
  
  There is a problem with running the PathWay Access
  telnet.exe program with ShivaRemote. In most cases,
  performance is very slow, and in some cases, it hangs.
  The telwin.exe program should be used instead.
  
  Despite its name, it is a DOS program, not a Windows
  program. It is identical to the telnet.exe program except
  that it is designed to run in a DOS box under Windows.
  However, it can be run in DOS without Windows as well.
  Its performance is much better than that of telnet.exe.
  

  
*********WRQ TCP Connection*********
  
  This section describes how to configure and use WRQ's TCP
  Connection with ShivaRemote dial-in.
  
  1.0  Introduction
  2.0  Installing TCP Connection (ODI)
       2.1  Running TCP Connection Setup (ODI)
       2.2  Configuring TCP Connection (ODI)
  3.0  Installing TCP Connection (NDIS)
       3.1  Running TCP Connection Setup (NDIS)
       3.2  Configuring TCP Connection (NDIS)
  4.0  Configuring IP Addressing
       4.1  Configuring BOOTP
       4.2  Configuring RARP
  5.0  Connecting
  6.0  Disconnecting
  7.0  Using TCP Connection with NetWare
  
  
  Walker Richer & Quinn, Inc.    Technical Support
  1500 Dexter Avenue North       Phone: (206) 217-7000
  Seattle, WA  98109             Fax: (206) 217-9492
  Phone: (206) 217-7500          BBS: (206) 217-0145
  Fax: (206) 217-0293            email:support@wrq.com
  
  
  1.0  Introduction
  
  TCP Connection is WRQ's implementation of the TCP/IP
  protocols for Windows.  ShivaRemote supports TCP
  Connection versino 4.01 and later.
  
  Using the RARP or BOOTP protocol, ShivaRemote can update
  the IP address used by TCP Connection when a dial-in
  connection is made.  Refer to section 4.0 below
  for configuration information.
  
  TCP Connection supports both ODI and NDIS, so it can be
  used with either the ShivaRemote ODI or NDIS dial-in
  driver.  Refer to section 2.0 below for information on
  ODI.  Refer to section 3.0 below for information on NDIS.
  

  2.0  Installing TCP Connection (ODI)
  
  This section describes how to install TCP Connection with
  the ShivaRemote ODI dial-in driver.  If you want to use
  the NDIS driver, refer to section 3.0 below.
  
  
  2.1  Running TCP Connection Setup (ODI)
  
  To install TCP Connection with ODI, follow these steps:
  
  1. Start Windows.  The TCP Connection must be run in
     Windows.
  
  2. From the Program Manager's menu, select File/Run, enter
     a:setup.exe, and select the OK button.  At the greeting
     message, select the Continue button.
  
  3. At the Destination Path window, enter the name of the
     directory into which TCP Connection should be
     installed.  In the examples below, the default of
     c:\wrqnet will be used.
  
  4. At the driver type dialog, select ODI and select the OK
     button.
  
  5. When Setup asks whether it is OK to modify
     configuration files (such as protocol.ini, net.cfg,
     config.sys, autoexec.bat, and system.ini), select the
     Continue button to allow modification.  Setup will copy
     the necessary files to your hard disk.
  
  6. At the Add Physical Network Interface dialog, highlight
     the Other Interface and select the OK button.  Enter
     the following values:
  
     Card Driver Filename      dialodi.exe
     Card Section Title        dialodi
     Card Section Contents     (leave empty)
     Card Type                 Ethernet
  
    Select the OK button.
  
  7. When Setup asks for the location of dialodi.exe, enter
     the ShivaRemote directory (usually c:\shiva).
  
  8. At the Basic TCP/IP Settings dialog, enter any values
     for IP Address, Subnet Mask, and Default Gateway.  It
     does not matter what these values are; they will be
     updated at connection time as described in section 4.0
     below.
  
  9. Allow Setup to create a Program Manager group and
     create icons.  When Setup is finished, allow it to
     restart your PC for changes to take effect.


  2.2  Configuring TCP Connection (ODI)
  
  Before the TCP Connection drivers are loaded, make sure
  that the Max Stacks entry in the net.cfg file (usually in
  the c:\wrqnet directory) is set to at least 8:
  
    Link Support
       Max Stacks 8
  
  In addition, you must disable the duplicate-address-
  checking feature of TCP Connection.  Add the following
  entry to the Protocol RN_IP0 section of the net.cfg file:
  
    Protocol RN_IP0
       CheckDupAddr False
       BootpRefresh True
  
  The "CheckDupAddr False" entry prevents TCP Connection
  from checking if a host on the remote network is using
  its IP address.  If this entry is omitted, TCP Connection
  will always report that its address is in use, even when
  this is not true.
  
  The "BootpRefresh True" entry instructs TCP Connection to
  obtain its IP address each time an application is run.
  If this entry is omitted, you will not be able to dial
  into more than one remote network without restarting
  Windows.  Refer to section 5.0 below for more
  details.
  
  The TCP Connection drivers for ODI are loaded in
  autoexec.bat or at the DOS prompt.  Make sure that the
  drivers are loaded in the following order:
  
    C:\> c:\wrqnet\lsl
    C:\> c:\shiva\dialodi
    C:\> c:\wrqnet\rodi /stacks:7
  
  Once net.cfg is updated and the ODI drivers are loaded,
  start Windows and proceed with section 4.0 below.
  
  
  3.0  Installing TCP Connection (NDIS)
  
  This section describes how to install TCP Connection with
  the ShivaRemote NDIS dial-in driver.  If you want to use
  the NDIS driver, refer to section 2.0 above.
  
  
  3.1  Running TCP Connection Setup (NDIS)
  
  To install TCP Connection with NDIS, follow these steps:
  
  1. Start Windows.  The TCP Connection must be un in
     Windows.
  
  2. From the Program Manager's menu, select File/Run, enter
     a:setup.exe, and select the OK button.  At the greeting
     message, select the Continue button.
  
  3. At the Destination Path window, enter the name of the
     directory into which TCP Connection should be
     installed.  In the examples below, the default of
     c:\wrqnet will be used.
  
  4. At the driver type dialog, select NDIS and select the
     OK button.
  
  5. When Setup asks whether it is OK to modify
     configuration files (such as protocol.ini, net.cfg,
     config.sys, autoexec.bat, and system.ini), select the
     Continue button to allow modification.  Setup will copy
     the necessary files to your hard disk.
  
  6. At the Add Physical Network Interface dialog, highlight
     the Other Interface and select the OK button.  Enter
     the following values:
  
     Card Driver Filename    dialndis.exe
     Card Section Title      SDIALIN$
     Card Section Contents   DriverName=SDIALIN$
     IRQ Value               3
     Card Type               Ethernet
  
     Note:  at the IRQ Value prompt, you must enter 3.
     Later, you will be instructed to change  this parameter
     to 0 on the rndis.exe command line.
  
     Select the OK button.
  
  7. When Setup asks for the location of dialndis.exe, enter
     the ShivaRemote directory (usually c:\shiva).
  
  8. At the Basic TCP/IP Settings dialog, enter any values
     for IP Address, Subnet Mask, and Default Gateway.  It
     does not matter what these values are; they will be
     updated at connection time as described in section
     4.0 below.
  
  9. Allow Setup to create a Program Manager group and
     create icons.  When Setup is finished, allow it to
     restart your PC for changes to take effect.
  
  
  3.2  Configuring TCP Connection (NDIS)
  
  The TCP Connection drivers for NDIS are loaded in
  config.sys and in autoexec.bat.  Make sure that the
  following drivers are loaded (in the specified order) in
  your config.sys file:
  
    device=c:\wrqnet\protman.dos /i:c:\wrqnet\
    device=c:\shiva\dialndis.exe
  
  The "/i" on the protman.dos line specifies the location
  of the protocol.ini NDIS configuration file.
  The TCP Connection program will copy the dialndis.exe
  file into its directory (usually c:\wrqnet).  In the
  example above, this has been changed to the ShivaRemote
  directory (usually c:\shiva).  It is a good idea to
  change this entry in config.sys so that the most recent
  ShivaRemote driver will always be used.
  
  Next, verify that the following commands are run in the
  autoexec.bat file (or at the DOS prompt):
  
    C:\> c:\wrqnet\rndis /irq:0 /stacks:7    (see note below)
    C:\> c:\wrqnet\netbind
  
  Note:  The /irq: parameter is set to 3 by the TCP
  Connection Setup program.  You must change this to 0
  (/irq:0) as specified in the line above.  If the IRQ
  value is anything other than 0, TCP Connection will not
  work at all.
  
  The /stacks:7 parameter is required so that TCP
  Connection can initialize properly.
  
  Finally, you must disable the duplicate-address-checking
  feature of TCP Connection.  Add the following entry to
  the [RN_IP0] section of the protocol.ini file (usually in
  the c:\wrqnet directory):
  
    [RN_IP0]
    CheckDupAddr=False
    BootpRefresh=True
  
  The "CheckDupAddr=False" entry prevents TCP Connection
  from checking if a host on the remote network is using
  its IP address.  If this entry is omitted, TCP Connection
  will always report that its address is in use, even when
  this is not true.
  
  The "BootpRefresh=True" entry instructs TCP Connection to
  obtain its IP address each time an application is run.
  If this entry is omitted, you will not be able to dial
  into more than one remote network without restarting
  Windows.  Refer to section 5.0 below for more details.
  
  Once the NDIS drivers are loaded and protocol.ini is
  updated, start Windows and proceed with section 4.0
  below.
  

  4.0  Configuring IP Addressing
  
  Before TCP Connection can be used, you must configure it
  to use either the BOOTP or RARP protocol to obtain its IP
  address.  If you will dial into a Shiva LanRover, you can
  use the BOOTP protocol, described in section 4.1 below.
  If you will not dial into a Shiva LanRover, you must use
  the RARP protocol, described in section 4.2 below.
  
  
  4.1  Configuring BOOTP
  
  If you will dial into a Shiva LanRover, you can take
  advantage of the BOOTP feature of the LanRover.  The
  LanRover acts as a BOOTP server for its dial-in clients,
  and can dynamically update TCP Connection with the
  appropriate IP address, DNS server address, and more.
  
  To enable BOOTP, run the Network Configuration program in
  the Program Manager's Reflection Network Series group. At
  the Reflection Network Series Settings dialog, select the
  Remote... button.
  
  Configure this dialog to match the following:
  
    * Select the Enable Remote Configuration checkbox
    * Select the BootP radio button in the Protocol section
    * Select the Use Broadcast Method checkbox in the Server section
    * Select all checkboxes in the Data to Obtain section
  
  When you are done, select the OK button.  When you are
  returned to the Reflection Network Series Settings
  dialog, select the OK button.
  
  
  4.2  Configuring RARP
  
  If you will not dial into a Shiva LanRover, you can take
  advantage of the RARP feature of ShivaRemote.
  ShivaRemote will respond to RARP requests from TCP
  Connection with the appropriate IP address.
  
  The RARP protocol can configure only the IP address; it
  cannot configure other information (such as the DNS
  server address) that BOOTP can.  If you need a DNS
  address, you must configure it manually as described in
  the TCP Connection documentation.
  
  To enable RARP, run the Network Configuration program in
  the Program Manager's Reflection Network Series group.
  At the Reflection Network Series Settings dialog, select
  the Remote... button.
  
  Configure this dialog to match the following:
  
    * Select the Enable Remote Configuration checkbox
    * Select RARP in the Protocol section
    * Select Local IP Address in the Data to Obtain section
  
  When you are done, select the OK button.  When you are
  returned to the Reflection Network Series Settings
  dialog, select the OK button.
  
  
  5.0  Connecting
  
  Because TCP Connection is a Windows-based implementation
  of TCP/IP, you can connect to a remote network using the
  ShivaRemote Connect for Windows program.
  
  Be sure to connect to the remote network before you run
  any TCP Connection applications.  When an application is
  run, TCP Connection attempts to obtain its IP address
  through either BOOTP or RARP (as described in section 4.0
  above).  This will only succeed if ShivaRemote is
  connected to a remote network.
  
  After you have connected,  verify that TCP Connection has
  obtained the proper address;  To do this, you must run a
  TCP Connection application (such as Ping), click on the
  RNS icon at the bottom of your display, select the
  About... menu item, and select IP Addresses from the drop-
  down list.  Compare the address displayed here to the
  address obtained by ShivaRemote by selecting the
  ShivaRemote Tools/Statistics... menu item and selecting
  IP from the drop-down list.
  
     Note: If you dial into a remote network more than
     once, you may be assigned a different IP address on
     each connection.  After each connection, verify that
     TCP Connection is using the address assigned for that
     connection.  If the IP address is not updated on the
     second connection (and on subsequent connections), make
     sure that the "BootpRefresh" parameter is set as
     described in sections 2.2 and 3.2 above.
  
  
  6.0  Disconnecting
  
  TCP Connection allows you to disconnect from the remote
  network at any time by using the ShivaRemote Connect for
  Windows program.  However, if you then reconnect (or
  connect to a different network), you must make sure that
  you obtain the same IP address.  Refer to section
  5.0 above for details.
  
  
  7.0  Using TCP Connection with NetWare
  
  Because TCP Connection can use the ShivaRemote ODI
  driver, it can be used with NetWare.  Refer to section
  2.0 above for details on configuring TCP Connection to
  use ODI.

  Load the drivers in the following order:
  
    C:\> c:\wrqnet\lsl
    C:\> c:\shiva\dialodi
    C:\> c:\wrqnet\rodi /stacks:7
    C:\> c:\nwclient\ipxodi
    C:\> c:\nwclient\vlm
  
  Note that TCP Connection makes extensive use of the ODI
  net.cfg file for its configuration.  When the lsl.com
  driver is loaded, make sure it is using the appropriate
  net.cfg file.
  
  For more information on NetWare, refer to the Novell
  NetWare VLM section.



*********Network Driver Interface Specification (NDIS)*********
  
  This section describes how ShivaRemote supports network
  software using the NDIS standard.
  
  1.0  Introduction
  2.0  NDIS Communications
  3.0  NDIS Configuration
       3.1   Configuration Sections
       3.2   The ShivaRemote Section
       3.3   Binding a Protocol to a Card
  4.0  Loading NDIS Drivers
       4.1   Protocol Manager
       4.2   NDIS Drivers
       4.3   The NetBind Utility
       4.4   Windows for Workgroups 3.11
  
  
  1.0  Introduction
  
  The Network Driver Interface Specification (NDIS) was
  developed by Microsoft and 3Com. It allows network
  protocols (such as IPX and TCP/IP) to communicate with
  network card drivers (such as Ethernet and Token-Ring).
  ShivaRemote includes a network card driver that conforms
  to version 2.0.1 of the NDIS standard.
  
  The ShivaRemote NDIS driver (dialndis.exe) pretends to be
  an Ethernet driver, so that a network protocol believes
  that it is on a local network. This is true even when
  dialing into a Token-Ring network; the remote networking
  server will do the translation between Ethernet and Token-
  Ring.
  
  
  2.0  NDIS Communications
  
  NDIS allows several protocols and several network card
  drivers to be loaded at the same time. Each protocol and
  card driver is called a module. Communication between
  these modules is done through a program called the
  Protocol Manager. The Protocol Manager file is called
  protman.dos, and is loaded in your config.sys file.
  
  When NDIS protocols and network card drivers are loaded,
  they all register their presence with the Protocol
  Manager. The Protocol Manager then instructs each
  protocol to communicate with the appropriate network card
  driver (or drivers). Communication betwen a protocol and
  a network card driver is called a binding.
  
  
  3.0  NDIS Configuration
  
  NDIS modules are configured through entries in the
  protocol.ini file. This is a simple text file that can be
  modified by any text editor, such as the DOS Edit program
  or the Windows Notepad program.
  
  
  3.1  Configuration Sections
  
  Each NDIS module has its own section, which is surrounded
  by brackets. This section name is followed by an
  arbitrary number of configuration entries. At a minimum,
  each section contains one entry (DriverName=) that
  specifies the driver's module name. For example, the
  Protocol Manager's section might look like this:
  
     [protman]
     DriverName=PROTMAN$
  
  Ironically, an NDIS driver does not find its section in
  protocol.ini by searching for a specific section name in
  brackets. Instead, it searches all of the sections until
  it finds one with a DriverName entry that matches its
  module name. In other words, the Protocol Manager does
  not look for a section named [protman]; it instead
  searches for a section that has the "DriverName=PROTMAN$"
  entry in it.
  
  
  3.2  The ShivaRemote Section
  
  The ShivaRemote NDIS driver's module name is SDIALIN$.
  Since ShivaRemote does not use protocol.ini for any
  configuration information, its section will look like
  this:
  
     [sdialin$]
     DriverName=SDIALIN$
  
  Remember that, since the bracketed section name is
  arbitrary, this section could also look like this:
  
     [SREMOTE]
     DriverName=SDIALIN$
  
  This is important, since a protocol is bound to a card by
  its section name, not by its driver name. To avoid
  confusion, it is a good idea to use the same name
  (SDIALIN$) for both the section and module names.
  
  
  3.3  Binding a Protocol to a Card
  
  A protocol is bound to a network card by the Bindings
  entry in the protocol's section. For example, to bind the
  Microsoft NetBEUI protocol to the ShivaRemote dial-in
  driver, the NetBEUI section would look like this:
  
     [SDIALIN$]
     DriverName=SDIALIN$
  
     [NETBEUI]
     DriverName=NETBEUI$
     Bindings=SDIALIN$
  
  Please note that the name given in the Bindings entry is
  the network card's section name, not its driver name.
  Thus, protocol.ini can also look like this:
  
     [SREMOTE]
     DriverName=SDIALIN$
  
     [NETBEUI]
     DriverName=NETBEUI$
     Bindings=SREMOTE
  
  It is legal, and often desired, to have multiple
  protocols bind to the same card. In the following
  example, the ShivaRemote dial-in driver is bound to both
  the NetBEUI protocol and the NetManage Chameleon TCP/IP
  protocol:
  
     [SDIALIN$]
     DriverName=SDIALIN$
  
     [NETBEUI]
     DriverName=NETBEUI$
     Bindings=SDIALIN$
  
     [NetManage]
     DriverName=NETMNG$
     Bindings=SDIALIN$
  

  4.0  Loading NDIS Drivers
  
  
  4.1  Protocol Manager
  
  NDIS drivers are loaded in the config.sys file. The
  Protocol Manager is always loaded first, with a device=
  statement:
  
     device=c:\net\protman.dos /i:c:\net
  
  In this example, the protman.dos driver is located in the
  c:\net directory. The command-line parameter "/i:c:\net"
  tells the Protocol Manager that the protocol.ini
  configuration file can be found in the c:\net directory.
  
  
  4.2  NDIS Drivers
  
  After the Protocol Manager is loaded, NDIS protocols and
  card drivers can be loaded in any order. In the example
  below, the ShivaRemote dial-in driver and the NetManage
  Chameleon TCP/IP driver are loaded:
  
     device=c:\net\protman.dos /i:c:\net
     device=c:\shiva\dialndis.exe
     device=c:\netmanag\netmanag.dos
  
  Since NDIS drivers are usually DOS device drivers, they
  cannot be unloaded from memory. You must restart your
  computer to remove them.
  
  
  4.3  The NetBind Utility
  
  After the drivers are loaded, the protocols and card
  drivers must be bound. This is done by a DOS program
  usually called netbind.exe, usually in the autoexec.bat
  file:
  
     c:\net\netbind.exe
  
  In some cases, this is done with a program called
  net.exe:
  
     c:\net\net start
  
  To determine which command to use, please refer to your
  network software's documentation.
  Once the binding has been done, the NDIS network
  configuration is complete. Once you dial into a remote
  network, your network software should be ready to use.
  
  
  4.4  Windows for Workgroups 3.11
  
  With Windows for Workgroups version 3.11, Microsoft has
  changed the way NDIS drivers are loaded. By default,
  drivers are no longer loaded in the config.sys file;
  instead, they are loaded when the "net start" command is
  executed.
  
  However, some network software requires that these
  drivers be loaded in config.sys. To do this, you must
  modify your Windows system.ini file, found in your
  Windows directory (usually c:\windows).
  
  In the [network drivers] section, change the
  "LoadRMDrivers" entry to no:
  
     [network drivers]
     LoadRMDrivers=No
  
  Then load the drivers in config.sys as described above:
  
     device=c:\windows\protman.dos /i:c:\windows
     device=c:\shiva\dialndis.exe
     device=c:\netmanag\netmanag.dos
  
*********Open Data-Link Interface (ODI)*********
  
  This section describes how ShivaRemote supports network
  software using the ODI standard.
  
  1.0  Introduction
  2.0  ODI Communications
  3.0  ODI Configuration
       3.1   Configuration Sections
       3.2   The ShivaRemote Section
       3.3   Binding a Protocol to a Card
  4.0  Loading ODI Drivers
  5.0  Unloading ODI Drivers
  

  1.0  Introduction
  
  The Open Datalink Interface standard was developed by
  Novell to allow network protocols (such as IPX and
  TCP/IP) to communicate with network card drivers (such as
  Ethernet and Token-Ring). ShivaRemote includes a network
  card driver that has been tested certified by Novell to
  conform to the ODI standard.
  
  The ShivaRemote ODI driver (dialodi.exe) pretends to be
  an Ethernet driver, so that a network protocol believes
  that it is on a local network. This is true even when
  dialing into a Token-Ring network; the remote networking
  server will do the translation between Ethernet and Token-
  Ring.
  
  
  2.0  ODI Communications
  
  ODI allows several protocols and several network card
  drivers to be loaded at the same time. Each protocol and
  card driver is called a module. Communication between
  these modules is done through a program called the Link
  Support Layer (LSL). The LSL file is called lsl.com, and
  is loaded in your autoexec.bat file or at the DOS prompt.
  
  When ODI protocols and card drivers are loaded, they all
  register their presence with the LSL. Each protocol then
  determines which card driver (or drivers) it should
  communicate with. Communication between a protocol and a
  card driver is called a binding.
  
  
  3.0  ODI Configuration
  
  ODI drivers are configured through entries in the net.cfg
  file. This is a simple text file that can be modified by
  any text editor, such as the DOS Edit program or the
  Windows Notepad program.
  
  
  3.1  Configuration Sections
  
  Each ODI module has its own section, which begins in the
  first column. This section name is followed by an
  arbitrary number of configuration entries, each of which
  is indented by one or more spaces. In most cases, a
  module's default settings are appropriate. If this is the
  case, a section in net.cfg is not needed.
  
  For example, the Link Support Layer (LSL) section may be
  empty:
  
     link support
  
  Some applications (such as FTP Software PC/TCP and OnNet)
  require that the LSL support more than 4 protocol stacks
  (the default). In this case, a configuration entry is
  necessary:
  
     link support
      max stacks 9
  
  
  3.2  The ShivaRemote Section
  
  The ShivaRemote ODI driver's name is DIALODI. Since
  ShivaRemote does not use the net.cfg file for any
  configuration information, its section will be empty:
  
     link driver DIALODI
  
  If desired, this section can be omitted.
  
  
  3.3  Binding a Protocol to a Card
  
  In the most simple case, where a single ODI network card
  driver is loaded, entries in net.cfg are not needed. If
  more than one ODI network card driver is loaded, net.cfg
  must specify which driver a protocol should use.
  
  For example, if you load both dialodi.exe and ne2000.com
  (the ODI driver for the Novell/Anthem NE2000 Ethernet
  card), and you want NetWare IPX to use the ShivaRemote
  driver, your net.cfg should look like this:
  
     link support
  
     link driver NE2000
        int  3
        frame Ethernet_802.2
  
     link driver DIALODI
  
     protocol IPXODI
        bind DIALODI
  
  If you want NetWare IPX to use the NE2000 driver, your
  net.cfg should look like this:
  
     link support
  
     link driver NE2000
        int  3
        frame Ethernet_802.2
  
     link driver DIALODI
  
     protocol IPXODI
        bind NE2000
  
  
  4.0  Loading ODI Drivers
  
  ODI drivers are loaded from the DOS prompt (or in the
  autoexec.bat file). The Link Support Layer is always
  loaded first:
  
     C:\> lsl
  
  The Link Support Layer will always look for the net.cfg
  file in the same directory that the lsl.com file is in.
  If you have more than one copy of lsl.com on your hard
  disk, make sure that you are loading the appropriate one.
  For example, to load the lsl.com in the Shiva directory:
  
     C:\> c:\shiva\lsl
  
  Next, the ODI network card driver must be loaded:
  
     C:\> c:\shiva\dialodi
  
  Finally, the ODI protocol driver is loaded. For Novell
  NetWare, this is ipxodi.com:
  
     C:\> c:\shiva\ipxodi
  
  
  5.0  Unloading ODI Drivers
  
  Because ODI drivers are loaded from the DOS prompt, and
  not in config.sys, they can be unloaded. Unload the
  drivers in the reverse order from which they were loaded:
  
     C:\> c:\shiva\ipxodi u
     C:\> c:\shiva\dialodi u
     C:\> c:\shiva\lsl u
  
  
