
Microsoft(R) LAN Manager 
Remote Access Service

Version 1.1

SUPPLEMENTAL INFORMATION
========================
Copyright(c) 1991-1992 Microsoft Corporation
All rights reserved.

Microsoft, MS, and MS-DOS are registered trademarks of Microsoft Corporation. 
Operating System /2 and OS/2 are registered trademarks licensed to Microsoft 
Corporation.

U.S. Patent Number 4955066

Table of Contents

Topic									Pg
------------								--
Introduction								2
Installation and Configuration						2
   Installing Windows for Workgroups 3.1				2
   Installing LAN Manager						2
   Installing MS OS/2 Serial Device Drivers for Built-in Ports		2
Configuring the Remote Access Server for 16 Simultaneous Connections	3
   PROTOCOL.INI								3
   CONFIG.SYS								3
Modems									3
   Supported Modems							4
   Notes on Supported Modems						4
   Using Non-Supported Modems						4
   Modem Initialization String						4
   Modem Listen String							5
   Error Control and Compression					5
   Things to Check Before Enabling Error Control and/or Compression	5
   Enabling Modem Error Correction and/or Compression			6
   Understanding MODEMS.INF						6
Using the Remote Access Client Software on Dual-role Computers		6
   Loading and Unloading the Remote Access Drivers with LAN Manager	7
   Loading the Remote Access Drivers into Upper Memory with LAN Manager	7
   Load Command Switches						7
Removing Remote Access from a LAN Manager Server with Local Security	8
Tuning									8
   Modifying LANMAN.INI on MS OS/2 Servers				8
   Increasing File Transfer Speed					8
Configuration Files							9
   PROTOCOL.INI								9
   Formatting Errors in Appendix C					10
Notes on EiconCard							10
Stacker Disk Compression						11
Adding the Remote Access Phone Book to Microsoft Windows 3.1		11
Adding the Remote Access Administrator's Utility to
	Microsoft Windows 3.1 						11
Maintenance and Troubleshooting						11
Callback Security and X.25						12




Introduction
============
This file contains supplemental information and changes to the Microsoft LAN 
Manager Remote Access Service Administrator's Guide and the Microsoft LAN 
Manager Remote Access Service User's Quick Reference. For an on-line version 
of the LAN Manager Remote Access Service User's Quick Reference, see 
USER_REF.TXT.


Installation and Configuration
==============================
The following information supplements and changes the information found in 
the Microsoft LAN Manager Remote Access Service User's Quick Reference and 
in Chapter 4 of the Microsoft LAN Manager Remote Access Service 
Administrator's Guide.


Installing Windows for Workgroups 3.1
-------------------------------------
If you plan to connect to the network using only Remote Access and a modem, 
click the Cancel button when Windows for Workgroups Setup prompts you for 
the type of network adapter you have.  Windows for Workgroups will give 
you several warning messages informing you that network functionality
cannot be provided without network adapters.  Disregard these messages
if you plan to install Remote Access later.  The Remote Access Setup 
program installs the device drivers required by Remote Access.

Note:  If you plan to use a network adapter card and Remote Access at the 
same time, install the appropriate Windows for Workgroups network drivers.


Installing LAN Manager
----------------------
If you plan to connect to the network using only Remote Access and a modem, 
choose "No Driver" from the Network Adapter Drivers list box in the LAN 
Manager Setup program.  The Remote Access Setup program installs the device 
drivers required by Remote Access.

Note:  If you plan to use a network adapter card and Remote Access at the 
same time, install the appropriate LAN Manager drivers.


Installing MS OS/2 Serial Device Drivers for Built-in Ports
-----------------------------------------------------------
The COM drivers supplied with MS OS/2 version 1.2 and earlier do not work 
properly with Remote Access. The version of MS OS/2 included in the Microsoft
LAN Manager 2.1 package contains the appropriate COM0x driver files. If for 
some reason you do not want to install this version of MS OS/2 on your 
system, you can still copy the COM0x files from Disk 2. These files are 
compressed, so you must use the UNPACK utility (UNPACK.EXE) to decompress 
the files and copy them to your workstation:

UNPACK [drive1] [path1] filename [drive2] [path2] [/v]

drive1    Specifies the drive from which you want to copy files. If you do not
	  specify a drive, the UNPACK utility uses the current drive.

