 
 
 
 
 
 
 
 
 
				Citrix 
				WinView 
				Application Notes 
 
				Revision 2  
 
 
Novell NetWare Connect 
 
 
 
 
 
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. 
 
 
 
 
 
 
 
June 23, 1994 
 
 
 
Citrix Systems 
210 University Drive 
Suite 700 
Coral Springs, FL 33071 
(305)755-0559 
FAX: (305)341-6880 


Overview 
 
This application note discusses the use of Novell NetWare Connect with a Citrix 
WinView Application Server. The intended audience for this document is an engineer 
who has had hands-on experience with the WinView, NetWare, and NetWare Connect 
products.   
 
The examples described in this document have been tested by Citrix. There are no 
known issues using NetWare Connect with WinView.  Any variations to the examples 
described may work; however, they have not specifically been tested by Citrix.  You 
should use the specified revision levels of all software products described and stay 
within the limits of the product specifications. 
 
Prior to using the Citrix Application Server with Novell Netware Connect, it is important 
to verify that Netware Connect is installed and working properly on the network.  
Consult the "Netware Connect Administrator's Guide," as it has a good troubleshooting 
section.  For more information on troubleshooting Netware Connect and WinView, 
review the "Diagnosing Problems" section of this application note. 
 
This application note 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.  It is always available in the Citrix Forum on CompuServe. 
 
NetWare Connect is a server-based solution for remote computing.  NetWare Connect 
provides two services that can be used in conjunction with WinView: 
 
* NASI Connection Service (NCS) 
NASI Connection Service (NCS) allows remote users to dial into a LAN 
and allows users on the LAN to dial out from one of the pooled 
communication ports.  WinView can acquire the NCS ports for 
REMOTE LINK asynchronous dial-in access.  The advanced Intelligent 
Console Architecture (ICA) protocol used by RLINK improves 
performance because it only sends screen updates, mouse and 
keyboard events over the NASI connection. 
 
* Remote Node Services (RNS) 
 
Remote Node Service (RNS) supports remote PCs that dial in using the 
NetWare Remote Node (NRN) software provided with NetWare 
Connect.  The remote PC, in effect, becomes another node on the LAN 
and has access to all network resources.  The WinView LAN client 
program, LANLINK, is used on the remote PC to connect to a WinView 
Application Server located on the LAN. The advanced ICA protocol 
used by LANLINK improves performance of NRN because LANLINK 
only sends screen updates, mouse and keyboard events over the RNS 
connection. 
Requirements 
 
To use NetWare Connect with a WinView Application Server, you will need to satisfy 
the following hardware and software requirements: 
 
 
		NetWare Connect Communication Server 
		 
