Client README.TXT for Dial-Up Manager Client
(updated 07/21/95).    

=======================================================================
NOTES ON THE Dial-Up Manager 
=======================================================================

This file provides important information not included in the 
Dial-Up Manager Client manual.
 
This file is divided into the following sections: 
 
1. Restrictions 
   1.1  Simultaneous connections to local and remote networks 
   1.2  Unloading WLODI.COM 

2. Troubleshooting 
   2.1  Connection Problems
   2.2  Problems attempting to log in to servers
   2.3  Throughput problems

3. Tips and Miscellaneous Information 
   3.1 Sharing your COM port with other programs 
   3.2  Printing help files
   3.3  Using VLM 1.20

4. Integrating Dial-Up Manager access with existing programs
   4.1  Connecting and disconnecting within Lotus Notes
   4.2  Launching Dial-Up Manager within Microsoft Office
   4.3  Launching within Novell NetWare Tools

5. Using Dial-Up Manager with Windows for Workgroups (WFW)    

=======================================================================
1.  Restrictions 
=======================================================================
The following restrictions apply when using the Dial-Up Manager. 
 
------------------------------------------------------------------------ 
1.1  Simultaneous Connections to Local and Remote Networks 
------------------------------------------------------------------------ 
The client workstation cannot have a local network connection (Ethernet,
token ring, etc.) as well as a remote Dial-Up Manager connection. You can
have only a single IPX connection at a time.  If you are already
connected to a local network, you need to log out and unload the network
modules.

If you are already connected to a network, unload the network modules in 
the reverse order in which they were loaded.  For example, if you are
connected to the network using the NETX shell, you would unload the 
modules as follows:

        NETX /U         (unload NETX shell)
        
        IPXODI /U       (unload IPX ODI driver)
        
        NE2000 /U       (unload ethernet card driver)
        
        LSL /U          (unload link services layer) 
        
Now, you can reload the network modules using Dial-Up Manager.
 
------------------------------------------------------------------------ 
1.2  Unloading WLODI.COM 
------------------------------------------------------------------------ 
If you have loaded WLODI.COM in high memory with the "LH WLODI" command,
then it is possible to accidently unload WLODI before unloading other
TSRs loaded after it (such as IPXODI.COM and VLM.EXE).  If you do this,
you will not be able to unload other TSRs loaded after WLODI.

Make sure you unload TSRs in the reverse order of loading them.  Use
the supplied batch files HANGUP.BAT or UNLOAD.BAT to do this.
 

=======================================================================
2.  Troubleshooting 
=======================================================================
This section describes how to deal with problems that may occur while 
using Dial-Up Manager.

------------------------------------------------------------------------ 
2.1  Connection problems
------------------------------------------------------------------------ 
If you are having trouble making a connection with Dial-Up Manager, one of 
the following may be the problem:

   -    You haven't loaded the Dial-Up Manager ODI driver (WLODI.COM). 

        If the driver is not loaded, the Status line at the bottom of 
        the screen will indicate "Driver Not Loaded".

   -    You haven't selected the correct modem in the Setup dialog. 

        Check the Setup dialog. If the modem is incorrect, you may get 
        a "Modem error" when trying to connect. Also, listen for the 
        telltale sounds the modem makes while picking up the phone, 
        dialing, etc.

   -    You haven't selected the correct COM port in the Setup dialog. 

        If you haven't, you will hear no sounds from the modem since 
        no data is being sent to it. Also, you may get a "Timeout" 
        error after trying to connect.

   -    Your modem and the server's modem have compatibility problems. 

        This can result in various errors when attempting to connect. 
        One common problem is that different modems try to negotiate 
        v.42bis and MNP in different orders. You may need to modify 
        your modem's command strings to force it to negotiate in a 
        manner compatible with the modem to which you are trying to 
        connect.  

   -    There is a high error rate over your serial port. 

        If the error rate is too high, you may get an error when 
        attempting to connect. Even if you do connect successfully, 
        the throughput of the connection may suffer. Check the Port 
        Statistics dialog for error rates. The ratio of "Rx errors" to 
        "Rx total" should be at least 1 in 1,000; ideally it should be 
        1 in 10,000 or better. If this seems to be a problem, lower 
        your baud rate.

