home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
nwc001.exe
/
README.NWC
< prev
next >
Wrap
Text File
|
1994-06-01
|
18KB
|
457 lines
This file (README.NWC) contains general information regarding NetWare
Connect.
**** IMPORTANT: If You Are Installing NWC001 it is Vital that you
-----------------------------------------------------------------
Access and Read NW001.TXT for Current Instructions. ****
--------------------------------------------------------
Contents of README.NWC
1.0 Special Notes for NetWare 4.x
2.0 Critical Information
2.1 Loading Btrieve(R) on NetWare 3.1x
2.2 Renaming Ports
2.3 Bringing Down the Server
2.4 Sharing Ports between ARAS and NCS
3.0 Installation Issues
3.1 Remote Installation
3.2 Reinstalling NetWare Connect
3.3 OPENNV Message
3.4 Installing NetWare Connect from Floppy Diskettes
4.0 Configuration Issues
4.1 Dynamic Reconfiguration in NetWare Connect
4.2 Configuration Report
4.3 Setting the Data Rate
4.4 Restricting Service by Port
For ARAS
4.5 Zone Names for ARAS
4.6 Dialback Support for Remote Macintosh* Users
For NCS
4.7 NCS and Inoperative Ports
4.8 NASI(tm) Requires Updated IPXODI
4.9 NCS Dial-in/Dial-out Groups
4.10 NetWare Connect Port Usage
4.11 NASI Command Line Option
For RNS/NRN
4.12 Unable to Attach to a Server Using NETX
4.13 Command Line Options for DIALCON with Two Frame Types
4.14 Enhancing Performance for Remote Nodes
5.0 X.25 Support
5.1 Installation
5.2 MPR v2.1 and NetWare Connect
5.3 Using NRN over X.25
6.0 Software Update
6.1 Additional Utility for NRN Users
6.2 Driver Update
6.3 Modem Scripts
7.0 Documentation Updates
Trademarks
======================================================================
1.0 SPECIAL NOTES FOR NETWARE 4.x
If you are installing NetWare Connect on a NetWare 4.x server, do not
create a user named SUPERVISOR. SUPERVISOR has a special meaning and
is maintained by the NetWare 4.x operating system for NetWare 3.1x
compatibility only.
NOTE: Bindery emulation must be enabled on the NetWare 4.x server
that will have NetWare Connect installed. The SET BINDERY CONTEXT
command in the AUTOEXEC.NCF file enables bindery emulation.
In addition, the NetWare 4.x server must have a read/write replica or
a master replica of its partition in order for bindery emulation to be
enabled.
Reinstall NetWare Connect if you do any of the following on your
NetWare 4.x server:
- Reinstall NetWare Directory Services(tm)
- Change the bindery context for the server
- Change the "IPX INTERNAL NET" address for the server
NetWare Connect 1.0 does not support X.25 services on NetWare 4.0(tm)
and NetWare 4.01(tm) servers.
======================================================================
2.0 CRITICAL INFORMATION
Although you should read this entire file, pay special attention to
this section. It contains information critical to your success in
using NetWare Connect.
2.1 Loading Btrieve on NetWare 3.1x
During the installation of NetWare Connect if you have problems
loading Btrieve, COPY the following files from the original NetWare
Connect diskettes to the SYS:SYSTEM subdirectory:
- For a NetWare 3.11 server, all the files in the root directory and
the NW3X directory on DISK3.
- BTRIEVE.* (the Btrieve Update) from the SYSTEM directory on DISK4.
Then, enter LOAD BTRIEVE at the system console prompt (:).
2.2 Renaming Ports
If you rename a port that is in the "WAITING" state, you must reset
the port. NetWare Connect does not allow you to rename a port that is
in use by any of the services.
2.3 Bringing Down the Server
Before you bring down the server, exit all NetWare Connect console
menus and then unload NetWare Connect by running NWCSTOP.
2.4 Sharing Port between ARAS and NCS
If an NCS remote user is calling into a port that is shared by ARAS
and the NCS Dial-in group, make sure the remote application turns off
the v.42 error control on the remote modem. Otherwise, the Service
Selector interprets the v.42 packets as ARAS packets, and will pass
control to ARAS instead of NCS. Refer to your modem documentation for
commands to disable v.42 error control. To verify which service is
taking control of the connection, see the View NetWare Connect Port
Status screen.
======================================================================
3.0 INSTALLATION ISSUES
3.1 Remote Installation
3.1.1 Problems Loading Btrieve
One of the following messages may appear if you are installing NetWare
Connect on a newly installed remote server:
Csinstal: Unable to *INSERT* record in PRODUCTINFO database file
Btrieve error in network partition code=3
Csinstal: Unable to *CLOSE* PRODUCTINFO database file
Btrieve error in network partition code=3
Loading module PFIXUP.NLM
Cannot open PRODUCTS.DAT file
To correct the problem, verify the following:
- Make sure BTRIEVE.NLM and BSPXCOM.NLM are loaded on the remote
server.
- Make sure BTRIEVE.NLM and BROUTER.NLM are loaded on the local
server.
If the problem still exists, make sure the PRODUCTS.DAT file exists on
the remote server. The PRODUCTS.DAT file is created when you load
INSTALL and select "Product Options" on the remote server. You can
load INSTALL on the remote server using RCONSOLE.
3.1.2 Installing on Multiple Remote Servers
Make sure you unload INSTALL after each installation of NetWare
Connect on remote servers.
3.2 Reinstalling NetWare Connect
If you reinstall NetWare Connect, do not try to use an old
NWCSTART.NCF file.
3.3 OPENNV Message
The following message may appear the first time you load NetWare
Connect:
OPENNV.NLM: could not open connection to NWSAA or NMA for NetView
Ignore this message if you do not have a NetWare for SAA* host
connection or the NetWare Management Agent(tm) installed on your LAN.
3.4 Installing NetWare Connect from Floppy Diskettes
If the light on your diskette drive remains on even after the files
are copied, continue with the installation.
======================================================================
4.0 CONFIGURATION ISSUES
4.1 Dynamic Reconfiguration in NetWare Connect
If you modify configuration parameters, the changes take effect only
when you return to the first-level menu of NWCCON.
4.2 Configuration Report
4.2.1 Installed and Loaded Services
A NetWare Connect configuration report displays two categories:
- Installed NetWare Connect Services
These are the services that are copied onto the server.
- Loaded NetWare Connect Services
These are the services that are selected in the NWCNCF utility.
These services may not be currently running. They are running only
when you start NetWare Connect with NWCSTART. To see if the services
are running, enter "MODULES" at the system console prompt (:).
4.2.2 Saving to a File
If you generate a configuration report and save it to a file, the
default filename and path is NWCRPT.TXT in the root directory of the
SYS: volume.
NetWare Connect allows you to change the default filename and path.
4.3 Setting the Data Rate
Before setting the data rate, make sure you load the communications
driver for that port. Only the supported data rates are displayed.
The maximum speed through the COM ports of a NetWare Connect server
is:
- 2400 bps if the port contains a 8450 or 16450 UART.
- 19.2 bps if the ports contains a 16550 UART.
Certified multiport adapter boards support much higher speeds (see
the manufacturers specifications).
4.4 Restricting Service by Port
Refer to page 5-8 of the NetWare Connect 1.0 Administration Guide.
If all ports are deleted from the list of authorized ports, the
default <Any Port> is automatically inserted into the list. If you
want to restrict a service from accessing any port, then unload the
service.
4.5 Zones Names for ARAS
Novell(R) recommends that the zone name you specify when binding the
AppleTalk* Remote Access Service (ARAS) is the same zone that your
server belongs to. (The server name appears in the zone specified when
you load AppleTalk.) Refer to the following pages in the NetWare
Connect 1.0 Administration Guide for information on specifying zones:
- when binding ARAS, see page 3-19.
- when loading AppleTalk, see page 4-8.
4.6 Dialback Support for Remote Macintosh Users
ARAS supports forced dialback only. Mobile Macintosh users cannot
define a dialback number from changing locations. The network
administrator must define the dialback number using NWCCON at the
communications server.
4.7 NCS and Inoperative Ports
Some NASI applications can select ports by specifying the general
name. If you select an inoperative port via a general name, then that
connection will fail and all subsequent attempts to establish a
connection using the same general name will fail.
4.8 NASI Requires Updated IPXODI
Make sure you are using IPXODI v2.0 or later with NASI.EXE. For the
latest drivers, refer to NOVFILES on CompuServe.
4.9 NCS Dial-in/Dial-out Groups
Here is an example of how to use the NCS Dial-In group feature on the
NetWare Connect server.
- Create two port groups in NWCCON, for example, INBOUND and
OUTBOUND.
- Make all the ports used for dialing in, members of the INBOUND
group.
- Make all the ports used for dialing out, members of the OUTBOUND
group. Novell recommends that you make ALL the ports members of
the OUTBOUND group to allow users to dial out of the INBOUND ports
when they are not in use.
- Add both port groups to the General Name List in NWCCON (under NCS
Configuration).
- Add ONLY the INBOUND group to the Dial-In group (under NCS
Configuration).
This way, all configured ports are available for dialing out and some
ports are available for dialing in. For more information on the NCS
Dial-In group, refer to pages 4 and 12 of the Addendum to the NetWare
Connect 1.0 Administration Guide.
4.10 NetWare Connect Port Usage
If the InBound and OutBound NCS port groups have been defined, NASI
Query will show one specific port name for each OutBound port and one
specific name for all of the ports in an InBound port group. Use only
the OutBound ports for dialing out of NetWare Connect or the general
name for the OutBound group and use the InBound port group for only
"remote control" applications (like ReachOut and Pc Anywhere).
NOTE: Attempting to dial out of an inbound group port will cause an
error.
When you specify a dial-in group through NCS configuration, NetWare
Connect creates a logical port using the first eight characters of the
NetWare Connect server name plus "DIALIN". For example, if the server
name is "Communications" the logical port name will be COMMUNICDIALIN.
The logical port may contain several physical ports. This will
prevent the remote control host software from controlling the port
until someone dials in.
If a remote NASI user is having problems connecting to a NASI session
on the LAN, try turning off the V.42bis compression on the remote
modem.
4.11 NASI Command Line Option
The /NS option should not be used until applications are developed
which support it. Users must have a valid name and password on the
NetWare Connect server.
4.12 Unable to Attach to a Server Using NETX
If the remote PC is unable to attach to a server using NETX, try
the following:
- In AUTOEXEC.NCF on the server or from the console prompt turn ON
the following:
SET REPLY TO GET NEAREST SERVER=ON
- In the NET.CFG on the remote PC, specify the preferred server
option:
PREFERRED SERVER=servername
If you still have problems attaching to a server, do the following:
- Verify that the frame type on the remote PC is the same as that
defined on the NetWare Connect server.
- Lower the data rate.
- Select a different modem type in the list of modems.
- Try a different modem.
4.13 Command Line Options for DIALCON with Two Frame Types
If you have a NetWare Remote Node (NRN) driver configuration with two
frame types, you must specify the ODI(tm) driver number on the command
line.
Use the /d option in DIALCON to specify the ODI driver number. Refer
to page 6-34 of the NetWare Connect 1.0 Administration Guide.
Specifying two frame types for a single driver configuration requires
loading the ODI driver twice.
4.14 Enhancing Performance for Remote Nodes
If you have a high-speed modem (9600 bps and above) and a fairly
error-free link, you can enhance performance by increasing the cache
buffers and the packet size. To increase the packet size, edit the
NET.CFG file and add the following line under the Link Driver NRN
section:
packet length x
Replace x with a value between 512 and 1428. For example, replace x
with 1024. Similarly, decrease the packet size if your connection is
prone to errors.
It is not practical to load executable files across the line. Please
put them on the remote drive before executing them.
======================================================================
5.0 X.25 SUPPORT
NetWare Connect 1.0 supports X.25 on NetWare 3.x only.
5.1 Installation
If you did not initially install the X.25 support, then remove NetWare
Connect (see page 3-24 of the NetWare Connect 1.0 Administration
Guide) and reinstall NetWare Connect with X.25 support.
5.2 MPR v2.1 and NetWare Connect
If you install the NetWare MultiProtocol Router(tm) (MPR) v2.1 on a
server that has NetWare Connect already installed, you must reinstall
NetWare Connect. Reinstallation of NetWare Connect is necessary
because MPR v2.1 overwrites the AIO and X.25 modules shipped with
NetWare Connect.
5.3 Using NRN over X.25
If you are using NRN to connect to an X.25 network, do the following:
- Specify the Modem type as "Manual" in DIALCON.
- Add the /PASS option on the server, as follows, when you load
AIOPAD:
load aiopad x25board=boardname x25port=portnumber /pass
The /PASS option disables AIOPAD from performing X.3 processing in
data transfer mode. This allows RNS to operate more efficiently.
Using the /PASS option, however, prevents the user from going into
command mode and changing the X.3 PAD parameters.
======================================================================
6.0 SOFTWARE UPDATE
6.1 Additional Utility for NRN Users
A TSR program called NetWarn is provided for NRN clients. NetWarn
notifies the remote user of the path of the executable being loaded.
It warns the remote user if a program is being loaded from the server
over the asynchronous link. This warning gives the remote user the
opportunity to stop the access and prevent the connection from being
tied up for an unacceptable period of time.
NOTE: Load NetWarn only after you have established a connection.
NetWarn is automatically installed in the SYS:SYSTEM\NRN subdirectory
and supports the following options:
netwarn [/d | /e | /u | /p | /s ]
where
/d Disables NetWarn
/e Enables NetWarn
/u Unloads NetWarn
/p Displays the path of the executable
/s=x Sets the executable file size in x KB
Although x can range from 0 through 9999, the default value for x is
5 KB.
NetWarn notifies the user only when an executable greater than 5 KB
is being loaded.
6.2 Driver Update
If you are using the newer communications adapters from Digiboard,
Novell recommends that you download the latest driver from the
Digiboard BBS at 612-943-0812.
6.3 Modem Scripts
The modem definition file shipped with NetWare Connect is updated
continuously. To access the most current modem scripts available, go
to NOVLIB Library 9 on CompuServe and download NWCMOD.EXE.
======================================================================
7.0 DOCUMENTATION UPDATES
Note the following changes to the NetWare Connect 1.0 Administration
Guide:
- Page 5-34
In the Archive Interval field, specify a value from 0 through 90.
- Page 6-21
Replace "NETX.COM" with "NETX.EXE".
Note the following changes and additional information to the Addendum
to the NetWare Connect 1.0 Administration Guide:
- Page 9
NASI Command Line Options: The maximum number of characters that you
can specify for the NASI username and password is 48 and 24,
respectively.
- Page 11
If you are executing NASI from a file, do not enclose the NASI
username, password, and session name within quotation marks.
- Page 14
The correct syntax for specifying a node address is 000000XX0000,
where XX can range from 01 through FF.
- Page 23
The command line option to specify a NASI username is /n, not /u.
- Page 24
The latest AIO version shipped with NetWare Connect is version 6.0.
In this version of AIO, NetWare Connect and NetWare Global MHS(tm)
do not support port sharing. Before you install NetWare Connect,
refer to the README file in the Global MHS product.
======================================================================
TRADEMARKS
Third-party trademarks are identified in this README file with an
asterisk (*).
Novell, Inc. has attempted to supply trademark information about
company names, products, and services mentioned in this README file.
The following list of trademarks was derived from various sources.
Novell, NetWare, and Btrieve are registered trademarks of Novell,
Inc. NASI, NetWare 4.0, NetWare 4.01, NetWare Connect, NetWare
Directory Services, NetWare Global MHS, NetWare Management Agent,
NetWare MultiProtocol Router, NLM, ODI are trademarks of Novell, Inc.
AppleTalk and Macintosh are registered trademarks of Apple Computer,
Inc.
CompuServe is a registered trademark of CompuServe Incorporated.
NetView is a registered trademark and SAA is a trademark of
International Business
Machines Corporation.
V.42bis software compression is licensed under U.S. Patent 4,558,302.
(C)Copyright 1993-1994 Novell, Inc. All rights reserved.
======================================================================
** End of README.NWC **