Hardware  (as specified in the NetWare Connect Administrator's Guide) 
 
*	386 minimum (Compaq Deskpro 386/20 with 10 meg RAM Tested) 
*	Intelligent multiport asynchronous card (DigiBoard PC8i Tested) 
*	For details of memory requirements, see the "NetWare Connect 
Administrators Guide." 
 
Software  (as specified in the NetWare Connect Administrators Guide) 
 
*	NetWare Connect, version 1.0 server software 
*	NWC001.EXE and  NWC002.EXE  from CompuServe in the Novell 
Netwire section (NOVLIB) 
*	NWCMOD.EXE  from CompuServe in the Novell Netwire section 
(contains new and updated modem initialization strings) 
 
 
	WinView Application Server 
 
Hardware 
 
*	486 or higher recommended (386-25 CPU Minimum) 
*	48 MB of RAM to support 10 concurrent Windows sessions (8 MB 
RAM for the OS, plus 4 MB RAM for each Windows session.) 
*	WinView supported Network Interface Card (NIC.)  See the 
WinView compatibility guide for details. 
 
Software 
 
*	WinView 2.21 or WinView 2.20 with the W220?2.ZIP updates from 
CompuServe in the Citrix "WinView 2.2 fixes" section (Library 2.)  
(Note:  There is no file named W220?2.ZIP.  The "?" character is a 
wildcard representing the nine update files that update WinView 
2.20 to WinView 2.21 functionality.)  Also QNACS.ZIP should be 
downloaded from this same library to update QNACS.EXE on the 
WinView server. 


	Remote Node Client  (NRN) 
 
Hardware 
 
*	286 CPU minimum 
*	2 MB of RAM for best performance, (minimum 640KB) 
*	Communications port  (a 16550 UART is highly recommended) 
*	NetWare Connect supported Modem See Netware Connect 
Supported List (14.4 KBaud recommended) 
 
Software 
 
*	DOS 3.3 or higher 
*	NetWare Connect remote client software; NRN.COM (2-11-94, 
33865 bytes)  DIALCON.EXE (3-2-94, 202079 bytes) 
*	NetWare Connect remote client patches from NWC001.EXE (6-13-
94, 475389 bytes) and NWC002.EXE (6-13-94, 251531.) 
*	DOSUP9.EXE  [from NOVLIB, the NetWire Forum on CompuServe, 
contains latest NetWare requester drivers, IPXODI.COM (10-7-93, 
30247 bytes), NETX.EXE (11-17-93, 78654 bytes) and LSL.COM 9-
10-93, 17805 bytes.) 
*	W220L2.ZIP from the Citrix CompuServe "WinView 2.2 fixes" 
section.  This contains the latest LANLINK client software pieces 
from WinView 2.21 (LANLINK.EXE, Release 2.21 Internal Date Mar 
17, 1994, 416120 bytes.) 
 
	NASI Client  (NCS) 
 
Hardware 
 
*	286 CPU Minimum 
*	2 MB of RAM recommended (minimum 640KB) 
*	Communications port  (16550 UART recommended) 
*	WinView supported Modem  See Compatibility Guide(14.4 K Baud 
recommended) 
  
Software 
 
*	DOS 3.3 or higher 
*	W220R2.ZIP from the Citrix CompuServe "WinView 2.2 fixes" 
section.  This contains the latest REMOTE LINK client software 
pieces from WinView 2.21 (RLINK.EXE, Release 2.21 Internal Date: 
Mar 17,1994, 415868 bytes.) 
Hardware Requirements: 
 
Many factors need to be considered when deciding what hardware is needed to run 
NetWare Connect and WinView.  The number of concurrent users, the application mix 
(Windows vs. DOS),  the client hardware (such as 16550, 16450, or 8250 UARTs), 
and the amount of memory in the WinView server and client all have an effect on 
performance.   Here are some guidelines to achieve optimal performance at minimal 
cost: 
  
*	Dedicated Communications server 
 
Read the NetWare Connect 1.0 Administration Guide section on "Choosing 
between a Dedicated and Non-dedicated Server."  It states that if you 
anticipate  heavy communication activity, then you're better off with a 
dedicated Communications server.  This is what we suggest.  Note that the 
8-port and 32-port NetWare Connect is bundled with "NetWare Runtime." 
the dedicated communication software.  The 2-port NetWare Connect is not 
bundled with "NetWare Runtime" and thus can only be used as a non-
dedicated communication server.  
 
*	Intelligent Multiport Asynchronous Adapter 
 
Citrix highly recommends using an intelligent  multiport asynchronous 
adapter.  Using a non-intelligent adapter will cause a huge drop in system 
performance.  The tests described in this application note used a DigiBoard 
PC8i multiport adapter. 
 
 
*	WinView Application Server Memory 
 
The maximum number of concurrent users supported on a single WinView 
application server is determined by the hardware configuration of the 
WinView application server.  Memory is the most critical resource for the 
WinView server in determining the number of users.  Use the following 
guideline: 8MB base memory plus 4MB for each Windows user/session, 
2MB for each DOS user/session.  Thus, a 24MB EISA system will support 4 
concurrent windows users.  For WinView to recognize more than 16MB of 
RAM, you will need either a EISA or MCA based system with a 32-bit disk 
controller.  Also, you should increase the CPU performance as the user 
count goes up. The following table shows recommended hardware 
configurations for your WinView server, organized by Windows user count: 


USERS	MEMORY	CPU/MHz	BUS	NIC 
 
4		24MB		486-25		EISA	16 bit 
6		32MB		486-33		EISA	32 bit EISA 
8		40MB		486-33		EISA	32 bit EISA bus mastering 
10		48MB		486-66		EISA	32 bit EISA bus mastering 
 
 
NOTE: The above user count recommendations are based on the 
assumption that each user will run one Windows session with 4 MB RAM 
allocated to that session.  If the users are running applications that require 
more than 4 MB of RAM per session, then the memory requirements per 
user will go up.  You may also need to increase the CPU power 
accordingly. 
 
*	Client RAM 
 
The client machine should contain a minimum of 2MB of RAM and use 
HIMEM.SYS or compatible memory manager to provide extended memory 
(XMS) support. XMS memory is used to cache Windows graphics 
information and improves performance.  If there is not enough memory for 
RAM caching, the graphics information will be cached to disk. This will 
reduce graphics performance.	 
	 
*	Client UART 
The serial adapter used in the client should use a 16550 Universal  
Asynchronous Receiver Transmitter (UART) for best performance. This 
device can operate at a higher baud rate than earlier devices, such as the 
16450 or 8250, and is required for baud rates greater than 9600. 
	  
*	The Network Interface Card  (NIC) 
 
The Network Interface Card (NIC) can affect system performance.  For 
systems that will support a large number of users, you should use a high 
performance bus master NIC in your WinView server and the NetWare 
Connect server.   
 
 
 
Special Software Notes: 
 
It is important to note that there are multiple revisions of WinView and NetWare 
Connect.  If you have WinView 2.20 or NetWare Connect 1.0.21, you may experience 
some problems.  To address these issues you need to get patches and updates from 
Novell and Citrix respectively.  These patches and updates functionally upgrade your 
products to their latest  levels.  
 
 
	WinView 2.21 (Internal Revision 2.208) 
 
*	Supports both the NASI Connection (NCS) and the Remote Node 
(NRN) Services of NetWare Connect. 
 
*	Supports the NASI Connection service of NACS.  
 
 
	WinView 2.20 (Internal Revision 2.182) 
 
*	Supports both the NASI Connection (NCS) and the Remote Node 
(NRN) Services of NetWare Connect if the all of the Citrix W220?2.ZIP 
updates are applied to the WinView Application Server.  Also, 
W220R2.ZIP and W220L2.ZIP must be downloaded and applied to all 
the remote node (LANLINK.EXE) and NASI  (RLINK.EXE) clients. 
 
Note:  The WinView update files are listed below and must be applied at 
the same time.  They can be downloaded from the Citrix Forum on 
CompuServe. 
 
WinView Server Updates  
W220A2.ZIP      Readme Updates 
W220B2.ZIP      Base Updates 
W220K2.ZIP      Kernel Updates 
W220D2.ZIP      Device Driver Updates 
W220U2.ZIP      Utilities Updates 
W220W2.ZIP     Windows Updates 
W220N2.ZIP      Netware Updates 
 
WinView Client updates 
 
W220L2.ZIP      Lanlink 
W220R2.ZIP     Remote Link 


NetWare Connect, version 1.0.34 and above 
 
*	Supports the NASI Connection Service (NCS) and the Remote Node 
Service (RNS) of NetWare Connect with WinView.  There are no known 
updates required at the time of this writing. 
 
	NetWare Connect, version 1.0.33 and below 
 
*	Supports the Remote Node Service (RNS) and the NASI Connection 
Service (NCS) of NetWare Connect with WinView if the Novell 
NWC001.EXE, NWC002.EXE patches are applied to the NetWare 
Connect server and remote node.  These files supersede the 
PTF440.EXE and PTF442.EXE patches.  You will still need to apply 
NWC001.EXE and NWC002.EXE even if the PTF44x updates were 
applied earlier. 
 
	NetWare Asynchronous Communications Services (NACS) 
 
*	This product supports the NASI Connection service only.  It does not 
have a remote node service.  The NASI service is configured similarly to 
the NCS of NetWare Connect. 
 
 
	DOSUP9.EXE, NWC001.EXE, NWC002.EXE, and NWCMOD.EXE 
 
*	These self extracting Novell modules can be downloaded from Novell's 
NOVLIB forum on CompuServe.  DOSUP9.EXE contains updated 
versions of NETX.EXE, LSL.COM, and IPXODI.COM.  NWC001.EXE 
and NWC002.EXE are updates to the NetWare Connect server and 
client software.  NWCMOD.EXE contains the latest modem scripts. 
 
Installation 
 
The installation for WinView and NetWare Connect is complicated by the fact that 
special patches and updates are needed.  This issue is being addressed and will be 
eliminated once the patches and updates are rolled into future revisions.  
		 
	For  NASI Connection Service (NCS)  and  Remote Node Service (RNS) 
	 
1)	Follow the normal procedures to install NetWare Connect and 
WinView.  Where are you installing? 
 
