Citrix WinView Application Note Novell, Inc. NetWare Connect 2.0 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 third-party products discussed within. August 9, 1995 Citrix Systems 210 University Drive Suite 700 Coral Springs, FL 33071 Phone (305) 755-0559 NetWare Connect 2.0 Overview The purpose of this application note is to describe how to integrate and use NW Connect 2.0 with WinView for Networks. This application note is not meant to replace the documentation supplied by third party manufact- urers, but instead is a summary of installation and operation notes that help an integrator combine the two products into a heterogeneous enviro- nment. NetWare Connect 2.0 is a software add-on component to a Novell NetWare 3.x or 4.x file server that provides access to a Novell Network via asynchronous connections, utilizing an intelligent multi-port serial controller in the fileserver. NetWare Connect provides two services that can be used in conjunction with WinView. When connected using Novell's included client dialer, DOSDial for DOS, your computer appears as a locally connected workst- ation on the network. When connected via a NASI terminal, your computer functions as if it had dialed into a modem directly connected to the WinView server. NASI Connection Services (NCS) NASI Connection Service (NCS) allows remote users to dial into a LAN and local users to dial out from one of the pooled communication ports. A WinView workstation is configured to connect to an NWC port for asynchr- onous dial-in access. When a user dials into the NWC server with the Remote Link Client, an NWC login authentication is required, and then a list of services (WinView servers which have a terminal attached to a port on the NWC server) is presented. When a WinView server is selected, the user is logged in, and it appears as if the user dialed into a modem that was attached directly to the WinView server. The only exception is the NWC login, and the service selector. The advanced Intelligent Console Architecture (ICA 2.0) protocol used by the Remote Link/LanLink/ IPLink Clients improves performance, because it sends only screen updates, mouse, and keyboard events over the NASI connection, as well as compressing the data that is transferred between the two. Point-To-Point Protocol Remote Node Services (PPPRNS) Point-To-Point Protocol Remote Node Service (PPPRNS) is a new feature implemented in NetWare Connect 2.0, which gives Remote Node access to the workstations dialing in. Remote Node is the ability to dial into a LAN, and be an extension of it. You can access network drives on servers on the LAN, access printers on the LAN, send E-Mail, etc. The remote PC acts as if it is at the host site, and not using any from of terminal emulation. The communication taking place on the physical LAN cable, is translated on the NWC Server, and sent over the modem to the remote workstation. In comparison, NetWare Connect 1.0 used the Novell NetWare Remote Node (NRN) communication protocol to allow remote node attachment to the LAN through the NWC 1.0 server. NWC 1.0's NRN was a proprietary protocol supported mainly by Novell, thus, users were forced to use only the Novell client software, and only the IPX transport was available. In creating and using PPPRNS in NWC 2.0, Novell used an industry standard protocol, PPP, and an industry standard PPP Link Control Protocol (LCP) extension, IPCP (Intern Protocol Control Protocol). This means, that in NWC 2.0, virtually any third-party TCP/IP with PPP stack can connect to the NWC server. The remote PC, in effect, becomes another node on the LAN and has access to all network resources. In comparing the two services/protocols provided by NWC 2.0, NCS is the easiest to implement of the two, but PPPRNS is the most versatile, providing direct IPX and TCP/IP protocol access to the LAN. Using PPPRNS, not only can WinServer servers be accessed, but any NetWare or IPX servers, as well as any TCP/IP resources, dependent on which tran- sport was installed. The Novell NWC client software, and information on each implementation, supporting the PPPRNS service are listed in the "Connection Types Supported" table. NW Connect provides DOSDial for DOS, which supports IPX and TCP/IP over PPPRNS. There are three versions of the Citrix WinView Client: Remote Link (Rlink), for asynchronous connections, LanLink, for LAN connections using IPX/SPX transport protocol, and Iplink, for connections over the TCP/IP transport protocol. Requirements Network/WinView Server: Novell Server with NW Connect 2.0 installed and operational Modems installed on the NW Connect server configured for dial in service. Citrix WinView for Networks 2.3 Citrix TCP/IP for WinView 1.0 (For TCP/IP connections) Remote Workstation: Novell NWC Client software (for LanLink or IPLink) Modem supported by the transport being used on the remote workstation. High-Speed serial port (16550AFN or equivalent) or Intelligent serial board WinView client software for the remote workstation's environment. Connection Types Supported The following table lists the different WinView client connections supported with NW Connect 2.0, the components needed, and the protocol used to communicate with the NW Connect server: A. Novell NWC DOSDial, Citrix LanLink (PPPRNS Protocol) B. Novell NWC DOSDial, Citrix IPLink (PPPRNS Protocol) C. Citrix Remote Link (NCS Protocol) Installation NetWare Server: Install NW Connect 2.0 on the NetWare server according to the Installation Guide. Please also read carefully any "readme" files or notes supplied with NW Connect 2.0. Notes: A) Under NWC Setup for PPPRNS, the NWC PPP ports, and the clients, should have their own IP network, i.e., if the network card installed in the NWC server has an IP address of 1.1.1.1, the PPP ports would be 1.1.2.x, and the IP address pool would fall under the 1.1.2.x network. B) Under NWC Setup for PPPRNS, the IPX network address should be a (network-wide) unique address, i.e., if the network card installed in the NWC server has an IPX address of 0000DADA, the PPPRNS IPX address would be 0000DADB. NOTE: IP and IPX addresses mentioned above are examples. Usage and assignment is specific to individual sites. Sample NetWare server AUTOEXEC.NCF and NetWare Connect NWCSTART.NCF files are included at the end of this document. A Transport: IPX Components: Novell NWC DOSDial, Citrix LanLink Connection: PPPRNS (IPX) WinView Remote Workstation: 1. Install both the NW Connect DOSDIAL and LanLink Client on the remote workstation according to their installation instructions. After installation is complete, verify that the system boots properly. 2. Start the NW Connect DOSDIAL client to establish an IPX and or IP connection to the NW Connect 2.0 host on the remote network. After you have exited the NWC DOSDial, change to the network drive (i.e., F:), which notifies the NWC DOS transport that a remote network connection has been established. NOTE: DO NOT proceed until this step is completed successfully. 3. Change to the drive/directory where the LanLink client was installed, and start it by running LANLINK.EXE. 4. To create an entry, select , and press . Enter a Label for the entry, and description (if needed). 5. Since LanLink will use the IPX transport, you may or may not be able to see server names in the "AppServer Name" list (press F6 )depending on whether or not you have loaded a Novell DOS redirector, NETX.EXE or the NetWare VLM's. If no redirector has been installed, you must enter the MAC address of the WinView server you wish to connect to (i.e.., 00DA004BC382). To identify the MAC address of the WinView server, from the WinView server console, run "CONFIG NETWORK | MORE ", and it will display the MAC address. 6. Fill out the rest of the screen as per the LanLink User's Guide, and save the configuration. 7. From the LanLink main menu, select "Connect," highlight the entry, and press enter. A connection should be established and a login prompt presented. Notes: 1. By default, on installation, WinView creates five workstations for each transport installed. 2. Keep in mind that if there will be connections using the same transport connecting via the physical network, they will count against the number of workstations created. For example, if you need three IPX connections for the NWC server, and you have four connecting through the physical network, you need a total of seven IPX workstations. Refer to the System Administrator's Guide for information on creating additional workstations. B Workstation: DOS Transport: TCP/IP Components: Novell NWC DOSDial, Citrix IPLink Connection: PPPRNS (TCP/IP) WinView Remote Workstation: 1. Install both the NWC DOSDial and IPLink client on the remote workstation as per their isntallatons guides. After installation is complete, verify that the system boots properly. 2. Start the NW Connect DOSDIAL client to establish an IPX and or IP connection to the NW Connect 2.0 host on the remote network. After you have exited the NWC dosdial, change to the network drive (i.e., F:), which notifies the NWC DOS transport that a remote network connection has been established. NOTE: DO NOT proceed until this step is completed successfully. 3. Change to the drive/directory where the IPLink client was installed, and start it by running IPLINK.EXE. 4. To create an entry, select , and press . Enter a Label for the entry, and description (if needed). 5. Since IPLink will work over the TCP/IP transport, if you have a functioning DNS system, or have a correct and valid HOSTS file, enter the name of the WinView sevrer you wish to connect to. If no name resolution is available, either add the name and IP address to your local HOSTS file, or enter the IP address of the WinView server you wish to connect to in the "AppServer Name" field (ex. 128.128.1.2). Refer to the NWC 2.0 user's guide on modifying the HOSTS file. 6. Fill out the rest of hte screen as per the IPLink User's Guide and save the configuration. 7. From the IPLink main menu, select "Connect," highlight the entry, and press enter. A connection should be established, and a login prompt presented. Notes: 1. By default, on installation, WinView creates five workstations for each transport installed. 2. Keep in mind that if there will be connections using the same transport connecting via the physical network, they will count against the number of workstations created. For example, if you need three TCP/IP connections for the NWC server, and you have four connecting through the physical network, you need a total of seven TCP/IP workstations. Refer to the System Administrator's Guide for information on how to create additional workstat- ions. C Transport: Serial Port (NCS) Components: Novell NWC DOSDial, Citrix Remote Link, Remote Link supported modem (16550 UART recommended) Connection: Novell NCS WinView Remote Workstation: 1. Install Remote Link client as per the Remote Link User's Guide. 2. Change to the drive/directory where the Rlink client was installed, and start it by running RLINK.EXE. 3. When installed, there are no entries in the server list. To create an entry, select , and press . Enter a Label for the entry, and a description (if needed), phone number, and login information. 4. Assign a name to the entry, and select the proper device under "Connection Type." Refer to the Remote Link User's Guide if you are using a supported intelligent serial board. 5. Change the emulation mode to "TTY." 6. Select the proper modem type, device name, baud rate, and flow control. Refer to the Remote Link User's Guide for these and other settings, as well as the advanced settings. 7. Press to save the entry. 8. To dial the WinView server, select the proper AppServer, and press enter. 9. The screen will clear and a message saying it is dialing will appear. Once the connection to the NWC server is made, it will ask for a login. Enter the user name, and password when requested. 10.Once the authentication is passed, a service selector will appear. 11.Select the WinView host to connect to by typing it's number, and pressing enter. From this point on, the connection will function as a standard WinView asynchronous connection. Refer to the Remote Link User's Guide for further information. Notes: 1. There is a server update package for NASI/NCS usage on WinView 2.3. This file can be downloaded from Citrix' BBS or CompuServe forum. The filename is NWCUPDB.EXE. This is a self-extracting archive. Install this update as per it's included instructions. 2. From the WinView console, start the workstation terminal configuration program, by running "Config Terminal." 3. If Workstation "NetWare Connect/NACS" is not listed, press ,

