#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'Basic Protocol Configuration GuideBasic Protocol Configuration GuideNovell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=9 ID="BP1"About This GuideThis guide is written for the network administrator responsible for installing and configuring NetWare® 4.1 protocol software as a server or a combined server/router. It is not intended to provide detailed information about LAN media or network protocols. For additional information, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide and the appropriate technical references.As the administrator, you must plan and implement the connection of the server to the physical internetwork. This task involves laying the network cables, installing network interface boards, adding and removing nodes, and placing servers, bridges, and routers. To perform these tasks, you should have technical knowledge of protocols, network addressing, routing, and operational issues.RENDERAS="SECT1"Chapter SummariesThis section briefly summarizes each chapter in this guide. Use these summaries to help you locate specific topics, or to help you decide which portions of this guide contain new information.IDREF="FM36382"Chapter 1, "Introduction," provides an overview of the components of the product and the installation and configuration procedures presented in subsequent chapters of the guide.IDREF="FM97977"Chapter 2, "Using INETCFG," describes the INETCFG utility used to perform the configuration procedures for the boards, protocols, interfaces, and bindings used by the NetWare 4.1 protocols.IDREF="FM13724"Chapter 3, "Configuring Boards," provides specific procedures for configuring LAN  boards.PAGENUM=10 ID="BP2"IDREF="FM34215"Chapter 4, "Configuring NetWare IPX," provides specific procedures for configuring the Internetwork Packet ExchangeTM (IPXTM) protocol parameters and binding IPX to  a LAN  interface.IDREF="FM52856"Chapter 5, "Configuring TCP/IP," provides specific procedures for configuring the TCP/IP protocol parameters and binding TCP/IP to  a LAN interface.IDREF="FM75172"Chapter 6, "Configuring AppleTalk," provides specific procedures for configuring the AppleTalk* protocol parameters and binding AppleTalk to  a LAN  interface.IDREF="FM89421"Chapter 7, "Configuring Remote Management," provides specific procedures for configuring SNMP node information and setting up the node for remote access.IDREF="FM93625"Chapter 8, "Testing the Configuration," provides specific procedures for testing and troubleshooting the configurations associated with NetWare 4.1 protocols.RENDERAS="SECT1"Conventions Used in This GuideThe NetWare 4.1 Basic Protocol Configuration Guide  uses the documentation conventions described in this section. Specifically, these conventions are used for the following:MARK=BULLETIDREF="FM13185"IDREF="FM13185"TerminologyIDREF="FM41243"New Terms and Important InformationIDREF="FM30574"System Messages IDREF="FM13464"User InputIDREF="FM38043"Special CharactersIDREF="FM32356"Graphic SymbolsPAGENUM=10 ID="BP3"PAGENUM=11RENDERAS="SECT2"ID="FM13185"TerminologyThe following terms summarize frequently performed actions:MARK=BULLET"Select" means to use the cursor keys to highlight an item and press MOREINFO="NONE"<Enter>. "Enter" means to type the indicated text and press MOREINFO="NONE"<Enter> (as one complete operation). It is shown in one of two ways; for example:Enter MOREINFO="NONE"LOAD MOREINFO="NONE"INETCFG or MOREINFO="NONE"LOAD MOREINFO="NONE"INETCFG MOREINFO="NONE"<Enter>RENDERAS="SECT2"ID="FM41243"New Terms and Important InformationHighlighting emphasizes new terms and important information.RENDERAS="SECT2"ID="FM30574"System MessagesRegular (nonboldface, nonitalic) monospaced character strings represent system prompts or responses; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"message exampleRENDERAS="SECT2"ID="FM13464"User InputThis guide uses the following conventions to denote user input:MARK=BULLETMOREINFO="NONE"Highlighted monospaced character strings represent user input, which must be entered exactly as shown; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD TCPIP MOREINFO="NONE"<Enter> or
   MOREINFO="NONE"Load tcpip MOREINFO="NONE"<Enter>Highlighted and lowercase character strings show descriptive names for items that you must replace with appropriate values. For example, in the following NetWare console command, you replace driver with the specific name of a driver:FORMAT="LINESPECIFIC"MOREINFO="NONE"UNBIND IP FROM driver MOREINFO="NONE"<Enter>
PAGENUM=12 ID="BP4"RENDERAS="SECT2"ID="FM38043"Special CharactersThis guide uses special characters to denote the following:MARK=BULLETAsterisks * in text denote third-party trademarks.Angle brackets < >, brackets [ ], braces { }, vertical bar |, parenthesis ( ), and quotation marks " are used as metacharacters and, as such, you must not type these as part of user input.Angle brackets < > enclose a descriptive name for any value that is provided as output by a computer; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"Error: <IP address> is illegal.
    Must be class A, B, or C.Characters enclosed in angle brackets can also represent keys; for example:MARK=BULLET"Press MOREINFO="NONE"<Ins>" means you press the MOREINFO="NONE"<Insert> key on your keyboard. Keys joined by a plus sign are pressed in combination. "Press MOREINFO="NONE"<Ctrl>+<Alt>+<Delete>" means you press those keys simultaneously.Square brackets [ ] enclose an option item; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IP TO board_name ADDR=ip_addr
   [MASK=mask_addr] MOREINFO="NONE"<Enter>If a command, such as the preceding one, is too long to fit on one line, it wraps to the next line; such a command must be entered after the console prompt (:) but before the end-of-line (EOL) character.Braces { } enclose multiple items separated by the vertical bar | character. You must specify only one of the items; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD TCPIP [FORWARD={YES|NO}]MOREINFO="NONE"<Enter>Vertical bars | separate items in a list of alternatives. If the list is enclosed in square brackets [ ], you can use any one or none of the items. If the list is enclosed in braces { }, you must use any one, but only one, of the items. PAGENUM=13 ID="BP5"RENDERAS="SECT2"ID="FM32356"Graphic SymbolsIn printed documentation, the following symbols appear in the left margin to identify different categories of information:PERFORMANCE="REQUIRED"This symbol identifies the first step of a procedure. To accomplish a specific task, follow the steps in the procedure.This symbol indicates sidelights, discussions, and general points of interest related to the current subject.This symbol points out key concepts or facts about the product. This symbol alerts you to situations that can produce critical or irreversible errors if you do not follow instructions carefully.This symbol points out hints, tips, or helpful information that you should know.Online documentation omits these symbols, but either maintains the font change or labels the information for easy identification.RENDERAS="SECT1"Related Novell PublicationsSee the following Novell publications for related information:MARK=BULLETBOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management GuideBOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX ReferenceBOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP ReferenceBOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* ReferenceLABEL="1"PAGENUM=1 ID="BP6"ID="FM36382"IntroductionNetWare® 4.1 internetworking software provides network connectivity using standard PC-compatible hardware. This combination of internetworking services allows you to integrate local area networks (LANs) running a variety of protocols into a cohesive corporate network.The features and applications of the network connectivity functions are discussed in separate sections of this chapter. RENDERAS="SECT1"Protocol FeaturesIDXID="w716"BOOK="_idx" COLLECTION="nw41" TIDREF="i3160"IDXID="w717"BOOK="_idx" COLLECTION="nw41" TIDREF="i2568"
The NetWare 4.1protocol software provides extensive internetworking services. It enables systems on separate LAN segments to communicate, even if the LAN types are different. It supports the most popular network protocols (NetWare IPXTM, AppleTalk, and TCP/IP) and the most popularIDXID="w718"BOOK="_idx" COLLECTION="nw41" TIDREF="i2039"IDXID="w719"BOOK="_idx" COLLECTION="nw41" TIDREF="i2367"
 data-link protocols (Ethernet, token ring, ARCNET*, LocalTalk*, and FDDI).The NetWare 4.1 protocol uses accepted networking standards wherever these are available to ensure compatibility with workstations, servers, and routers from other vendors. LAN interfaces use the Novell® IDXID="w720"BOOK="_idx" COLLECTION="nw41" TIDREF="i3080"
