Citrix WinView Application Notes DCA RLN Server 2.0x This application note is for informational use only and Citrix makes no representations or warranties with respect to the contents or use of this document or of any of third-party products discussed within. July 27, 1994 Citrix Systems 210 University Drive Suite 700 Coral Springs, FL 33071 (305) 755-0559 FAX (305) 341-6880 Overview: --------- This application note facilitates the configuration of DCA's RLN Server 2.0x with Citrix "WinView for Networks". The RLN Server 2.0x provides remote network access to DOS clients. Remote PC's can connect to a DCA RLN Server with DCA's client software. DCA's client TSR's in conjunction with Netware's ODI drivers can form a virtual connection to the remote network known as a RLN (Remote Lan Node) connection. WinView's network client software, LANLINK, can then be used to connect the remote PC to a WinView server across the RLN connection. Disclaimer: ----------- The scenarios described in this document have been tested by Citrix. Other variations to the scenarios described in this document may work, however they have not specifically been tested by Citrix. In order to recreate the configurations, you should use the specified revision levels of all software products described in this document and stay within the bounds of the features and functions described in this document. Please note that this application note is a living document and will be modified as new information and versions of the software described herein become available. Make sure you have the latest version of this document before you begin. The latest version is always available in the Citrix Forum on Compuserve. Requirements: ------------- DCA RLN Server software that is required: DCA Remote LAN Node Server v2.0.1 (2 disks) DCA RLN Client Maker v2.0.1 (2 disks) * DCA RLN Manager v2.0.1 (2 disks) * DCA's RLN Manager lets you setup and configure RLN Servers on your TCP/IP network from a TCP/IP DOS node running Windows. The software has not been tested under WinView. Please note that the RLN Manager software is NOT a required part of RLN Server. All necessary configuration and management can be performed from the RLN Server console. DCA RLN Server hardware that is required: Please consult the DCA RLN Server's Administator's Guide Chapter 3 for PC requirements for DCA RLN Server 2.0. Setup: ------ 1) It is suggested that you follow the individual steps in the Administrator's Guide to install the RLN Server software: Chapter 3 - Installing the RLN Server Hardware Chapter 4 - Installing the RLN Server Software 2) The Shiva Administration software will need to be installed on a DOS machine with Windows 3.1 (Enhanced Mode) that is on the same network of the Shiva LanRover unit. This software will be used to configure the various Shiva units. The administration software will NOT work under WinView 2.21. 3) Configure the Shiva Lan Rover and its ports with the Shiva Administrator software. Refer to the following chapters in the Shiva LanRover Administrator's Guide for the PC: Chapter 3 - "Working with Shiva Net Manager" Chapter 4 - "Configuring General Settings" Chapter 5 - "Configuring Ports" Chapter 10 - "Configuring Netware IPX" Chapter 11 - "Security" Chapter 15 - "User Lists" 4) The Shiva Remote Dial-In software should be installed onto every remote client that will be dialing into the Shiva LanRover to complete an RLN connection. The installation can be done from DOS or Windows. The SETUP program will prompt you for the following client information: COM port to which modem is connected Modem type Protocols to be used (IPX, IP, or Netbios) 5) Apply the updates from Shiva to each client. The following are the new files and sizes that will be needed to successfully run LanLink across an IPX RLN connection: CONNECT EXE 06/29/94 249,246 CONNECTW EXE 06/29/94 110,160 DIAL 386 06/29/94 14,781 DIALODI EXE 07/12/94 35,528 MODEMS INI 06/17/94 31,740 SREMOTE TXT 06/29/94 14,536 WFW311 WRI 06/29/94 32,000 6) Each client needs to be configured to match its hardware. This section covers configuring an IPX RLN connection via Shiva's DOS based CONNECT.EXE. Though it is possible to accomplish the same job with the CONNECTW.EXE for Windows. CONNECT.EXE needs to be run to configure the client: CONNECT Dial-In Name is any valid userid configured by Shiva NetManager and downloaded to the LanRover unit Phone Number ALT-S, P (pulls down System Menu and selects Port Setup) Port should be COM port modem is connected to Modem should be modem connected to client OK ALT-F, S (pulls down File Menu and selects Save) Enter a name to save as (i.e. filename) OK ALT-X (exits CONNECT) 7) LanLink needs to be installed onto every potential RLN client. Insert the LanLink client disk into the RLN client, change the current drive and type INSTALL. Operation: ---------- 1) This section covers making an IPX RLN connection from DOS. Shiva also supplies software to accomplish the same task from Windows. To make a connection across the Shiva RLN, go to the Shiva directory on your DOS client: CD\SHIVA Load Netware's LSL.COM and Shiva's DIALODI.COM LSL DIALODI Make connection via Shiva's CONNECT.EXE CONNECT @filename (filename is name created in Installation Step 6.) Load Novell's IPXODI.COM and NETX.EXE IPXODI NETX The above commands can be put into a batch file to simplify the job. Also note that Netware's VLM.EXE can be used in place of NETX.EXE. 2) After a successful connection has been made, LanLink can be run from the client's local drive. When running LanLink over an RLN connection it is important to use the following configuration: AppServer List (add or edit an entry) AppServer Name. . [(press enter for list) ] Connection Type . [IPX ] Error Correction. (X) Yes ( ) No Compression . . . (X) Yes ( ) No Under F7=Advanced Settings Transmit ACK Timeout . . . . . . . [60 ] Transmit NCK Timeout . . . . . . . [45 ] Receive Partial Packet Timeout . . [15 ] Save these settings (F4 = Save and Exit) and return to LanLink's main menu. 3) From the LanLink main menu, Choose "Connect to AppServer", highlight the entry edited in step 2, and press enter. A WinView Login prompt should appear momentarily. Notes: ------ The DCA RLN Server is a convenient way to access remote LAN's. However, RLN's are limited to the speed of modems which are relatively slow as compared to a network. Running large programs across the RLN can thus be very slow. It is suggested that you move any commonly run executables to the remote client if there is room. LanLink especially should be installed on the client and NOT run from a remote server. LanLink greatly improves the performance of the RLN because the execution of the applications is performed on the WinView server only requiring screen updates and keystrokes to be sent across the wire. The majority of the network traffic will be between the WinView server and the Netware server which should be on the same local network. Problems: --------- There are no known problems when using DCA RLN Server in conjunction with a WinView server at this time.