path1     Specifies the directory from which you want to copy files. If you 
	  do not specify a directory, the UNPACK utility uses the current 
	  directory on the specified drive.

filename  Specifies the name of the compressed file. This filename has an at 
	  symbol (@) as the third character of its extension.

drive2    Specifies the drive to which you want the files copied. If you do 
	  not specify a drive, the UNPACK utility uses the current drive.

path2     Specifies the directory to which you want the files copied. If you 
	  do not specify a directory, the UNPACK utility uses the current 
	  directory on the specified drive. The utility always uses the 
	  original filename and extension as the destination filename.

/v        Checks whether the sectors written can be read.


Configuring the Remote Access Server for 16 Simultaneous Connections
=====================================================================
To get a Remote Access server to run optimally with 16 simultaneous 
connections, install 16 megabytes of memory on your Remote Access server,
and adjust the following LAN Manager parameters in your PROTOCOL.INI and
CONFIG.SYS files:

PROTOCOL.INI
------------
[TCPIP_XIF]
   NBSESSIONS = 100
   NUMNAMES = 60
   ;NUMNCBS = 85

   Note:
   Commenting out the NUMNCBS = line lets the TCP/IP stack 
   assume the highest value possible.

[NETBEUI_XIF)
   NAMES = 160
   SESSIONS = 160
   NCBS = 180

CONFIG.SYS
----------
   IFS = c:\LANMAN\NETPROG\HPFS386.IFS /I: C:\LANMAN /AUTOCHECK <drives> 
         /CACHE:2048

   Notes:
   1.   Add to the AUTOCHECK parameter the drive letters that correspond
	to your HPFS drives. For example, if you have disk partitions C, D,
	and E,the AUTOCHECK parameter should look like this: 
        /AUTOECHECK CDE

   2.   Set the CACHE size to 2048 so that the LAN Manager file server 
        frees more resources for the Remote Access server.


Modems
======
The following information supplements the information found in Appendix A 
of the Microsoft LAN Manager Remote Access Service Administrator's Guide.


Supported Modems
----------------
In addition to the modems listed in Appendix A, Remote Access also supports 
the following modems:

-  Codex 3260
-  Codex 2264
-  Hayes Ultra 1440
-  Microporte Pocket
-  Microcom QX/4232hs
-  Motorola UDS
-  MultiTech Multimodem 224E
-  Racal-Milgo RMD 3221
-  Racal-Milgo RMD 3222
-  Telebit Qblazer


Notes on Supported Modems
-------------------------
The Hayes V-Series 9600 modem will connect only at 9600 baud with another 
Hayes V Series 9600 baud modem.  If you install a Hayes V-Series 9600 modem 
on a Remote Access server, ensure that Remote Access client workstations 
also have Hayes V-Series 9600 modems.  Otherwise, connections will probably
be established at 2400 baud.

The Racal Vadic 9642PA, Racal Milgo RMD 3222, and Penril Alliance V.32 
modems will operate correctly only when the baud rate is set to match the 
actual connection rate.  For example, if you select a baud rate of 19200 
baud and the connection is established at 9600 baud, you should disconnect, 
select a baud rate of 9600, and reconnect.


Using Non-Supported Modems
--------------------------
If you have a modem that is not supported by Remote Access, try using the 
settings for a modem that is supported. If you are unable to find a modem 
setting that is compatible, you can modify your MODEMS.INF file as described 
in the Microsoft LAN Manager Remote Access Service Administrator's Guide. 
Consult your modem manuals or modem manufacturer for further help. Here are 
some tips to keep in mind as you begin this task:


Modem Initialization String
---------------------------
Refer to your modem manual for the specific commands you use to do the 
following:

-  Recall factory settings
-  Track presence of data carrier detect (DCD high when carrier detected)
-  Hang up and disable auto-answer when DTR goes from ON to OFF (high to 
   low)
-  Return result codes
-  Return verbose codes
-  Enable character echo in command state
-  Wait approximately 55 seconds for carrier
-  Make normal asynchronous connection (only needed if your modem supports 
   synchronous connections)
-  Disable error control (disable MNP4, V42, or other error control scheme)
-  Disable compression (disable MNP5, V.42bis, or other compression scheme)
-  Disable +++ escape sequence
-  Disable software and hardware flow control