Open Data-Link InterfaceTM (ODITM) specification, so you can choose LAN controller boards from many vendors and many media types.PAGENUM=1 ID="BP7"PAGENUM=2RENDERAS="SECT2"IDXID="w721"BOOK="_idx" COLLECTION="nw41" TIDREF="i2568"
NetWare 4.1 ApplicationsNetWare 4.1 internetworking serves a variety of purposes:MARK=BULLETIt provides support for Network Applications running on the server.It off-loads the routing job from busy servers.It optimizes internetwork capacity by localizing traffic and containing problems on the originating LAN segment.It provides greater security by isolating traffic on segmented departmental LANs.It connects dissimilar media, such as Ethernet and token ring.It extends the physical reach of networks beyond the limits of each LAN segment.IDREF="FM60509"Figure 1-1 shows an internetwork including several LAN types (Ethernet, 10BASE-T, token ring, and LocalTalk) and various system types (PC, Macintosh*, and Sun* workstations). Each of these system types uses a different network protocol: PCs running NetWare use IPX, Macintoshes use AppleTalk, and Sun workstations use TCP/IP. The NetWare server shown on the 10BASE-T LAN supports all these protocols so that each workstation can access the server using its native network protocol.Because various workstations are on different LANs than server A, servers B and C also act as routers. The routers permit all systems on this internetwork to reach the NetWare server despite differences in LAN types.PAGENUM=3 ID="BP8"LABEL="1-1" FLOAT="0"ID="FM60509"Multiprotocol Internetwork with Various LAN TypesFILEREF="fig1_1.tif"PAGENUM=3 ID="BP9"PAGENUM=4RENDERAS="SECT2"IDXID="w722"BOOK="_idx" COLLECTION="nw41" TIDREF="i2568"IDXID="w723"BOOK="_idx" COLLECTION="nw41" TIDREF="i3147"IDXID="w724"BOOK="_idx" COLLECTION="nw41" TIDREF="i2568"IDXID="w725"BOOK="_idx" COLLECTION="nw41" TIDREF="i3610"
Supported ProtocolsFor a server to communicate with workstations and other servers, it must support the same protocols at several levels. The important protocol levels for servers are the physical, data-link, frame type, and network levels. For two systems to communicate directly, they must use the same protocol at each level. If they use different protocols below the network layer, a router can reconcile the differences and enable communication.IDXID="w726"BOOK="_idx" COLLECTION="nw41" TIDREF="i3309"
The physical protocol level includes hardware and electrical signaling characteristics of a LAN link. Examples include 10BASE-T, 10BASE5 (Ethernet thicknet), or a synchronous modem. Generally, all aspects of the physical layer are accomplished in hardware. Because NetWare 4.1 is based on popular PC-compatible hardware, a wide variety of data-link interface hardware is available, ensuring compatibility with other systems.IDXID="w727"BOOK="_idx" COLLECTION="nw41" TIDREF="i933"
The data-link protocol level defines the transmission of datagrams between systems that share a LAN physical link. Examples include 802.3 (Ethernet), 802.5 (token ring), or High-level Data Link Control (HDLC). Generally, most of the data-link protocol is also accomplished in hardware by a VLSI controller chip, although some functions require software assistance. Some data-link protocols, such as 802.3, can run over different physical media, such as 10BASE-T or 10BASE5. However, different media cannot be connected without a translating device, such as a repeater or router. Again, network interfaces supporting a wide variety of data-link protocols are available for PC-compatible systems.The IDXID="w728"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
frame type or encapsulation method defines a way to run multiple network-level protocols over a single LAN link. Examples include 802.2. This layer is implemented in software, and NetWare 4.1 supports all popular frame types.IDXID="w729"BOOK="_idx" COLLECTION="nw41" TIDREF="i2880"
The network protocol level enables applications to communicate over different LAN links, despite possible differences in frame type, data-link, or media specifications. This is such a beneficial function that each major class of workstation has evolved its own native or preferred network protocol. PAGENUM=4 ID="BP10"PAGENUM=5Of course, this means that a given workstation does not usually communicate with a different type of server. NetWare 4.1 internetworking overcomes this obstacle by supporting the three popular workstation network and service protocols on the server.Each network protocol also specifies a routing protocol that routers use to maintain a road map of the internetwork. Workstations and servers do not need to run the routing protocol unless they are also operating as routers. The transport layer protocols provides connection or connectionless end-to-end communication for applications.NetWare 4.1 internetworking supports the most commonly used IDXID="w730"BOOK="_idx" COLLECTION="nw41" TIDREF="i3906"
protocols, as listed in IDREF="FM79433"Table 1-1, ensuring compatibility with other servers.LABEL="1-1" PGWIDE=0 TOCENTRY="1"ID="FM79433"Workstation Types, Network Protocols, and Associated Routing ProtocolsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Workstation TypeCOLNAME=2 ROTATE="0" MOREROWS="0"Network ProtocolCOLNAME=3 ROTATE="0" MOREROWS="0"Associated Routing ProtocolVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IBM* PC-compatibleCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w731"BOOK="_idx" COLLECTION="nw41" TIDREF="i1873"IDXID="w732"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
Internetwork Packet Exchange (IPX)COLNAME=3 ROTATE="0" MOREROWS="0"IDXID="w733"BOOK="_idx" COLLECTION="nw41" TIDREF="i3904"IDXID="w734"BOOK="_idx" COLLECTION="nw41" TIDREF="i3859"IDXID="w735"BOOK="_idx" COLLECTION="nw41" TIDREF="i2753"IDXID="w736"BOOK="_idx" COLLECTION="nw41" TIDREF="i2927"
Routing Information Protocol (RIP)/ NetWare Link Services ProtocolTM (NLSPTM)COLNAME=1 ROTATE="0" MOREROWS="0"Apple* MacintoshCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w737"BOOK="_idx" COLLECTION="nw41" TIDREF="i931"IDXID="w738"BOOK="_idx" COLLECTION="nw41" TIDREF="i950"
Datagram Delivery Protocol (DDP)COLNAME=3 ROTATE="0" MOREROWS="0"IDXID="w739"BOOK="_idx" COLLECTION="nw41" TIDREF="i3912"IDXID="w740"BOOK="_idx" COLLECTION="nw41" TIDREF="i3929"
Routing Table Maintenance Protocol (RTMP)COLNAME=1 ROTATE="0" MOREROWS="0"UNIX® (Sun, HP*, others)COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w741"BOOK="_idx" COLLECTION="nw41" TIDREF="i1868"IDXID="w742"BOOK="_idx" COLLECTION="nw41" TIDREF="i1906"
Internetwork Protocol (IP)COLNAME=3 ROTATE="0" MOREROWS="0"IDXID="w743"BOOK="_idx" COLLECTION="nw41" TIDREF="i3904"IDXID="w744"BOOK="_idx" COLLECTION="nw41" TIDREF="i3859"
Routing Information Protocol (RIP)Open Shortest Path First Protocol (OSPF)IPX RIP and IP RIP are not the same protocol.PAGENUM=5 ID="BP11"PAGENUM=6For each network protocol, there is a family or suite of associated protocols at various levels. Many of these protocols do not fall into neat categories, but servers must support them nevertheless. IDREF="FM93168"Table 1-2 describes these associated protocols by protocol family.LABEL="1-2" PGWIDE=1 TOCENTRY="1"ID="FM93168"Associated ProtocolsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Network ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"Associated ProtocolCOLNAME=3 ROTATE="0" MOREROWS="0"FunctionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare IPXCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w745"BOOK="_idx" COLLECTION="nw41" TIDREF="i4073"
Service Advertising Protocol (SAP)COLNAME=3 ROTATE="0" MOREROWS="0"Distributes information about service names and addressesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w746"BOOK="_idx" COLLECTION="nw41" TIDREF="i2643"
NetBIOS PropagationCOLNAME=3 ROTATE="0" MOREROWS="0"Floods certain NetBIOS packets on the internetworkCOLNAME=1 ROTATE="0" MOREROWS="0"AppleTalkCOLNAME=2 ROTATE="0" MOREROWS="0"AppleTalk IDXID="w747"BOOK="_idx" COLLECTION="nw41" TIDREF="i189"
Address Resolution Protocol (AARP)COLNAME=3 ROTATE="0" MOREROWS="0"Maps DDP addresses to data-link addressesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w748"BOOK="_idx" COLLECTION="nw41" TIDREF="i4872"
Zone Information Protocol (ZIP)COLNAME=3 ROTATE="0" MOREROWS="0"Distributes information about zonesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w749"BOOK="_idx" COLLECTION="nw41" TIDREF="i2573"IDXID="w750"BOOK="_idx" COLLECTION="nw41" TIDREF="i2607"
Name Binding Protocol (NBP)COLNAME=3 ROTATE="0" MOREROWS="0"Converts entity names into DDP addressesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w751"BOOK="_idx" COLLECTION="nw41" TIDREF="i198"IDXID="w752"BOOK="_idx" COLLECTION="nw41" TIDREF="i130"
AppleTalk Echo Protocol (AEP)COLNAME=3 ROTATE="0" MOREROWS="0"Determines whether a certain DDP node is accessible over an internetworkPAGENUM=6 ID="BP12"PAGENUM=7The NetWare ODI design permits network protocols to be freely combined with IDXID="w753"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
frame types, ensuring compatibility with all network protocol/frame type combinations. IDREF="FM19277"Table 1-3 shows the recommended combinations. These frame types are also known as "encapsulation" types. Note that 802.2 and 802.2/SNAP frame types work over 802.3, 802.5, and FDDI data-link protocols, and the resulting combinations are not listed explicitly.LABEL="1-3" PGWIDE=1 TOCENTRY="1"ID="FM19277"Recommended Combinations of NetWare Protocol and Frame TypesCOLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="5*"COLNAME=3 COLWIDTH="5*"COLNAME=4 COLWIDTH="5*"NAMEST=1 NAMEEND=4 SPANNAME=SPAN1T4 ALIGN=LEFTVALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Frame TypeCOLNAME=2 ROTATE="0" MOREROWS="0"IPXCOLNAME=3 ROTATE="0" MOREROWS="0"IPCOLNAME=4 ROTATE="0" MOREROWS="0"AppleTalkVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Ethernet II (DIX)COLNAME=2 ROTATE="0" MOREROWS="0"yesCOLNAME=3 ROTATE="0" MOREROWS="0"yesCOLNAME=4 ROTATE="0" MOREROWS="0"yesCOLNAME=1 ROTATE="0" MOREROWS="0"IEEE 802.3/IPX*COLNAME=2 ROTATE="0" MOREROWS="0"yesCOLNAME=3 ROTATE="0" MOREROWS="0"-COLNAME=4 ROTATE="0" MOREROWS="0"-COLNAME=1 ROTATE="0" MOREROWS="0"IEEE 802.2COLNAME=2 ROTATE="0" MOREROWS="0"yesCOLNAME=3 ROTATE="0" MOREROWS="0"-COLNAME=4 ROTATE="0" MOREROWS="0"-COLNAME=1 ROTATE="0" MOREROWS="0"IEEE 802.2/SNAPCOLNAME=2 ROTATE="0" MOREROWS="0"yesCOLNAME=3 ROTATE="0" MOREROWS="0"yesCOLNAME=4 ROTATE="0" MOREROWS="0"yesCOLNAME=1 ROTATE="0" MOREROWS="0"LocalTalk/LAPCOLNAME=2 ROTATE="0" MOREROWS="0"-COLNAME=3 ROTATE="0" MOREROWS="0"-COLNAME=4 ROTATE="0" MOREROWS="0"yesCOLNAME=1 ROTATE="0" MOREROWS="0"ARCNETCOLNAME=2 ROTATE="0" MOREROWS="0"yesCOLNAME=3 ROTATE="0" MOREROWS="0"yesCOLNAME=4 ROTATE="0" MOREROWS="0"yesSPANNAME=SPAN1T4 ROTATE="0" MOREROWS="0"*Cannot use checksums, which might limit some applications.No single LAN frame type supports all protocols, and no single protocol runs over all frame types. Fortunately, the ODI driver specification permits a single interface to provide multiple frame types concurrently, so NetWare 4.1 servers can run any combination of protocols on the same physical interfaces.PAGENUM=7 ID="BP13"PAGENUM=8RENDERAS="SECT1"ID="FM56973"IDXID="w754"BOOK="_idx" COLLECTION="nw41" TIDREF="i2568"IDXID="w755"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"IDXID="w756"BOOK="_idx" COLLECTION="nw41" TIDREF="i2568"IDXID="w757"BOOK="_idx" COLLECTION="nw41" TIDREF="i2313"Configuration and ManagementNetWare 4.1 internetworking enhances the NetWare configuration process with a new version of INETCFG, a utility that guides you through the internetwork configuration with menus, windows, and context-sensitive help. For example, INETCFG provides facilities for configuring boards and protocols. This utility replaces an older style of configuration, which required you to edit IDXID="w758"BOOK="_idx" COLLECTION="nw41" TIDREF="i2138"IDXID="w759"BOOK="_idx" COLLECTION="nw41" TIDREF="i427"
LOAD and BIND commands manually.You can configure and manage all functions of the NetWare 4.1 protocols from the server's local console. All local operations, including server restart, are also available through remote console access. Refer to the BOOK="utlrfenu" COLLECTION="nw41"NetWare 4.1 Utilities Reference for more information about the NetWare remote console utility.The IDXID="w760"BOOK="_idx" COLLECTION="nw41" TIDREF="i2506"
MONITOR NLM file lets you view IPX and LAN interface statistics, as well as numerous system resources, such as memory pools, CPU usage, and NetWare Loadable ModuleTM (NLMTM) files.Management of the IPX, TCP/IP, and AppleTalk stacks is implemented through the Simple Network Management Protocol (SNMP) according to the most recent standard IDXID="w761"BOOK="_idx" COLLECTION="nw41" TIDREF="i2315"IDXID="w762"BOOK="_idx" COLLECTION="nw41" TIDREF="i2443"
Management Information Base (MIB) definitions for each protocol. The IDXID="w763"BOOK="_idx" COLLECTION="nw41" TIDREF="i4445"IDXID="w764"BOOK="_idx" COLLECTION="nw41" TIDREF="i312"IDXID="w765"BOOK="_idx" COLLECTION="nw41" TIDREF="i1989"
IPXCON, TCPCON, and ATCON NLM files use SNMP to examine protocol statistics and tables, and modify some parameters. You can manage the instrumented protocols with the Novell IDXID="w766"BOOK="_idx" COLLECTION="nw41" TIDREF="i2869"
NetWare Management SystemTM (NMSTM) product or any other SNMP-based console.LABEL="2"PAGENUM=9 ID="BP14"ID="FM97977"Using INETCFGThe Internetworking Configuration utility (INETCFG) is a menu-driven utility used to configure the NetWare® 4. 1 protocol software. It is installed during the installation of NetWare 4.1software.Both NetWare 4.1 and INETCFG support the use of the most popular data-link protocols (Ethernet, token ring, ARCNET, LocalTalk, and FDDI) and the most popular network protocols (IPXTM, TCP/IP, and AppleTalk). You can run INETCFG while the server is running. Each time the utility is used, it reads the existing AUTOEXEC.NCF file and optionally transfers any LOAD and BIND commands it finds to a configuration file that is referenced at system initialization (or reinitialization) time. This eliminates manual reconfiguration of existing servers; however, you should check configurations within INETCFG after the automated transfer of configuration information from an existing AUTOEXEC.NCF file.When you use INETCFG to save new configuration information, it also updates its databases and automatically creates the appropriate LOAD and BIND commands in the configuration file. To modify an existing configuration, select it from the appropriate menu and proceed through the menu hierarchy until the screen appears on which the change can be made.Although interfaces and protocols can be configured using INETCFG, most application services continue to be configured in AUTOEXEC.NCF using LOAD commands, such as LOAD NFS, LOAD AFP, LOAD ATPS, and so forth.PAGENUM=9 ID="BP15"PAGENUM=10This chapter explains the following aspects of INETCFG:MARK=BULLETIDREF="FM10421"IDREF="FM10421"When Configuration Changes Take EffectIDREF="FM10846"INETCFG MenusIDREF="FM38835"Using Command KeysIDREF="FM27568"Using Context-Sensitive HelpIDREF="FM11637"Loading INETCFGIDREF="FM39973"Reviewing the AUTOEXEC.NCF FileRENDERAS="SECT1"ID="FM10421"When IDXID="w767"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"
Configuration Changes Take EffectMost configuration changes take effect only after you bring down the system and restart it. For example, if you enable a disabled board, disable an enabled board, change parameters on a board, configure a new protocol, change the configuration of an existing protocol, bind a protocol to a network interface, and so forth, you must bring down and restart the system. This procedure is explained in detail at the appropriate points in the configuration procedures.Configuration changes to filters take effect immediately.RENDERAS="SECT1"IDXID="w768"BOOK="_idx" COLLECTION="nw41" TIDREF="i1790"IDXID="w769"BOOK="_idx" COLLECTION="nw41" TIDREF="i1790"ID="FM10846"INETCFG MenusINETCFG uses a series of menus, windows, and dialog boxes to configure related sets of parameters. This configuration interface allows you to enter names of new interfaces, specify parameters, and override defaults without having to use the command line.The items in the main menu (Internetworking Configuration) correspond to the basic steps used to configure NetWare 4.1 network connectivity. These items should be configured in the order presented in the following configuration procedures.PAGENUM=10 ID="BP16"PAGENUM=11The items displayed in the Internetworking Configuration main menu are explained in the following list:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Boards---Determines which LAN boards are used in the server. This option allows you to add new boards, modify the hardware parameters associated with the boards, enable or disable configured boards, or delete boards.CLASS=MENUITEM MOREINFO="NONE"Interfaces---Not used for LAN drivers.CLASS=MENUITEM MOREINFO="NONE"Protocols---Specifies global parameters for network layer protocols.CLASS=MENUITEM MOREINFO="NONE"Bindings---Enables a selected network protocol or bridge frame to be routed across a particular LAN interface.CLASS=MENUITEM MOREINFO="NONE"Manage Configuration---Enables you to perform the following tasks:MARK=BULLETConfigure SNMP information.Export/import configuration information to or from a disk file.Edit the AUTOEXEC.NCF file.CLASS=MENUITEM MOREINFO="NONE"View Configuration---Enables you to view the following information:MARK=BULLETAll LOAD and BIND commands.LAN board LOAD and BIND commands.Protocol commands.Board, interface, and protocol binding information in a matrix format. The summary can be saved to a file.Console messages captured during system restart or generated by the loaded modules.PAGENUM=11 ID="BP17"PAGENUM=12RENDERAS="SECT1"IDXID="w770"BOOK="_idx" COLLECTION="nw41" TIDREF="i1790"ID="FM38835"Using Command KeysIDXID="w771"BOOK="_idx" COLLECTION="nw41" TIDREF="i1653"
The bottom line of each INETCFG screen shows the command keys that can be used on that screen and the action that the key performs.MARK=BULLETIDXID="w772"BOOK="_idx" COLLECTION="nw41" TIDREF="i1589"IDXID="w773"BOOK="_idx" COLLECTION="nw41" TIDREF="i1790"IDXID="w774"BOOK="_idx" COLLECTION="nw41" TIDREF="i2022"
The MOREINFO="NONE"<Esc> key exits the current configuration window or help screen and returns you to the previous screen. Press MOREINFO="NONE"<Esc> from the main screen to exit the program and save your configuration changes.The MOREINFO="NONE"<Enter> key allows you to view a list of configuration options or modify the selected option's configuration.The MOREINFO="NONE"<Ins> key adds a new configuration.The MOREINFO="NONE"<Del> key deletes a configured option.The MOREINFO="NONE"<Up-arrow> and MOREINFO="NONE"<Down-arrow> keys move the highlight bar up and down through the available choices to indicate the current selection.Other keys might be meaningful in specific screens. If so, these command keys and their functions are displayed at the bottom of that particular screen.RENDERAS="SECT1"IDXID="w775"BOOK="_idx" COLLECTION="nw41" TIDREF="i1790"ID="FM27568"Using Context-Sensitive HelpINETCFG provides three levels of context-sensitive help in most of its menu levels; some menus have only two levels.MARK=BULLETContext-sensitive help is displayed in a single "fast help" line across the bottom of the screen. The text displayed is specific to the currently selected menu option, the parameter where the cursor is positioned, or the active window. It describes the significance of a menu option, provides help in specifying a parameter, or tells you the purpose of a window.Full context-sensitive help is displayed when you press the MOREINFO="NONE"<F1> key while a menu or parameter screen is displayed. It provides more comprehensive information than the "fast help." If the help message contains more than one screen, you can use the MOREINFO="NONE"<Page Down> and MOREINFO="NONE"<Page Up> keys to view the other screens.PAGENUM=13 ID="BP18"More general screen-oriented help is displayed when you press MOREINFO="NONE"<F1> a second time while viewing the full context-sensitive help. This second level of help explains the overall purpose of the menu or parameter screen from which help was requested.Press MOREINFO="NONE"<Esc> one time to exit each level of help screens. For example, if you are in a second-level help screen, you must press MOREINFO="NONE"<Esc> twice to exit help completely.RENDERAS="SECT1"ID="FM11637"Loading IDXID="w776"BOOK="_idx" COLLECTION="nw41" TIDREF="i1790"IDXID="w777"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
INETCFGIf INETCFG is not running, complete the following steps to load it:PERFORMANCE="REQUIRED"At the server prompt, type: FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>Each time INETCFG is run on the system, you are given the opportunity to import LOAD and BIND commands, if any are present, from your existing AUTOEXEC.NCF file to a new configuration file. This is an automatic process that transfers network interface and protocol-related command lines, then comments out those lines in AUTOEXEC.NCF.This process does not affect LOAD commands for other application-level services (for example, LOAD NFS, LOAD AFP, and LOAD ATPS).If there are no LOAD or BIND commands in your AUTOEXEC.NCF file, the Internetworking Configuration main menu is displayed. Go directly to 
IDREF="FM13724"Chapter 3, "Configuring Boards," to continue the configuration.
PAGENUM=13 ID="BP19"PAGENUM=14PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> as prompted.A new window displays the following prompt:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Transfer LAN driver, protocol and remote
    access commands?At this point, you must choose whether to allow INETCFG to import these command lines automatically or to transfer them yourself.INETCFG saves your old AUTOEXEC.NCF file to the backup file SYS:/SYSTEM/AUTOEXEC.BAK; if you must restore this file later, copy it to AUTOEXEC.NCF and restart the server.PERFORMANCE="REQUIRED"You should select 
