Article ID: 157740
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange MS-DOS client 5.0
- Microsoft Exchange Client 4.0
This article was previously published under Q157740
SUMMARY
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 INFORMATION
Server Considerations
Configure 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:
- In Control Panel, click the Network icon.
- Click RAS, click Network, and click Server Settings.
- Click TCP, and select the "Allow remote clients to request a predetermined IP address" check box.
Client Configuration
Install 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).
- Configure Lanman with the following options:
- TCP/IP (only) bound to the network card driver
- A static IP address, subnet mask, and default gateway
- DHCP disabled
- Manually add entries for the Microsoft Exchange Server computer name and IP address in the HOSTS file. This file is located in the <drive>:\Lanman.dos\Etc directory, where <drive> is the letter of the local hard disk drive where LanMan is installed.
- Configure Lanman with the following options:
- Username and HostName in the Advanced dialog box
- Windows Sockets enabled in the Advanced dialog box
- Computername, Username, and Domain in the Workstation Settings dialog box
- Install the Microsoft Exchange client for MS-DOS. By default, the installation will install the ShivaRemote files in the same directory that the Microsoft Exchange client for MS-DOS is installed in.
- In the Config.sys file, manually add the following line:
DEVICE=C:\EXCHANGE\DIALNDIS.EXE(after DEVICE=...\PROTMAN.DOS /i:C:\LANMAN.DOS)
- In the Config.sys file, remark out or remove the line that loads the network card driver.
In the \Lanman.Dos\Protocol.ini file, manually edit the following:
[TCPIP_XIF] ;BINDINGS = "LAN Card Driver" Remark out this line BINDINGS = SDIALIN$ Add this line [SDIALIN$] Add this line DriverName = SDIALIN$ Add this line- Restart the computer and press F5 when the "Starting MS-DOS" text message is displayed. This will bypass the Config.sys and Autoexec.bat files if you are using MS-DOS 6.xx.
- Run Connect.exe from the Microsoft Exchange client installation directory to bring up the ShivaRemote Connect window.
- On the Tools menu, click Port Setup to configure the modem port. (You may receive an Out of Memory message if you attempt to select a port/modem without first booting with an F5.)
- Click the Options button to select the IP protocol and type the static IP address of the client computer. For more information on creating and saving a connection file, refer to the ShivaRemote Online Guide.
- Save the new connection information and quit the Connect.exe utility.
- Restart the computer again. If you receive any error messages during startup, resolve these before continuing.
- Open the connection file you want and click the Connect button. After the connection has been established, quit the Connect program. You should see the message regarding the static IP address. Make sure this is the same IP address which is statically assigned to the client computer.
- Next, attempt to PING the Microsoft Exchange server computer's IP address and host name. The PING.EXE utility is located in the \LANMAN.DOS\NETPROG directory. If PINGing the host name fails, but PINGing the IP address works, the HOSTS file must be modified (see Step 2 above). This step is necessary for the Microsoft Exchange client to connect to the server.
- Start the Microsoft Exchange client.
NOTE: To disconnect, either run Connect.exe again and select Disconnect or type connect /d from the command line.
Updated modem scripts for use with ShivaRemote can be found on Shiva's web page at www.shiva.com
Additional configuration information can also be found in the Config.hlp file installed during installation of the ShivaRemote software.
Sample Configuration Files
NOTE: 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
In the Autoexec.bat example, the following line should be part of the line that preceded it:
2.2a
Use these Config.sys, Autoexec.bat, and Protcol.ini files as models.
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
The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Microsoft in no way guarantees the accuracy of this third-party contact information.
Keywords: kbenv kbsetup kbusage KB157740