rofile, dd, and select "NetWare Connect/NACS ." Enter the proper user name and password for access to the NWC server's ports. 4. Highlight " NetWare Connect/NACS ", and press to create a device. Assign the new device a name. Select "ICA_NASI (REMOTE LINK)" for the workstation type. Select the proper modem type for the port attached. Configure the rest of the settings as per the WinView System Administrator's Guide. Press to save and exit. If more workstations are needed, follow the same method to create additional ones now. Troubleshooting To troubleshoot client problems first isolate which client software is not setup correctly. You can accomplish this by only loading the NW Connect client software, and then trying to look at the network before starting LanLink or IPLink. If you can not see the network, troubleshoot the NW Connect 2.0 server and client configuration as per the NWC Instal- lation Guide and Administration Guide. Additional Notes: Listed below are samples of the remote workstation and server configura- tion files that NW Connect 2.0 uses. They will differ depending in on your hardware and soft ware configurations. They are provided as examples only. A sample Server AUTOEXEC.NCF file located in the sys:system directory: file server name 312NWC IPX internal net 1234baba load conlog load SMC8000 port=300 frame=ETHERNET_802.3 name=IPXNET bind IPX to IPXNET net=A load SMC8000 port=300 name=IPNET frame=ETHERNET_II load tcpip forward=yes bind IP to IPNET address=128.128.1.220 mask=255.255.255.0 load AIODGXI port=110 mem=D0000 name=PCXI8 nwcstart load nwccon load monitor load remote "" load rspx A sample server nwcstart.ncf file located in sys:system directory: ; ; These are support modules used by NetWare Connect services. ; load NWCSS ; Load BSPXCOM for NetWare Connect Service Manager load BSPXCOM ; ; NASI Connection Service ; load sys:\system\ncs.nlm ; ; PPP Remote Node Service ; load ipxstack load ipxrtr load PPPRNS A sample remote workstation startnet.bat file located in NWClient directory: c:\nwcnet\bin\yesno.exe "Do you want to load the remote client software? (y/n)" if errorlevel 1 goto LoadNet goto LoadRem :LoadNet echo off lh C:\NWCLIENT\lsl.com /C=C:\NWCLIENT\net.cfg lh C:\NWCLIENT\nesl.com lh C:\NWCLIENT\ncomx.com lh C:\NWCLIENT\nwremote.com REM Load IPX REM @ LH C:\NWCLIENT\IPXODI.COM @ lh c:\nwclient\ipxodi.com REM Load TCPIP REM @ C:\NWCNET\BIN\TCPIP.EXE @ c:\nwcnet\bin\tcpip.exe C:\NWCLIENT\vlm.exe /C=C:\NWCLIENT\net.cfg @ SET NWLANGUAGE=ENGLISH echo on goto Exit :LoadRem REM **DO NOT DELETE** :Exit A sample remote workstation net.cfg file located in the NWClient directory: Link Support MemPool 6192 Buffers 10 1580 Link Driver NCOMX Port 3f8 Int 4 Modem Name Frame ETHERNET_802.3 Protocol TCPIP PATH SCRIPT C:\NWCNET\SCRIPT PATH PROFILE C:\NWCNET\PROFILE PATH LWP_CFG C:\NWCNET\HSTACC PATH TCP_CFG C:\NWCNET\TCP NetWare DOS Requester FIRST NETWORK DRIVE = F NETWARE PROTOCOL = NDS BIND PNW The lines below are added to your autoexec.bat file in your root directory: PATH C:\NWCLIENT;%PATH% PATH C:\NWCNET\BIN;%PATH% @CALL C:\NWCLIENT\STARTNET The line below is added to your config.sys file in your root directory: LASTDRIVE=Z