XCLN: Using ShivaRemote with Exchange (Win 3.x/LanMan TCP/IP)

ID: Q159904

The information in this article applies to:

Microsoft Exchange Windows 3.x client, versions 4.0, 5.0

SUMMARY

A white paper on ShivaRemote is located on Microsoft TechNet and can also be found on the following World Wide Web location:

http://www.microsoft.com/exchange/support/

This article explains how to use ShivaRemote with the Microsoft Exchange Windows 3.x client, with LAN Manager version 2.2c with TCP/IP. 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, double-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.

The following article has additional information on RAS:

Q158124 XCLN: ShivaRemote with Exchange - RAS Server Considerations

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 LAN Manager has already been installed, run Setup.exe from the LAN Manager installation directory (Lanman.dos by default).

Configure LAN Manager 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 LAN Manager is installed.

Configure LAN Manager 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 Windows 3.x client.

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

Run Connectw.exe to bring up the ShivaRemote Connect window.

On the Tools menu, click Port Setup to configure the modem port.

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. If you receive any errors 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 IP address and host name of the computer running Microsoft Exchange Server. 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 Windows 3.x client (online, as a test). Type the User Name (Exchange Mailbox Name), the Password (Windows NT Domain Password), and the Domain (Windows NT Domain Name that your account is in) and verify you can be properly logged in.

If the above step allows you to properly send/receive mail, ShivaRemote and Microsoft Exchange are configured correctly.

The Microsoft Exchange client remote capabilities can now be configured (remote mail or offline folders).

To set up the Microsoft Exchange client to automatically dial while working offline:

In Control Panel Mail-Fax, select the properties for Exchange Server in the profile and on the "dial up networking" tab.

Click the Shiva connection name that was tested in step 1 under "dial using the following connection."

Type the user name, password, and domain name in the dialog box.

Start the Microsoft Exchange client offline and select either the "remote mail/connect" or the "sync this folder" check box. Shiva will dial and transmit necessary information (depending on whether off-line folders [.ost files] or .pst files are being used).

NOTE: To disconnect, either run Connect.exe again and select Disconnect or type "connect /d" from the command line.

Sample Configuration Files

Use these Config.sys, Autoexec.bat, and Protocol.ini files as models.

NOTE: In order to format this article for the Web, some line breaks in this file sample had to be changed. In the Config.sys file, the following line should be part of the line that preceded it:


   /i:C:\LANMAN.DOS

In the Autoexec.bat file, the following line should be part of the line that preceded it:


   2.2a

   Config.sys
   ----------

   device=c:\dos\himem.sys /testmem:off
   device=c:\dos\emm386.exe noems
   LASTDRIVE=Z
   DOS=HIGH,UMB
   DEVICEhigh=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
   devicehigh=c:\doscln\dialndis.exe
   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
   NET LOGON shivat *
   @REM ==== LANMAN 2.2a == DO NOT MODIFY BETWEEN THESE LINES == LANMAN
   2.2a
   ====
   set shiva=c:\exchange\shiva

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$

REFERENCES

Updated modem scripts for use with ShivaRemote can be found on Shiva's web page at www.shiva.com under "support"/modem scripts.

Additional configuration information can also be found in the Config.hlp file installed during installation of the ShivaRemote software.

For more information about specific remote options with the Microsoft Exchange client, see the following article in the Microsoft Knowledge Base:

Q139934 XCLN: The Microsoft Exchange Client and Mobile Users

For additional information on supported Shiva configurations for use with the Microsoft Exchange Server, please see the following articles in the Microsoft Knowledge Base:

Q158124 XCLN: ShivaRemote with Exchange - RAS Server Considerations

Q158095 Using ShivaRemote with Exchange (Windows 3.x/LanMan NetBEUI)

Q158077 Using ShivaRemote with Exchange (Windows 3.x/real-mode IPX)

Q158111 ShivaRemote with Exchange (WFW 3.11/WFW TCP/IP or NetBEUI)

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.

Additional query words: remote deliver now sync all folders exclnfaqold

Keywords : kbenv kbsetup kbusage XCLN
Version : WINDOWS:4.0,5.0
Platform : WINDOWS
Issue type :