2)	Install NWC001.EXE and NWC002.EXE. Note that these patch 
files contain both SERVER and CLIENT FILES.   
 
3)	For WinView 2.20 only, download all of the WinView W220?2.ZIP 
updates along with QNACS.ZIP from the Citrix CompuServe forum 
(Library 2) and install these on the WinView server.   
 
4)	For WinView 2.20 only, install the W220L2.ZIP and/or 
W220R2.ZIP updates on the client. (LANLINK.EXE for NRN, 
RLINK.EXE for NASI).  
 
5)	For WinView 2.21 download QNACS.ZIP from the Citrix 
CompuServe forum (Library 2) and install this on the WinView 
server. 
 
	 
Configuration Notes 
 
To achieve optimal performance, it is important to configure WinView and NetWare 
Connect properly.  Some configuration guidelines are: 
 
Configuring the NetWare Connect Communications Server 
 
1)	The underlying NetWare Connect component is the Remote Node 
Service (RNS).  RNS runs on the server providing connectivity for 
NRN users.  Therefore, this service must be configured in order to 
establish an NRN connection.  By running the NWCCON.NLM on 
NetWare Connect, you can configure the RNS service. 
 
2)	NOTE: It is imperative that the user download Novell's 
NWC001.EXE and NWC002.EXE, which are available on 
CompuServe.  There are patches contained in these files which will 
greatly enhance performance and stability when using NRN.  These 
files contain both NetWare Connect Server and NetWare 
Remote Node (NRN) modules.  It's important that both the 
Server and Remote Node (client) are updated. 
 