CLASS=MENUITEM MOREINFO="NONE"Yes to transfer these commands automatically to INETCFG, then press 
MOREINFO="NONE"<Enter>.If you select 
CLASS=MENUITEM MOREINFO="NONE"No, refer to the instructions in the 
BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.INETCFG requires that all driver (*.LAN or *.LDI) files reside in the SYS:/SYSTEM directory. If INETCFG finds references to a file in another directory, it asks whether you want to copy the file to SYS:/SYSTEM during the import process. Press MOREINFO="NONE"<Enter> to acknowledge the message, then press MOREINFO="NONE"<Enter> again to copy the driver file.If INETCFG cannot import a line, it notifies you with an error message. (Such messages often indicate a syntax error in an AUTOEXEC.NCF file.)PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to acknowledge this message.INETCFG checks the AUTOEXEC.NCF file for initialization commands on entry and exit. If your AUTOEXEC.NCF file does not contain these commands, INETCFG asks the following question:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Add Initialization Commands to
   AUTOEXEC.NCF?PAGENUM=14 ID="BP20"PAGENUM=15If you respond 
Yes, INETCFG comments out the imported lines and adds the initialization commands defined in 
IDREF="FM40132"Table 2-1 after those that set the internal IPX network number, the file server name, and other NetWare operating parameters.LABEL="2-1" PGWIDE=0 TOCENTRY="1"ID="FM40132"Commands Inserted in the New AUTOEXEC.NCF FileCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"CommandCOLNAME=2 ROTATE="0" MOREROWS="0"ActionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"LOAD CONLOG COLNAME=2 ROTATE="0" MOREROWS="0"Loads a utility that captures the console messages generated during system initialization and writes the messages into the file ETC/CONSOLE.LOG. These messages can be viewed later to help troubleshoot your server installation, if necessary.To save disk space, use the CONLOG parameter "Maximum = X", where X is the maximum size of the console log in kilobytes. When the log reaches this maximum, the older entries are overwritten by new entries.COLNAME=1 ROTATE="0" MOREROWS="0"INITSYS.NCFCOLNAME=2 ROTATE="0" MOREROWS="0"Initializes your system with the configuration information entered by INETCFG.COLNAME=1 ROTATE="0" MOREROWS="0"UNLOAD CONLOGCOLNAME=2 ROTATE="0" MOREROWS="0"Placed at the end of the file, this command stops the logging of console messages when startup is complete. It is inserted automatically if it was present in the original AUTOEXEC.NCF file, or the user can insert it manually.To support other applications, you might also have existing LOAD commands for IPXS, TLI, AFTER311, STREAMSTM, or any combination of these NLMTM files. The INETCFG AUTOEXEC conversion program adds those command lines above the automatically inserted INITSYS command line (which includes a LOAD SNMP command line). SNMP depends on these NLM files, and its LOAD command must be located after these NLM LOAD commands. SNMP automatically loads these NLM files if you do not have explicit LOAD commands. INETCFG does not let you know that these command lines have been moved. IDXID="w778"BOOK="_idx" COLLECTION="nw41" TIDREF="i4184"IDXID="w779"BOOK="_idx" COLLECTION="nw41" TIDREF="i2140"PAGENUM=15 ID="BP21"PAGENUM=16RENDERAS="SECT1"ID="FM39973"Reviewing the AUTOEXEC.NCF FileIf you want to review the new AUTOEXEC.NCF file and the translated commands before you continue, perform these steps:PERFORMANCE="REQUIRED"From the Internetworking Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"Manage Configuration, then press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Select the last entry, 
CLASS=MENUITEM MOREINFO="NONE"Edit AUTOEXEC.NCF, then press 
MOREINFO="NONE"<Enter>.The new AUTOEXEC.NCF file is displayed. You can edit the file manually.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save your changes, then press 
MOREINFO="NONE"<Esc> again to return to the Internetworking Configuration menu.LABEL="3"PAGENUM=17 ID="BP22"ID="FM13724"Configuring BoardsWhen you select and configure a LAN board, you are actually configuring one or more physical interfaces that correspond to individual connections over which packets are sent and received. Configuring a board causes the driver associated with the board to load each time you initialize the server.Most drivers that are compatible with the NetWare® 4.1 protocol software have a IDXID="w780"BOOK="_idx" COLLECTION="nw41" TIDREF="i1227"IDXID="w781"BOOK="_idx" COLLECTION="nw41" TIDREF="i2096"driver description file that defines the hardware parameters necessary for the driver to operate with the board you select. This file has the ".LDI" extension, and also specifies the valid range of values for each parameter. If a driver has an LDI file, the parameters associated with that driver are presented in the Board Configuration window; you simply choose a value for each parameter. If a driver has no LDI file, you must enter the required values in the Board Parameters field.This chapter explains the following tasks:MARK=BULLETIDREF="FM34011"Configuring a LAN BoardIDREF="FM31286"Enabling or Disabling a LAN BoardIDREF="FM23675"Deleting a LAN BoardPAGENUM=17 ID="BP23"PAGENUM=18RENDERAS="SECT1"IDXID="w782"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"IDXID="w783"BOOK="_idx" COLLECTION="nw41" TIDREF="i4811"ID="FM34011"Configuring a LAN BoardConfiguring, or reconfiguring, a board involves choosing a driver for the board, assigning a name to the board, and specifying values for the board parameters. To configure or reconfigure a board, complete the following steps:PERFORMANCE="REQUIRED"At the server prompt, type:IDXID="w784"BOOK="_idx" COLLECTION="nw41" TIDREF="i1790"FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Boards, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Configured Boards window is displayed.If you are configuring a new board, continue with IDREF="FM73933"Step 3.If you are changing an existing board configuration, select that board, press 
MOREINFO="NONE"<Enter>, then continue with IDREF="FM29012"Step 6.The 
CLASS=MENUITEM MOREINFO="NONE"Configured Boards window displays a list of configured boards with the following 
IDXID="w785"BOOK="_idx" COLLECTION="nw41" TIDREF="i482"
information:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Board Name---Name you assign to the board.IDXID="w786"BOOK="_idx" COLLECTION="nw41" TIDREF="i483"CLASS=MENUITEM MOREINFO="NONE"Driver---Name of the driver associated with the board.IDXID="w787"BOOK="_idx" COLLECTION="nw41" TIDREF="i1226"CLASS=MENUITEM MOREINFO="NONE"Int---Interrupt request level (IRQ) used by the board.IDXID="w788"BOOK="_idx" COLLECTION="nw41" TIDREF="i1880"CLASS=MENUITEM MOREINFO="NONE"IOAddr---Base input/output port address for the board.IDXID="w789"BOOK="_idx" COLLECTION="nw41" TIDREF="i1996"CLASS=MENUITEM MOREINFO="NONE"MemAddr---Base memory address of the board.IDXID="w790"BOOK="_idx" COLLECTION="nw41" TIDREF="i2376"CLASS=MENUITEM MOREINFO="NONE"Slot---Number of the slot where the board is installed.IDXID="w791"BOOK="_idx" COLLECTION="nw41" TIDREF="i4169"CLASS=MENUITEM MOREINFO="NONE"Status---Status of the board, which is "Enabled" by default.IDXID="w792"BOOK="_idx" COLLECTION="nw41" TIDREF="i4284"CLASS=MENUITEM MOREINFO="NONE"Comment---Comment you enter about the board or its configuration.Not every board-driver configuration requires all this information; in fact, some configurations require other, link-specific parameters that are not shown in the CLASS=MENUITEM MOREINFO="NONE"Configured Boards window.PAGENUM=19 ID="BP24"PERFORMANCE="REQUIRED"ID="FM73933"Press 
MOREINFO="NONE"<Ins> to display the list of available drivers.PERFORMANCE="REQUIRED"Scroll through the list, select the appropriate driver for the first LAN board installed in your system, then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If you select a driver, the 
CLASS=MENUITEM MOREINFO="NONE"Board Configuration window for that driver is displayed. Continue with IDREF="FM34492"Step 5.If the driver has an LDI file, the parameters you need to configure for the board are displayed as separate fields in the window.If the driver has no LDI file, only the CLASS=MENUITEM MOREINFO="NONE"Board Name, CLASS=MENUITEM MOREINFO="NONE"Board Parameters, and CLASS=MENUITEM MOREINFO="NONE"Comment fields are provided as a means for entering the parameters manually.PERFORMANCE="REQUIRED"ID="FM98610"If the driver you need is not listed, press 
MOREINFO="NONE"<Ins> again.The CLASS=MENUITEM MOREINFO="NONE"New Driver window is displayed. You must now tell the system where to copy the driver from.PERFORMANCE="REQUIRED"Enter the full path name of the driver at the > prompt, then press 
MOREINFO="NONE"<Enter>.If INETCFG cannot find the driver file you enter, the message "MOREINFO="NONE"Driver file not found" is displayed.You can also use this window for copying drivers and NLMTM files from a floppy diskette to the SYS:/SYSTEM directory.IDXID="w793"BOOK="_idx" COLLECTION="nw41" TIDREF="i1227"IDXID="w794"BOOK="_idx" COLLECTION="nw41" TIDREF="i2096"
To add a driver to the list of available drivers, insert the diskette containing the driver in one of the disk drives, specify the complete path and filename of the driver (for example, A:\NEWDRV\DRIVER), then pressMOREINFO="NONE" <Enter>. The driver and its description file, if any, are copied into the SYS:SYSTEM directory. (Note the file extension is not required.)PERFORMANCE="REQUIRED"ID="FM34492"Enter a name in the 
CLASS=MENUITEM MOREINFO="NONE"Board Name field, then press 
MOREINFO="NONE"<Enter>.You can use up to 10 alphanumeric characters for the board name.
IDXID="w795"BOOK="_idx" COLLECTION="nw41" TIDREF="i4807"IDXID="w796"BOOK="_idx" COLLECTION="nw41" TIDREF="i4808"PAGENUM=19 ID="BP25"PAGENUM=20PERFORMANCE="REQUIRED"ID="FM29012"Specify the board parameters:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If the driver selected has a description file, the parameters are listed as separate fields. Highlight each field, press 
MOREINFO="NONE"<Enter>, and select the appropriate value for the parameter from the pop-up menu displayed.Use the context-sensitive help text if you need an explanation about any parameter. Highlight the parameter and press MOREINFO="NONE"<F1> to display the help text. Press the MOREINFO="NONE"<Esc> key to exit the help screen. When in doubt, accept the default values.PERFORMANCE="REQUIRED"If the driver selected does not have a description file, the 
CLASS=MENUITEM MOREINFO="NONE"Board Configuration Without A Driver Description File window is displayed. You must type the load line parameters in the 
CLASS=MENUITEM MOREINFO="NONE"Board Parameters field; use the following as an example:MOREINFO="NONE"PORT=300 INT=3These parameters are appended to the "LOAD driver" line.INETCFG automatically manages frame types. Do not put a "frame =" option in the CLASS=MENUITEM MOREINFO="NONE"Board Parameters field.PERFORMANCE="REQUIRED"If you want, enter some descriptive text in the 
CLASS=MENUITEM MOREINFO="NONE"Comment field.PERFORMANCE="REQUIRED"ID="FM41538"Press 
MOREINFO="NONE"<Esc>, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save changes to the board configuration, then press 
MOREINFO="NONE"<Enter>.IDXID="w797"BOOK="_idx" COLLECTION="nw41" TIDREF="i481"
If there are any conflicts with the hardware parameters of other boards, one or more messages describe them. You must determine whether the conflict is acceptable or whether it interferes with the operation of the server and, if necessary, resolve it.The 
CLASS=MENUITEM MOREINFO="NONE"Configured Boards window is redisplayed with the board you just configured. Note that the board status is 
CLASS=MENUITEM MOREINFO="NONE"Enabled; you can use the 
MOREINFO="NONE"<Tab> key to toggle between 
CLASS=MENUITEM MOREINFO="NONE"Enabled and 
CLASS=MENUITEM MOREINFO="NONE"Disabled.LAN boards with a single network interface need no further configuration; however, an Enabled driver does not get loaded unless a protocol is bound to it.PERFORMANCE="REQUIRED"To configure the remaining boards, if any, repeat 
IDREF="FM73933"Step 3 through 
IDREF="FM41538"Step 7.PERFORMANCE="REQUIRED"When you are finished, press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.
PAGENUM=21 ID="BP26"RENDERAS="SECT1"ID="FM31286"Enabling or Disabling a LAN BoardIDXID="w798"BOOK="_idx" COLLECTION="nw41" TIDREF="i1847"IDXID="w799"BOOK="_idx" COLLECTION="nw41" TIDREF="i1847"
To enable or disable a LAN board, complete the following steps:PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Boards, then press 
MOREINFO="NONE"<Enter>.A new window displays the list of configured boards.PERFORMANCE="REQUIRED"Highlight the board you want to enable (or disable), then press 
MOREINFO="NONE"<Tab>.The status of the board is changed from 
CLASS=MENUITEM MOREINFO="NONE"Disabled to 
CLASS=MENUITEM MOREINFO="NONE"Enabled (or 
CLASS=MENUITEM MOREINFO="NONE"Enabled to 
CLASS=MENUITEM MOREINFO="NONE"Disabled). The 
MOREINFO="NONE"<Tab> key acts as a toggle switch.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.RENDERAS="SECT1"ID="FM23675"Deleting a LAN BoardIDXID="w800"BOOK="_idx" COLLECTION="nw41" TIDREF="i1847"
To delete a LAN board, complete the following steps:PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Boards, then press 
MOREINFO="NONE"<Enter>.A new window displays the list of configured boards.PERFORMANCE="REQUIRED"Highlight the board you want to delete, then press 
MOREINFO="NONE"<Delete>.A message is displayed indicating that deleting the board also deletes all existing binds to the board's interfaces.
PAGENUM=22 ID="BP27"PERFORMANCE="REQUIRED"When prompted, select 
CLASS=MENUITEM MOREINFO="NONE"Yes, then press 
MOREINFO="NONE"<Enter> to delete the board.The board is removed from the list of configured boards.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.LABEL="4"PAGENUM=23 ID="BP28"ID="FM34215"Configuring NetWare IPXThis chapter describes how to configure basic NetWare® 4.1 IPX RouterTM software. It assumes you are willing to accept the system defaults for most parameters; however, you can configure other parameters if your needs extend beyond this configuration. To get information about any of the parameters you see on the IPXTM configuration screens, highlight the parameter, then press MOREINFO="NONE"<F1>.For more detailed conceptual information, as well as detailed parameter descriptions, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide or the BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.Specifically, this chapter explains the following tasks:MARK=BULLETIDREF="FM36493"Configuring IPX Protocol ParametersIDREF="FM24309"Binding IPX to a LAN InterfaceBefore you can bind IPX to any interface, you must configure the network interface boards for your server. See IDREF="FM13724"Chapter 3, "Configuring Boards."PAGENUM=23 ID="BP29"PAGENUM=24RENDERAS="SECT1"IDXID="w801"BOOK="_idx" COLLECTION="nw41" TIDREF="i759"IDXID="w802"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"ID="FM36493"Configuring IPX Protocol ParametersFor the most basic NetWare IPX Router configuration, you need only enable the CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding option as described here. You can (and should) accept the defaults on all the other parameters. To configure the IPX protocol parameters, complete the following steps:PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Protocols, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"IPX, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"IPX Configuration window is displayed.PERFORMANCE="REQUIRED"If this machine is to function as a router, the 
CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding option must be enabled. If it is disabled, select 
CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding, press 
MOREINFO="NONE"<Enter>, select 
CLASS=MENUITEM MOREINFO="NONE"Enable, then press 
MOREINFO="NONE"<Enter>.IDXID="w803"BOOK="_idx" COLLECTION="nw41" TIDREF="i3174"
This option enables or disables the forwarding of incoming IPX packets. Disabling IPX packet forwarding is equivalent to setting the LOAD command-line option ROUTING to NONE. Use this parameter carefully; disabling packet forwarding disables all IPX routing on the server.It is not necessary to change the values of any of the other parameters in this window. Leave all other parameters at their default values. For a complete discussion of other parameters displayed in this window, see the 
BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.
PAGENUM=24 ID="BP30"PAGENUM=25PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>; if prompted, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save changes to the configuration, then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.You can now bind the IPX protocol to a LAN interface, as described in the section that follows.RENDERAS="SECT1"ID="FM24309"Binding IPX to a LAN InterfaceAfter you configure the IPX protocol parameters, complete the following steps to bind IPX to a LAN interface:IDXID="w804"BOOK="_idx" COLLECTION="nw41" TIDREF="i464"IDXID="w805"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Bindings, then press 
MOREINFO="NONE"<Enter>.A new window displays a list of the configured protocol-to-network interface bindings.If you are creating a new configuration, continue with 
IDREF="FM32198"Step 3.If you are changing an existing configuration, select that configuration, press 
MOREINFO="NONE"<Enter>, then continue with 
IDREF="FM33915"Step 6.PERFORMANCE="REQUIRED"ID="FM32198"Press 
MOREINFO="NONE"<Ins>.A new window displays a list of the configured protocols.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"IPX, then press
MOREINFO="NONE" <Enter>.A new window displays a list of the configured network interfaces.PERFORMANCE="REQUIRED"Select a LAN board from the list, then press
MOREINFO="NONE" <Enter>.A new window displays parameters for binding IPX to a LAN interface.
PAGENUM=26 ID="BP31"PERFORMANCE="REQUIRED"ID="FM33915"The 
CLASS=MENUITEM MOREINFO="NONE"IPX Network Number selection is highlighted. Enter a valid IPX network number, then press
MOREINFO="NONE" <Enter>.The IPX network number is the four-byte network number assigned to the board. The range is 00000001-FFFFFFFE.
IDXID="w806"BOOK="_idx" COLLECTION="nw41" TIDREF="i1940"IDXID="w807"BOOK="_idx" COLLECTION="nw41" TIDREF="i2870"PERFORMANCE="REQUIRED"The 
CLASS=MENUITEM MOREINFO="NONE"Frame Type selection is highlighted. Press 
MOREINFO="NONE"<Enter> to select the Frame Type from the pop-up list displayed.The options displayed in the pop-up list depend on the network medium.
IDXID="w808"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"It is not necessary to change the values of any other bind options in this window. Leave all other options at their default values. For detailed information about the other options, see the 
BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide or the 
BOOK="ipxrtenu" COLLECTION="nw41"NetWare 4.1 IPX Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>; if prompted, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save changes to the configuration, then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.To implement a new IPX binding to a LAN interface, you must issue the REINITIALIZE SYSTEM command at the server console or restart the server.To implement changes to an existing IPX binding to a LAN interface, you must issue the UNBIND IPX FROM <
Boardname> command at the server console, followed by the REINITIALIZE SYSTEM command, or restart the server.LABEL="5"PAGENUM=27 ID="BP32"ID="FM52856"Configuring TCP/IPThis chapter describes how to configure basic TCP/IP support. It assumes you are willing to accept the system defaults for most parameters; however, you can configure other parameters if your needs extend beyond this basic configuration. To get information about any of the parameters on the IP configuration screens, highlight the parameter, then press MOREINFO="NONE"<F1>.For more detailed conceptual information as well as detailed parameter descriptions, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide or the BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference.Specifically, this chapter explains the following tasks:MARK=BULLETIDREF="FM11433"Configuring TCP/IP Protocol ParametersIDREF="FM22976"Binding TCP/IP to a LAN InterfaceBefore you can bind TCP/IP to any interface, you must configure the network interface boards for your server. See IDREF="FM13724"Chapter 3, "Configuring Boards."PAGENUM=27 ID="BP33"PAGENUM=28RENDERAS="SECT1"ID="FM11433"IDXID="w809"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w810"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w811"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w812"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"Configuring TCP/IP Protocol ParametersFor the most basic IP server configuration, you need only enable the CLASS=MENUITEM MOREINFO="NONE"TCP/IP Status option as described here. If you want your server to also act as a router, enable the CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding option. You can (and should) accept the defaults on all the other parameters.To configure the TCP/IP protocol parameters, complete the following steps:IDXID="w813"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w814"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Protocols, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP Configuration window is displayed.PERFORMANCE="REQUIRED"The 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP Status option is selected. If it is disabled, press 
MOREINFO="NONE"<Enter>, select 
CLASS=MENUITEM MOREINFO="NONE"Enable, then press 
MOREINFO="NONE"<Esc>.
IDXID="w815"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w816"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"PERFORMANCE="REQUIRED"If this machine is to function as a router, the 
CLASS=MENUITEM MOREINFO="NONE"IP Packet Forwarding option must be enabled. 
IDXID="w817"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w818"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"If this machine is to function as an end node, do not enable the 
CLASS=MENUITEM MOREINFO="NONE"IP Packet Forwarding option.It is not necessary to change the values of any of the other parameters in this window. Leave all other parameters at their default values. For a complete discussion of other parameters displayed in this window, see the 
BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.
PAGENUM=28 ID="BP34"PAGENUM=29PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>; if prompted, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save changes to the protocol configuration, then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.You can now bind the TCP/IP protocol to a LAN interface, as described in the section that follows.RENDERAS="SECT1"ID="FM22976"Binding IDXID="w819"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w820"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"
TCP/IP to a LAN InterfaceAfter you configure the TCP/IP protocol parameters, complete the following steps to bind TCP/IP to a LAN interface:IDXID="w821"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Bindings, then press 
MOREINFO="NONE"<Enter>.A new window displays a list of the configured protocol-to-network interface bindings.If you are creating a new configuration, continue with 
IDREF="FM37095"Step 3.If you are changing an existing configuration, select that configuration, press 
MOREINFO="NONE"<Enter>, then continue with 
IDREF="FM32797"Step 6.PERFORMANCE="REQUIRED"ID="FM37095"Press 
MOREINFO="NONE"<Ins>.A new window displays a list of the configured protocols.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"TCP/IP, then press 
MOREINFO="NONE"<Enter>.A new window displays a list of the configured network interfaces.PERFORMANCE="REQUIRED"Select a LAN board from the list, then press 
MOREINFO="NONE"<Enter>.A new window displays the parameters for binding TCP/IP to a LAN interface.
PAGENUM=30 ID="BP35"PERFORMANCE="REQUIRED"ID="FM32797"The 
CLASS=MENUITEM MOREINFO="NONE"IDXID="w822"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w823"BOOK="_idx" COLLECTION="nw41" TIDREF="i2166"
Local IP Address selection is already highlighted. Enter the IP address assigned to this interface, then press 
MOREINFO="NONE"<Enter>.This is the node's local IP address on the network connected to this interface. The address must be entered as four decimal or hexadecimal numbers separated by dots (for example, 123.45.6.7). Each IP address on an IP internetwork must be unique and is usually assigned by the network administrator.PERFORMANCE="REQUIRED"The 
CLASS=MENUITEM MOREINFO="NONE"IDXID="w824"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w825"BOOK="_idx" COLLECTION="nw41" TIDREF="i4319"
Subnetwork Mask of Connected Network selection is highlighted. Enter the subnetwork mask of the network attached to this interface, then press 
MOREINFO="NONE"<Enter>.This setting must match the mask used by the other nodes on the network. You can enter the subnetwork mask in decimal or hexadecimal form.If you do not specify the mask, the standard IP network mask is used. You can use the default subnetwork mask if your network is not subnetted. In the standard mask, each bit of the address network number is set to one and each bit of the address host number is set to zero (FF.0.0.0).It is not necessary to change the values of any other parameters in this window. Leave all other parameters at their default values. For more information about subnetwork masks or any of the other parameters displayed in this window, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide or the 
BOOK="tcpipenu" COLLECTION="nw41"NetWare 4.1 TCP/IP Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>; if prompted, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save changes to the configuration, then press 
MOREINFO="NONE"<Enter>.A new window displays the configured protocol-to-interface bindings. The TCP/IP binding you just configured is highlighted in the list.
PAGENUM=30 ID="BP36"PAGENUM=31PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.To implement a new TCP/IP binding to a LAN interface, you must issue the REINITIALIZE SYSTEM command at the server console or restart the server.To implement changes to an existing TCP/IP binding to a LAN interface, you must issue the UNBIND TCP/IP FROM <
BoardName> command at the server console, followed by the REINITIALIZE SYSTEM command, or restart the server.
CLASS=MENUITEM MOREINFO="NONE"IDXID="w826"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w827"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w828"BOOK="_idx" COLLECTION="nw41" TIDREF="i4813"CLASS=MENUITEM MOREINFO="NONE"LABEL="6"PAGENUM=33 ID="BP37"ID="FM75172"Configuring AppleTalkThis chapter describes how to configure basic AppleTalk support. It assumes you are willing to accept the system defaults for most parameters; however, you can configure other parameters if your needs extend beyond this basic configuration. To get more information about any of the parameters on the AppleTalk configuration screens, highlight the parameter, then press MOREINFO="NONE"<F1>.For more detailed conceptual information, as well as parameter descriptions, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide or the BOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* Reference.Specifically, this chapter explains the following tasks:MARK=BULLETIDREF="FM11560"Configuring AppleTalk Protocol ParametersIDREF="FM38605"Binding AppleTalk to a LAN InterfaceBefore you can bind AppleTalk to any interface, you must configure the network interface boards for your server. See IDREF="FM13724"Chapter 3, "Configuring Boards."PAGENUM=33 ID="BP38"PAGENUM=34RENDERAS="SECT1"ID="FM11560"Configuring AppleTalk Protocol ParametersFor the most basic AppleTalk server configuration, you need only enable the CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding option as described here. You can (and should) accept the defaults on all the other parameters.To configure the AppleTalk protocol parameters, complete the following steps:PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Protocols, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"AppleTalk, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"AppleTalk Configuration window is displayed.PERFORMANCE="REQUIRED"If this machine is to function as a router, the 
CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding option must be enabled.If this machine is to function as an end node, do not enable the 
CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding option.It is not necessary to change the values of any other parameters in this window. Leave all other parameters at their default values. For a complete discussion of the other parameters displayed in this window, see the 
BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide or the BOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* Reference.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc>; if prompted, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save changes to the configuration, then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.You can now bind AppleTalk to a LAN interface, as specified in the section that follows.
PAGENUM=35 ID="BP39"RENDERAS="SECT1"ID="FM38605"Binding AppleTalk to a LAN InterfaceThe following procedure assumes that the server is being attached to an existing AppleTalk network from which it will derive its configuration. Refer to the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide for information about configuring a seed interface.After you configure the AppleTalk protocol parameters, complete the following steps to bind AppleTalk to a LAN interface:PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Bindings, then press 
MOREINFO="NONE"<Enter>.A new window displays a list of the configured protocol-to-network interface bindings.If you are creating a new configuration, continue with 
IDREF="FM30333"Step 3.If you are changing an existing configuration, select that configuration, press 
MOREINFO="NONE"<Enter>, then continue with 
IDREF="FM38345"Step 6.PERFORMANCE="REQUIRED"ID="FM30333"Press 
MOREINFO="NONE"<Ins>.A new window displays a list of the configured protocols.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"AppleTalk, then press 
MOREINFO="NONE"<Enter>.A new window displays a list of the configured network interfaces.PERFORMANCE="REQUIRED"Select a LAN board from the list, then press 
MOREINFO="NONE"<Enter>.If the board you select has an Ethernet interface, the 
CLASS=MENUITEM MOREINFO="NONE"Types of AppleTalk Networks window is displayed. Continue with 
IDREF="FM38345"Step 6. If the board you select has any other type of LAN interface, this selection is made for you. Skip 
IDREF="FM38345"Step 6 and continue with 
IDREF="FM31526"Step 7.PERFORMANCE="REQUIRED"ID="FM38345"Select a type of AppleTalk network: 
CLASS=MENUITEM MOREINFO="NONE"Extended Network or 
CLASS=MENUITEM MOREINFO="NONE"Non-Extended Network, then press 
MOREINFO="NONE"<Enter>.
PAGENUM=36 ID="BP40"A new window for binding AppleTalk to a LAN interface is displayed. For information about the difference between extended and non-extended networks, see the BOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* Reference.It is not necessary to change the values of any other parameters in this window. Leave all other parameters at their default values. For a complete discussion of the other parameters displayed in this window, see the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide or the 
BOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* Reference.PERFORMANCE="REQUIRED"ID="FM31526"Press 
MOREINFO="NONE"<Esc>, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save the changes to the configuration, then press 
MOREINFO="NONE"<Enter>.A new window displays the configured protocol-to-interface bindings. The AppleTalk binding you just configured is highlighted in the list.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.To implement a new AppleTalk binding to a LAN interface, you must issue the REINITIALIZE SYSTEM command at the server console or restart the server.To implement changes to an existing AppleTalk binding to a LAN interface, you must issue the UNBIND APPLETALK FROM <
BoardName> command at the server console, followed by the REINITIALIZE SYSTEM command, or restart the server.LABEL="7"PAGENUM=37 ID="BP41"ID="FM89421"Configuring Remote ManagementSNMP enables network management clients to exchange information about the configuration and status of nodes on an internetwork. The information available is defined by a set of managed objects referred to as the Management Information Base (MIB).IDXID="w829"BOOK="_idx" COLLECTION="nw41" TIDREF="i2315"IDXID="w830"BOOK="_idx" COLLECTION="nw41" TIDREF="i2443"This chapter describes how to configure SNMP information and set up the remote configuration for this node. Specifically, this chapter explains the following tasks:MARK=BULLETConfiguring SNMP InformationSetting up Remote AccessRENDERAS="SECT1"Configuring SNMP InformationTo configure SNMP information for a specific node, complete the following steps:IDXID="w831"BOOK="_idx" COLLECTION="nw41" TIDREF="i4187"PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Configure SNMP Parameters, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"SNMP Parameters window is displayed.
PAGENUM=38 ID="BP42"PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"SNMP Parameters window, select 
CLASS=MENUITEM MOREINFO="NONE"Monitor State, then press 
MOREINFO="NONE"<Enter>.IDXID="w832"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w833"BOOK="_idx" COLLECTION="nw41" TIDREF="i2508"
The following options allow you to indicate how the SNMP Agent handles SNMP read operations coming from outside this node.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Any CommunityMay ReadCOLNAME=2 ROTATE="0" MOREROWS="0"Allows all read operations no matter what community name is provided in the incoming read request.COLNAME=1 ROTATE="0" MOREROWS="0"Leave as Default SettingCOLNAME=2 ROTATE="0" MOREROWS="0"Avoids changing the Monitor Community name from its default (which is usually "public"). The default Monitor Community can still be changed manually through SNMP command-line options.COLNAME=1 ROTATE="0" MOREROWS="0"No Community May ReadCOLNAME=2 ROTATE="0" MOREROWS="0"Disables all read operations no matter what community name is provided in the incoming read request.COLNAME=1 ROTATE="0" MOREROWS="0"Specified Community May ReadCOLNAME=2 ROTATE="0" MOREROWS="0"Allows only read operations that contain the name specified in the Monitor Community field.PERFORMANCE="REQUIRED"Select one of the options described above and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"If you selected 
CLASS=MENUITEM MOREINFO="NONE"Specified Community May Read, enter a name in the 
CLASS=MENUITEM MOREINFO="NONE"Monitor Community field and press 
MOREINFO="NONE"<Enter>.
IDXID="w834"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w835"BOOK="_idx" COLLECTION="nw41" TIDREF="i2505"Enter the name of the community that is allowed to read management information. SNMP management stations that belong to this community can read the network management database.
PAGENUM=38 ID="BP43"PAGENUM=39PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Control State, then press 
MOREINFO="NONE"<Enter>.IDXID="w836"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w837"BOOK="_idx" COLLECTION="nw41" TIDREF="i825"The following options allow you to indicate how the SNMP Agent handles SNMP write operations coming from outside this node.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Any CommunityMay WriteCOLNAME=2 ROTATE="0" MOREROWS="0"Allows all set operations no matter what community name is provided in the incoming read request.COLNAME=1 ROTATE="0" MOREROWS="0"Leave as Default SettingCOLNAME=2 ROTATE="0" MOREROWS="0"Avoids changing the Control Community from its default, which is usually not to allow any write requests. The default can be changed manually through SNMP command-line options.COLNAME=1 ROTATE="0" MOREROWS="0"No Community May WriteCOLNAME=2 ROTATE="0" MOREROWS="0"Disables all set operations no matter what community name is provided in the incoming read request.COLNAME=1 ROTATE="0" MOREROWS="0"Specified Community May WriteCOLNAME=2 ROTATE="0" MOREROWS="0"Allows only set operations that contain the name specified in the Control Community field.PERFORMANCE="REQUIRED"Select one of the options described above and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"If you selected 
CLASS=MENUITEM MOREINFO="NONE"Specified Community May Write, enter a name in the 
CLASS=MENUITEM MOREINFO="NONE"Control Community field and press 
MOREINFO="NONE"<Enter>.
IDXID="w838"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w839"BOOK="_idx" COLLECTION="nw41" TIDREF="i820"Enter the name of the community that is allowed to read and write management information. SNMP management stations that belong to this community can read or modify any value in the network management database.
PAGENUM=39 ID="BP44"PAGENUM=40PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Trap State, then press 
MOREINFO="NONE"<Enter>.IDXID="w840"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w841"BOOK="_idx" COLLECTION="nw41" TIDREF="i4570"The following options allow you to indicate how the SNMP Agent handles SNMP trap operations coming from outside this node.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Do Not Send TrapsCOLNAME=2 ROTATE="0" MOREROWS="0"Disables all SNMP traps no matter what community name is provided in the incoming trap request.COLNAME=1 ROTATE="0" MOREROWS="0"Leave as Default SettingCOLNAME=2 ROTATE="0" MOREROWS="0"Avoids changing the Trap Community from its default (which is usually "public"). The default can still be changed manually through SNMP command-line options.COLNAME=1 ROTATE="0" MOREROWS="0"Send Traps With Specified Community COLNAME=2 ROTATE="0" MOREROWS="0"Enter the community name to include in trap messages in the Trap Community field.PERFORMANCE="REQUIRED"Select one of the options described above and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"If you selected 
CLASS=MENUITEM MOREINFO="NONE"Send Traps With 
CLASS=MENUITEM MOREINFO="NONE"Specified Community, enter a name in the 
CLASS=MENUITEM MOREINFO="NONE"Trap Community field and press 
MOREINFO="NONE"<Enter>.
IDXID="w842"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w843"BOOK="_idx" COLLECTION="nw41" TIDREF="i4569"Enter the community name to be included in trap messages.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Other SNMP Parameters and press 
MOREINFO="NONE"<Enter>.Enter other SNMP command-line parameters in the window that is displayed, then press 
MOREINFO="NONE"<Enter>.The parameters should be entered in the same format they would appear when entered on the "LOAD SNMP" command line.PERFORMANCE="REQUIRED"When you are finished, press 
MOREINFO="NONE"<Esc>; if prompted, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save changes to the 
CLASS=MENUITEM MOREINFO="NONE"SNMP Parameters, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration menu is displayed.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Configure SNMP Information, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"General SNMP Information For This Node window is displayed.
PAGENUM=40 ID="BP45"PAGENUM=41PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Node Name for SNMP, then press 
MOREINFO="NONE"<Enter>.
IDXID="w844"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w845"BOOK="_idx" COLLECTION="nw41" TIDREF="i2951"Enter the name SNMP reports to the management client for this node, then press 
MOREINFO="NONE"<Esc>.By convention, this is the IP host name for the node. If the node does not have an IP host name, it is recommended that you use the NetWare® file server name for this node.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Hardware Description, then press 
MOREINFO="NONE"<Enter>.
IDXID="w846"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w847"BOOK="_idx" COLLECTION="nw41" TIDREF="i1639"Enter the hardware description for this node, then press 
MOREINFO="NONE"<Esc>.The hardware description can include the CPU type, bus speed, size of memory, size and type of disks, printers, tape drives, and so on. This description, combined with the information about the software taken from the system, makes up the SNMP system description.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Physical Location, then press 
MOREINFO="NONE"<Enter>.
IDXID="w848"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w849"BOOK="_idx" COLLECTION="nw41" TIDREF="i3307"Enter the location description for this node, then press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Human Contact, then press 
MOREINFO="NONE"<Enter>.
IDXID="w850"BOOK="_idx" COLLECTION="nw41" TIDREF="i3211"IDXID="w851"BOOK="_idx" COLLECTION="nw41" TIDREF="i1736"Enter the contact information for the persons responsible for this node, then press 
MOREINFO="NONE"<Esc>. The contact information should include phone numbers and mailing addresses.PERFORMANCE="REQUIRED"When you are finished, press 
MOREINFO="NONE"<Esc>; if prompted, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save changes to the 
CLASS=MENUITEM MOREINFO="NONE"SNMP Information, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration menu is displayed.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.
PAGENUM=41 ID="BP46"PAGENUM=42RENDERAS="SECT1"Setting Up Remote AccessIDXID="w852"BOOK="_idx" COLLECTION="nw41" TIDREF="i4184"IDXID="w853"BOOK="_idx" COLLECTION="nw41" TIDREF="i3739"
To configure this node for remote access, complete the following steps:PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Configure Remote Access To This Server, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Configure Remote Access to this Server window is displayed.PERFORMANCE="REQUIRED"Configure the remote parameters as described in 
IDREF="FM76283"Table 7-1.LABEL="7-1" PGWIDE=1 TOCENTRY="1"ID="FM76283"Remote Configuration OptionsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"ValuesCOLNAME=3 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w854"BOOK="_idx" COLLECTION="nw41" TIDREF="i4184"
Remote AccessCOLNAME=2 ROTATE="0" MOREROWS="0"Enabled, DisabledDefault: DisabledCOLNAME=3 ROTATE="0" MOREROWS="0"Enables remote access to this server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w855"BOOK="_idx" COLLECTION="nw41" TIDREF="i4184"IDXID="w856"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
PasswordCOLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Enter a password to secure remote communications. When enabled, this node requires a password of any user accessing this node through RCONSOLE, ACONSOLE, or XCONSOLE.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w857"BOOK="_idx" COLLECTION="nw41" TIDREF="i4184"IDXID="w858"BOOK="_idx" COLLECTION="nw41" TIDREF="i3675"
RCONSOLE ConnectionCOLNAME=2 ROTATE="0" MOREROWS="0"Enabled, DisabledDefault: DisabledCOLNAME=3 ROTATE="0" MOREROWS="0"Enables remote access to this node through RCONSOLE. RCONSOLE allows access to the file server console from a workstation.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w859"BOOK="_idx" COLLECTION="nw41" TIDREF="i4184"IDXID="w860"BOOK="_idx" COLLECTION="nw41" TIDREF="i78"
ACONSOLE ConnectionCOLNAME=2 ROTATE="0" MOREROWS="0"Enabled, DisabledDefault: DisabledCOLNAME=3 ROTATE="0" MOREROWS="0"Enables remote access to this node through ACONSOLE.ACONSOLE allows access to the file server console through a modem. When you enable this option, you also need to specify the communications port and baud rate used by the system.You may also have to set up special commands for modems that do not respond to the standard modem AT command set through the Expert Modem Setup option.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w861"BOOK="_idx" COLLECTION="nw41" TIDREF="i4184"IDXID="w862"BOOK="_idx" COLLECTION="nw41" TIDREF="i3749"
Remote InstallationCOLNAME=2 ROTATE="0" MOREROWS="0"Enabled, DisabledDefault: DisabledCOLNAME=3 ROTATE="0" MOREROWS="0"Enables software installation or updates from a remote NetWare server.PAGENUM=43 ID="BP47"PERFORMANCE="REQUIRED"When you are finished, press 
MOREINFO="NONE"<Esc>; if prompted, select 
CLASS=MENUITEM MOREINFO="NONE"Yes to save changes to the remote configuration, then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.LABEL="8"PAGENUM=45 ID="BP48"ID="FM93625"Testing the ConfigurationAs is true for nearly all data communications products, the typical NetWare® 4.1 operating environment includes a number of hardware and software elements from which problems can arise, but usually do not.With NetWare 4.1 protocol software, the situation can be further complicated by the fact that the networking environment can include hardware and software supplied by multiple vendors. When something does go wrong, it is not always a simple matter to isolate the malfunctioning component.This chapter describes a set of basic test procedures for NetWare 4.1 internetworking software. At various points it also includes some specific recommendations or actions. Even at those points, however, you have to exercise informed judgement as to what is best to do in the situation at hand.This chapter covers the following topics:MARK=BULLETIDREF="FM35203"Troubleshooting TipsIDREF="FM21795"Testing NetWare 4.1 Network ProtocolsIDREF="FM23029"Reporting a ProblemPAGENUM=45 ID="BP49"PAGENUM=46RENDERAS="SECT1"IDXID="w863"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"IDXID="w864"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"ID="FM35203"Troubleshooting TipsSome fundamental troubleshooting guidelines for networks can be summarized as follows:MARK=BULLETIf there is any reason to believe that the problem lies with one or more individual workstations, check them out first. This includes any applications being used on the workstation.If there is any reason to believe that the problem lies within a LAN, such as adapter cards or cabling, check it out next.After verifying that the workstations and the LANs are operating correctly, check out any transceivers that link workstations to the LAN.If the previous steps are completed satisfactorily, the problem might be in third-party software. Refer to the manufacturer's manuals for troubleshooting procedures for their software.The preceding steps, satisfactorily performed, should isolate the problem to NetWare 4.1 software. Assuming other system software is performing properly, you should initiate tests on NetWare 4.1 servers as described in the next section.This section identifies some other areas you should check if you have trouble with your PC after installing the server software.RENDERAS="SECT2"Hard Disk Access ProblemsIf you cannot access the hard disk, check the following items:MARK=BULLETCables between the hard disks and the controllers: ensure that Pin 1 of each cable is attached to Pin 1 of each connector.Power cables: ensure that they are properly attached.DCB jumper settings: ensure that they are correct.Controller addresses: ensure that each is valid.EISA nonvolatile RAM configuration parameters, if you are using EISA: ensure that they are correct.PAGENUM=47 ID="BP50"RENDERAS="SECT2"Volume ErrorsIf you get disk errors when mounting a volume, check the memory in the PC by loading MONITOR. You should have 20 percent or more available for cache buffers.RENDERAS="SECT2"Communication ProblemsIf your PC cannot communicate with the network, determine whether the following conditions are satisfied:MARK=BULLETEach network board is properly and securely seated.The cable is properly connected. (Run COMCHECK to verify connections.)All cabling is properly terminated.LSLENH is loaded before the board driver is loaded.The internal network number of the PC does not conflict with other server internal network numbers or other network addresses.RENDERAS="SECT2"ID="FM92518"Displaying Your ConfigurationYou can view the new AUTOEXEC.NCF file, as well as the INETCFG-generated LOAD and BIND commands, all at once or grouped according to boards, protocols, and protocol-board bindings. To modify the parameters, you must use the applicable INETCFG menus described in earlier chapters of this manual. Display the configuration information as follows: PERFORMANCE="REQUIRED"At the server prompt, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>The 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu is displayed.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration menu is displayed.
PAGENUM=48 ID="BP51"PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"Edit 
CLASS=MENUITEM MOREINFO="NONE"AUTOEXEC.NCF, then press 
MOREINFO="NONE"<Enter>.Your AUTOEXEC.NCF file should look something like this:
FORMAT="LINESPECIFIC"MOREINFO="NONE"file server name XYZXYX
ipx internal net 12341234
load conlog
load lslenh
SYS:ETC\initsys.ncf
load remote
load rspx
load c:command
#LOAD NE2000 PORT=300 INT=3 
   FRAME=ETHERNET_II