Modem Listen String
-------------------
Refer to your modem manual for the specific command you use to make the modem 
answer after one ring. This is needed for Remote Access servers and also for 
client workstations that will be using callback.


Error Control and Compression
-----------------------------
Microsoft disables error control and compression for the following reasons:

-  The Remote Access asynchronous protocol (ASYBEUI) implements error 
   control. Therefore, enabling error control within the modem introduces
   redundancy and may cause unnecessary re-transmission of data.

-  Remote Access does not yet support Hardware Flow Control.  Flow Control
   is needed to regulate data transfer when compression is enabled.

-  Not all processors can accommodate the 19200 or greater baud rate 
   required to make compression worthwhile at 9600 baud (see the following 
   table). Note that the baud rate specified in the MAXBAUD parameter of 
   MODEMS.INF refers to the computer-to-modem speed, not the modem-to-modem 
   speed.

-  Not all UARTs can accommodate the 19200 or greater baud rate
   required to enable compression. A 16450 or higher serial port UART chip 
   is required.

Operating system                Processor       Maximum baud rate*
----------------                ---------       ------------------
MS-DOS & Microsoft Windows      8086            2400
				80286           9600
				80386           19200
				80486           38400
MS OS/2**                       80286           4800
				80386           9600
				80486           19200

*May vary depending on CPU speed, memory speed, software running, and other 
 factors.
**Does not apply to MS OS/2 computers with multiport adapters.

Things to Check Before Enabling Error Control and/or Compression 
--------------------------------------------------------------------
-  Your computer can accommodate the higher baud rates required for 
   compression. Make sure your Remote Access client workstation has a
   80386 or higher processor and also has 16450 or higher serial port
   UART chip installed.

-  Your Remote Access server has a multiport adapter installed, relieving 
   the main processor of some of the interrupt processing load.

-  You have identical or compatible modem types on the server and client 
   workstations.

-  Your telephone line has little or no static. This minimizes the impact 
   of redundant error control.

Enabling Modem Error Correction and/or Compression
--------------------------------------------------
-  Set the MAXBAUD parameter for your modem in the MODEMS.INF file to the 
   maximum baud rate at which you will be communicating. Valid baud rates 
   are 1200, 2400, 4800, 9600, 19200, and 38400.

-  For MS-DOS workstations running LAN Manager Enhanced, change digit 14 of 
   the WRKHEURISTICS line in LANMAN.INI from 1 to 0. This causes the LAN 
   Manager workstation to transfer data in 64K blocks. This large block size 
   ensures a smooth, constant flow of data from the computer to the modem. 
   The modem's compression buffers will fill up quickly, thereby minimizing 
   data transmission delays.

-  For MS OS/2 workstations, change digit 11 of the WRKHEURISTICS line in 
   LANMAN.INI from 0 to 1. This causes the LAN Manager workstation to 
   transfer data in 64K blocks. This large block size ensures a smooth, 
   constant flow of data from the computer to the modem. The modem's 
   compression buffers will fill up quickly, thereby minimizing data 
   transmission delays.

-  Increase the value of the MAXDYNMEM parameter in the LANMAN.INI file of 
   the Remote Access server to accommodate Remote Access clients that use a 
   large frame size for data transfer. There is a trade-off between gaining 
   faster file transfer, and the amount of memory required on the Remote 
   Access server.  You will have to increase the amount of memory installed
   on your Remote Access server.  For more details on tuning the Remote
   Access server, see Chapter 6 in the Microsoft LAN Manager Remote
   Access Service Administrator's Guide.

Note: Microsoft cannot guarantee proper functionality at baud rates
      higher than those indicated in the default MAXBAUD = line of
      your MODEMS.INF file.

Understanding MODEMS.INF
------------------------
In addition to the macros listed in Appendix A, the following macros can 
also be used in the MODEMS.INF file:

Macro   Function
-----   ------------
hxx     Inserts a character represented by the next two hexadecimal 
	digits. For example, to send Ctrl+P (ASCII character 16), 
	use *h10 (10 hex is 16 decimal).

w       (wild card character) Matches any one character coming from the 
	modem.