------------------------------------------------------------------------ 
2.2  Problems attempting to log in to servers
------------------------------------------------------------------------ 
If, once you've established a Dial-Up Manager connection, you have problems 
initially attaching to a remote access server or you have problems 
logging in to a server, it may be due to one of the following causes:

   -    The Remote Access Server may be improperly configured.

        One typical problem is that the remote access server has not
        been configured for IP or IPX. For a Dial-Up Manager server,
        this would happen if a BIND was not made to IP or IPX. For
        other remote access servers, the configuration for IP or IPX
        may have been incorrect. This will prevent all communication
        with the network. Contact your administrator.

   -    Your access to the network may be restricted.

        Your administrator has the capability of limiting your access 
        to particular addresses on the network. If you attempt to 
        attach a server to which you have no access, you will be 
        unsuccessful. For a Dial-Up Manager server, this can be the result
        of Domain Filtering.

------------------------------------------------------------------------ 
2.3  Throughput problems
------------------------------------------------------------------------ 
If throughput seems slow, it may be due to one of the following causes: 

   -    You are using NETX, and not VLM for NetWare connections 

        Using NETX will cause significant slowing of file transfers.
        You should always use the latest VLM for connecting to Novell
        servers.

   -    There is a high error rate over your serial port. 

        Check the Port Statistics dialog for error rates. The ratio of 
        "Rx errors" to "Rx total" should be 1 in 10,000 or better for 
        maximum throughput. If this seems to be a problem, lower your 
        baud rate.

   -    Your serial port's baud rate is too low.

        You can't send or receive data any faster than your baud rate. 
        If your baud rate is set too low, it may limit the throughput 
        of your connection. However, you don't want to set it so high 
        that a high error rate occurs.

        On a reasonably fast machine with a 16550 UART, you should be 
        able to set your baud rate to the maximum (115200 bps) without 
        problem.

   -    You may be running programs from a network drive.

        Try to run local copies of programs so the program does not 
        have to be transported over the phone line. Make sure you have 
        local copies of programs such as LOGIN, ATTACH, and MAP so you 
        can make network connections quickly.
        
=======================================================================
3.  Tips and Miscellaneous Information 
=======================================================================
------------------------------------------------------------------------ 
3.1  Sharing your COM Port with Other Programs 
------------------------------------------------------------------------ 
Dial-Up Manager supplies a VxD (WLODIV.386) that optimizes serial
communication in Windows enhanced mode.  If WLODI.COM is loaded, the VxD
automatically loads when you start Windows.  Dial-Up Manager will properly
share the COM port, in most cases, with other Windows applications.

------------------------------------------------------------------------ 
3.2  Printing Help Files 
------------------------------------------------------------------------ 
Dial-Up Manager Help provides a handy tool for printing help files called the
Navigator. To print out the entire help file, do the following:

   1    Access Dial-Up Manager Help. 

   2    Press the Navigator button. The Dial-Up Manager Navigator screen
        appears. 

   3    Press File Print and the Print popup dialog appears. 

   4    Choose All Topics and Press OK. The entire help file is then sent 
        to your printer. 

You can also choose to print just the current topic or the current topic
and its subtopics. 

------------------------------------------------------------------------ 
3.3  Using VLM 1.20
------------------------------------------------------------------------ 
You should always use the new NetWare Client (VLM 1.20), which is 
included in the Dial-Up Manager Client.

Unlike previous versions, VLM 1.20 will display error messages
whenever you disconnect from a Dial-Up Manager connection, and then try to
re-connect to a different network. You will be prompted to "Retry or
Cancel" for these network errors; you should always answer "Cancel."

=======================================================================
4.  Integrating Dial-Up Manager access with existing programs
=======================================================================
This section contains instructions on how to add icons to the toolbars
of the following applications:

   -    Lotus Notes.  Adds two icons to your Lotus Notes toolbar: the
        Dial-Up Manager Launch icon, which launches Dial-Up Manager, and the
        Dial-Up Manager Disconnect icon, which terminates a connection.

   -    Microsoft Office. Adds a Dial-Up Manager launch icon to the
        Microsoft Office toolbar.

   -    NetWare Tools.  Adds a Dial-Up Manager launch icon to the NetWare
        Tools toolbar.