#LOAD TOKEN NAME=FRED INT=4 PORT=340 
   FRAME=TOKEN-RING_SNAP
#BIND IPX TO NE2000 NET=11111111
#BIND IPX TO FRED NET=22222222
unload conlogPERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Manage Configuration menu.PERFORMANCE="REQUIRED"To display other information, such as the LOAD and BIND commands for the configuration, select the 
CLASS=MENUITEM MOREINFO="NONE"View Configuration option on the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.
MARK=BULLETTo display all converted LOAD and BIND commands, select CLASS=MENUITEM MOREINFO="NONE"All INETCFG Commands.To display only the converted LOAD and BIND commands for LAN boards, select CLASS=MENUITEM MOREINFO="NONE"LAN Board Commands.To display only the converted LOAD commands, select CLASS=MENUITEM MOREINFO="NONE"Protocol Commands.To display only the converted BIND commands, select CLASS=MENUITEM MOREINFO="NONE"Protocol-to-Port Bind Commands.PAGENUM=48 ID="BP52"PAGENUM=49To display the messages that were logged during system initialization, select CLASS=MENUITEM MOREINFO="NONE"Console Messages.If CONLOG was loaded, the Console Log file messages generated during system initialization can be displayed. These messages can indicate errors that occur during system initialization and can be helpful in localizing problems. The file contains all the messages saved from the console. Only the last 8 KB of the log file are shown. If the file is larger than 8 KB, use other NetWare utilities, such as EDIT, to display the entire file (SYS:/ETC/CONSOLE.LOG).All displays in the CLASS=MENUITEM MOREINFO="NONE"View Configuration menu are read-only. PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> again, and respond 
CLASS=MENUITEM MOREINFO="NONE"Yes when prompted, to exit INETCFG.RENDERAS="SECT1"ID="FM21795"Testing NetWare 4.1 Network ProtocolsThe following sections are essentially a set of procedures for verifying the correct operation of NetWare 4.1 network protocols. Once you have correctly and completely installed and configured NetWare 4.1 network protocols, testing the protocols is relatively easy.RENDERAS="SECT2"ID="FM42424"Testing IPXNetWare 4.1 software provides IPXCON, the IPXTM console utility that enables you to manage networks that support IPX. To start IPXCON from the server console, typeIDXID="w865"BOOK="_idx" COLLECTION="nw41" TIDREF="i312"IDXID="w866"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD IPXCONMOREINFO="NONE" <Enter>
PAGENUM=50 ID="BP53"The IPXCON screen is displayed showing the host address and statistics, such as the number of packets received, the number of packets sent, the number of forwarded packets, the number of active local circuits, the number of known networks, the number of known services, and the address of the current system being managed. If the system is sending and receiving packets and this display shows any active circuits or known networks, then the IPX protocol is probably functioning correctly.In addition, the display also has a menu listing a number of Available Options, as shown in IDREF="FM47227"Figure 8-1.IDXID="w867"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"LABEL="8-1" FLOAT="0"ID="FM47227"IPXCON Available Options MenuFILEREF="fig15_1.tif"The following functions are associated with each of the IPXCON options:CLASS=MENUITEM MOREINFO="NONE"SNMP Access Configuration---Allows you to change SNMP parameters, increase the poll rate, increase the number of retries for a request, select a different IPX system to manage, change the community string, and change the protocol you are using to manage systems.CLASS=MENUITEM MOREINFO="NONE"IPX Information---Displays a snapshot of vital IPX statistics. In addition, more detailed screens are available that show error counts.CLASS=MENUITEM MOREINFO="NONE"IPX Router Information---Provides snapshot information about the operation of NLSPTM software, RIP, and SAP on this system.CLASS=MENUITEM MOREINFO="NONE"NLSP Information---Provides detailed information about the operational state of your network, including statistics on this NLSP system. You can view the current NLSP LANs and the systems in your network, and information about all NLSP neighbors.CLASS=MENUITEM MOREINFO="NONE"Circuits---Displays a table of all the IPX circuits on this system.PAGENUM=50 ID="BP54"PAGENUM=51CLASS=MENUITEM MOREINFO="NONE"Forwarding---Displays a table of all known IPX destination networks.CLASS=MENUITEM MOREINFO="NONE"Services---Displays a table listing all services known to this system and detailed information about destinations offering the service.RENDERAS="SECT3"Verifying an IPX DestinationDisplaying the table of all known IPX destination networks is a simple way to verify that the server can actually communicate with one or more destinations. If the destination is displayed, you know that both the server and the responding destination are operating properly. If the selected destination is one or more hops away, you also know that the servers in between are working.To check on a destination, follow these steps:PERFORMANCE="REQUIRED"From the CLASS=MENUITEM MOREINFO="NONE"Available Options menu, select CLASS=MENUITEM MOREINFO="NONE"Forwarding, then press MOREINFO="NONE"<Enter>.A new window displays the Forwarding Table with the following information on all known IPX destination networks:
MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Network---Eight-digit IPX network number, including the server's internal network numbers as well as LAN network numbers.CLASS=MENUITEM MOREINFO="NONE"Protocol---Routing protocol through which the destination was learned. The possible values are as follows:CLASS=MENUITEM MOREINFO="NONE"local---Destination is the local system or the destination network is locally attached.CLASS=MENUITEM MOREINFO="NONE"RIP---NLSP accepted this route by participating in the RIP routing protocol or the system is running in RIP-only mode.CLASS=MENUITEM MOREINFO="NONE"NLSP---Destination network is represented through the NLSP protocol.CLASS=MENUITEM MOREINFO="NONE"Circuit---First hop circuit to the destination network.CLASS=MENUITEM MOREINFO="NONE"Destination---Name of the destination network.You can select a destination network to display additional information, including the address of the first hop router and any services that are accessible to the network. If this is an NLSP destination, you can also display the path to the destination and the characteristics of that path.
PAGENUM=52 ID="BP55"PERFORMANCE="REQUIRED"To display additional information about a destination, position the cursor until your selection is highlighted, then press 
MOREINFO="NONE"<Enter>.A new window displays the Destination Information for the selected IPX destination network.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the 
CLASS=MENUITEM MOREINFO="NONE"Forwarding Table window.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> again to return to the IPXCON main window.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> once more, and respond 
CLASS=MENUITEM MOREINFO="NONE"Yes to the prompt to exit the IPXCON utility.RENDERAS="SECT2"ID="FM14910"Testing TCP/IPOnce TCP/IP has been configured and the IP addressing specified, you can test the configuration to determine whether IP packets can be sent and received between the two networks. The easiest way to do this is with the PING utility. Testing can be initiated from either a workstation or a host.For purposes of illustration, assume that the network configuration being tested consists of a DOS workstation running TCP/IP client software on a physical network, a NetWare server, and a UNIX® host on another network, as shown in IDREF="FM14406"Figure 8-2. The workstation is attempting to connect to the UNIX host, and a NetWare server running NetWare 4.1 software is routing IP packets between the two networks.LABEL="8-2" FLOAT="0"ID="FM14406"TCP/IP InternetworkFILEREF="fig15_2.tif"PAGENUM=53 ID="BP56"RENDERAS="SECT3"Test 1: Verify Connectivity to ServerTo test the IP connection between the workstation and the server, enter the following command from the DOS workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"PING 191.1.1.60 MOREINFO="NONE"<Enter>If the response returned is "MOREINFO="NONE"191.1.1.60 is alive," the IP packet was successfully sent to the remote address, and the remote host (the server) returned the packet successfully.If you do not receive confirmation that the IP packet was returned correctly, there is a problem. At this point, the board in the NetWare server should appear as another host on the local network, so there should not be any routing issues.Things to check include the following:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The network portion of the IP addresses on both the workstation and the server should be the same.The workstation and the server should use the same subnetwork mask, which can be the default mask.The physical connection between the two hosts exists and is a good connection.RENDERAS="SECT3"Test 2: Verify Server RoutingThe second step is to ping from the DOS workstation through the server to the second board that is connected to the remote network, using the following command at the workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"PING 191.1.1.140 MOREINFO="NONE"<Enter>If the response returned is "MOREINFO="NONE"191.1.1.140 is alive," the IP packet was successfully sent through the server to the remote address, and the second board in the remote host (the server) returned the packet successfully.PAGENUM=53 ID="BP57"PAGENUM=54If the test is not successful, check the following:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Using the INETCFG CLASS=MENUITEM MOREINFO="NONE"View Configuration Information option, verify that the following LOAD command has been correctly configured:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD TCP/IP FORWARD=YESFor more information about using INETCFG, refer to IDREF="FM97977"Chapter 2, "Using INETCFG." If the server was not configured using INETCFG, the AUTOEXEC.NCF file on the server should be edited to include this line.Verify the TCP/IP configuration on the server by entering the following command at the console prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"CONFIG MOREINFO="NONE"<Enter>Verify that the IP addresses and the subnetwork masks of both boards in the server are recognized as the values you configured for TCP/IP.Verify that the DOS workstation has the following entries in the NET.CFG file, indicating that the server (191.1.1.60) is the router to route packets from network 191.1.1.32 to network 191.1.1.128.FORMAT="LINESPECIFIC"MOREINFO="NONE"IP_ROUTER 191.1.1.60
IP_NETMASK 255.255. 255.224Once you can successfully ping the second board in the server, the routing on the DOS workstation (the local TCP/IP host) is set up correctly and the NetWare server is sending and receiving packets correctly.RENDERAS="SECT3"Test 3: Verify Router to End SystemThe final step is to ping from the DOS workstation through the server to the UNIX TCP/IP host on the remote network, using the following command at the workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"PING MOREINFO="NONE"191.1.1.137 MOREINFO="NONE"<Enter>If the response returned is "MOREINFO="NONE"191.1.1.137 is alive," the IP packet was successfully sent through the server to the remote host, and the remote host (the UNIX host) returned the packet successfully.PAGENUM=55 ID="BP58"If the test is not successful:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Ping from the UNIX host to the NetWare server using the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"PINGMOREINFO="NONE" 191.1.1.140 MOREINFO="NONE"<Enter>If this does not work, check the items described in Test 1 to resolve the problem. After the UNIX host has successfully pinged 191.1.1.140, continue with the next step.Ping from the UNIX host to the first board in the NetWare server (the board that is connected to the local network, 191.1.1.32), using the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"PINGMOREINFO="NONE" 191.1.1.60 MOREINFO="NONE"<Enter>If this does not work, continue with the next step.Verify that the routing is configured correctly on the UNIX host to ensure that IP packets can be routed to the NetWare server, that the NetWare server at 191.1.1.140 is recognized as the router to route packets from network 191.1.1.128 to network 191.1.1.32.On a UNIX system, the general command is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"ROUTE ADD <destination network> 
   <gateway address> <metric>For the UNIX host, check the manual for the exact syntax for adding routes. In this example, the command is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"ROUTE ADDMOREINFO="NONE" 191.1.1.32 191.1.1.140 1This ROUTE command specifies that if there is a packet to be routed to network 191.1.1.32, send it to the router at address 191.1.1.140, which is only one hop away (the packet must be forwarded through only one router to get to its remote network destination).To assign the NetWare server (IP address 191.1.1.140) as the default router for the UNIX system to route packets for any network other than the local, the command syntax is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"ROUTE ADD MOREINFO="NONE"0.0.0.0 191.1.1.140 1