Using the Remote Access Client Software on Dual-role Computers
===============================================================
A user who plans to use a computer both in and out of the office types 
UNLOAD <protocol> to unload any network protocol drivers that are used 
at the office before loading the Remote Access drivers and attempting a
remote connection.

Note:  The UNLOAD command will not unload device drivers or TSRs that do 
not conform to the LAN Manager 2.1 Demand Protocol Architecture (DPA). 
Type LOAD /I to see the names of the protocols that can be unloaded using 
the UNLOAD command. If the protocol you are running cannot be unloaded 
using the UNLOAD command, you may unload it by running the LAN Manager 
Setup program, removing that protocol from your configuration, and 
rebooting your computer.


Loading and Unloading the Remote Access Drivers with LAN Manager
------------------------------------------------------------------
On MS-DOS computers, typing RASLOAD /U unloads the Remote Access drivers 
and, if necessary, stops the Workstation service. Typing RASLOAD /U /Y 
answers yes to all the questions normally asked when stopping the 
Workstation service, and carries out the command without prompting.


Loading the Remote Access Drivers into Upper Memory with LAN Manager
--------------------------------------------------------------------
On MS-DOS client workstations, the Remote Access Setup program adds the 
following lines to the [asybeui_xif] section of PROTOCOL.INI:

load="asybeui", "vcommiod[u]", "wantsr[u]"
unload="wantsr /u[c]", "vcommiod /u[c]", "asybeui[du]"

The [u] switch in the LOAD= line allows MS-DOS 5 to load the Remote Access 
drivers into upper memory. You can also use a third-party memory manager
to load the drivers into upper memory. For example, if you are using 
Quarterdeck expanded memory manager 386, you would insert the Quarterdeck 
LOADHI command as follows:

load="loadhi lanroot\drivers\protocol\asybeui\asybeui[cbr]", 
     "loadhi vcommiod[c]", "loadhi wantsr[c]"
unload="wantsr /u[c]", "vcommiod /u[c]", "asybeui[du]"


Load Command Switches
---------------------
The LOAD command accepts the following switches:

[u]     When used in the LOAD=  line, the program is loaded into upper 
	memory blocks on MS-DOS 5, if possible; otherwise the program is 
	loaded into conventional memory. When used in the UNLOAD=  line, 
	the program is unloaded.

[c]     No attempt is made to load the program into upper memory blocks.

[b]     Binds the protocol to the hardware device driver.

[r]     Registers the protocol with the LAN Manager redirector.

[D]     Deregisters the protocol from the LAN Manager redirector.

The default switches are [ubr]. Before binding, be sure the program is 
already loaded; that is, use [u] or [c] before using [b]. Before registering, 
be sure that the file is both loaded and bound; that is, use [u] or [c] and 
[b] before using [r].  Refer to the Microsoft LAN Manager Administrator's 
Guide for more details on the LOAD and UNLOAD commands.


Removing Remote Access from a LAN Manager Server with Local Security
====================================================================
If you are removing Remote Access from a server that has local security, do 
the following:

1. Type NET STOP WORKSTATION. This logs you off from both the network and 
   the server with local security.
2. Log back on to the server.
3. Proceed as usual.

Note: For more information about local security, refer to the Microsoft LAN 
Manager Administrator's Guide.



Tuning
======
The following information supplements and changes the information found in
Chapter 6 of the Microsoft LAN Manager Remote Access Service Administrator's
Guide.


Modifying LANMAN.INI on MS OS/2 Servers
---------------------------------------
The following parameter can be added to the [remoteaccess] section of 
LANMAN.INI:

CALLBACKTIME
Determines the amount of time the server must wait before calling a client 
back. The range is 2 through 12 seconds; the default is 3. This parameter 
helps to accommodate modems that take a long time to drop the DCD signal 
on the client side.

The following information applies to the MAXNAMES parameter:
A maximum of 64 NetBIOS names can be allocated to the TCP/IP protocol stack. 
A maximum of 31 NetBIOS names can be allocated to the Microsoft loop back 
driver (LOOPDRV.OS2).


Increasing File Transfer Speed
------------------------------
-  For MS-DOS workstations running LAN Manager Enhanced, change digit 14 of 
   the WRKHEURISTICS line of LANMAN.INI from 1 to 0. This causes the LAN 
   Manager workstation to transfer data in 64K blocks.