These procedures show how to add icons that launch the Dial-Up Manager
Windows Client program.  If you want to create an icon that launches
Dial-Up Manager and establishes a remote connection, you must specify the
name of a batch file instead of the WLINKW.EXE program.  For more
information about creating and using batch files, refer to the
Dial-Up Manager documentation. 

------------------------------------------------------------------------ 
4.1  Connecting and Disconnecting Within Lotus Notes
------------------------------------------------------------------------ 

4.1.1  Benefits
------------------------------------------------------------------------ 
Remotely connecting to Lotus Notes via Dial-Up Manager offers a number of
benefits over remotely connecting using the Remote Notes feature.

The benefits of Dial-Up Manager for remote access to Notes include:

   -    Access to all Notes servers.  

        Remote users dialing in with Dial-Up Manager have full access to 
        all Notes servers on the network. Remote users are no longer 
        limited to connecting to one Notes server at a time.

   -    Access to the rest of the network as well.

        The same Dial-Up Manager connection you use to access Notes servers 
        can be used to access file servers, network printers, E-mail, 
        etc.

Once you have set up Notes for remote access, you can then read and
respond to mail and perform any other database operations.  You can 
use Notes' powerful "Replication" feature to create mail off-line, then
connect with Dial-Up Manager to only send and receive mail.

4.1.2  Before You Start
------------------------------------------------------------------------ 
Before using Dial-Up Manager to access Notes, you should first install Notes
on your remote workstation, then replicate all databases you want to
access.  The first time you replicate, you may want to be directly 
connected to the LAN.  This will speed up the process.

Make sure that you have set up Dial-Up Manager to connect from Windows.
If you have not already done this, you will need to exit from Windows
and load the Dial-Up Manager drivers.  See Chapter II-4 of the Dial-Up Manager
for instructions.

You need to create a Dial-Up Manager connection called "NOTES".  This
connection should dial up the Dial-Up Manager server on the Notes network
that you wish to access.  The "NOTES" connection will be invoked
by the supplied Notes macro file (WLINK.MAC).

If you are using NETBIOS to run Notes, remember to modify your
LOADVLM.BAT file to load NETBIOS directly after IPXODI.

4.1.3  Adding the Dial-Up Manager Launch Icons to Lotus Notes
------------------------------------------------------------------------ 
To add the Dial-Up Manager Launch icon to the Lotus Notes toolbar, do the
following:

   1     Copy the following files from your Dial-Up Manager directory
         to your NOTES\WIN subdirectory:  WLINK.BMP, WLINK.MAC,
         WLINKD.BMP, and WLINKD.MAC.

   2     Start Notes.  Within Notes, select Tools, then SmartIcons.

   3     Scroll to the end of the Available icons list on the left.

   4     Select the Dial-Up Manager Launch icon. (It is a yellow bolt on a
         purple background.)

   5     Drag and drop the icon into the Default Set list on the right.
         We recommend you place it near the File Save icon.

   6     Click on the Dial-Up Manager Launch icon in the Default Set list.

   7     Press Edit Icon. The Edit SmartIcons window appears.

   8     In the Description field, type Dial-Up Manager Launch.

   9     Press Formula. The SmartIcons Formula window appears.

  10     Press OK, Done, and OK.

  11     Click on the Dial-Up Manager Disconnect icon in the Default Set
         list.

  12     Press Edit Icon. The Edit SmartIcons window appears.

  13     In the Description field, type Dial-Up Manager Disconnect.

  14     Press Formula. The SmartIcons Formula window appears.

  15     Press OK, Done, and OK.

You can now launch Dial-Up Manager within Notes by pressing the Dial-Up Manager
Launch icon.  This will use the "NOTES" connect that you have 
previously defined in Dial-Up Manager.

You can disconnect Dial-Up Manager within Notes by pressing the Dial-Up Manager
Disconnect icon.