PAGENUM=56 ID="BP59"If there are other non-NetWare TCP/IP routers on the network, verify that those routers support RIP or OSPF. The NetWare TCP/IP router supports RIP or OSPF. If the other routers do not support RIP or OSPF, then static routes have to be added to all routers. Configuring static routes for the TCP/IP router is explained in the BOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management Guide.If routing is configured correctly on one network but not on the other, packets might be sent to a host on the remote network, but the remote host will not be able to route the packets back. In this example, the workstation might have the correct routing entries in the NET.CFG file (resulting in the PING packet being correctly sent to the UNIX host on the remote network), but the UNIX host does not know how to route the packet back because it does not have a ROUTE ADD command set up correctly.After the preceding steps have been completed and routing has been configured correctly on both networks, the hosts on one network should be able to ping hosts on the remote network.RENDERAS="SECT2"ID="FM17760"Testing AppleTalkNetWare 4.1 provides ATCON, the AppleTalk console utility that enables you to test networks that support AppleTalk. To start ATCON from the server console, typeIDXID="w868"BOOK="_idx" COLLECTION="nw41" TIDREF="i312"IDXID="w869"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD ATCONMOREINFO="NONE" <Enter>The ATCON main menu is displayed, as shown in IDREF="FM53116"Figure 8-3.IDXID="w870"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"LABEL="8-3" FLOAT="0"ID="FM53116"ATCON Main MenuFILEREF="fig15_3.tif"PAGENUM=56 ID="BP60"PAGENUM=57The ATCON menu options are as follows:CLASS=MENUITEM MOREINFO="NONE"AURP Information---View the current status of the AppleTalk Update-based Router Protocol tunnel and its peers (if enabled).CLASS=MENUITEM MOREINFO="NONE"Interfaces---ViewIDXID="w871"BOOK="_idx" COLLECTION="nw41" TIDREF="i215"
 information about the server's directly connected interfaces and other logical interfaces AppleTalk might be configured with. You can find out whether each of the interfaces is seeded correctly by looking at the status of the interface.CLASS=MENUITEM MOREINFO="NONE"Log Files---View the NetWare System and Volume logs. This includes all NetWare messages written to these logs. ATCON allows you to set the level of logging and clear the logs after viewing them.CLASS=MENUITEM MOREINFO="NONE"Lookup Network Entities---Executes an NBP lookup for an AppleTalk service, such as a printer. You can use this test to verify that all services, or all services of a particular type, are available. If you specify a name, you can use this test to verify that the specified service is available.After you have executed an IDXID="w872"BOOK="_idx" COLLECTION="nw41" TIDREF="i1286"
