Novell NetWare Connect Version 2.0

1
Novell NetWare Connect Version 2.0
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 by asynchronous
connections, utilizing an intelligent multiport serial controller in the file server.
NetWare Connect provides two services that can be used in conjunction with
WINFRAME. When connected using DOSDIAL for DOS or Remote Client Dialer
for Windows, your computer appears as a locally connected workstation on the
network. When connected by a NASI ICA connection, your computer functions as
if it had dialed into a modem directly connected to the WINFRAME host.
NASI Connection Service (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 NASI ICA
connection is configured to connect to a NetWare Connect port for asynchronous
dial-in access. When a user dials into the NetWare Connect server with the Citrix
ICA Client, a NetWare Connect login authentication is required and then a list of
services (WINFRAME hosts that have an ICA connection attached to a port on the
NetWare Connect server) is presented. When a WINFRAME host is selected, the
user is logged in, and it appears as if the user dialed into a modem that was
attached directly to the WINFRAME host. The only exception is the NetWare
Connect login and the service selector. The advanced Independent Computing
Architecture protocol used by the Citrix ICA Clients improves performance
because it sends only compressed screen updates and mouse and keyboard events
over the NASI connection.
A NASI ICA connection is required for each simultaneous NASI connection to
the WINFRAME server. Use Citrix Connection Configuration to create and maintain
NASI connections.
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 in to a remote network
and act as a network workstation. 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
on the host network. The communication taking place on the LAN is translated on
the NetWare Connect Server and sent over the modem to the remote workstation.

2
Requirements
In contrast, NetWare Connect 1.0 used the Novell NetWare Remote Node (NRN)
communication protocol to allow remote node attachment to the LAN through the
NetWare Connect 1.0 Server. NetWare Connect 1.0’s NRN was a Novell
proprietary protocol. Users were forced to use only the Novell client software and
only the IPX transport was available. In creating and using PPPRNS in NetWare
Connect 2.0, Novell used an industry standard protocol, PPP, and an industry
standard PPP Link Control Protocol (LCP) extension, IPXCP (Internetwork
Packet Exchange Control Protocol). With NetWare Connect 2.0, virtually any
third-party TCP/IP with a PPP stack can connect to the NetWare Connect 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 NetWare Connect 2.0, NCS
is the easiest of the two to implement, but PPPRNS is the most versatile,
providing direct IPX and TCP/IP protocol access to the LAN. When using
PPPRNS, not only can WINFRAME hosts be accessed, but also any NetWare or
IPX servers and any TCP/IP resources, depending on which transport is installed.
The Novell NetWare Connect client software and information about each
implementation supporting the PPPRNS service are listed in “Connection Types
Supported.” NetWare Connect provides two client components for DOS,
Windows, and Windows for Workgroups that support IPX and TCP/IP over
PPPRNS: DOSDIAL for DOS and Remote Client Dialer for Windows and
Windows for Workgroups.
Network
K
K
K
Citrix WINFRAME host connected to a NetWare network
NetWare server with NetWare Connect Version 2.0 installed and operational
Modems installed on the NetWare Connect server configured for dial-in
service
Remote Workstation
K
K
K
K
Citrix ICA Client software for the remote workstation’s environment
Novell NetWare Connect client software loaded and operational (see
“Connection Types Supported” below)
Modem supported by the transport being used on the remote workstation
High-speed serial port (16550 or equivalent) or intelligent serial port board

3
Connection Types Supported
Following is a list of the different ICA Client connections supported with
NetWare Connect 2.0, the components needed, and the protocol used to
communicate with the NetWare Connect server.
K
K
DOS
K Novell NetWare Connect DOSDIAL, ICA Client for DOS (PPPRNS
Protocol)
K ICA Client for DOS (NCS Protocol)
Windows 16-bit
K Novell NetWare Remote Client Dialer for Windows, ICA Win16 or DOS
Client (PPPRNS Protocol)
Installation
NetWare Server
Install NetWare Connect 2.0 on the NetWare server. Please carefully read any
Readme files or notes supplied with NetWare Connect 2.0.
Notes Under NetWare Connect Setup for PPPRNS, the NetWare Connect PPP
ports and the clients should have their own IP network (for example, if the
network card installed in the NetWare Connect 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).
Under NetWare Connect Setup for PPPRNS, the IPX network address should be a
(network-wide) unique address. In other words, if the network card installed in the
NetWare Connect server has an IPX address of 0000DADA, the PPPRNS IPX
address would be 0000DADB.
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 in this note.
You need to configure sufficient connections to support both local LAN users and
remote NetWare Connect users.
Sample Configuration 1
Workstation
DOS
Transport
TCP/IP and/or IPX
Components Novell NetWare Connect DOSDIAL, ICA Client for DOS
Connection
PPPRNS

4
Verify that ICA connections (TCP/IP or IPX) are configured on the WINFRAME
server for the network protocol in use. Make sure you have enough connections
configured to support both local LAN connections and remote NetWare Connect
connections.
To install a WINFRAME remote workstation
1. Install both the NetWare Connect DOSDIAL and the Citrix ICA Client for
DOS software on the remote workstation. After installation is complete, verify
that the system boots properly.
2. Start the NetWare Connect DOSDIAL client to establish an IPX and/or IP
connection to the NetWare Connect 2.0 host on the remote network. Exit
NetWare Connect DOSDIAL, change to the network drive, and verify that a
remote network connection has been established.
Note
Do not proceed until this step is completed successfully.
3. Start the ICA Client.
4. Create a remote application. If you select IPX as the transport, it is possible
you will not be able to see server names in the WINFRAME server list,
depending on whether or not you loaded a Novell DOS redirector,
NETX.EXE, or VLMs. If no redirector is installed, you must enter the MAC
address of the WINFRAME server to which you want to connect (for example,
00DA004BC382). To identify the MAC address of the WINFRAME server, click
the Windows NT Diagnostics icon and select Network from the WINFRAME
server console under Administrative Tools.
5. If you configured PPPRNS to use TCP/IP on the NetWare Connect 2.0 server
and also configured it during client set up, choose Novell TCP/IP as the
transport.
6. If you have a functioning DNS system or have a correct and valid HOSTS file,
enter the name of the WINFRAME host to which you want to connect. 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 WINFRAME host you want to connect
to in the Properties dialog box (for example, 128.128.1.2). The HOSTS file is
under the TCP directory, in the directory in which the TCP/IP transport is
installed.

5
Sample Configuration 2
Workstation
Transport
Components
Connection
DOS
Serial Port (NCS)
Citrix ICA Client for DOS and client supported modem
(16550 UART recommended)
Novell NCS
Use Citrix Connection Configuration to set up NASI connections on your
WINFRAME server.
To install the WINFRAME remote workstation
1. Install the ICA Client for DOS but do not choose any networking components.
2. Change to the directory where the client is installed and run WFCLIENT.EXE.
3. When installed, there are no entries in the server list. Create an entry by
clicking Entry, New, and filling out the fields on the Properties dialog box.
4. Assign a name to the entry, select Serial for the transport (unless you are using
one of the supported intelligent serial boards), and click Settings.
5. Fill in this form to match your configuration, including baud rate, port, and
modem type.
6. Click OK to exit the device setting and return to the Properties screen.
7. Type a telephone number and add the user information, if desired.
Note If no user information is entered, it will be requested when the
attachment to WINFRAME is made.
8. Click OK to save the entry.
9. To dial the WINFRAME host, either double-click the name or highlight the name
by single-clicking it and then selecting Entry, Connect.
10. A dialog box appears with a message telling you the computer is dialing. When
the connection to the NetWare Connect server is made, you are asked to log
on. Type the username and password when requested.
11. When the authentication is passed, a service selector appears.
12. Select the WINFRAME host to connect to by typing its number and pressing
ENTER. From this point on, the connection functions as a standard WINFRAME
asynchronous connection. See the Citrix ICA Client Administrator’s Guides
for further information.

6
Troubleshooting
To troubleshoot client problems, first isolate which client software is set up
incorrectly. For example, load only the NetWare Connect client software and
attempt to access the network before starting the Citrix ICA Client. If you cannot
access the network, troubleshoot the NetWare Connect 2.0 server and client
configuration.
Note Listed below are samples of the remote workstation and server configuration
files that NetWare Connect 2.0 uses. They will differ depending on your hardware
and software 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
The following is a sample server NWCSTART.NCF file, located in the
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

7
The following is a sample remote workstation STARTNET.BAT file, located in
the NetWare Connect client directory:
c:\nwcnet\bin\yesno.exe "Do you want to load the remote client software?
(y/n) "
if errorlevel 1 go to LoadNet
go to 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
go to Exit
:LoadRem
REM **DO NOT DELETE**
:Exit
A sample remote workstation NET.CFG file, located in the NetWare Connect
client 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

8
The sample lines below are added to the AUTOEXEC.BAT file in your root
directory:
PATH C:\NWCLIENT;%PATH%
PATH C:\NWCNET\BIN;%PATH%
@CALL C:\NWCLIENT\STARTNET
The sample line below is added to the CONFIG.SYS file in your root directory:
LASTDRIVE=Z