3)	If you are using NLICLEAR.NLM on the NetWare Connect server, 
unload it. You should remove this NLM from the AUTOEXEC.NCF 
file if you are loading it there.  NLICLEAR will remove any not-
logged-in connections from the NetWare Connect server.  WinView 
maintains a not-logged-in connection to pass data through without 
actually logging directly into the NetWare Connect server. 
 
4)	From the NetWare server console prompt, type LOAD INSTALL. 
 
a)	For For Netware version 3.12, choose "Edit the 
STARTUP.NCF file," and add the following statements: 
 
	SET MINIMUM PACKET RECEIVE BUFFERS=500 
	SET MAXIMUM PACKET RECEIVE BUFFERS=2000 
 
b)	For Netware version 3.11, choose "Edit the STARTUP.NCF 
file" and add the following statement: 
 
	SET MINIMUM PACKET RECEIVE BUFFERS=500 
 
	Save the STARTUP.NCF and choose "Edit the 
AUTOEXEC.NCF" file.  Add the following statement to 
AUTOEXEC.NCF: 
 
	SET MAXIMUM PACKET RECEIVE BUFFERS=2000 
 
After these changes have been made and saved, DOWN the server, 
and bring it back up. 


Configuring the NRN Client Software 
 
The NRN software setup is fairly simple.  Run LSL.COM, NRN.COM, 
and DIALCON.EXE to establish a connection to the NetWare Connect 
server.  Exit the DIALCON program and run IPXODI.COM and 
NETX.EXE.  You should now be attached and be able to login to a 
Netware file server 
 
Configuring the WinView server for Remote Node Services 
 
Once a WinView server has been installed, it should already be 
configured for LANLINK connections via IPX/SPX (IPX preferred).  
Confirm this by choosing "CONFIGURE WORKSTATIONS" from the 
WinView program selector or type "CONFIG TERM" from an OS/2 
prompt.  There should be two LANLINK subsystems, one IPX the other 
SPX, with terminals configured below each subsystem resembling 
Figure #1 below: 
 
Figure #1 - Configure Workstations Screen 
 
 
If you do not have Lanlink virtual terminals created as in the example in 
Figure #1, you will not be able to make Lanlink connections to the 
WinView server.  For information on configuring Lanlink terminals, 
consult the System Administrator's Guide. 
 
