Citrix WinView Application Notes Addendum to Novell NetWare Connect Application Note Revision 2 This application note is for informational use only and Citrix Systems makes no representations or warranties with respect to the contents or use of this document or of any third-party products discussed within. January 18, 1995 Citrix Systems 210 University Drive Suite 700 Coral Springs, FL 33071 (305)755-0559 Support FAX: (305)341-8424 Overview NCDOC2.DOC should be reviewed before reading this addendum further. Since NCDOC2.DOC was written WinView 2.3 and the third level of updates for WinView 2.2x have been released. With the release of WinView 2.3 and the third set of updates for WinView 2.2x, the following changes have been made in the way WinView interoperates with Netware Connect: * QNACS.ZIP is no longer required and is no longer available. The changes made to QNACS.EXE have been incorporated into the third level updates. * The Netware Asynchronous Service Selector (modem pooling) is now supported. Prior to WinView 2.3 or the third level updates for WinView 2.2x, NASI ports were permanently acquired for dial-in. * The second level updates (W220?2.ZIP) are no longer available on CompuServe. They have been replaced with the third level updates (W220?3.ZIP) * The third level updates should be applied to both WinView 2.20 (internal revision 2.182) and WinView 2.21 (internal revision 2.208). The third level updates should not be applied to WinView 2.3 (internal revision 2.325) as any changes that the updates provided are included in WinView 2.3 The only configuration and operational changes from NCDOC2.DOC concern the new modem pooling ability. This will be covered in the following sections. Modem Pooling The modems managed by Netware Connect can be dynamically shared for various tasks on the Netware LAN. Ports defined for modem pooling all share a common group name with which software on the network may request free ports from within the group. Prior to WinView 2.3 and the third level updates for WinView 2.2x, WinView aquired a Netware Connect port using the Specific Name of the Netware Connect port for RLINK dial-in terminals. Using this method, WinView remains in control of the port for as long as WinView is up and running (and the terminal is defined); preventing the port from being used for other purposes. This method was documented in NCDOC2.DOC on page 13 under "Configuring NCS Ports". With the third level updates applied, WinView still configures workstations via NASI, but uses the Netware Connect Group Name instead of the Specific (port) Name. Netware Connect maintains a list of all host services which have configured devices under the modem pool group. When a user dials in with RLINK, Netware Connect answers the modem and queries the user as to which host they wish to connect to, then passes control to the host server. This method not only allows a group of ports to be used by multiple host servers, but they also may be used for dial-out when not in use (if configured as such). Configuring Netware Connect for Modem Pooling 1. On the Netware Connect fileserver, type "load NWCCON" to start the Netware Connect configuration program. Configure a new group on Netware Connect. The group should contain all the ports you wish to be used for modem pooling. All of these ports must have the same modem (manufaturer and model) attached to them. "DIALIN" is the group name we will use for later examples. 2. Set the ports and/or group for dial-in/dial-out or just dial-in. 3. Configure the service NCS. a) Add the group name that you created (for example - DIALIN) to the "General Name List" b) Add the group to the "Dial-In Group" as in figure #1 below Figure #1 Configuring WinView for Modem Pooling 1. Run "QUERY NACS" from an OS/2 prompt to view NASI devices. You should see something like this displayed: PORT NAME GROUP SERVER PORT STATUS nwc01 any_port nwc2 1 idle nwc02 any_port nwc2 2 idle nwc2____dialin modmpool nwc2 0 idle Note the "PORT NAME" of the last entry in this QUERY NACS display. This is a representation of all the ports in the NCS dial-in group. In this example it is "nwc2____dialin". This name is derived from the name of the Netware Connect fileserver (NWC2) concatenated with underscore characters and the word "dialin". Enough underscore characters are added to make a total of fourteen characters. The last part of the port name will always be "dialin", regardless of the actual name of your dial-in group. It is purely coincidence that the group name used in these examples is the same as the last part of this port name. 2) Choose "CONFIGURE WORKSTATIONS" from the WinView program selector or type "CONFIG TERM" from an OS/2 prompt. You will be presented with a screen much like Figure #1 on page 11 of NCDOC2.DOC. 3) Press F10 then "P" to pull down the "Profile" menu. 4) Press "A" to select "Add subsystem." Your screen will look like Figure #2 on page 13 of NCDOC2.DOC. 5) Choose "NetWare Connect/NACS" from the "Add a Workstation Subsystem" menu. 6) You will then be prompted for a UserID and password that is valid on the default NetWare Connect server as in Figure #3 on page 14 of NCDOC2.DOC. This UserID and password is used for all WinView connections. If the UserID or password is changed on the Netware Connect server in the future then it must be changed here also. You can use the Edit function on the pull down menu to change the username and password fields at a later time if necessary.The username "GUEST" with no password is sufficient in order to make use of Netware Connect ports. 7) With the new Netware Connect/NACS subsystem highlighted, press "P" to pull down the "Profile" menu, then "N" for "New." 8) At this point, refer to the "WinView System Administrator's Guide" for information on configuring new terminals. (NOTE: You can configure as many workstations as you want on as many WinView servers as you want. Netware Connect will pass useage off to the first free available workstation it sees from the WinView server chosen by the user.) After you specify a workstation name, the "Choose a Device Name" popup will be displayed. You should see the same port name originally displayed in QUERY NACS. In our examples it's "nwc2____dialin". Choose this as your workstation device name. Make sure that you configure the "workstation type" as "*ICA_NASI (REMOTE LINK)", NOT "*ICA (REMOTE LINK/LANLINK)". The modem type will depend on the actual modems connected to the Netware Connect ports that are configured under the Dial-In Group. You can repeat the above procedure for as many ports that are configured in the Netware Connect dial-in group. At the time of this writing, WinView does not support Netware Connect's "Modem Independence" feature. This means that the modems configured under the Dial-In Group must be the same type (manufacturer and model.) WinView also does not support the dialback feature at this time. Remote Link Client Configuration IMPORTANT: You must configure the "Emulation Mode" in Rlink as TTY, NOT ICA. This is because when Rlink dials into a port on Netware Connect that is configured for modem pooling, Netware Connect will prompt the user to login. This login prompt and the subsequent "Service Selector" menu will not be correctly displayed if Rlink is setup for ICA. Other than the "Emulation Mode" setting, Rlink should be configured normally. Consult the "Remote Link User's Guide" for more information. Additional Notes When Rlink makes a connection with the Netware Connect server, the user will be required to login to the Netware Connect server. They may use any valid user ID and password on the Netware Connect fileserver (NOT a valid user ID for WinView.) The "Service Selector" will then be displayed. The "Service Selector" is a numbered menu containing a list of host servers making use of Netware Connect's modem pooling. Select a WinView host by entering in the number corresponding to the WinView host that you wish to connect to and press ENTER. Control will then be passed to the WinView host. WinView will sense an RLINK terminal attempting to connect and automatically switch to ICA emulation. A WinView login prompt will then be displayed and the user can log into WinView normally. 5