NBP lookup, you can then perform an Echo test on a selected node (that was discovered by NBP lookup) to verify node-to-node communication on the AppleTalk network.CLASS=MENUITEM MOREINFO="NONE"Packet IDXID="w873"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
Statistics---View IDXID="w874"BOOK="_idx" COLLECTION="nw41" TIDREF="i220"
statistics about the packets that IDXID="w875"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
the server received, sent, forwarded, or dropped. These statistics are updated dynamically as the server operates.CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration---Allows you to view the current configuration of the AppleTalk protocol stack and the application support provided (if any).CLASS=MENUITEM MOREINFO="NONE"Routing IDXID="w876"BOOK="_idx" COLLECTION="nw41" TIDREF="i3910"
TableIDXID="w877"BOOK="_idx" COLLECTION="nw41" TIDREF="i238"---View information about all IDXID="w878"BOOK="_idx" COLLECTION="nw41" TIDREF="i3915"
AppleTalk networks that are accessible to the server, either directly (on one of its own network interface boards) or remotely. The system checks the status of the networks periodically and verifies the status as "Good," "Going Bad," or "Bad," depending on how long it has been since information about the network was received. This interval is twice the value you entered in the "Routing Table Update Timer" field.CLASS=MENUITEM MOREINFO="NONE"Zones ListIDXID="w879"BOOK="_idx" COLLECTION="nw41" TIDREF="i252"---View IDXID="w880"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
all the IDXID="w881"BOOK="_idx" COLLECTION="nw41" TIDREF="i4877"
AppleTalk zones that are accessible to the AppleTalk server either directly (on one of its own network interface boards) or remotely, through other servers.PAGENUM=58 ID="BP61"For large networks, viewing the routing table and zone list could cause ATCON to retrieve and display thousands of entries, a process that would consume too much CPU time on the server. To avoid this, ATCON stops when it has retrieved 1000 items and then displays the information it has collected. (It takes about a minute to reach this limit.) ATCON also displays a message indicating that the list is only part of the whole pool of information.You can disable this limit and see the complete list of entries by loading ATCON with the "-w" switch, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD ATCON -w MOREINFO="NONE"<Enter>ATCON retrieves and displays all the information available.RENDERAS="SECT3"ID="FM32550"Looking IDXID="w882"BOOK="_idx" COLLECTION="nw41" TIDREF="i2238"
Up IDXID="w883"BOOK="_idx" COLLECTION="nw41" TIDREF="i2573"IDXID="w884"BOOK="_idx" COLLECTION="nw41" TIDREF="i2608"
an IDXID="w885"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
AppleTalk IDXID="w886"BOOK="_idx" COLLECTION="nw41" TIDREF="i215"
ServiceIDXID="w887"BOOK="_idx" COLLECTION="nw41" TIDREF="i238"The Lookup portion of the CLASS=MENUITEM MOREINFO="NONE"Lookup Network Entities function in ATCON performs similarly to looking up a service in the Macintosh Chooser. When you use the CLASS=MENUITEM MOREINFO="NONE"Lookup Service function, the server sends NBP requests to the zone you specify. AppleTalk services respond to the request by sending NBP replies to the requester. If an NBP lookup test is completed successfully, a window opens, showing the name(s) of the service(s) and network address(es).An NBP lookup is a simple way to test that the server can actually communicate with one or more services in an AppleTalk zone. If the lookup succeeds, you know that both the server and the responding service are operating properly on the AppleTalk internetwork. If the selected zone is one or more hops away, you also know that the servers in between are working.The CLASS=MENUITEM MOREINFO="NONE"Lookup Network Entities function is available only if AppleTalk is configured to support both routing and applications services. This option can be configured through the CLASS=MENUITEM MOREINFO="NONE"Bindings options in INETCFG. If AppleTalk is currently running on the server and it is currently configured to support routing only, and you want to use CLASS=MENUITEM MOREINFO="NONE"Lookup Network Entities, change the binding options to enable the CLASS=MENUITEM MOREINFO="NONE"Support Applications through this Interface option, configure an CLASS=MENUITEM MOREINFO="NONE"Internal Network Number, and configure one or more CLASS=MENUITEM MOREINFO="NONE"Internal Zone(s).PAGENUM=58 ID="BP62"PAGENUM=59ID="FM28789"To check the status of an AppleTalk service, follow these steps:PERFORMANCE="REQUIRED"From the ATCON main menu, select CLASS=MENUITEM MOREINFO="NONE"Lookup Network Entities, then press MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Edit Lookup Parameters and Execute Tests window, shown in 
IDREF="FM91848"Figure 8-4, displays the parameters for the Lookup Service.LABEL="8-4" FLOAT="0"ID="FM91848"Edit Lookup ParametersFILEREF="fig15_4.tif"The lookup parameters you can edit are as follows:CLASS=MENUITEM MOREINFO="NONE"NameIDXID="w888"BOOK="_idx" COLLECTION="nw41" TIDREF="i2238"---Default equal sign (=) means "all." For example, if you specify a type of service in the next field and leave the equal sign here, t
IDXID="w889"BOOK="_idx" COLLECTION="nw41" TIDREF="i2602"
he Lookup Service test asks for the names of all services of that type within a zone. You can enter the name of any service on your internetwork.CLASS=MENUITEM MOREINFO="NONE"TypeIDXID="w890"BOOK="_idx" COLLECTION="nw41" TIDREF="i2238"---
IDXID="w891"BOOK="_idx" COLLECTION="nw41" TIDREF="i4620"
Default equal sign (=) means "all." In this case, the Lookup Service test asks for the names of all services of all types within a zone. You can specify a particular type, such as LaserWriter* or AppleShare*. If you don't know the type you are looking for, you can enter the default equal sign (=) wildcard to get a list of all types.CLASS=MENUITEM MOREINFO="NONE"ZoneIDXID="w892"BOOK="_idx" COLLECTION="nw41" TIDREF="i2238"---
IDXID="w893"BOOK="_idx" COLLECTION="nw41" TIDREF="i4880"
List of available zones on the internetwork accessible by this AppleTalk server.CLASS=MENUITEM MOREINFO="NONE"Number of RetriesIDXID="w894"BOOK="_idx" COLLECTION="nw41" TIDREF="i2238"---Number of times the server sends out NBP requests. The server sends out NBP requests up to two times if it receives no responses. The range of values is 2 to 32767 seconds; the default value is 2.CLASS=MENUITEM MOREINFO="NONE"Retry IntervalIDXID="w895"BOOK="_idx" COLLECTION="nw41" TIDREF="i2238"---Time interval between retries. The range of values is 1 to 32767 seconds; the default value is 1.
PAGENUM=60 ID="BP63"PERFORMANCE="REQUIRED"If you want, enter a service name in the 
CLASS=MENUITEM MOREINFO="NONE"Name field and a service type in the 
CLASS=MENUITEM MOREINFO="NONE"Type field.Alternatively, you can leave the default equal sign (=) for a more general Lookup Service test.PERFORMANCE="REQUIRED"Position the cursor on the 
CLASS=MENUITEM MOREINFO="NONE"Zone field, then press 
MOREINFO="NONE"<Enter>.This action displays a list of zones 
IDXID="w896"BOOK="_idx" COLLECTION="nw41" TIDREF="i238"
available on the 
IDXID="w897"BOOK="_idx" COLLECTION="nw41" TIDREF="i252"
internetwork
IDXID="w898"BOOK="_idx" COLLECTION="nw41" TIDREF="i2238"
.PERFORMANCE="REQUIRED"Select a zone name from the list, then press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Number of Retries field and enter a value between 2 and 32767.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"Retry Interval field and enter a value between 1 and 32767.PERFORMANCE="REQUIRED" Select 
CLASS=MENUITEM MOREINFO="NONE"Perform Lookup, then press 
MOREINFO="NONE"<Enter>.You should see the results of the Lookup, similar to 
IDREF="FM13305"Figure 8-5.LABEL="8-5" FLOAT="0"IDXID="w899"BOOK="_idx" COLLECTION="nw41" TIDREF="i2238"ID="FM13305"Sample Lookup WindowFILEREF="fig15_5.tif"The server reports the name, type, and network address of any services it finds as a result of the Lookup. If the Lookup fails, the name of the service does not appear. If no services are IDXID="w900"BOOK="_idx" COLLECTION="nw41" TIDREF="i2573"IDXID="w901"BOOK="_idx" COLLECTION="nw41" TIDREF="i2608" available that meet the parameters specifiedIDXID="w902"BOOK="_idx" COLLECTION="nw41" TIDREF="i2238", a IDXID="w903"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"message is displayed.IDXID="w904"BOOK="_idx" COLLECTION="nw41" TIDREF="i215"PERFORMANCE="REQUIRED"You can display more detailed information about any of the entities listed by selecting the desired entity and pressing 
MOREINFO="NONE"<F3>. A window is displayed, similar to 
IDREF="FM27446"Figure 8-6, that reports both the network address and socket address of the selected entity.
PAGENUM=61 ID="BP64"LABEL="8-6" FLOAT="0"ID="FM27446"Detailed Entity InformationFILEREF="fig15_6.tif"RENDERAS="SECT3"Using IDXID="w905"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
Echo IDXID="w906"BOOK="_idx" COLLECTION="nw41" TIDREF="i2956"
to IDXID="w907"BOOK="_idx" COLLECTION="nw41" TIDREF="i215"
Verify IDXID="w908"BOOK="_idx" COLLECTION="nw41" TIDREF="i238"
ConnectivityIDXID="w909"BOOK="_idx" COLLECTION="nw41" TIDREF="i1286"When you execute an Echo test, the server sends a specified number of packets across the network to a specified node; the node should then IDXID="w910"BOOK="_idx" COLLECTION="nw41" TIDREF="i2956"
return the same number of packets. If an Echo test is completed successfully, the number of packets that the server receives is equal to the number of packets it sent. Using an Echo test, you can carry out either of the following tasks:MARK=BULLETYou can check to determine whether the server can communicate with a particular node on a directly connected network. If the communication is successful, you know that AppleTalk is working on that interface and that the specified node is up and running.You can check to determine whether the server can communicate with a node on a "remote" AppleTalk network (a network that is not directly connected to the server). If the communication is successful, you know that the server can reach another AppleTalk network and that all AppleTalk routers in between must be routing correctly.To verify that the server can communicate with a node on a local or remote AppleTalk network, first follow the steps described earlier, in IDREF="FM32550""Looking Up an AppleTalk Service."When you have located a service, complete the following steps:PERFORMANCE="REQUIRED"In the CLASS=MENUITEM MOREINFO="NONE"Lookup window (IDREF="FM13305"Figure 8-5), highlight the name of the entity on which you want to perform the Echo test, then press MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Available Actions menu opens.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Edit Echo Parameters from the 
CLASS=MENUITEM MOREINFO="NONE"Available Actions menu, then press 
MOREINFO="NONE"<Enter>.The 
CLASS=MENUITEM MOREINFO="NONE"Edit Echo Parameters window opens, as shown in 
IDREF="FM57277"Figure 8-7.
PAGENUM=62 ID="BP65"LABEL="8-7" FLOAT="0"ID="FM57277"Edit Echo ParametersFILEREF="fig15_7.tif"The 
CLASS=MENUITEM MOREINFO="NONE"Edit Echo Parameters window displays the test parameters you can edit:CLASS=MENUITEM MOREINFO="NONE"Number of Packets to SendIDXID="w911"BOOK="_idx" COLLECTION="nw41" TIDREF="i1286"---Default number of Echo packets sent out is 50. 
IDXID="w912"BOOK="_idx" COLLECTION="nw41" TIDREF="i220"
You can specify the number of packets you want to echo in the 
CLASS=MENUITEM MOREINFO="NONE"Number of Packets to Send field. The maximum number of packets is 65535. 
IDXID="w913"BOOK="_idx" COLLECTION="nw41" TIDREF="i1286"
If you want to check throughput speed, 
IDXID="w914"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
you can specify a relatively high number and time the procedure.CLASS=MENUITEM MOREINFO="NONE"TimeoutIDXID="w915"BOOK="_idx" COLLECTION="nw41" TIDREF="i1286"
 (seconds)