Configuring the LANLINK Client Software for RNS Connections 
 
You are now ready to configure LANLINK.  From the LANLINK main 
menu, press ENTER on the AppServer List.  Now press the INSERT 
key to configure a new AppServer.  Enter any name on the line marked 
"Label."  Move the cursor down to AppServer Name and press the F6 
key.  This will bring up a list of all available AppServers on the remote 
LAN, select one by hitting Return.  (NOTE: If no application servers 
appear on the AppServer list, then the WinView Server is not 
advertising itself on the network.  This may indicate a router that is 
filtering the WinView SAP ID.  You may not be able to connect via 
LANLINK until the application server is visible on the LAN.  You should 
be able use the WinView Server's network address in this field.)  Move 
down to "Connection Type" and press ENTER.  Choose "IPX" 
connection.  Next, select "Yes" for both "Error Correction" and 
"Compression."  Now press the F7 key for the advanced options.  Make 
the following changes: 
 
Transmit ACK Timeout	[ 40 ] 
Transmit NAK Timeout	[ 30 ] 
Receive Partial Packet Timeout	[ 10 ] 
[Note that the above values are double the original default values.] 
 
Press the F4 key twice to save and exit.  This will return you to the 
LANLINK main menu.  You are now ready to connect to an application 
server. 
 
	 
Running LANLINK to Connect to a WinView Application Server 
 
From the LANLINK main menu, choose "Connect to AppServer."  
Choose the WinView server that configured in the preceding step.  After 
pressing the ENTER key, you should see in the left hand corner of the 
screen the name of the WinView server, its node address, and the 
message "LOCATING."  You will then get three "connecting" dots which 
will inform you of the communication between the workstation and the 
AppServer.  If you get a message indicating "Excessive error retries," 
go back to the Advanced options on the AppServer Update screen and 
triple the original timeout values that were doubled earlier.  In other 
words, the new values should be: 
 
Transmit ACK Timeout	[ 60 ] 
Transmit NAK Timeout	[ 45 ] 
Receive Partial Packet Timeout	[ 15 ] 
[Note that the above values are triple the original default values.] 
 
Now try connecting again.  You should now be prompted to login to the 
WinView server.  This will complete your LANLINK connection to the 
WinView server via NetWare Connect. 


Configuring WinView  for NASI Communication Service (NCS) 
 
Once a WinView server has been installed, add the "NetWare 
Connect/NACS" subsystem by doing the following:  
 
1)	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 above. 
 
2)	Press F10 then "P" to pull down the "Profile" menu.  
 
3)	Press "A" to select "Add subsystem."  Your screen will look like 
Figure #2 below: 
 
Figure #2 - Workstation Configuration Screen (Add Subsystem) 
 
 
4)	Choose "NetWare Connect/NACS" from the "Add a Workstation 
Subsystem" menu. 
 
5)	You will then be prompted for a UserID and password that is valid 
on the default NetWare Connect server as in Figure #3 below  This 
UserID and password is used for all WinView connections.  If the 
UserID or password is changed on the Netware Connect server at a 
later date then it must be changed here also. Use the Edit function 
on the pull down menu to change these fields when necessary. 


Figure #3 Workstation Configuration Screen (Netware Connect Password) 
 
 
6)	With the new Netware Connect/NACS subsystem highlighted, press 
"P" to pull down the "Profile" menu, then "N" for "New." 
 
7)	At this point, refer to the WinView System Administrator's Guide for 
information on configuring new ICA terminals.  When you are 
prompted for the device name, you must specify the name of one of 
the NCS ports.  For example you might use "AIO_123456" for the 
device name  instead of "COM1" or "DIGI6." 
 
8)	Once there are terminals created, you should have no problems 
dialing into the Netware Connect NCS port with the RLINK software.  
Netware Connect will be totally transparent to the remote RLINK 
user.  In other words, it will seem as if RLINK is dialing directly into 
WinView. 


Configuring REMOTE LINK (RLINK) for NASI Dial-out 
 
	The RLINK software may be used to dial-out of a Netware Connect 
