Setup Considerations for Microsoft's LAN Manager
------------------------------------------------
If you are using Microsoft's LAN Manager with LAN Distance,
complete the setup and tuning steps in the following sections.
NOTE: LAN Distance does not support the LAN Manager TCP/IP protocol.
DOS/Windows - LAN Manager Requester
-----------------------------------
If you are using LAN Manager Requester and LAN Distance on a Windows
workstation:
o Install the LAN Manager Requester for DOS, choosing the options
described below:
- Choose to install a LAN Manager Enhanced Workstation.
- When the LAN Manager Requester installation program prompts you for
your LAN adapter type, select your LAN adapter type from the list.
If your workstation does not have a LAN adapter, select ANY LAN adapter
type in the list. Do not select "No adapter". This is the easiest way to
get LAN Manager Requester set up.
If you have a LAN adapter, your workstation will be enabled for shuttling
between your LAN-attached environment and your remote environment after
you complete this list of steps.
Do not restart your workstation.
o Add the following line to the [workstation] section in your
LANMAN.DOS\LANMAN.INI file:
[workstation]
; 0 1
; 0123456789012345
wrkheuristics = 1111211012112000
If you had already added this line to tune other heuristics, the only
change necessary for running with LAN Distance is to change bit 14 from
a 1 to a 0. See the Microsoft LAN Manager Administrator's
Reference for a full description of these heuristics.
o Install the LAN Distance Remote for Windows and choose the Basic
Settings option to configure your initial setup.
When LAN Distance installation completes, it will ask you if you want
to be shuttled as a remote workstation or a LAN-attached workstation.
If your workstation does not have a LAN adapter, select "Yes" to
be shuttled for remote connectivity.
o Restart your workstation.
o If you do not have a LAN adapter in your workstation, disable the
LAN Distance Shuttle feature:
1) Open the LAN Distance program group.
2) Open the Settings icon in the LAN Distance program group.
3) Turn to the Workstation tab.
4) Deselect the "Enable Shuttling Between LAN and Remote Workstation"
checkbox.
5) Close the Settings window.
o Complete steps further below under "LAN Manager Server".
Shuttle NOTE:
------------------
When you use LAN Manager Requester in the remote environment,
the PROTOCOL.INI file in your \WAL subdirectory becomes your active
PROTOCOL.INI file.
If you use the LAN Distance Shuttle feature to shuttle your workstation
back to a LAN attached environment, then the PROTOCOL.INI file in your
\LANMAN.DOS subdirectory becomes the active PROTOCOL.INI file.
Sample Files:
------------------
Sample CONFIG.SYS (remote version, CONFIG.RWS)
DEVICE=C:\DOS\SETVER.EXE
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\LANMAN.DOS\DRIVERS\DOSUTILS\EMM386.EXE NoEMS
DOS=HIGH,UMB
FILES=30
STACKS=9,256
LASTDRIVE=Z
DEVICE=c:\WAL\protman.dos /I:c:\WAL
DEVICEHIGH=c:\WAL\dxmj0mod.sys
DEVICEHIGH=c:\WAL\dosvmac.sys
DEVICEHIGH=c:\WAL\winamac.sys
DEVICEHIGH=c:\WAL\pcmdd.sys
Sample AUTOEXEC.BAT (remote version, AUTOEXEC.RWS)
c:\WAL\DOSBIND
C:\DOS\SMARTDRV.EXE
@ECHO OFF
PROMPT $p$g
PATH c:\WAL;C:\WINDOWS;C:\DOS
SET TEMP=C:\DOS
@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
NET START WORKSTATION
@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES
Sample CONFIG.SYS (LAN-attached version, CONFIG.LAN)
DEVICE=C:\DOS\SETVER.EXE
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\LANMAN.DOS\DRIVERS\DOSUTILS\EMM386.EXE NoEMS
DOS=HIGH,UMB
FILES=30
STACKS=9,256
LASTDRIVE=Z
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\TOKENRNG\IBMTOK\IBMTOK.DOS
Sample AUTOEXEC.BAT (LAN-attached version, AUTOEXEC.LAN)
C:\DOS\SMARTDRV.EXE
@ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;C:\DOS
SET TEMP=C:\DOS
@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
NET START WORKSTATION
LOAD NETBEUI
@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES
Sample \LANMAN.DOS\LANMAN.INI
;*****************************************************************;
;** Microsoft LAN Manager **;
;** Copyright(c) Microsoft Corp., 1991 **;
;*****************************************************************;
[networks]
netservices = chknet, minses
[workstation]
wrkservices = encrypt,messenger,minipop
wrkheuristics = 1111211012112000
computername = DOSREQ8
domain = LMANDOM
othdomains =
numdgrambuf = 3
lanroot = C:\LANMAN.DOS
[netshell]
username = palt61us
[version]
lan_manager = 2.1.0
[messenger]
[services]
chknet = netprog\chknet.exe
minses = netprog\minses.exe /n
workstation = netprog\netwksta.exe
messenger = services\msrv.exe
netpopup = services\netpopup.exe
encrypt = services\encrypt.exe
minipop = services\minipop.exe
OS/2 - LAN Manager Requester
----------------------------
If you are using LAN Manager Requester and LAN Distance on an OS/2
workstation:
o Install LAN Manager Requester for OS/2
NOTE: Because LAN Distance requires OS/2 version 2.0 or higher, you must
install Microsoft LAN Manager Requester version 2.2.
When the LAN Manager Requester installation program prompts you for
your LAN adapter type, select your LAN adapter type from the list.
If your workstation does not have a LAN adapter, select ANY LAN adapter
type in the list. Do not select "No adapter". This is the easiest way to
get LAN Manager Requester set up.
o Copy your CONFIG.SYS to CONFIG.LAN. (optional)
Copy this file if you have a LAN adapter in your workstation and
you intend to use LAN Manager in both a LAN-attached environment
and in a remote environment with LAN Distance. You will use the (.LAN)
file when you are in a LAN-attached environment.
You can also copy your \LANMAN\LANMAN.INI file to \LANMAN\LANMAN.LAN
at this point. Keeping a separate copy of this for your LAN-attached
environment will give you slightly improved performance when you
are directly attached to the LAN.
o Edit your CONFIG.SYS:
1) Delete or REM the PROTMAN.OS2 device statement from your CONFIG.SYS.
REM DEVICE=C:\LANMAN\PROTMAN\DRIVERS\PROTMAN.OS2
2) Delete or REM the DEVICE= statement for your LAN adapter.
Perform this step EVEN if you have a LAN adapter in your workstation.
For example, if you selected IBM Token Ring adapter when you installed
LAN Manager Requester, delete or remove the IBMTOK.OS2 driver
statement in your CONFIG.SYS:
REM DEVICE = C:\...\IBMTOK.OS2
o Edit your STARTUP.CMD:
(Temporarily) remark out the starting of the LAN Manager Requester:
REM NET START WORKSTATION
REM NET LOGON ...
o Edit LANMAN.INI:
1) If you are using LAN Manager with Netbeui, edit your
net statement to look like:
net1 = netbios$, 0, nb30
LAN Distance cannot start unless you make this change.
2) Add/change the wrkheuristics parameter in the [workstation] section
to look like:
[workstation]
; 0 1 2 3
; 01234567890123456789012345678901234
wrkheuristics = 11111111213000111110010111200112211
If you already have a wrkheuristics parameter, the only changes that
you need to change for LAN Distance are to change the 11th, 12th,
and 13th bits (counting from 0) from a 1 to a 0.
These are the RAW data transfer protocol bits.
See the Microsoft LAN Manager Administrator's Reference for a
full description of these heuristics.
3) Edit/add the sesstimeout value in the [workstation] section as follows:
[workstation]
sesstimeout = 300
o Install the LAN Distance Remote for OS/2 and use the Basic Settings
Option to configure your initial setup.
o Edit CONFIG.SYS
Check/edit statements in your CONFIG.SYS to make sure they look like
the following. Make sure they appear in this relative order.
LIBPATH=C:\IBMCOM\DLL;C:\LANMAN\NETLIB;....
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM ; only want IBMCOM version of this
DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2 ; only want IBMCOM version of this
RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2 ; only want IBMCOM version of this
DEVICE=C:\WAL\WCLVPCM.OS2
DEVICE=C:\IBMCOM\MEMMAN.OS2
DEVICE=C:\IBMCOM\VLAN.OS2
RUN=C:\IBMCOM\VLANINIT.EXE
DEVICE=C:\IBMCOM\MACS\PDFH.OS2
DEVICE=C:\IBMCOM\MACS\MACFH.OS2
DEVICE=C:\IBMCOM\MACS\WCLCPMAC.OS2
DEVICE=C:\LANMAN\NETPROG\RDRHELP.SYS ; have to move these to here
IFS=C:\LANMAN\NETPROG\NETWKSTA.SYS /i:C:\LANMAN ; have to move these to here
DEVICE=C:\LANMAN\NETPROG\NETVDD.SYS ; have to move these to here
Note: If you install LAN Distance before you install LAN Manager Requester,
your CONFIG.SYS will look quite a bit different than this. You may
notice multiple versions of PROTMAN.OS2 and NETBEUI.OS2 being loaded.
Be sure to REM out the versions in the \LANMAN paths, and use the
versions in the \IBMCOM path.
o Copy your CONFIG.SYS to CONFIG.REM. (optional)
Copy this file if you have a LAN adapter in your workstation and
you intend to use LAN Manager in both a LAN-attached environment
and in a remote environment with LAN Distance. You will use the (.REM)
file when you are using LAN Distance in a remote environment.
If you are keeping a separate copy of \LANMAN\LANMAN.INI for your
LAN environment, you must copy \LANMAN\LANMAN.INI to \LANMAN\LANMAN.REM.
o Complete steps further below under "LAN Manager Server".
"SHUTTLING" with on an OS/2 Workstation
---------------------------------------
The Shuttle feature in the LAN Distance Remote for OS/2 does not
work with LAN Manager Requester. The steps above have enabled you
to manually "shuttle" between a LAN-attached and a remote environment.
When you are LAN-attached, simply copy your CONFIG.LAN to CONFIG.SYS
and LANMAN.LAN to LANMAN.INI (if appropriate) and restart your
workstation.
When you are in a remote environment, copy your.REM files and restart
your workstation.
Sample Files:
------------------
Sample CONFIG.SYS (LAN-attached version - CONFIG.LAN)
-----------------------------------------------------
LIBPATH=C:\LANMAN\NETLIB;C:\MUGLIB\DLL;...
REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES
DEVICE=C:\LANMAN\DRIVERS\PROTMAN\PROTMAN.OS2 /i:C:\LANMAN
DEVICE=C:\LANMAN\DRIVERS\TOKENRNG\IBMTOK\IBMTOK.OS2
DEVICE=C:\LANMAN\DRIVERS\PROTOCOL\NETBEUI\NETBEUI.OS2
DEVICE=C:\LANMAN\NETPROG\RDRHELP.SYS
IFS=C:\LANMAN\NETPROG\NETWKSTA.SYS /i:C:\LANMAN
DEVICE=C:\LANMAN\NETPROG\NETVDD.SYS
REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN 2.2a ====
Sample LANMAN.INI
-----------------
;*****************************************************************;
;** Microsoft LAN Manager **;
;** Copyright(c) Microsoft Corp., 1993 **;
;*****************************************************************;
; LAN Manager initialization file, for workstation configuration.
[networks]
; This info is read by redir at device init time. It is available to
; apps via NetBiosEnum.
; net1 = netbeui$,0
net1 = netbios$, 0, nb30
[workstation]
computername = OS2REQ
domain = LMANDOM
othdomains =
wrkheuristics = 11111111213000111110010111200112211
sesstimeout = 300
wrkservices = messenger,netpopup
wrknets = net1
[messenger]
[netshell]
refresh = 15
remote =
username = JOEUSER
[version]
lan_manager = 2.2a.0
[tcpip_node]
Hub =
HubIPAddr =
Domains =
DoUAS = yes
DoView = yes
DoLogon = yes
DoWho = no
DoSend = no
DoRepl = yes
DoUser1 = no
DoUser2 = no
DoUser3 = no
UserMailSlot1 =
UserMailSlot2 =
UserMailSlot3 =
[services]
; Correlates name of service to pathname of service program.
; The pathname must be either
; 1) an absolute path (including the drive specification)
; OR
; 2) a path relative to the LanMan root
workstation = services\wksta.exe
tcpip_node = services\node.exe
messenger = services\msrvinit.exe
netpopup = services\netpopup.exe
Sample \IBMCOM\PROTOCOL.INI (used in remote environment)
--------------------------------------------------------
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
netbeui_nif = netbeui.nif
[netbeui_nif]
DriverName = netbeui$
TI = 60000
T1 = 10000
T2 = 2000
SESSIONS = 48
NAMES = 27
NCBS = 125
NETFLAGS = 0x1000
BINDINGS = PDFH_nif
[VLAN_KERNEL]
DRIVERNAME = VLANKNL$
CFGTYPE = "LOCKED"
MODE = "LEARN_WFLOWS"
LANTYPE = "802.5"
MAXADDRESSES = 512
[PDFH_nif]
DRIVERNAME = PDFH$
NETADDRESS = "T4000012B2C35"
[COM1]
DRIVERNAME = WCLCPMC$
CFGTYPE = "LOCKED"
PCMSUPPORT = "YES"
MACTYPE = "802.5"
CONN_TYPE = "SWITCHED"
PORTNAME = "COM1"
Sample \LANMAN\PROTOCOL.INI (used in LAN-attached environment)
--------------------------------------------------------------
[PROTMAN]
DRIVERNAME = PROTMAN$
[NETBEUI_XIF]
Drivername = netbeui$
SESSIONS = 40
NCBS = 85
BINDINGS = "IBMTOK_NIF"
[IBMTOK_NIF]
; protocol.ini section for the IBM Token Ring Adapter
drivername = IBMTOK$
LAN Manager Server
------------------
Complete the following tuning steps so that the LAN Manager server
can work with the slower LAN Distance WAN connections:
o Edit the LANMAN.INI file:
1) Edit the sesstimeout value in the [workstation] section as follows:
[workstation]
sesstimeout = 300
2) Add a srvheuristics parameter (or change the current one) in
the [server] section:
[server]
; 0 1
; 01234567890123456789
srvheuristics = 11110151111211021331
If you already have a srvheuristics parameter, the only change
necessary for LAN Distance is to change bit 15 from a 0 to a 2.
This will increase the Opportunistic Lock Timeout.
See the Microsoft LAN Manager Administrator's Reference
for a full description of these heuristics.
o If you are running the NETBIOS protocol over a LAN Distance WAN connection,
edit the \LANMAN\PROTOCOL.INI file:
The NETBIOS timer values must be relaxed to handle the slower
WAN connection. Add or the change the following parameters in
the NETBEUI_XIF section:
[NETBEUI_XIF]
TI = 60000
T1 = 10000
T2 = 2000