IDXID="w916"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
---Default Timeout value is 2 seconds. If you want, specify the number of seconds that ATCON waits for response packets. The maximum number of seconds allowed is 9999, but Novell recommends that you do not set the Timeout value too high. At 9999 seconds, ATCON waits approximately 2 hours for an Echo reply.CLASS=MENUITEM MOREINFO="NONE"Number of Data BytesIDXID="w917"BOOK="_idx" COLLECTION="nw41" TIDREF="i1285"---Default Echo packets contain 10 data bytes, which are always included in Echo packets. If you want, specify the number of data bytes in each packet. Each packet can contain from 0 to 581 bytes.PERFORMANCE="REQUIRED"ID="FM14116"Modify one or more parameters, or leave the default values.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Perform Echo, then press 
MOREINFO="NONE"<Enter>.When you select 
CLASS=MENUITEM MOREINFO="NONE"Perform Echo, ATCON sends out the specified number of Echo packets to the specified address. A window is displayed, similar to IDREF="FM23187"Figure 8-8, that reports the test results.
PAGENUM=63 ID="BP66"LABEL="8-8" FLOAT="0"ID="FM23187"Echo Test ResultsFILEREF="fig15_8.tif"The values in the 
CLASS=MENUITEM MOREINFO="NONE"Sent and 
CLASS=MENUITEM MOREINFO="NONE"Received fields should increase, as shown in 
IDREF="FM23187"Figure 8-8. CLASS=MENUITEM MOREINFO="NONE"SentIDXID="w918"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"---As ATCON sends out 
IDXID="w919"BOOK="_idx" COLLECTION="nw41" TIDREF="i1286"
packets, the value in this field should increase. ATCON sends out the next packet only when the response to the previous packet has returned or when the Timeout value has expired.CLASS=MENUITEM MOREINFO="NONE"ReceivedIDXID="w920"BOOK="_idx" COLLECTION="nw41" TIDREF="i1286"---If Echo 
IDXID="w921"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
receives a response before the Timeout value, the value in this field increases. If the value does not increase, the router did not receive any Echo packets.If the value in the 
CLASS=MENUITEM MOREINFO="NONE"Received field does not increase, the AppleTalk connection might still be functioning properly. The problem might be as simple as an AppleTalk server accidentally switched off or a cable connection worked loose. If the value in the 
CLASS=MENUITEM MOREINFO="NONE"Received field does not increase, carry out these tasks:
MARK=BULLETCheck that there are other AppleTalk nodes---Macintosh workstations or AppleTalk servers, for example---on the network you specified.Make sure that any routers between the local Macintosh and the target network are plugged in, switched on, and properly configured.Check the network board in the server to make sure it is IDXID="w922"BOOK="_idx" COLLECTION="nw41" TIDREF="i1286"
connected IDXID="w923"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
properly IDXID="w924"BOOK="_idx" COLLECTION="nw41" TIDREF="i2956"
to the IDXID="w925"BOOK="_idx" COLLECTION="nw41" TIDREF="i238"
network. IDXID="w926"BOOK="_idx" COLLECTION="nw41" TIDREF="i215"PAGENUM=64 ID="BP67"RENDERAS="SECT3"ID="FM18937"ID="FM24429"Checking the Server IDXID="w927"BOOK="_idx" COLLECTION="nw41" TIDREF="i215"
Configuration IDXID="w928"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
and IDXID="w929"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
FunctionAfter you configure the server, you should use ATCON to check that the configuration is the one you intended the server to work with.To check the network interfaces configured in the server, select CLASS=MENUITEM MOREINFO="NONE"Interfaces from the ATCON main menu, then press MOREINFO="NONE"<Enter>. The CLASS=MENUITEM MOREINFO="NONE"Interfaces window appears, as shown in IDREF="FM90066"Figure 8-9.LABEL="8-9" FLOAT="0"ID="FM90066"Interfaces WindowFILEREF="fig15_9.tif"The following paragraphs describe the fields in the CLASS=MENUITEM MOREINFO="NONE"Interfaces window. CLASS=MENUITEM MOREINFO="NONE"Network IDXID="w930"BOOK="_idx" COLLECTION="nw41" TIDREF="i215"
& AddressIDXID="w931"BOOK="_idx" COLLECTION="nw41" TIDREF="i106"---AppleTalk IDXID="w932"BOOK="_idx" COLLECTION="nw41" TIDREF="i313"
network number and node address of the server on a given networkIDXID="w933"BOOK="_idx" COLLECTION="nw41" TIDREF="i2956"
 interface. On the internal network, the server node number is always 2. The server address on external interfaces can change when you bring it up because the server acquires the address dynamically.CLASS=MENUITEM MOREINFO="NONE"TypeIDXID="w934"BOOK="_idx" COLLECTION="nw41" TIDREF="i215"---Indicates the type of AppleTalk network associated with a given port. CLASS=MENUITEM MOREINFO="NONE"PortIDXID="w935"BOOK="_idx" COLLECTION="nw41" TIDREF="i224"---Interface between the server and an AppleTalk network. Port 0 is associated with the internal network. The first AppleTalk and interface board attachment, as configured through INETCFG, is associated with Port 1, the second AppleTalk attachment is associated with Port 2, and so on.CLASS=MENUITEM MOREINFO="NONE"Status---Indicates the status of the AppleTalk network associated with a given port. CLASS=MENUITEM MOREINFO="NONE"Zone(s)IDXID="w936"BOOK="_idx" COLLECTION="nw41" TIDREF="i252"