NASI port.  For example, Netware users may want to dial-out of their 
local LAN into a WinView server on another remote LAN.  Netware 
Connect acts as a modem pool for these client workstations.  You must 
run NASI.EXE (3-25-94, 33270 bytes) supplied with Netware Connect 
NWC001.EXE update prior to running RLINK.  After NASI is loaded, run 
the RLINK software and set it up as follows: 
 
1)	Select "AppServer List" from the REMOTE  LINK Main Menu. 
 
2)	Press F10 then "A" for "Add..." 
 
3)	For the "Label" and "Description," type in anything you wish.  You 
may want to add the name of the WinView server you will be dialing 
into in one of these fields. 
 
4)	In the "Phone Number" field, type in the phone number you will 
dialing into to. 
 
5)	Skip to the "Connection Type" field and press the "Enter" key.  From 
the menu select "NASI." 
 
6)	The "Emulation Mode" field under most circumstances will be set for 
ICA. 
 
7)	Set the "Modem Type" to the modem that is connected to the 
Netware Connect port you will be dialing out. 
 
8)	For "Device Name," you must use the actual port name (specific 
name) of the Netware Connect port you will dial out of. 
 
9)	Set both "Error Correction" and "Compression" to "Yes." 
 
Finally your screen should look much like Figure #4 below: 
 
Figure #4 
 
Limitations With NetWare Connect and WinView 
 
WinView does not support NetWare Connect AppleTalk Remote Access Service 
(ARAS). 
 
At this time WinView does not support the "Netware Asynchronous Service Selector" 
feature.  In other words WinView is unable to use NCS ports dynamically, therefore 
Netware Connect NCS ports must be dedicated to WinView for dial-in use. 
 
Operational Considerations 
 
Here are some operational tips to use when planning for a NetWare Connect and 
WinView setup: 
 
*	If you are planning to run Windows applications via LANLINK, then for best results 
you should have a 16550 UART on the client machine.  
 
*	It is also recommended that you connect at a baud rate of at least 9600.  
 
 
 
 
 
 
 
 
Diagnosing Problems 
 
The NetWare Connect product has a good troubleshooting section in their "Netware 
Connect Administrators Guide" (make sure you check the addendum too).  For any 
communication/connection problems, the NetWare Connect diagnostic tools should be 
used. 
 
Troubleshooting NCS Connections 
 
The following figures are screen captures from Novell's NASIDIAG.EXE utility.  This 
information is included as a reference when attempting to configure WinView to 
acquire Netware Connect (or NACS) NASI ports.  NASIDIAG should be run from a 
DOS workstation as the first step in ensuring that the Netware Connect NASI ports can 
be seen on the network (and therefore be seen by WinView).  Before running 
NASIDIAG.EXE, you must run the NASI.EXE TSR. NASI.EXE will prompt you for a 
valid username, password and session name on the Netware Connect server.  Use the 
supervisor username and password of the Netware Connect server you will be using 
with WinView.  Once NASI is loaded in memory, execute NASIDIAG and you will be 
presented with the screen in figure #5. 
 
Figure #5 - NASIDIAG.EXE main menu 
 
 
 
The first option on the NASIDIAG main menu is "List Available NCS Servers."  This 
option will provide the user with all the available Netware Connect or NACS servers 
that have NASI ports available.  Be aware that if your Netware Connect server does 
not have any ports currently configured for NASI Connections Service (NCS), then it 
will not appear in this list.  An example of the "List Available NCS Servers is shown in 
Figure #6 below. 
 


Figure #6 - "List of Available NCS Servers" Option 
 
 
 
Again, the Netware Connect server must have ports available for NASI Connection 
Service (NCS) or it will not appear in this list.   For example, at Citrix we actually have 
two Netware Connect Servers and one NACS server, but only the NACS and one 
Netware Connect server (SUPLABNWC) have NCS configured.  Also, notice that the 
file server name can be different that the NCS name (e.g. NACS and NACSTRIX.)  
Finally, the most important option of NASIDIAG is the second option on the main menu 
- "List Available NCS Ports."  Figure #7 shows an example of the NASI ports available 
on the Citrix in-house LAN. 
 
Figure #7 - "List Available NCS Ports" Option 
 
 
 