------------------------------------------------------------------------ 
4.2  Launching Dial-Up Manager Within Microsoft Office
------------------------------------------------------------------------ 
You can add the Dial-Up Manager icon to the Microsoft Office toolbar.
Pressing the icon will launch Dial-Up Manager, automatically dialing in and
establishing your remote connections.  The following procedure shows
how to add the Dial-Up Manager icon, however, you can also add the Dial-Up Manager
name to the Microsoft Office menu.  For information about this procedure,
refer to your Microsoft Office documentation.

To add the Dial-Up Manager icon to the Microsoft Office toolbar, perform the
following:

   1    Start Microsoft Office.

   2    Press the Microsoft Office button. When the drop-down menu
        appears, select Customize.

   3    Select the Microsoft Office Toolbar. 

   4    Press Add.

   5    In the Description field, type Dial-Up Manager. 

   6    In the Command Line field, type the complete pathname of the
        Dial-Up Manager windows program, i.e., C:\WFC16\WLINKW.EXE.

   7    In the Working Directory field, type the name of your Dial-Up Manager
        directory, i.e., C:\WFC16.

   8    Select Application Icon from the Button Image list box. 

   9    Press OK.  The X should appear in the Dial-Up Manager box. Press OK
        again to complete the setup.

------------------------------------------------------------------------ 
4.3  Launching Within Novell NetWare Tools
------------------------------------------------------------------------ 
You can add the Dial-Up Manager icon to the NetWare Tools toolbar.  When you
click on the icon, Dial-Up Manager launches.  This will automatically dial in
and establish your connection to the remote server.

To add the Dial-Up Manager icon to the NetWare Tools toolbar, perform the
following steps:

   1    Start NetWare Tools.

   2    Press User Defined button 1 by pressing [Alt]-1.  The command
        line box will appear.

   3    In the Command Line field, type the complete pathname of the
        Dial-Up Manager program, i.e., C:\WFC16\WLINKW.EXE.
        The Dial-Up Manager Connections screen appears.

   4    Configure Dial-Up Manager the way you want and press Exit.

To add the Dial-Up Manager "Disconnect" icon to the NetWare Tools toolbar,
perform the following steps:

   1    Start NetWare Tools.

   2    Press User Defined button 2 by pressing [Alt]-2.  The command
        line box will appear.

   3    In the Command Line field, type the complete pathname of the
        Dial-Up Manager disconnect program, i.e., C:\WFC16\WLINKWD.EXE.
        The Dial-Up Manager Disconnect box appears.

The next time you invoke NetWare Tools, the Dial-Up Manager disconnect
icon will appear on the toolbar.  You can invoke a Dial-Up Manager 
disconnect by pressing the button (a Dial-Up Manager icon with a red
slash through it). 

------------------------------------------------------------------------ 
5.  Using Dial-Up Manager with Windows for Workgroups (WFW)
------------------------------------------------------------------------ 
WFW has a number of built-in networking features.  Because of this, you
will need to carefully configure WFW to work correctly with Dial-Up Manager.
This section outlines the steps you need to follow.

   1    Install the NetWare Client (VLM 1.20), by running the Dial-Up Manager
        installation and checking "Novell NetWare Files", or by using
        the NetWare installation disk.

   2    Launch the WFW NetWork Setup and click on the Networks button.
        Choose "Install Windows support for the following network only".
        
   3    Choose Novell NetWare (Workstation Shell 4.0 and above).

   4    WFW will give you an option to copy new files over.  Answer
        "No" and close.

An alternative to the above is to select "No Windows support for
networks" from the Networks button in the WFW Network Setup.  This
instructs WFW that you are on a stand-alone machine with no networking
capabilities.  Choosing to install VLM's in the Dial-Up Manager
install will override this setting and install the appropriate drivers
and make the necessary changes to the INI files.  However, this
is not recommended since the Network Setup dialog may not match 
your system initialization (INI) files.

Another alternative is to "Install Microsoft Windows Network", which 
is a peer to peer network that supports NDIS based protocols (however,
Novell only supports ODI based protocols).  This option also contains
a subsection that allows you to install an additional network, which
usually contains either NetWare 3.x or NetWare 4.x drivers.  What WFW
does to make NDIS and ODI work together is to map ODI calls to NDIS
calls, which is done through a "shim" called ODIHLP.EXE.  This option
appears to work, but you may see error messages when starting Windows
and your peer to peer functionality will probably not work.