-  For MS OS/2 workstations, change digit 11 of the WRKHEURISTICS line of 
   LANMAN.INI from 0 to 1. This causes the LAN Manager workstation to 
   transfer data in 64K blocks.

-  Increase the value of the MAXDYNMEM parameter in the LANMAN.INI file of 
   the Remote Access server to accommodate Remote Access clients that use a 
   large frame size for data transfer.

Note:  There is a trade-off between gaining faster file transfer, and the 
amount of memory required on the Remote Access server.  Read Chapter 6 of 
the Microsoft LAN Manager Remote Access Service Administrator's Guide for 
more details on tuning the Remote Access server.


Configuration Files
===================
The following information supplements information found in Appendix C of 
the Microsoft LAN Manager Remote Access Service Administrator's Guide.


PROTOCOL.INI
------------
In addition to the entries made to the PROTOCOL.INI file by the Remote Access 
Setup program, the following entries can also be added to the [asybeui_xif] 
section of PROTOCOL.INI:

Note: Changes made to the [ASYBEUI_XIF] section in PROTOCOL.INI will be 
overwritten when the configuration is updated with the Remote Access Setup 
program.  To make a change permanent, add it to the ASYBEUI PROTOCOL.INI 
fragment file found in the DRIVERS\PROTOCOL\ASYBEUI subdirectory of your 
LAN Manager directory.


Entry           Default
-----           ----------
datagrampackets 2*

dlcretries      8

looppackets     1

maxin           1

maxout          2

maxtransmits    2

mintransmits    1

names           17

ncbs            85 for MS OS/2
		12 for MS-DOS

netbiosretries  4

packets         128 for MS OS/2
		24 for MS-DOS

piggybackacks   1

pipeline        2

selectors       # of sessions (MS OS/2 only)

sessions        40 for MS OS/2
		6 for MS-DOS

stacksize       2048


*To submit multiple asynchronous NetBIOS commands to the client stack 
 simultaneously, increase the DATAGRAMPACKETS value to 10.

The entries listed above are the default parameters for Microsoft 
AsyBEUI 2.1. The parameter names and their definitions are identical
to those used for NetBeui. Refer to the NetBeui parameters Chapter 10 
of the Microsoft LAN Manager Installation and Configuration Guide for 
definitions and ranges.

Formatting Errors in Appendix C
-------------------------------
The sample PROTOCOL.INI file listed in Appendix C, page 100, of the Remote Access Service Administrator's
Guide reads as follows:

   [ASYBEUI_XIF] DRIVERNAME = ASYBEUI BINDINGS = "ASY_NIF", "ASY_NIF2"
   LOAD = ASYBEUI,VCOMMIOD[U],WANTSR[U] UNLOAD = "WANTSR /U[C]", "VCOMMIOD
   /U[C]", "ASYBEUI[D]"

   [ASY_NIF1] DRIVERNAME = ASYMAC$

   [ASY_NIF2] DRIVERNAME = ASYMAC$

It should read:

   [ASYBEUI_XIF]
      DRIVERNAME = ASYBEUI
      BINDINGS = "ASY_NIF1", "ASY_NIF2"
      LOAD = ASYBEUI,VCOMMIOD[U], WANTSR[U]
      UNLOAD = "WANTSR /U"[C], "VCOMMIOD /U[C]", "ASYBEUI[D]"

   [ASY_NIF1]
      DRIVERNAME = ASYMAC$

   [ASY_NIF2]
      DRIVERNAME = ASYMAC$

The sample LANMAN.INI file listed in Appendix C, page 102, of the
Remote Access Service Administrator's Guide reads as follows:

      netx = asybeui$, 0 nety = asybeui$, 1 ...

It should read:

     netx = asybeui$, 0
     nety = asybeui$, 1
       .
       .

Notes on EiconCard
==================
When Remote Access Service version 1.1 was released in October 1992,
the Eicon X.25 adapters did not support more than 13 ports. Please
check with Eicon product support for information on when Eicon will
support 16 ports.


Stacker Disk Compression
========================
Remote Access Service supports only version 2.0 of Stacker. If you 
are running Stacker version 1.1, please upgrade to version 2.0.

