Article ID: 157740 - Last Review: October 28, 2006 - Revision: 5.1 XCLN: Using ShivaRemote w/ Exchange (MS-DOS/LanMan TCP/IP)This article was previously published under Q157740 On This PageSUMMARY A white paper on ShivaRemote is located on Microsoft
TechNet. This article shows you how to use ShivaRemote 3.59 with the Microsoft
Exchange MS-DOS client and LAN Manager version 2.2c with TCP/IP. Note that because the Microsoft Exchange MS-DOS client does not provide remote functionality, you have to run Connect.exe first to establish the connection before starting Microsoft Exchange Server or accessing network resources. Conventional memory must be optimized in order for the configuration in this article to work (with LanMan TCP). This configuration will not work if Doublespace/Drvspace is implemented, because of the additional conventional memory requirements for the compression drivers. Use the Config.sys, Autoexec.bat, and Protcol.ini files shown at the end of this article as models. MORE INFORMATIONServer ConsiderationsConfigure the Remote Access Server (either Windows NT or a Shiva LanRover) to allow remote clients to request a predetermined IP address. To use this option in Windows NT:
Client ConfigurationInstall LAN Manager version 2.2c software on the client computer. This is located on the Windows NT 3.51 Server compact disc in the Clients\Lanman\Disks\Disk1\Setup directory.NOTE: If Lanman has already been installed, run Setup.exe from the LanMan installation directory (Lanman.dos by default).
Updated modem scripts for use with ShivaRemote can be found on Shiva's web page at www.shiva.com (http://support.microsoft.com/?scid=www.shiva.com) Additional configuration information can also be found in the Config.hlp file installed during installation of the ShivaRemote software. Sample Configuration FilesNOTE: In order to format these samples for the Web, some line breaks had to be changed. In the Config.sys example, the following line should be part of the line that preceded it (this occurs twice):/i:C:\LANMAN.DOS 2.2a
Config.sys
----------
device=c:\dos\himem.sys /testmem:off
device=c:\dos\emm386.exe noems
devicehigh=c:\win95\command\drvspace.sys /move
LASTDRIVE=Z
DOS=HIGH,UMB
DEVICEhigh=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
devicehigh=c:\doscln\dialndis.exe
rem DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\DEPCA\DEPCA.DOS
DEVICEhigh=C:\LANMAN.DOS\DRIVERS\PROTOCOL\tcpip\tcpdrv.dos
/i:C:\LANMAN.DOS
DEVICEhigh=C:\LANMAN.DOS\DRIVERS\PROTOCOL\tcpip\nemm.dos
Autoexec.bat
------------
@REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN
2.2a
====
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
C:\LANMAN.DOS\DRIVERS\PROTOCOL\tcpip\umb.com
NET START WORKSTATION
LOAD TCPIP
SOCKETS
rem NET LOGON shivat *
@REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN
2.2a
====
set EXCHANGE=C:\DOSCLN
set RPC_BINDING_ORDER=ncalrpc,ncacn_np,ncacn_spx,ncacn_ip_tcp,netbios
Protocol.ini
------------
[PROTMAN]
DRIVERNAME = PROTMAN$
DYNAMIC = YES
PRIORITY = NETBEUI
[TCPIP_XIF]
DRIVERNAME = TCPIP$
IPADDRESS0 = 200 200 200 201
SUBNETMASK0 = 255 255 255 0
DEFAULTGATEWAY0 =
NBSESSIONS = 6
; the following two parameters added after documentation was completed
TCPSEGMENTSIZE = 1450
TCPWINDOWSIZE = 1450
LOAD = tcptsr[c],tinyrfc[c],emsbfr[cr]
UNLOAD = "unloadt /notsr[dc]"
; BINDINGS = "DEPCA_NIF"
BINDINGS = SDIALIN$
NETFILES = C:\LANMAN.DOS\ETC
DISABLEDHCP = 1
LANABASE = 0
[SDIALIN$]
DRIVERNAME=SDIALIN$
[DEPCA_NIF]
; protocol.ini section for the DEC EtherWORKS (MC, LC, Turbo & DEPCA)
Adapters
DriverName = DEPCA$
MaxMulticast = 12
MaxTransmits = 32
AdapterName = DE200
RamAddress = 0xD000
Interrupt = 3
; use Interupt = 5 for turbo board
| Article Translations
|

Back to the top