---Indicates the zone configuration for a given interface. If you configured more than one zone on an extended network, the zones list is arranged vertically in line with the network number. The first zone in the list is the default zone.PAGENUM=65 ID="BP68"RENDERAS="SECT1"ID="FM23029"Reporting a ProblemIf there is still an unresolved problem at this point, depending on its severity with regard to the overall networking environment, you will probably have to call your Novell® support representative.IDXID="w937"BOOK="_idx" COLLECTION="nw41" TIDREF="i3795"
If you need to report a problem, the support personnel will need as much of the following information as you can give them:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"A description of your environment, including workstation model, connection method, server configuration, and anything else that is pertinent.A copy of any error messages that were logged as a result of the failure or the console log itself.A description of the sequence of events leading to the failure.Information as to whether you have been able to duplicate the problem. (One-time incidents might be important, but they are extremely difficult to analyze.) PAGENUM=67 ID="BP69"Glossaryadapter A piece of hardware, typically an interface card, installed in a computer, that connects the computer to other hardware or devices.addressAn identifier assigned to networks, stations, and other devices so that each device can be separately designed to receive and reply to messages.ID="FM45325"administratorThe person who sets up a server, creates user login accounts and passwords, creates groups, sets security, and maintains the server. ANSI (American National Standards Institute)A nonprofit organization in the U.S. that defines standards in many industries. It is supported by over one thousand trade organizations, professional societies, and companies. ANSI is affiliated with the Consultative Committee for International Telegraphy and Telephony (CCITT) and the International Organization for Standardization (ISO).AppleTalkThe Apple Computer suite of protocols that enables the hardware and software on an AppleTalk network to interact and to send data.AppleTalk networkA collection of connected, individually controlled computers, printers, and other devices, together with the hardware and AppleTalk software used to link them.ID="FM40112"ASCII (American Standard Code for Information Interchange)An 8-bit code for data transfer that was adopted by ANSI to ensure compatibility among data devices.ATCON utilityA diagnostic tool for use at the server. ATCON provides information about the server's AppleTalk stack and server, and about other AppleTalk networks on the internetwork.clientA node or workstation on a network that requires services from a server.coaxialA type of cable that uses two conductors: a central, solid wire core surrounded by insulation and, surrounding that, a braided-wire conductor sheath. A coaxial cable is well-suited for networking because it can accommodate high bandwidth but is relatively resistant to interference.consoleThe monitor and keyboard from which the server or host activity can be viewed and controlled.ID="FM37918"default zoneThe zone name in a zones list that has been specifically defined as the default zone. In the Novell implementation, if no default zone is defined, the first zone name in the zone list is the default zone. See also IDREF="FM23964"zone; IDREF="FM31006"zones list.delayThe time, in microseconds, to send a byte of data from one system to another.ID="FM85927"Designated RouterThe NLSP router responsible for exchanges of link state information on behalf of all other NLSP routers on the same LAN.device driverThe software or firmware that translates operating system requests into a format that is recognizable by specific hardware, such as adapters.ID="FM32459"EthernetA system of high-performance coaxial cables widely used in the communications industry. Ethernet cables can be part of an AppleTalk network or a TCP/IP network, for example.extended networkAn AppleTalk Phase 2 network on high-speed media, such as Ethernet or token ring. An extended network is capable of supporting the Phase 2 addressing extensions of a network range and zones list. See also IDREF="FM24859"network range; IDREF="FM31006"zones list.FDDI (Fiber Distributed Data Interface)The ANSI standard for high-speed (100 Mbps) fiber-optic connections.filterThe process on a router that selectively discards packets of a certain type, or packets originating from or destined for a certain location. See IDREF="FM34609"routing information filter.gatewayAn internetworking device that operates from the network to application layers of the Open Systems Interconnection (OSI) model. Sometimes used as a synonym for router. ID="FM74381"hopA measure of distance, in routers, on a network. The number of hops to a destination network is the number of routers that must be traversed to reach the network. The number of hops is part of each network entry in a RIP packet. See also IDREF="FM40922"RIP (Routing Information Protocol); IDREF="FM66278"tick.hop countThe routing metric used to measure the distance between a source and a destination; each hop equals the transmission of a packet across one router.ID="FM39468"INETCFG (Internetworking Configuration utility)A menu-based NetWare Loadable Module (NLM) file that simplifies the installation of Novell internetworking products by allowing a network administrator to configure interface boards and network protocols. INETCFG enables network administrators to bind protocols to different LAN boards, and also to view the entire or selected portions of the configuration.interface groupA set of specified interfaces. It allows protocols to request an X.25 virtual circuit through any one interface from within the group, without having to specify a specific interface.ID="FM17639"internal networkA virtual network that consists of two software nodes: the AppleTalk protocol stack and the AppleTalk router. See also IDREF="FM25948"network.InternetThe collection of networks and gateways that use the TCP/IP suite of protocols. Written in lowercase, it is an abbreviation for internetwork.Internet addressA 32-bit address assigned to hosts using TCP/IP.ID="FM30635"internetworkAny interconnected group of networks, such as an interconnected group of AppleTalk networks. Network users in an internetwork can share information and network devices. See also IDREF="FM25948"network.Internetworking Configuration (INETCFG) utilitySee IDREF="FM39468"INETCFG (Internetworking Configuration utility).IP addressA 32-bit address assigned to hosts using TCP/IP.IP (Internet Protocol)A TCP/IP protocol that provides datagram delivery of messages.IPX (Internetwork Packet Exchange)A NetWare protocol similar to the Xerox Network Systems (XNS) protocol, providing datagram delivery of messages.IPX addressAn address comprising a four-byte network number, a six-byte node number, and a two-byte socket number. The network number is assigned to each LAN segment, server, or router. The node number identifies a specific system, and is typically the number assigned by the manufacturer or the network interface device. The socket number distinguished processes within the same computer. LAN (local area network)A group of computers and other devices connected by a communications link that allows any device to interact with any other device on the network.LAN driverA device driver that renders the different types of packet frames used by each specific network type into a form that AppleTalk can process.LocalTalk networkA system of cables, cable extenders, and connector boxes that connect computers and network devices as part of the AppleTalk network system. LocalTalk kits are manufactured by Apple Computer. Generally, where this reference refers to a LocalTalk connection, you can use any system of cables and connectors that supports AppleTalk protocols at 230.4 Kbps to interconnect Macintosh computers and other AppleTalk devices.ID="FM42184"LSP (Link State Packet)A packet generated by an NLSP router that lists the router's neighbors and attached IPX networks.ID="FM18367"neighborAn NLSP router that can form an adjacency with another NLSP router. Two NLSP routers are considered neighbors when they can communicate directly---that is, without the aid of an intermediate router.NetBIOS (Network Basic Input/Output System)An application program interface typically used on LANs comprising IBM and compatible microcomputers. NetBIOS separates application programs from the networking subsystem, so that application program implementers can support multiple network designs, and a network system can support independently developed applications.NetWareThe Novell network operating system that provides the ability to share services across dissimilar platforms. It uses the NetWare Core Protocol (NCP), Internetwork Packet Exchange (IPX), and Sequenced Packet Exchange (SPX) protocols transparently.NetWare Loadable ModuleSee IDREF="FM26432"NLM (NetWare Loadable Module).ID="FM25948"networkA collection of interconnected, individually controlled computers, together with the hardware and software used to connect them. See also IDREF="FM17639"internal network; IDREF="FM30635"internetwork.network addressA unique Network-layer number that refers to a logical network device. Also known as a protocol address. See also IDREF="FM35470"network number; IDREF="FM34134"node address.network administrationThe task of managing the software and hardware that connects computers in a network. This task includes assigning addresses to devices, maintaining network data files across the network, and setting up internetwork routing. Network administration can also include system tasks on a server, such as starting up and shutting down the system, adding and removing user accounts, and backing up and restoring data.network managementThe process of ensuring consistent reliability and availability of a network, as well as timely transmission and routing of data. It can be performed by dedicated devices or programmed general-purpose devices.network monitoringA network management function that constantly checks the network and reports any problems. ID="FM35470"network numberIn an AppleTalk network, a decimal integer between 1 and 65,279. You assign a network number to each nonextended network supporting AppleTalk. See also IDREF="FM24859"network range.In a TCP/IP network, the number of the network. Hexadecimal numbers must start with the character pair 0x or 0X. It can be specified with or without trailing zeros. For example, the addresses 130.57 and 130.57.0.0 denote the same IP network. ID="FM24859"network rangeOn an AppleTalk network, a contiguous range of decimal integers between 1 and 65,279, such as 1-10. You assign a network range to each extended network supporting AppleTalk. See also IDREF="FM35470"network number.network topologyThe arrangement of nodes on a network; usually a star, ring, tree, or bus organization.ID="FM26432"NLM (NetWare Loadable Module)An application or driver that resides on a NetWare server; it provides additional resource management capabilities.NLSP (NetWare Link Services Protocol)The link state protocol used by IPX routers and servers to share information about their routes with other devices on the network. NLSP enables network managers to interconnect small or large IPX networks without routing inefficiencies.ID="FM29508"nodeAn addressable entity on a network. This term sometimes refers to a device itself. Some examples of nodes are Macintosh computers, printers, and file servers. The node acquires a unique 8-bit node number dynamically when it connects to the network. It tries to use that address and node number again when it connects to the network the next time. If the node finds that its previous number is already in use, it tries again until it finds a unique node address. See also IDREF="FM34134"node address.ID="FM34134"node addressA number acquired dynamically by each node when it comes up on a network. You cannot assign an AppleTalk node address explicitly. A device's node address is combined with the network number to form its unique network address. See also IDREF="FM29508"node.nonextended networkAn AppleTalk network that does not support AppleTalk Phase 2 extensions, such as zone lists and network ranges.packet forwardingThe act of copying a packet from one interface to another through an intermediate system.PING (Packet Internet Grouper)A program used to test the reachability of destinations by sending them an Internet Control Message Protocol (ICMP) echo request and waiting for a reply.pollingAny procedure that sequentially and periodically contacts terminals in a network.port(1) The logical point of contact between a LAN driver and a protocol that you bind to it. (2) The hardware that enables a component to communicate with a peripheral, such as a parallel port. (3) A unique server input/output address assigned to a LAN driver in NetWare software.ID="FM26161"protocolA set of rules for transmitting data within a network or internetwork. A protocol specifies the format, timing, and sequence in which the network transmits data. Common protocols include AFP, ALAP, RTMP, NCP, and IPX.ID="FM40922"RIP (Routing Information Protocol)A distance vector protocol that provides a measure of distance, or hops, from a transmitting system to a receiving system.routerThe software that connects multiple networks so that all the nodes on each network can access services and nodes on any other network. It operates at the Network layer (Layer 3) of the OSI model for forwarding decisions. An AppleTalk router connects AppleTalk networks into an internetwork so that all the nodes on each network can access services and nodes on any other connected network. It receives and forwards AppleTalk packets on the networks to which it is directly connected. routingThe transmission of a datagram from one node to another on the same or a different network. It also refers to the paths that are chosen to transmit an IP datagram from its origin to its destination, based on the IP addresses contained in the datagram.ID="FM34609"routing information filterA type of filter that restricts the exchange of routing information between routers. These filters increase security by limiting the visibility of selected networks and reduce the network bandwidth consumed by the periodic exchange of routing information between routers.Routing Information TableIn the context of RIP, a table stored in an IPX RIP router that contains network numbers, routes to a particular destination network, and metrics---such as hops and ticks---associated with those routes. The router uses this information to forward packets to their destination by the best possible route. See also IDREF="FM74381"hop; IDREF="FM66278"tick.routing protocolA type of protocol that enables routing through the implementation of a specific routing algorithm. Examples of routing protocols include RIP, OSPF, NLSP, and IS-IS.routing tableA database in a router that keeps track of routes (and in some cases, metrics associated with those routes) to a particular network destination.routing updateA message sent from a router to indicate network reachability and associated cost information; it is typically sent at regular intervals and after a change in network topology.ID="FM14203"SAP (Service Advertising Protocol)A Novell protocol that disseminates information about network services and their addresses to all nodes in an IPX network.serverA combination of controller software and mass-storage devices that allows computer users to share common files and applications on a network. A server on an AppleTalk network might be a Macintosh computer running AppleShare software or an IBM PC (or a compatible computer) running the NetWare 4.1 protocol software.SNMP (Simple Network Management Protocol)A type of network management protocol used with various network protocols, such as IPX and IP.subnet address maskA bit mask used to select bits from an Internet address to create a subnet.subnetworkThe portion of the backbone that is partitioned by routers.subnetwork addressingThe process of using a single Internet ID to identify a number of subnetworks within an organization.System IDA unique, six-byte hexadecimal number that identifies an NLSP router.ID="FM41934"TCP (Transmission Control Protocol)The major transport protocol in the Internet suite of protocols, providing reliable, connection-oriented, full-duplex streams; it uses IP for delivery.ID="FM12010"TCP/IP (Transmission Control Protocol/Internet Protocol)The protocol suite developed by the Advanced Research Projects Agency (ARPA). It includes TCP as the primary transport protocol and IP as the Network-layer protocol.TCPCONA diagnostic tool from Novell that provides information about a NetWare server or router TCP/IP stack and about other TCP/IP networks on the internetwork.ID="FM66278"tickThe time delay to reach a network. The number of ticks is part of each network entry in a RIP packet. A tick is about 1/18 of a second. (There are 18.21 ticks in a second.) See also IDREF="FM40922"RIP (Routing Information Protocol).topologyThe physical layer of network components (cables, stations, gateways, and hubs). Three basic interconnection topologies are star, ring, and bus networks.Transmission Control ProtocolSee IDREF="FM41934"TCP (Transmission Control Protocol); IDREF="FM12010"TCP/IP (Transmission Control Protocol/Internet Protocol).transmission mediumThe physical path for carrying information, such as twisted-pair wires, coaxial cable, fiber-optic cable, terrestrial microwave, and satellite transmission methods.workstationA node through which a user can access a server or other nodes. ID="FM23964"zoneA logical grouping of devices physically located on one or more networks. Each nonextended network must have exactly one zone name assigned to it. Each extended network must have at least one zone name, and can have up to 255 zone names, assigned to it. See also IDREF="FM31006"zones list.ID="FM31006"zones listA list of up to 255 unique zone names. See also IDREF="FM23964"zone.