If your network directory (for example, LANMAN.DOS, WINDOWS, DOS, DOSNET)
is on a Stacker drive, please make sure that Stacker is started before 
the protocol manager in your CONFIG.SYS file.


Adding the Remote Access Phone Book to Microsoft Windows 3.1
=================================================================
1.  From the Program Manager, choose File.
2.  From the File menu, choose New.
3.  From the New Program Object dialog box, choose Program Item.
4.  Choose OK.
5.  In the Program Item Properties dialog box, fill in the edit fields as 
    follows:
       -  Description: REMOTE ACCESS PHONE BOOK
       -  Command Line: RASPHONE.EXE
6.  Choose Change Icon.
7.  In the Select Icon dialog box, type in the File Name field:
       -  C:\LANMAN.DOS\NETPROG\RASPHONE.ICO (if you are running LAN Manager 
	  Enhanced)
       -  C:\LANMAN.DOS\BASIC\RASPHONE.ICO (if you are running LAN Manager 
	  Basic)
     If you have installed LAN Manager to a directory other than 
     c:\lanman.dos, replace C:\LANMAN.DOS with that directory name.
8.  Choose OK.
9.  In the Program Properties dialog box, choose OK.


Adding the Remote Access Administrator's Utility to Microsoft Windows 3.1
==========================================================================
1.  From the Program Manager, choose File.
2.  From the File menu, choose New.
3.  From the New Program Object dialog box, choose Program Item.
4.  Choose OK.
5.  In the Program Item Properties dialog box, fill in the edit fields as 
    follows:
       -  Description: REMOTE ACCESS ADMIN UTILITY
       -  Command Line: RASADMIN.EXE


Maintenance and Troubleshooting
===============================
The following information supplements the information found in Chapter 5 of 
the Microsoft LAN Manager Remote Access Service Administrator's Guide.


User complains about abnormal disconnection when starting Microsoft Windows 
3.0 
---------------------------------------------------------------------------
When running MS-DOS and the Microsoft Windows 3.0 graphical environment and 
using a serial mouse, be sure to start the Windows environment before 
connecting. Alternatively, you can upgrade to Microsoft Mouse version 8.0 
or later. When using the version 8.0 mouse driver, change the second line 
in the MOUSE.INI file from AUTOMATIC SEARCH to SERIAL1 or SERIAL2, depending 
on which serial port the mouse is attached to.

Note: Contact Microsoft for information on upgrading mouse drivers.


User is unable to access LAN resources even though the connection appears 
intact.  
-------------------------------------------------------------------------
Ensure that modem pooling equipment and telephone switches on the server 
side are configured to drop the DTR when the server disconnects. 

If you have configured the Remote Access server to use the RASLANNETS= 
parameter in the LANMAN.INI file, ensure that the Remote Access server's 
configuration allows access to the resource in question. Refer to the LAN 
Manager Remote Access Service Administrator's Guide for more information 
on LANMAN.INI parameters.


User complains about screen black out.
-------------------------------------
When running MS-DOS and the version 7.0.4 mouse driver, the screen may 
black out after a popup message appears. Upgrade the mouse driver to 
version 8.0 or later.


User complains that Remote Access server is not calling back as expected.
-------------------------------------------------------------------------
-  The user's account may not been properly configured.  Use the Remote 
   Access Administrator's Utility to ensure that  the correct callback 
   permission has been assigned for the user.  Refer to the Microsoft LAN 
   Manager Remote Access Service Administrator's Guide for information on 
   how to assign Callback to a user account.
-  The user's modem may not be resetting itself quickly enough when the 
   phone line is disconnected prior to callback.  Increase the CALLBACKTIME=
   parameter in the [remoteaccess] section of the Remote Access server's 
   LANMAN.INI file.  Read the section on "Tuning" in this document for more 
   information on the CALLBACKTIME= parameter.


User encounters errors while installing Remote Access.
------------------------------------------------------
-  There may be insufficient DOS memory available. If LAN Manager is 
   installed, type NET STOP WORKSTATION and try again. Otherwise, unload 
   some terminate-and-stay-resident (TSR) programs and try again.
-  There may be insufficient storage space on the user's hard disk. Ensure 
   that the user's hard disk has a least 1MB of free space.


Callback Security and X.25
==========================
The Remote Access Service does not support callback on X.25 networks.