The "List Available NCS Ports" option of NASIDIAG will actually show which ports are 
available for use.  Notice that even though the Netware Connect server named 
"SUPLABNWC" appears in the "List Available NCS Servers" option (Figure #5) none of 
it's ports show up in the "List Available NCS Ports."  This is because the supervisor 
username and password of the server named "NACS" was used when NASI was 
loaded, which was not the same name as the supervisor for the "SUPLABNWC" 
server.  This was done intentionally to show potential pitfalls when using NASIDIAG.  
The important thing to remember is if you cannot see (and test) the ports with 
NASIDIAG, you will be unable to use them with WinView.  
 
The next step is to run SLIST from an OS/2 prompt on the WinView server.  You 
should be able to see the Netware Connect file server name in this list.  If you do not 
see any Netware file servers with the SLIST utility, then WinView is incorrectly 
configured or you have a cabling/routing problem.  If all available file servers appear 
other than the desired Netware Connect server, then the Netware Connect server is 
improperly configured.  Consult the "Netware Connect Administrator's Guide."   
 
As the next step, type "QUERY NACS" from the WinView console.  You can also type 
"QNACS" instead of "QUERY NACS."  Make sure you downloaded QNACS.ZIP from 
the Citrix CompuServe forum (Library 2) and have applied the updated QNACS.EXE to 
the WinView server.  You should see the same ports that were displayed with the 
NASIDIAG utility.  If this is not the case, then more than likely the Netware Connect 
User ID and/or password is invalid.  See step 5 of "Configuring the WinView Server for 
NASI Communication Service (NCS.)" 
 
If all the previous steps go without a hitch, you should have no problems configuring a 
WinView terminal to use NASI port with WinView's "CONFIGURE WORKSTATIONS" 
utility.  See the section of this document titled "Configuring WinView for NASI 
Communication (NCS)" for more information. 
 
Troubleshooting RNS Connections 
 
From a WinView standpoint, there is not much to troubleshoot when using RNS 
connections.  First, make sure that you can use LANLINK from a DOS workstation on 
the same LAN segment as the WinView server.  If this does not work, then make sure 
you have LANLINK terminals created as on page 10 of this app note.  Also, make sure 
the WinView server is attached to the network by typing SLIST at an OS/2 prompt.  If 
all goes well you should be able to login through Netware Connect as a remote LAN 
node and run LANLINK.  If you are unable to login as a remote node, review the 
"Netware Connect Administrator's Guide."  If a remote node connection is made but 
does not return from the DIALCON utility, make sure the NWC001 and NWC002 
patches are applied to both the server and the remote node. 
 


Tested Hardware Configurations 
 
The following Netware Connect hardware configurations were used for Citrix in-house 
compatibilty testing and the production of this document.  It is not the intent of Citrix 
Systems to endorse or promote the following hardware items. 
 
Netware Connect Server #1 
 
*	Computer Make and Model:  Compaq DeskPro 386-20e 
*	BIOS:  Compaq 
*	System RAM:  10 MB 
*	Disk Controller:  Compaq IDE 
*	Hard Drive Make and Model:  Conner CP 3181 110 MB 
*	Multiport Adapter:  DigiBoard PC8i  
	IRQ:  None 
	Port:  110 
	Mem:  D0000 
*	Network Interface Card:  3Com 3C507 
	IRQ:  9 
	Port:  300 
	Mem:  C8000 
*	Modems:  MultiTech MultiModem II 1432 BA, Hayes Optima 28.8 kbps 
*	Netware Server Version:  3.11 
 
Netware Connect Server #2 
 
*	Computer Make and Model:  Compudyne 
*	BIOS:  AST (12/7/93, Ver. 1.2R2.0) 
*	System RAM:  8 MB 
*	Disk Controller:  IDE 
*	Hard Drive Make and Model:  Conner 210 MB 
*	Multiport Adapter:  DigiBoard PC8i  
	IRQ:  None 
	Port:  320 
	Mem:  E0000 
*	Network Interface Card:  3Com 3C503 
	IRQ:  5 
	Port:  300 
	Mem:  C8000 
*	Modems:  MultiTech MultiModem II 1432 BA, USRobotics Sportster 14.4 
*	Netware Server Version:  3.12 Run-time 
 

19 
 

