Officeconnect Networking Kit User Guide, 4/98

OfﬁceConnect® ¨ Networking Kit User Guide

A member of the OfficeConnect family

http://www.3com.com/

Part No. 09-1394-000 Published April 1998

3Com Corporation Copyright © 1998, 3Com Corporation. All rights reserved. No part of this documentation may be reproduced 5400 Bayfront Plaza in any form or by any means or used to make any derivative work (such as translation, transformation, or Santa Clara, California adaptation) without written permission from 3Com Corporation. 95052-8145 3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of 3Com Corporation to provide notification of such revision or change. 3Com Corporation provides this documentation without warranty, term, or condition of any kind, either implied or expressed, including, but not limited to, the implied warranties, terms or conditions of merchantability, satisfactory quality, and fitness for a particular purpose. 3Com may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time. If there is any software on removable media described in this documentation, it is furnished under a license agreement included with the product as a separate document, in the hard copy documentation, or on the removable media in a directory file named LICENSE.TXT or !LICENSE.TXT. If you are unable to locate a copy, please contact 3Com and a copy will be provided to you. UNITED STATES GOVERNMENT LEGEND If you are a United States government agency, then this documentation and the software described herein are provided to you subject to the following: All technical data and computer software are commercial in nature and developed solely at private expense. Software is delivered as “Commercial Computer Software” as defined in DFARS 252.227-7014 (June 1995) or as a “commercial item” as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in 3Com’s standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this User Guide. Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries. 3Com, the 3Com logo, DynamicAccess, EtherDisk, EtherLink, Net Age, and OfficeConnect are registered trademarks of 3Com Corporation. AutoLink and PACE are trademarks of 3Com Corporation. 3ComFacts is a service mark of 3Com Corporation. Anixter is a registered trademark of Anixter Bros., Inc. Artisoft and LANtastic are registered trademarks of Artisoft, Inc. Banyan and VINES are registered trademarks of Banyan Systems Incorporated. CompuServe is a registered trademark of CompuServe, Inc. DEC and PATHWORKS are registered trademarks of Digital Equipment Corporation. DeskJet and HP are registered trademarks of Hewlett-Packard Company. AT, IBM, and OS/2 are registered trademarks of International Business Machines Corporation. Microsoft, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. NetWare and Novell are registered trademarks of Novell, Inc. All other company and product names may be trademarks of the respective companies with which they are associated. Guide written by John Jeter, Jean Ghandchi, and Nick Franks. Revised by Phillip Schlueter. Edited by Nancy Kurahashi. Illustrated by Tim Buckreus and Mary Inden. Produced by Becky Whitmer.

CONTENTS

ABOUT THIS GUIDE Finding Speciﬁc Information in This Guide 1 Conventions 2

1 GETTING STARTED What This Guide Covers 1-1 What This Chapter Covers 1-1 Networking Kit Contents 1-2 Understanding Networking 1-3 Understanding the PC’s Role in Networking 1-5 Understanding Network Interface Cards 1-7 Understanding the Hub 1-8 Understanding Network Software 1-11 Understanding Network Servers 1-11 System Requirements 1-12 Required Hardware 1-12 Required Software 1-12 Where to Go from Here 1-12

2 INSTALLING YOUR NETWORK HARDWARE Getting Ready 2-1 Preinstallation 2-2 PCs with Plug and Play 2-3 PCs Without Plug and Play 2-3 Installing the NIC 2-4 Connecting NICs to the Hub 2-7 Interpreting the LED Indicators 2-9 NIC Link LED 2-9 Hub LED Status Indicators 2-10

3 EXPRESS SOFTWARE INSTALLATION FOR WINDOWS 95 Before Starting 3-1 Installing NIC Software 3-2

4 ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95 Before Starting 4-1 Verifying Each PC’s Identiﬁcation 4-2 Enabling File and Print Sharing 4-4 Giving Permission to Share Resources 4-5 Granting Access to a PC’s Hard Drive 4-6 Granting Access to a Printer 4-8 Adding the Network Printer to a PC’s Printers Folder 4-11 Verifying Your Network’s Shared Resources 4-18

5 CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT Is Custom Installation Right for You? 5-1 Windows 95 Setup for Custom Installation 5-2 Before Starting 5-2 Configuring a NIC in a Plug and Play PC 5-3 Configuring a NIC in a Non–Plug and Play PC 5-7 Disabling Plug and Play on the NIC 5-7 Configuring the NIC for Non–Plug and Play 5-8 Windows NT Setup for Custom Installation 5-11 Starting Custom Installation 5-12 Configuring the NIC 5-13 To Accept Configuration Settings 5-13 To Change Configuration Settings 5-14 Testing the NIC and the Network Connection 5-14 Installing TCP/IP Under Windows 95 5-16 To Not Install TCP/IP 5-16 To Install TCP/IP 5-17 Configuring TCP/IP Under Windows 95 5-17 To Obtain an IP Address Automatically 5-17 To Specify an IP Address Manually 5-18 iv

Configuring DNS 5-19 To Obtain a DNS Address Automatically 5-20 To Specify a DNS Address Manually 5-20 Identifying Your PC on the Network 5-22 Configuring DynamicAccess Software 5-23 To Not Configure DynamicAccess Software 5-23 To Configure DynamicAccess Software 5-24 Repeating a Previous Installation 5-24 To Not Save Installation Settings 5-25 To Save Installation Settings 5-25 Completing NIC Software Installation 5-28 Completing Installation for Windows 95 5-28 Completing Installation for Windows NT 5-30

6 SOFTWARE INSTALLATION FOR DOS, WINDOWS 3.1, AND WINDOWS FOR WORKGROUPS Installing NetWare Drivers for DOS, Windows 3.1, and Windows for Workgroups 6-1 AutoLink Requirements 6-1 Running the AutoLink Install Program 6-1 Obtaining NetWare Loadable Modules 6-3 Installing Other Supported Network Drivers 6-3 Configuring the NIC 6-4 Changing Configuration Settings 6-6 Reconfiguring the NIC for EISA 6-8 Changing NIC Configuration from ISA to EISA 6-8 Changing NIC Configuration from EISA to ISA 6-9

A SPECIFICATIONS Hub Specifications A-1 NIC Specifications A-1 RJ-45 Connector Pin Assignments A-2 Cable Specifications A-2

B DESIGNING YOUR NETWORK Determining Network Requirements B-1 Purpose of the Network B-2 Performance Factors B-2 Sharing Resources B-3 Peer-to-Peer Network B-3 Client/Server Network B-4 Network Checklist B-5

C TROUBLESHOOTING Checklist C-1 Resolving Hardware Conﬂicts in Windows 95 and Windows NT C-1 Changing the I/O Base Address or the Interrupt Request Level C-2 Windows 95 C-2 Windows NT C-3 Windows 95 and Windows NT Troubleshooting C-3 Diagnostic Testing Under Windows 95 and Windows NT C-4 Starting the 3Com NIC Diagnostics Program C-4 Running Tests C-5 NIC Test C-5 Network Test C-6 Uninstalling the NIC Software for Windows 95 or Windows NT C-6 Uninstalling the NIC Software for DOS, Windows 3.1, or Windows for Workgroups C-7 Reinstalling NIC Software C-7 Performing Automated Installations C-7 Installing from the Hard Disk C-7 Installing from a Diskette C-8 Diagnostic Testing for DOS, Windows 3.x, and Windows for Workgroups C-8 Starting the DOS Conﬁguration and Diagnostic Program C-9 Running the Group 1 Tests C-9 Running the Group 3 Test C-10 Setting Up an Echo Server C-10 Starting the Group 3 Test C-11 Getting Help If a Test Fails C-11 Changing the Test Setup C-13 vi

Using the Help Library C-14 Opening the EtherDisk Diskette Help Library C-14 Troubleshooting the Hub C-15

D EXPANDING YOUR NETWORK Understanding Connection Concepts D-1 Connecting Additional Hubs D-2 Using UTP Cable D-2 Using Coaxial Ethernet Cable D-5 Positioning the Hub D-6 Using the Nonskid Feet D-6 Stacking Multiple Hubs D-6 Wall-Mounting the Hub D-8

E TECHNICAL SUPPORT Online Technical Services E-1 World Wide Web Site E-1 3Com FTP Site E-2 3Com Bulletin Board Service E-2 Access by Analog Modem E-2 Access by Digital Modem E-3 3ComFacts Automated Fax Service E-3 Support from Your Network Supplier E-3 Support from 3Com E-3 Returning Products for Repair E-5

GLOSSARY

INDEX

3COM END USER SOFTWARE LICENSE AGREEMENT

3COM CORPORATION LIMITED WARRANTY

vii FCC DECLARATION OF CONFORMITY

FCC CLASS B STATEMENT

VCCI CLASS 2 STATEMENT

viii ABOUT THIS GUIDE

This guide describes how to set up your own network using the 3Com® OfﬁceConnect® Networking Kit. It includes detailed instructions on creating a peer-to-peer network through Windows 95 and other network operating systems, such as Windows NT and Novell NetWare.

This guide is appropriate for anyone who is familiar with the basic elements of a PC and is interested in networking several PCs or other devices, such as a printer or scanner.

If the information in the release notes shipped with your product differs from the information in this guide, follow the instructions in the release notes.

Finding Speciﬁc This table shows the location of speciﬁc information in this guide. Information in This Guide If you are looking for Turn to Description of your Networking Kit components Chapter 1 Overview of networking Chapter 1 Instructions for installing network interface cards (NICs) Chapter 2 Instructions for connecting NICs to the hub Chapter 2 Instructions for installing network client software on Windows 95 Chapter 3 Plug and Play PCs Instructions for enabling file and printer sharing through Windows 95 Chapter 4 Instructions for installing network client software on Windows NT or Chapter 5 Windows 95 non–Plug and Play PCs Instructions for installing network client software on PCs that are not Chapter 6 running Windows 95 or Windows NT Technical specifications for the NIC, hub, and cables Appendix A Network design information Appendix B Troubleshooting and diagnostic procedures Appendix C Information on expanding your network Appendix D Technical assistance Appendix E 2 ABOUT THIS GUIDE

Conventions Table 1 and Table 2 list conventions that are used throughout this guide. Table 1 Notice Icons

Icon Notice Type Description Information note Information that describes important features or instructions Caution Information that alerts you to potential loss of data or potential damage to an application, system, or device Warning Information that alerts you to potential personal injury

Table 2 Text Conventions

Convention Description Screen displays This typeface represents information as it appears on the screen. The words “enter” When you see the word “enter” in this guide, you must type and “type” something, and then press the Return or Enter key. Do not press the Return or Enter key when an instruction simply says “type.” Keyboard key names If you must press two or more keys simultaneously, the key names are linked with a plus sign (+). Example: Press Ctrl+Alt+Del Menu commands Menu commands or button names appear in italics. Example: and buttons From the Help menu, select Contents. Words in italicized Italics emphasize a point or denote new terms at the place type where they are defined in the text. 1 GETTING STARTED

The 3Com® OfﬁceConnect® Networking Kit contains everything you need to create a network with your personal computers (PCs).

What This Guide This guide provides all the information you need to install the components Covers of your Networking Kit. It tells you how to:

■ Insert a network interface card (NIC) into each PC to be included in your network

■ Attach each network PC to a hub with cables

■ Install NIC software on each network PC

■ Conﬁgure the NIC on each network PC

This guide also provides basic instructions for conﬁguring a simple Windows 95 peer-to-peer network (a standard type of small network). However, you should be familiar with the particular operating system (Windows 95, for example) running on your PCs, so that you can conﬁgure your network correctly once you’ve installed all the components. This guide is not intended to be a substitute for your operating system documentation.

If your PCs are running Windows 95 and you want to quickly install a peer-to-peer network, use the Quick Steps to Networking with Windows 95 guide included in your kit.

What This Chapter This chapter deﬁnes the types of PCs that are compatible with your kit. Covers It also describes your kit’s contents and provides a brief introduction to networking. If you’re already familiar with basic networking concepts and your kit’s contents, you can start with Chapter 2, “Installing Your Network Hardware.” 1-2 CHAPTER 1: GETTING STARTED

Networking Kit Your Networking Kit can be either of two models: a four-port version or Contents an eight-port version. This guide describes both types of kits.

The four-port kit includes the components shown in Figure 1-1:

! PWR Alert PKT Port Status Hub COLL 1 green = link OK, off =2 link fail, yellow = partition. 3 4

OFFICE CONNECT

Hub TP4

Quick Steps to Networking with Windows 95

Networking Kit User Guide NICs Nonskid feet

Stacking clips Quick Steps Guide User Guide

® EtherDisk For the EtherLink ® Configuration and Diagnostics NetWare ® Version 5.0 OS/2 ODI Drivers® III PC Card(DOS Family 1.44 MB) DOS and OS/2 NDIS 2.x, 3.x,2.01 and Drivers 4.x DOS and Transcend

Supports both ® Services and and SmartAgent 83-0705-000 Multifunction CardPCMCIA Services Release 2.1 A:>INSTALL PC Card Standard ™ Driver Agents © 1995, 3Com Corporation. All rights reserved. © 1994, 1995, Card Cables Novell, Inc. All rights reserved. NIC software Hub power adapter Figure 1-1 Contents of the Four-Port OfﬁceConnect Networking Kit

Table 1-1 lists the Networking Kit contents for both the four-port version and the eight-port version. Table 1-1 Networking Kit Contents

Kit Type 4-Port 8-Port Contents Version Version OfficeConnect Hub TP4 (with four ports) ✔ Two EtherLink® III ISA TPO (3C509B) network interface cards ✔ (NICs) Two 25-foot Category 5 unshielded twisted-pair (UTP) cables ✔ OfficeConnect Hub 8/TPC (with eight ports) ✔ Three EtherLink III ISA TPO (3C509B) NICs ✔ Three 50-foot Category 5 UTP cables ✔ (continued) Understanding Networking 1-3

Table 1-1 Networking Kit Contents (continued)

Kit Type 4-Port 8-Port Contents Version Version 3Com EtherDisk® diskettes 1 and 2 ✔ ✔ AC/DC power adapter for the hub ✔ ✔ OfficeConnect Networking Kit User Guide ✔ ✔ Quick Steps to Networking with Windows 95 guide ✔ ✔ Rubber nonskid feet for placing the hub on a desktop ✔ ✔ Plastic clips for stacking more than one hub together ✔ ✔

Understanding When two or more people get together to discuss topics of mutual Networking interest, they’ve formed a network. Networking is about communication, which is sharing information, experiences, and resources. That’s what the Networking Kit is about, too.

A computer network is a group of computers connected to one another so they can share resources and information.

When you use the Networking Kit to create a network, you can:

■ Share resources — You and others on the network can share resources, such as a data ﬁle or directory, hard disk drive, printer, scanner, or modem.

■ Exchange information — You can communicate and exchange information with all designated users on the network.

■ Provide server support — You can store ﬁles and applications in a central location on one PC hard drive (this PC is called a server), where they can be accessed by any network users who have the proper authorization. (The other PCs that use the server are called clients.) 1-4 CHAPTER 1: GETTING STARTED

Computer 2

Printer

Computer 1

10–30 VDC 1A MAX – +

MDI/X

OfficeConnect Hub Figure 1-2 Sample OfﬁceConnect Networking Kit Network

Figure 1-2 shows a sample OfﬁceConnect network composed of two PCs, a printer, and a hub.

Figure 1-2 shows an OfﬁceConnect network created with two network interface cards (NICs) and a four–port hub. Your kit may have three NICs and an eight–port hub. Table 1-1 provides a complete list of your kit’s components.

The Networking Kit provides a simple approach to building a network made of PCs and peripheral devices, such as printers, scanners, and modems. The network you create using the Networking Kit is easy to set up, yet ﬂexible enough to grow as your networking needs increase.

The next few sections brieﬂy explain the following basic components of a personal PC network:

■ PCs

■ NICs

■ Hub

■ Software

■ Server Understanding Networking 1-5

Understanding Even though the PCs you’re intending to use for your network may have the PC’s Role been built by different manufacturers, they all contain certain basic in Networking components common to all PCs (see Figure 1-3).

Hard drive Screw

Backplate

Diskette drives System board (motherboard) PCI slots ISA/EISA expansion Processor (CPU) slots (bus)

Figure 1-3 Components of a Typical PC

Table 1-2 on page 1-6 describes each PC component. See the documentation that came with your PC for detailed information about each component.

The type of PC that you’ll need for your network depends mostly on the task you want to accomplish with it. For example, if you just want the PC to be on the network to access a printer attached to another PC, you won’t need to add extra RAM and hard drive space. However, if several users will be accessing a program on the PC, you may want to make sure that the PC has sufﬁcient RAM and hard drive space. 1-6 CHAPTER 1: GETTING STARTED

Table 1-2 PC Component Deﬁnitions

PC Component Definition Bus An electronic pathway along which signals are transmitted from one area of a PC to another. Expansion slots Connectors on the bus into which you insert optional devices, such as NICs. They provide access to every part of the PC, including the memory and the central processing unit (CPU). Your PC could have any mix of the following types of expansion slots:

■ ISA (black)

■ EISA (brown)

■ PCI (white and shorter than ISA/EISA slots) Backplates The narrow metal panels that cover access to the expansion slots. They must be removed to insert NICs into the PC. Diskette drive A storage device that reads data from and writes data to diskettes (such as 3.5” diskettes) that you insert and remove by hand. Hard disk drive A permanent internal storage device that uses a set of rotating, magnetically coated disks to store data or programs. Your PC stores files on the hard drive. Memory The PC’s workplace, where all computing activity takes place. The primary type of memory installed in a PC is random access memory (RAM). The operating system copies applications from disk into memory, where all program execution and data processing takes place, and then writes the results back to disk. Processor or CPU The computing and control part of the PC. (central processing unit) System board (motherboard) A large printed circuit board containing all the parts that make the PC work. Understanding Networking 1-7

Understanding A network interface card (NIC) (Figure 1-4) is a printed circuit board that Network Interface plugs into a PC expansion slot to provide added capabilities to the PC. Cards

Backplate

RJ-45 port Link LED Edge connector

Figure 1-4 EtherLink III ISA TPO NIC

The NIC works with a family of programs, called a network operating system (NOS), to control the ﬂow of information over the network. You connect the NIC to the network media (cabling, such as UTP or coaxial), which in turn connects to all the devices on the network.

Your Networking Kit contains either two or three 3Com EtherLink III ISA TPO (3C509B) NICs, depending on your kit’s model.

ISA stands for Industry Standard Architecture bus, which has its roots in the original IBM AT personal computer. Although most PCs support the ISA bus, other buses exist, such as EISA (Extended Industry Standard Architecture) and PCI (Peripheral Component Interconnect). If you’re not sure which type of bus your PC supports, check your PC documentation.

A TPO (twisted-pair only) connector is the type of connector that accepts UTP cable to connect the NIC to the hub (see the next section, “Understanding the Hub”). Your Networking Kit contains unshielded twisted-pair (UTP) cables with an RJ-45 connector on each end. 1-8 CHAPTER 1: GETTING STARTED

If you need more cables than are supplied with your Networking Kit, you need to purchase them separately. Using a connector to attach two cables doesn’t work. (See cable speciﬁcations in Appendix A.) If you need cables longer than those supplied with your Networking Kit, note that the maximum Ethernet cable length allowed is 300 feet (100 meters).

The NIC slides into an expansion slot inside your PC and provides a connection for the UTP cable that connects your PC to the hub. (See Figure 1-2 on page 1-4.)

The NIC has an opening (port) on its backplate that looks similar to the one on the back of your telephone at home. It accepts the RJ-45 connector found on the end of the UTP cable.

CAUTION: Don’t try to plug a telephone line into the NIC or hub. The voltage differences may damage these devices.

The NIC backplate also has a light-emitting diode (LED) called the link LED. It shows whether there’s an active connection between the NIC and the hub. (See “NIC Link LED” on page 2-9 for more information.)

Understanding The hub is the heart of your network. It acts as a central concentration the Hub point for all the PCs and peripheral devices on your network.

To understand how the hub functions, visualize the wiring connecting your network as railroad tracks and the hub as a central railway station. If you try to connect every departure station with every destination station directly with a separate set of tracks, you’ll have a great tangle of rails. But if all departures feed into a central station, where they can be switched to appropriate destinations (as at a railway hub), trafﬁc ﬂow becomes much simpler.

Your Networking Kit contains one of the following hub types, depending on the model:

■ OfﬁceConnect Hub TP4

■ OfﬁceConnect Hub 8/TPC Understanding Networking 1-9

The OfﬁceConnect Hub TP4 (Figure 1-5) is a stand-alone hub with four 10BASE-T RJ-45 ports for UTP cable connections. You can connect up to four PCs or other network devices to the hub.

! PWR Alert PKT Port Status COLL 1 green = link OK, off =2 link fail, yellow = partition. 3 4

OFFICE CONNECT Power LED LED display Hub TP4 panel Figure 1-5 Front Panel of OfﬁceConnect Hub TP4

The OfﬁceConnect Hub 8/TPC (Figure 1-6) is a stand-alone hub with eight 10BASE-T RJ-45 ports for UTP cable connections. You can connect up to eight PCs or other network devices to the hub. The Hub 8/TPC also gives you the option to use 10BASE2 coaxial Ethernet cabling to connect up to 30 hubs.

! Alert PWR COLL Port Status 1 2 3 green = link OK, off4 = link fail, yellow = partition. 5 6 7 8 COAX Network Utilization 1% 2% 3% 6% 12% OFFICE 25% CONNECT 50% Power LED 80% Hub 8/TPC

LED display panel Figure 1-6 Front Panel of OfﬁceConnect Hub 8/TPC 1-10 CHAPTER 1: GETTING STARTED

The fourth RJ-45 port on the Hub TP4 (Figure 1-7) and the eighth port on the Hub 8/TPC (Figure 1-8) are switchable MDI/MDIX ports. (Ports are numbered in ascending order from right to left; therefore, the MDI/MDIX port is located farthest to the left on the rear panel.) MDI stands for Media Dependent Interface; MDIX stands for Media Dependent Interface with internal crossover switch.

MDI/X Power input 4

1X MDI/MDIX switch MDI/MDIX port

RJ-45 ports Figure 1-7 Rear Panel of OfﬁceConnect Hub TP4

+ COAX

MDI/X 8 Power input

BNC 1X coaxial connector MDI/MDIX port MDI/MDIX switch RJ-45 ports Figure 1-8 Rear Panel of OfﬁceConnect Hub 8/TPC Understanding Networking 1-11

The switch that controls the MDI/MDIX port is located to the left of the MDI/MDIX port. Table 1-3 describes how to use the MDI/MDIX switch. Table 1-3 MDI/MDIX Switch Positions

Position Meaning Out (MDIX) The MDI/MDIX port is used to connect one PC or peripheral device to the hub. The MDI/MDIX port is configured just like the other RJ-45 ports when set to MDIX. This is the standard setting for small networks using just one hub. All of the hub’s nonswitchable RJ-45 ports are permanently set to MDIX mode. In (MDI) The MDI/MDIX port is used to connect the hub to another hub.

All of the other RJ-45 ports are permanently set to MDIX mode (nonswitchable).

See Appendix D for information about expanding your network by using the MDI/MDIX port.

The BNC bayonet-lock connector on the rear panel of the Hub 8/TPC (Figure 1-8) provides a port for a thin Ethernet coaxial cable (10BASE2) connection that you can also use to connect hubs together, as shown in Figure D-4 on page D-5. The Hub TP4 does not have a BNC connector.

A series of LEDs on the hub’s front panel indicates the hub’s operating status. See “Hub LED Status Indicators” on page 2-10 for information about interpreting the hub LEDs.

Understanding In addition to the hardware necessary to create your network, you’ll need Network Software software to run it. Windows 95 has built-in support for networking, but you may require additional software for non–Windows 95 systems. See “System Requirements” later in this chapter for more information about software needed for your network.

Understanding A server is a special PC, usually with significant additional memory and Network Servers storage capacity, on which you can store programs, applications, files, and services that you want to make available to network users. When a user is able to access a network server from his or her PC, a client/server relationship exists. When a user exchanges a file or sends a message to another PC user, a client-to-client (or peer-to-peer) relationship exists. 1-12 CHAPTER 1: GETTING STARTED

To set up a PC as a server, you need a server NOS, such as Novell NetWare Server or Microsoft Windows NT. For more details about using a computer as a network server, contact your networking products supplier.

For more information about networking basics, see Appendix B, which has a worksheet that can help you plan your network installation.

System Be sure that you have the required equipment to set up your network, as Requirements described in this section. You may need to refer to the hardware and software documentation that came with your equipment.

Required Hardware The Networking Kit NICs can be installed in any IBM-compatible PC with an available ISA or EISA expansion slot. Almost all PCs currently on the market meet these requirements. (See “Installing the NIC” in Chapter 2 for more information about compatible expansion slots.)

Required Software If your PC is running Windows 95, most of the software you need (the NOS and device drivers) is already included. You may need the troubleshooting information and programs on the 3Com EtherDisk diskettes included with your Networking Kit.

If you’re not running Windows 95, you’ll need operating system software to conﬁgure your NIC. You’ll also need a network operating system (NOS), such as:

■ Novell Personal NetWare

■ NetWare Lite

■ Microsoft Windows for Workgroups

■ Artisoft LANtastic

The Networking Kit does not include operating system or NOS software. You must purchase these components separately.

The Networking Kit’s EtherDisk diskettes contain software (conﬁguration programs, diagnostic programs, and device drivers) that allows your NIC to work with all of the NOSs mentioned in this section.

Where to Go To get your network up and running, you ﬁrst need to install your kit’s from Here hardware components. Go to the next chapter. INSTALLING YOUR 2 NETWORK HARDWARE

This chapter explains the following tasks you need to perform to get started with setting up your network. It tells you how to:

■ Set up your PCs (preinstallation) so that you can use the 3Com Installation Wizard to install and conﬁgure each NIC

■ Insert a NIC in each PC to be networked

■ Connect the hub to each installed NIC using the cables supplied with your kit

Getting Ready Inspect the Networking Kit contents for damage. Familiarize yourself with the kit items (see Figure 1-1). You need these components:

■ EtherDisk diskettes

■ NICs (see the caution on page 2-4 before removing the NICs from their containers)

■ Hub

■ Power adapter for the hub

■ UTP cables

■ Nonconductive tool (not supplied in your kit) for removing the PC cover and installing a NIC

If your network will be somewhat large and complex, you might want to take some time to plan it carefully before starting installation. You can use the worksheet supplied in Appendix B to design your network.

Ready? Let’s get started by beginning with the preinstallation procedure described in the next section. 2-2 CHAPTER 2: INSTALLING YOUR NETWORK HARDWARE

Preinstallation You only need to run the preinstallation procedure if your PCs are running Windows 95.

If your PCs are running Windows 95, do not install the NIC until you’ve run the preinstallation procedure described in this section.

If your PCs are not running Windows 95, omit this section and go to the section, “Installing the NIC.”

The preinstallation routine tests your Windows 95 PC to:

■ Find out whether your PC supports the Windows 95 Plug and Play feature.

■ Make sure that the latest NIC driver can be successfully installed on your PC.

■ Make sure that the right version of the 3Com NIC Diagnostics program is copied to your PC’s hard drive during the software installation process.

To perform the preinstallation procedure for each PC that you want to attach to the network, follow these steps: 1 Turn the power on and boot (start) Windows 95. 2 Insert EtherDisk diskette 2 in the PC diskette drive (usually drive A). 3 Click Start in the Windows 95 taskbar at the bottom of the screen. 4 From the Start menu, select Run. 5 Enter the following text in the Open ﬁeld: a:\preinstl 6 Click OK. The 3Com Ethernet Preinstallation Software screen appears (Figure 2-1).

Figure 2-1 3Com Ethernet Preinstallation Software Screen Preinstallation 2-3

A list of available Interrupt Request Levels (IRQs) is displayed. An IRQ is like a mailbox ﬂag that signals when mail is ready to be sent or received at that address. The NIC needs to be assigned an available IRQ either automatically (through the Windows 95 Plug and Play feature) or manually. Write down the displayed IRQs and save the information. You may need to verify that one of the available IRQs is assigned to the NIC later during the installation process. 7 Click OK. The preinstallation software tests your PC to ﬁnd out whether it has a non–Plug and Play BIOS (Basic Input/Output System).

PCs with If the PC has a Plug and Play BIOS, the system completes preinstallation Plug and Play and displays the Windows 95 desktop.

A Plug and Play BIOS usually indicates that the PC supports the Windows 95 Plug and Play feature. If the PC supports the Windows 95 Plug and Play feature, you can then use the 3Com Installation Wizard to perform:

■ An Express software installation as described in Chapter 3, “Express Software Installation for Windows 95” (recommended) or

■ A Custom software installation as described in Chapter 5, “Custom Software Installation for Windows 95 and Windows NT”

Be sure to run preinstallation for all your network PCs before continuing with “Installing the NIC.”

PCs Without If the PC doesn’t have a Plug and Play BIOS, a message is displayed. If this Plug and Play is the case with your PC, click OK. The system completes preinstallation.

Because the PC has a non–Plug and Play BIOS, your installation tasks are a little different. You need to:

■ Complete preinstallation on all of the PCs to be networked.

■ Finish the hardware installation procedures in this chapter.

■ Disable the Plug and Play feature on the NIC to be inserted in this PC. (See “Disabling Plug and Play on the NIC” on page 5-7.) 2-4 CHAPTER 2: INSTALLING YOUR NETWORK HARDWARE

■ Conﬁgure the NIC for a non–Plug and Play BIOS. (See “Conﬁguring the NIC for Non–Plug and Play” on page 5-8.)

■ Perform a Custom software installation using the 3Com Installation Wizard, as described in “Starting Custom Installation” on page 5-12.

If you are installing the NIC in a Windows 95 PC that does not have a Plug and Play BIOS installed, you must install the NIC software using the Custom installation option.

Once you have completed preinstallation for all your network PCs, go to the next section.

Installing the NIC Before you install a Networking Kit NIC in any Windows 95 PC, make sure that you run preinstallation for that PC, as described in the preceding section. Once you’ve completed preinstallation, you’re ready to install the NIC.

CAUTION: Each NIC is packed in an antistatic container to protect it during shipment. To avoid damaging any static-sensitive components on the NIC, before you remove it from the container, touch the metal chassis of your PC. Also, be careful to handle the NIC by its edges only.

To install a NIC, follow these steps: 1 Remove all jewelry from your hands and wrists. Use only insulated or nonconductive tools to prevent damaging your equipment. 2 Turn off the PC. Unplug the power cable. Detach all other cables from the PC. 3 Remove the PC cover. (See your PC documentation for details.) 4 Find an available ISA (black) expansion slot and remove the screw from the corresponding backplate (Figure 2-2). Keep the backplate screw. You’ll need it for step 6. Remove the backplate and store it for future use. Your Networking Kit includes ISA NICs that are conﬁgured to work in ISA expansion slots. Most PCs have ISA, EISA, or PCI expansion slots (see Figure 2-3). ISA slots are usually black. EISA slots are usually brown, and are as long as ISA slots. PCI slots are usually white, and they are shorter than ISA and EISA slots. If you’re not sure what type of expansion slots your PC has, see your PC documentation for details. Installing the NIC 2-5

Screw

Backplate

Expansion slots Figure 2-2 Removing the Backplate

EISA ISA

PCI Figure 2-3 PC Expansion Slot Types

If you can’t ﬁnd an available ISA expansion slot, use an EISA slot. Your installation tasks are a little different with the NIC inserted in an EISA slot. You need to:

■ Finish the hardware installation procedures in this chapter.

■ Reconﬁgure the NIC from ISA mode to EISA mode. (See “Reconﬁguring the NIC for EISA” on page 6-8.) If your EISA-bus PC is running Windows 95 or Windows NT, you then need to:

■ Disable the Plug and Play feature on the NIC. (See “Disabling Plug and Play on the NIC” on page 5-7.)

■ Conﬁgure the NIC for a non–Plug and Play BIOS. (See “Conﬁguring the NIC for Non–Plug and Play” on page 5-8.) 2-6 CHAPTER 2: INSTALLING YOUR NETWORK HARDWARE

■ Perform a Custom software installation using the 3Com Installation Wizard, as described in “Starting Custom Installation” on page 5-12. You can’t perform an Express software installation. If your EISA-bus PC is running an operating system other than Windows 95 or Windows NT, you then need to follow the instructions in Chapter 6. 5 Carefully insert the NIC into the slot, pressing ﬁrmly with steady pressure until it’s seated properly (Figure 2-4). The NIC’s metal backplate should be positioned so that you can easily fasten it with the backplate screw. You shouldn’t be able to see any of the NIC’s edge connector (see Figure 1-4 on page 1-7).

Remove backplate

Insert NIC

ISA/EISA expansion PCI slots slots (bus) Figure 2-4 Inserting the NIC

Not all PCs have expansion slots positioned on the bottom of the chassis, as shown in Figure 2-4. You may be using a PC with the expansion slots on a vertical panel. If so, follow the same insertion instructions, except install the NIC horizontally. If it helps, position the PC on its side temporarily to insert the NIC securely. Connecting NICs to the Hub 2-7

6 Fasten the NIC with the backplate screw. 7 Replace the PC cover. If you need to reinsert screws, make sure that they are fastened tightly. 8 Reconnect the monitor, keyboard, mouse, and anything else that you disconnected before you opened the PC.

Repeat the steps in this section for each PC to be networked.

When you’ve ﬁnished installing a NIC in each PC to be networked, go to the next section.

Connecting NICs This section describes connecting each installed NIC to the hub. Before you to the Hub continue, ﬁnish installing all the NICs for your network, as described in the preceding section.

Your Networking Kit contains either a four-port Hub TP4 or an eight-port Hub 8/TPC. The setup instructions for both models are identical.

To connect the hub to each installed NIC, follow these steps: 1 Choose one of the UTP cables from your Networking Kit. Insert one of the RJ-45 connectors on the cable into the NIC RJ-45 port, as shown in Figure 2-5.

+ COAX RJ-45 port

RJ-45 port Twisted-pair cable Figure 2-5 Connecting the NIC to the Hub (Hub 8/TPC Shown) 2-8 CHAPTER 2: INSTALLING YOUR NETWORK HARDWARE

2 Insert the RJ-45 connector on the other end of the same UTP cable into any of the hub’s RJ-45 ports. You can plug PCs and other peripheral devices into any port on the hub’s rear panel. The port farthest to the left is a switchable port that allows you to connect the hub to another hub. When connecting the hub to a NIC or other peripheral device (not another hub), be sure that the MDI/MDIX switch is set to the OUT (MDIX) position. (For more information, see “Understanding the Hub” in Chapter 1 and “Connecting Additional Hubs” in Appendix D.) 3 Repeat steps 1 and 2 to connect the NICs in your other PCs to the hub. Peripheral devices, such as printers, may be network-ready (that is, they already have NICs inside them) if they have RJ-45 ports. You can also connect a peripheral device (such as a printer) directly to one of the network PCs through a serial or parallel port. In some instances, depending on the operating system and drivers you use, all of the PCs in your network may be able to access a printer or modem attached to one of the PCs through its serial or parallel port, thus freeing one RJ-45 port on the hub. (See Chapter 4, “Enabling File and Printer Sharing Through Windows 95,” for more information.) For complete information, see the documentation that came with the peripheral device, or contact the supplier of the device. 4 Plug the hub power adapter into the hub and then into an AC power socket (Figure 2-6). As soon as you plug the hub power adapter into the power socket, the green PWR (Power) LED on the hub lights steadily. A solid green Power LED indicates normal operation.

To AC Power input socket

Hub power + adapter MDI/X 4 RJ-45 ports MDI/MDIX switch 1X

MDI Twisted-pair cable

MDIX To NIC

Figure 2-6 Connecting the Hub to a Power Socket Interpreting the LED Indicators 2-9

When you’ve ﬁnished connecting the hub to NICs in all the PCs to be networked, check the LED information in the next section. Then you can proceed to the software installation chapter that’s appropriate for your setup, as described at the end of this chapter.

Interpreting the This section explains the meaning of the light-emitting diodes (LEDs) on LED Indicators the NIC and hub. The NIC has one LED on its backplate. The hub has a series of LEDs on its front panel.

NIC Link LED The LED on the NIC backplate (Figure 1-4 on page 1-7) detects the presence of a link between the hub and the NIC. The LED lights when a signal is sent between the hub and the NIC, conﬁrming an active connection.

When you ﬁrst install the NIC and start up the PC, the LED lights, but the link is inactive. For the link LED to be active (enabled), you need to have loaded the network drivers as described in the next chapters, or run the Group 3 test (see “Running the Group 3 Test” on page C-10).

If you have any problems, ﬁrst make sure that the hub is operational and then check the LED on the NIC connected to the hub.

The meaning of the link LED activity is shown in Table 2-1. Table 2-1 NIC LED Descriptions

LED Status Meaning On Link is working. Off Link has not been established, or there is a problem with the connection between the NIC and the hub. Blinking Cable polarity is reversed. Reversed cable polarity occurs when the pins in an RJ-45 connector are inserted into the wrong places. This condition usually indicates a faulty cable. If you are using a cable not supplied in your kit, see Appendix A for the correct RJ-45 connector pin assignments. 2-10 CHAPTER 2: INSTALLING YOUR NETWORK HARDWARE

Hub LED Status The OfﬁceConnect Hub LEDs are on the hub front panel, as shown in Indicators Figure 2-7. LEDs for both the eight-port Hub 8/TPC and four-port Hub TP4 are described in this section.

Interpreting the hub front panel LEDs is described in Table 2-2.

You can ﬁnd additional hub setup and troubleshooting information in Appendix D, “Expanding Your Network.”

8-Port Hub 8/TPC

Port Status Network Utilization OFFICE CONNECT

! PWR COLL 1 2 3 4 5 6 7 8 COAX 1% 2% 3% 6% 12% 25% 50% 80% Alert green = link OK, off = link fail, yellow = partition. Hub 8/TPC

Alert Port Status LEDs Network Utilization LEDs Collision LED Power LED

4-Port Hub TP4

Port Status OFFICE CONNECT

! PWR PKT COLL 1 2 3 4 Alert green = link OK, off = link fail, yellow = partition. Hub TP4

Alert Port Status LEDs Collision LED Packet LED Power LED Figure 2-7 OfﬁceConnect Hub LED Panel Interpreting the LED Indicators 2-11

Table 2-2 Hub LED Descriptions

Name Color Function Alert Orange Alerts you to excessive network use or an isolated (partitioned*) 10BASE-T port. PWR (Power) Green Indicates that the power supply to the hub is present. PKT (Packet) Yellow Flashes each time a network packet is sent or received. (Hub TP4 only) COLL (Collision) Yellow Flashes each time a collision is detected on the network. Collisions are part of normal network operation. Port Status Indicates the status of each port. Green The link between the port and the next piece of network equipment is OK. If nothing is connected or the cable is bad, the LED is off. Yellow Partitioning on the port has occurred because of a fault on that segment.† The COAX (coaxial) port LED can only be yellow or green. It is yellow if the port has been partitioned. If the port is not in use, yellow is OK. Off Nothing is connected or the cable is bad. Network Utilization Indicates how much your network is being used. (Hub 8/TPC only) Green 1%, 2%, 3%, 6%, or 12% of bandwidth used (as lit). Yellow 25%, 50%, 60% of bandwidth used. Orange More than 65% of bandwidth used. * Partitioning means that the port is shut off and no data can be transmitted. † A segment is the length of Ethernet cable connected to a port. When you daisy-chain equipment together with the BNC connectors (that is, using 10BASE2 cable), all the equipment forms a segment.

When you’ve ﬁnished connecting the hub to NICs in all the PCs to be networked, continue with your network installation by going to the appropriate chapter. Go to:

■ Chapter 3 if your PCs are Plug and Play-compatible and are running Windows 95. To determine whether a PC is Plug and Play-compatible, see “Preinstallation” at the beginning of this chapter.

■ Chapter 5 if your PCs are not Plug and Play-compatible and are running Windows 95 or Windows NT.

■ Chapter 6 if your PCs aren’t running Windows 95 or Windows NT.

EXPRESS SOFTWARE INSTALLATION 3 FOR WINDOWS 95

This chapter describes how to install network software for a NIC inserted in a Windows 95 PC with a Plug and Play BIOS (which usually indicates that the PC supports the Windows 95 Plug and Play feature).

To determine whether your Windows 95 PC has a Plug and Play BIOS, perform the preinstallation procedure described on page 2-2. If your Windows 95 PC doesn’t support the Windows 95 Plug and Play feature, don’t use the instructions in this chapter. See Chapter 5 instead. If your PC isn’t running Windows 95, or if you’ve inserted the NIC in an EISA expansion slot, see Chapter 6.

Under Windows 95, Plug and Play automatically conﬁgures the NIC and PC and installs the NIC software, including the:

■ Device driver

■ I/O base (input/output location) assignment

■ IRQ (interrupt request line) assignment

The device driver allows the PC to control the NIC. The PC uses the NIC’s I/O base assignment to ﬁnd the NIC when it needs to, just as a letter carrier uses your street address to deliver and pick up your mail. The IRQ works like the ﬂag on the mailbox for that address, signaling when it’s appropriate to pick up or deliver mail.

Before Starting Before installing NIC software for each PC, make sure that you’ve ﬁnished connecting the hub to the NICs in all the PCs to be networked, as described in Chapter 2.

Have your Windows 95 CD (or diskettes) and your Networking Kit EtherDisk diskettes ready.

If you can’t ﬁnd your Windows 95 CD or diskettes, you can still continue with the procedure. Your hard drive may already have the required Windows ﬁles. 3-2 CHAPTER 3: EXPRESS SOFTWARE INSTALLATION FOR WINDOWS 95

Installing NIC To install the NIC software, follow these steps: Software 1 Turn the PC power on and boot (start) Windows 95. Windows detects the NIC and displays the New Hardware Found screen, as shown in Figure 3-1.

Figure 3-1 New Hardware Found Screen

If your PC is running OEM Windows 95 (version B), then the screens that appear are slightly different from those shown in this section. Follow the displayed directions and insert the appropriate diskette or CD when prompted. 2 Insert EtherDisk diskette 1 in the PC diskette drive (usually drive A). 3 Click OK. The Install From Disk screen appears (Figure 3-2).

Figure 3-2 Install From Disk Screen Installing NIC Software 3-3

4 Make sure that the drive letter in the ﬁeld corresponds to the diskette drive containing the EtherDisk diskette. Click OK. The system copies ﬁles from the EtherDisk diskette to the PC hard drive and builds a driver information database.

■ If you’ve never assigned computer and workgroup names for this PC, Windows displays the Network screen (Figure 3-3). In this case, continue at step 5.

■ If you’ve previously assigned computer and workgroup names for this PC, the 3Com Installation Wizard welcome screen appears (Figure 3-5). In this case, go to step 8. You can ﬁll in the Network screen ﬁelds later, as described in Chapter 4, “Enabling File and Printer Sharing Through Windows 95.”

Figure 3-3 Network Screen

5 Click OK. The Identiﬁcation tab of the Network screen appears (Figure 3-4).

Figure 3-4 Identiﬁcation Tab of the Network Screen 3-4 CHAPTER 3: EXPRESS SOFTWARE INSTALLATION FOR WINDOWS 95

6 Type in names for the PC and its workgroup according to the following guidelines.

Computer name Identifies the computer on the network for other users. This entry must be a unique name of 15 characters or fewer, containing no spaces. Workgroup Identifies the group to which your computer belongs. If you’re setting up a simple peer-to-peer network, this entry must be the same for all the PCs in your network. Computer Description Displays additional details to other users on the network about this PC. For example, you could specify that the PC has a printer attached. Filling in this field is optional.

7 Click Close. The 3Com Installation Wizard welcome screen appears (Figure 3-5).

Figure 3-5 3Com Installation Wizard Welcome Screen Installing NIC Software 3-5

The Installation Wizard provides two ways to install the NIC software:

■ Express installation — Recommended for PCs that support the Windows 95 Plug and Play feature. Express installation automatically installs all the NIC software features, conﬁgures and tests the NIC, and tests the network connection between the NIC and the hub. Express installation does not work in non–Plug and Play PCs.

■ Custom installation — Recommended for PCs that don’t support the Windows 95 Plug and Play feature, and large network installations. Custom installation gives you more control over the installation process by allowing you to omit certain installation features and skip some network tests. Custom installation works in both Plug and Play and non–Plug and Play PCs. To view online Installation Wizard Help information at any point, click the Help button in the lower right corner of the screen. 8 Select the Express Installation or Custom Installation radio button, and then click Next.

■ If you selected Custom Installation, go to “Starting Custom Installation” on page 5-12.

■ If you selected Express Installation, go to step 9. Express installation is designed to be ﬂexible enough for very large organizations with established networks. It performs an additional test for an Internet TCP/IP (Transmission Control Protocol/Internet Protocol) connection to a DHCP (Dynamic Host Conﬁguration Protocol) server. If you’re setting up a simple peer-to-peer network and not using your kit to attach to a large existing client/server network that provides Internet access, the Installation Wizard informs you that it can’t detect a DHCP server on your network. The system displays the following message: Can’t contact DHCP server. Don’t worry about the DHCP message. It simply tells you that no DHCP server is attached to your network, which is normal for peer-to-peer networks. 3-6 CHAPTER 3: EXPRESS SOFTWARE INSTALLATION FOR WINDOWS 95

9 Click OK to acknowledge the DHCP message. The Installation Complete screen appears (Figure 3-6).

Figure 3-6 Installation Complete Screen

10 Click Finish. The system copies more ﬁles to the PC hard drive and then prompts you to insert the Windows 95 CD. 11 Insert the Windows 95 CD in the CD-ROM drive and click OK. The Copying Files screen appears (Figure 3-7).

Figure 3-7 Copying Files Screen Installing NIC Software 3-7

12 Type or use the pull-down menu to replace the A:\ entry with the following entry: d:\win95 The CD-ROM drive is usually the D drive, but your CD-ROM drive may be different. Enter the appropriate drive letter. If you have Windows 95 diskettes instead of a Windows 95 CD, remove the EtherDisk diskette, insert the appropriate Windows 95 diskette (Windows veriﬁes your choice), and select the appropriate diskette drive, such as the A drive. 13 Click OK. Windows copies ﬁles from the Windows 95 CD (or diskettes) to the PC hard drive. Windows then prompts you to restart the PC (Figure 3-8).

Figure 3-8 System Settings Change Screen

14 Remove the EtherDisk diskette (or Windows diskette) from drive A and click Yes to restart. (You can also remove the Windows 95 CD.) Your PC may display a message regarding a missing DHCP server upon restart. In most cases, your network doesn’t require a DHCP server, so you can ignore the message and continue. Windows 95 restarts and prompts you for a network password (Figure 3-9).

Figure 3-9 Enter Network Password Screen 3-8 CHAPTER 3: EXPRESS SOFTWARE INSTALLATION FOR WINDOWS 95

15 Type your user name (unless one is already displayed). If you haven’t previously entered a user name for this PC, the User name ﬁeld is empty. Type your user name now. 16 Type the network password and click OK. Conﬁrm the password if the system prompts you to do so. When the Windows 95 desktop is displayed, note that it now shows a Network Neighborhood icon.

Note also that a 3Com NIC Diagnostics program icon appears in the Windows 95 taskbar tray. To start the diagnostic program, double-click the tray icon. To disable the tray icon, right-click the icon and select Disable Tray Icon.

Congratulations! Your Networking Kit is now installed.

However, before you can effectively use your peer-to-peer network, you need to conﬁgure Windows 95 to allow resource sharing. Sharing resources is described in Chapter 4, “Enabling File and Printer Sharing Through Windows 95.” ENABLING FILE AND 4 PRINTER SHARING THROUGH WINDOWS 95

This chapter explains the ﬁnal few tasks you need to perform before your Windows 95 peer-to-peer network is functioning properly. It describes how to enable (activate) ﬁle and printer sharing through Windows 95.

If you’re not installing a Windows 95 peer-to-peer network, skip this chapter.

To configure your Windows 95 peer-to-peer network, you need to perform the following five steps. You must: 1 Verify each PC’s identification. 2 Activate each PC’s file and printer sharing. 3 Give permission to share resources on each PC. 4 Add the network printer to each PC’s Printers folder. 5 Confirm your network’s shared resources.

Although this chapter focuses on enabling ﬁle and printer sharing, you can also use this method to enable sharing for other resources.

Your Windows 95 documentation may be more current than the information in this guide. See your Windows 95 documentation if the instructions in this chapter don’t match your system.

Before Starting Before starting, verify that you’ve installed the kit’s hardware and software as described in the preceding chapters. If you’ve completed these tasks, you’re ready to continue. To get started with enabling ﬁle and printer sharing, go to the next section. 4-2 CHAPTER 4: ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95

Verifying Each PC’s During the NIC driver software installation, you may have been given the Identiﬁcation opportunity to deﬁne the following information for each PC:

■ Computer name

■ Workgroup

■ Computer description

There may be several PCs or other devices on your network, and each one needs to have a unique computer name. In addition, all the PCs must belong to the same workgroup to share resources. To verify that the identifying information for each PC is correct across your network, complete the following steps: 1 Right-click the Network Neighborhood icon on your Windows 95 desktop.

The Network Neighborhood menu appears. 2 Click Properties. The Configuration tab of the Network screen appears (Figure 4-1). All of the network components displayed in the Configuration tab were added when you installed the NIC driver software. 3 Click the Identification tab to display the Computer name, Workgroup, and Computer Description fields, as shown in Figure 4-2. 4 Make sure that each PC has a unique computer name. Make sure that all the networked PCs have the same workgroup name. Entering a computer description is optional. For detailed information regarding the Identification tab fields, see step 6 on page 3-4. If you change any of the identifying information shown in the Identification tab (Figure 4-2), you’ll have to restart Windows 95.

Once you’ve veriﬁed each PC’s identiﬁcation, go to the next section. Verifying Each PC’s Identification 4-3

Figure 4-1 Conﬁguration Tab of the Network Screen

Figure 4-2 Identiﬁcation Tab of the Network Screen 4-4 CHAPTER 4: ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95

Enabling File and Enabling (activating) file sharing on a PC allows other users in the same Print Sharing workgroup to access files and directories on that PC. Enabling printer sharing on a PC allows other users in the same workgroup to print files on the printer attached to that PC.

To enable file and printer sharing, follow these steps for each networked PC whose files and printer (if present) are to be accessed by other PCs in the same workgroup: 1 Right-click the Network Neighborhood icon on your Windows 95 desktop. The Network Neighborhood menu appears. 2 Click Properties. The Configuration tab of the Network screen appears (Figure 4-1). 3 Click the File and Print Sharing button. The File and Print Sharing screen appears (Figure 4-3).

Figure 4-3 File and Print Sharing Screen

4 Select both check boxes in the File and Print Sharing screen to display check marks as shown in Figure 4-3. 5 Click OK. The Conﬁguration tab of the Network screen appears with a new File and printer sharing for Microsoft Networks component displayed at the bottom of the component list, as shown in Figure 4-4. Giving Permission to Share Resources 4-5

Figure 4-4 Conﬁguration Tab with File and Print Sharing Enabled

6 Click OK. Windows 95 prompts you to restart. 7 Click Yes to restart Windows 95.

You‘ve just enabled overall ﬁle and print sharing for this PC. However, before users can access any resources on this PC, you must specify the resources that can be shared. The next section describes how to turn sharing on for selected resources.

Giving Permission This section shows you how to set sharing (turn sharing on) for a PC’s to Share Resources hard drive and printer. Turning sharing on for these resources allows all PCs in the network workgroup to use them.

You can also restrict access to certain resources and certain users. See your Windows 95 documentation for additional information. 4-6 CHAPTER 4: ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95

Granting Access to a Follow these steps to allow all users in the workgroup to access all the PC’s Hard Drive ﬁles on the hard drive of a particular PC: 1 From the Windows 95 desktop, double-click the My Computer icon.

You can accomplish the same task by double-clicking the Explorer icon, which gives you access to specific directories and files. For this procedure, you want to grant access to all directories and files on the C hard drive, which can be accomplished through the My Computer icon. The My Computer window appears (Figure 4-5).

Figure 4-5 My Computer Window

2 Right-click the hard drive icon (the C drive in this example). The Hard Drive menu appears (Figure 4-6). 3 From the Hard Drive menu, select Sharing, as shown in Figure 4-6. The hard drive Properties screen appears (Figure 4-7). 4 Select the Shared As radio button, as shown in Figure 4-7. You can enter a different share name and add a comment if you want. 5 Select the Full radio button under Access Type. This option allows complete read and write access by other network users to all ﬁles on this PC’s hard drive. Giving Permission to Share Resources 4-7

Figure 4-6 Hard Drive Menu

Figure 4-7 Hard Drive Properties Screen

You can limit access to the hard drive by selecting Read-Only or Depends on Password. See your Windows 95 documentation for details. 4-8 CHAPTER 4: ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95

6 Click OK. The My Computer window reappears, as shown in Figure 4-8. Note that the (C:) hard drive icon now appears with a hand under it, showing that it is a shared resource.

Figure 4-8 My Computer Window Showing Shared (C:) Hard Drive

This completes the procedure for allowing users to share the ﬁles and directories on the PC’s hard drive. The next section describes how to share a printer.

Granting Access Follow these steps to allow all users in the workgroup to use the printer to a Printer attached to a particular PC. (It’s assumed that you’ve already installed the printer through Windows 95.) 1 From the Windows 95 desktop, double-click the My Computer icon. The My Computer window appears (Figure 4-9).

Figure 4-9 Printers Icon Selected Giving Permission to Share Resources 4-9

2 Double-click the Printers folder, as shown in Figure 4-9. The Printers window appears (Figure 4-10). The example shows that one printer has already been installed and conﬁgured. That printer is represented by the single printer icon labeled HP DeskJet.

Figure 4-10 Printers Window

3 Right-click the printer icon, as shown in Figure 4-10. The Printer menu appears, as shown in Figure 4-11.

Figure 4-11 Printer Menu 4-10 CHAPTER 4: ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95

4 From the Printer menu, select Sharing, as shown in Figure 4-11. The Sharing tab of the printer Properties screen appears (Figure 4-12).

Figure 4-12 Sharing Tab of the Printer Properties Screen

5 Click the Shared As radio button. The Sharing tab appears, as shown in Figure 4-12. You can enter a different share name and add a comment if you want. 6 Click OK. The Printers window reappears, as shown in Figure 4-13. Note that the printer icon now appears with a hand under it, showing that it is a shared resource.

Figure 4-13 Shared Printer

This completes the procedure for granting permission to share the printer attached to a particular PC. However, other networked PCs won’t be able to access the shared printer until that printer has been added to each PC’s Printers folder. The next section explains this ﬁnal setup task. Adding the Network Printer to a PC’s Printers Folder 4-11

Adding the Network After granting permission to share the printer attached to one of the Printer to a PC’s network’s PCs, you must add the shared printer to the Printers folder on Printers Folder all the other PCs attached to the network.

For the PCs that are not locally (directly) attached to the printer, follow these steps: 1 Make sure that your network printer is powered on, that it’s online (ready), and that the PC that’s directly attached to the printer is also powered on and ready. 2 From the Windows 95 desktop, double-click the My Computer icon. The My Computer window appears (Figure 4-14).

Figure 4-14 Printers Icon Selected

3 Double-click the Printers folder, as shown in Figure 4-14. The Printers window appears (Figure 4-15). No printer icon is displayed in the example, indicating that this PC is not yet conﬁgured to use a printer.

Figure 4-15 Printers Window of a PC Not Locally Attached to the Printer

4 Double-click the Add Printer icon. 4-12 CHAPTER 4: ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95

The Add Printer Wizard starts and displays the welcome screen shown in Figure 4-16.

Figure 4-16 Add Printer Wizard Welcome Screen

5 Click Next. The Add Printer Wizard prompts you to select the type of printer attachment, local or network, as shown in Figure 4-17.

Figure 4-17 Attachment Type Screen Adding the Network Printer to a PC’s Printers Folder 4-13

6 Select the Network printer radio button. The printer that you’re adding is not locally (directly) attached to the PC you’re conﬁguring. You need to attach the printer through the network. 7 Click Next. The Add Printer Wizard prompts you for the printer’s network path, as shown in Figure 4-18.

Figure 4-18 Add Printer Wizard Network Path Screen

8 Click Browse. The Browse for Printer screen appears, as shown in Figure 4-19. For this example, the network printer is currently attached to the PC named Computer_1.

Figure 4-19 Browse for Printer Screen 4-14 CHAPTER 4: ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95

9 Double-click Computer_1 in the Browse for Printer screen. The printer that is locally (directly) attached to the PC named Computer_1 is displayed, as shown in Figure 4-20.

Figure 4-20 Locally Attached Printer Screen

10 Select the printer displayed in the Browse for Printer screen, as shown in Figure 4-21.

Figure 4-21 Selecting the Network Printer Screen

11 Click OK. The Add Printer Wizard displays the network path for the printer, as shown in Figure 4-22. Leave the Do you print from MS-DOS-based programs? query set to No. Adding the Network Printer to a PC’s Printers Folder 4-15

Figure 4-22 Add Printer Wizard Network Path Screen (Completed)

Figure 4-23 Existing Driver Inquiry Screen

12 Click Next. If the Add Printer Wizard detects that a driver is already installed for the selected printer, it asks whether you want to keep the existing driver, as shown in Figure 4-23. Leave the Keep existing driver (recommended) setting selected, as shown in Figure 4-23. 4-16 CHAPTER 4: ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95

13 Click Next. The Add Printer Wizard displays a name for the printer and gives you the chance to change it, as shown in Figure 4-24.

Figure 4-24 Printer Name Screen

Changing the name here only affects the name as it’s shown in this PC’s Printers ﬁle. It doesn’t affect the PC that’s directly attached to the printer.

If Windows 95 detects more than one printer on your network, it gives you the chance at this point to designate the printer as the default printer, forcing all your Windows applications to print directly to that printer.

14 Click Next. The Add Printer Wizard asks whether you want to print a test page, as shown in Figure 4-25. Leave the setting at Yes (recommended), so that you can conﬁrm that your network printer connection is working. Adding the Network Printer to a PC’s Printers Folder 4-17

Figure 4-25 Test Page Inquiry Screen

15 Click Finish. Windows 95 sends a test page to the printer and asks you to conﬁrm that the test page printed correctly, as shown in Figure 4-26.

Figure 4-26 Printer Text Page Completed Screen

16 If the test page printed correctly, click Yes. If the test page didn’t print correctly, click No. Follow the displayed Windows 95 troubleshooting instructions. 4-18 CHAPTER 4: ENABLING FILE AND PRINTER SHARING THROUGH WINDOWS 95

Verifying Your To confirm that your network’s setup and shared resources are configured Network’s Shared correctly, you can perform the following simple test. The examples used Resources in this procedure show a network involving two PCs, Computer_1 and Computer_2, and one printer attached to Computer_2. 1 From the Windows 95 desktop of the first network PC (Computer_1 in this example), double-click the Network Neighborhood icon.

The Network Neighborhood window appears, as shown in Figure 4-27.

Figure 4-27 Network Neighborhood Window

If all your network PCs don’t initially appear in the list, wait 2 minutes, close the window, and then double-click the Network Neighborhood icon again. The Network Neighborhood window shown in Figure 4-27 displays all of the networked PCs belonging to the workgroup you assigned (Workgroup_1 in this example), indicating that the network is conﬁgured properly. 2 Double-click Computer_2 in the Network Neighborhood window. The Computer_2 window appears, as shown in Figure 4-28.

Figure 4-28 Computer_2 Window Verifying Your Network’s Shared Resources 4-19

The Computer_2 window shows the Computer_2 resources that you configured for sharing across the network: hard drive (C) and the printer that is directly attached to Computer_2. 3 Double-click the Hard Drive (C) folder to confirm that you have access to all the directories and files on Computer_2’s hard drive. The Contents of C Drive on Computer_2 window appears, as shown in Figure 4-29. Your files might be shown in a different format, depending on your PC’s Windows 95 viewing configuration.

Figure 4-29 Contents of C Drive on Computer_2

Being able to view Computer_2’s hard drive (C) directories from Computer_1 indicates that you’ve successfully completed the setup of your peer-to-peer network. Congratulations!

CUSTOM SOFTWARE 5 INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

This chapter describes how to use the 3Com Installation Wizard to perform a Custom installation of the NIC software on PCs running Windows 95 or Windows NT.

To conﬁrm that the instructions in this chapter are appropriate for your PC, see Table 5-1. Table 5-1 NIC Software Installation Roadmap

Does the PC Have a Plug and Play Other Operating BIOS?* Windows 95 Windows NT Systems Yes See Chapter 3 to See Chapter 5 to See Chapter 6 to use Express use Custom use Non-Wizard installation. installation. installation. or See Chapter 5 to use Custom installation. No See Chapter 5 to See Chapter 5 to See Chapter 6 to use Custom use Custom use Non-Wizard installation. installation. installation.

* See “Preinstallation” in Chapter 2 for instructions on determining whether your PC has a Plug and Play BIOS.

Is Custom Custom installation is right for you if either of the following statements Installation Right is accurate: for You? ■ You have one or more non–Plug and Play PCs that are running Windows 95 or Windows NT

■ You are a knowledgeable network user who needs to use different conﬁguration settings or change test sequences for automated Windows 95 or Windows NT installations (usually for large networks) 5-2 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

Custom installation loads the latest drivers from the EtherDisk diskette and gives you the following options. It lets you:

■ Conﬁgure the NIC for a non–Plug and Play PC

■ Test the NIC and its hub connection

■ Configure TCP/IP (Configuring TCP/IP is only beneficial if you are using your kit to attach to an existing large network that has Internet access.)

■ Configure DynamicAccess® software (Configuring DynamicAccess is beneficial only for networks large enough to require a dedicated network administrator.)

■ Save, change, or disable configuration settings and test options that you select during the installation for use in future installations (Saving configuration settings is beneficial primarily for maintaining large networks). If your PC is running Windows 95, go to the next section. If your PC is running Windows NT, go to “Windows NT Setup for Custom Installation” on page 5-11.

Windows 95 Setup This section describes how to set up your Windows 95 environment to for Custom install and conﬁgure the NIC using the 3Com Installation Wizard Custom Installation installation option. This section includes procedures for PCs with and without a Plug and Play BIOS. See “Preinstallation” in Chapter 2 for instructions on determining whether your PC has a Plug and Play BIOS.

Before Starting Before installing NIC software for each PC, make sure that you’ve ﬁnished connecting the hub to the NICs in all the PCs to be networked, as described in Chapter 2.

Have your Windows 95 CD (or diskettes) and your Networking Kit EtherDisk diskettes ready.

If you can’t ﬁnd your Windows 95 CD or diskettes, you can still continue with the procedure. Your hard drive may already have the required Windows ﬁles. Windows 95 Setup for Custom Installation 5-3

To ﬁnd Windows 95 setup instructions in this section that are appropriate for your PC, see Table 5-2. Table 5-2 Windows 95 Custom Software Installation Roadmap

Does the PC Have a Plug and Play BIOS? Windows 95 Custom Installation Instructions Yes See “Configuring a NIC in a Plug and Play PC,” page 5-3. No See “Configuring a NIC in a Non–Plug and Play PC,” page 5-7.

Conﬁguring a NIC in a This section describes how to set up your system environment when Plug and Play PC installing the NIC in a Windows 95 PC that has a Plug and Play BIOS installed.

To install the NIC software, follow these steps: 1 Turn on the PC power and boot (start) Windows 95. Windows detects the NIC and displays the New Hardware Found screen, as shown in Figure 5-1.

Figure 5-1 New Hardware Found Screen

If your PC is running OEM Windows 95 (version B), then the screens that appear are slightly different from those shown in this section. Follow the displayed directions and insert the appropriate diskette or CD when prompted. 2 Insert EtherDisk diskette 1 in the PC diskette drive (usually drive A). 5-4 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

3 Click OK. The Install From Disk screen appears (Figure 5-2).

Figure 5-2 Install from Disk Screen

■ If you’ve never assigned computer and workgroup names for this PC, Windows displays the Network screen (Figure 5-3). In this case, continue at step 5.

■ If you’ve previously assigned computer and workgroup names for this PC, the 3Com Installation Wizard welcome screen appears (Figure 5-5). In this case, go to step 8. You can ﬁll in the Network screen ﬁelds later, as described in “Identifying Your PC on the Network” on page 5-22.

Figure 5-3 Network Screen Windows 95 Setup for Custom Installation 5-5

5 Click OK. The Identiﬁcation tab of the Network screen appears (Figure 5-4).

Figure 5-4 Identiﬁcation Tab of the Network Screen

6 Type in names for the PC and its workgroup according to the following guidelines.

Computer name Identifies the PC on the network for other users. This entry must be a unique name of 15 characters or fewer, containing no spaces. Hyphens are allowed. Workgroup Identifies the group to which your PC belongs. If you’re setting up a simple peer-to-peer network, this entry must be the same for all the PCs in your network. Computer Description Displays additional details to other users on the network about this PC. For example, you could specify that the PC has a printer attached. Filling in this field is optional. 5-6 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

7 Click Close. The 3Com Installation Wizard welcome screen appears (Figure 5-5).

Figure 5-5 3Com Installation Wizard Welcome Screen

The Installation Wizard provides two ways to install the NIC software:

■ Custom installation — Recommended for PCs that don’t support the Windows 95 Plug and Play feature, and large network installations. Custom installation gives you more control over the installation process by allowing you to omit certain installation features and skip some network tests. Custom installation works in both Plug and Play and non–Plug and Play PCs. To view online Installation Wizard Help information at any point, click the Help button in the lower right corner of the screen. 8 Select the Custom Installation or Express Installation radio button, and then click Next.

■ If you selected Custom Installation, go to “Starting Custom Installation,” on page 5-12. The rest of this chapter describes Custom installation.

■ If you selected Express Installation, go to step 9 on page 3-6. Express installation is described in Chapter 3. Windows 95 Setup for Custom Installation 5-7

Conﬁguring a NIC in a Each NIC in your kit is conﬁgured to work in a Plug and Play PC. If a Non–Plug and Play PC Windows 95 PC does not support Plug and Play, you must disable Plug and Play on the NIC before you can install the NIC software.

Disabling Plug and Play on the NIC Follow these steps to disable Plug and Play on the NIC: 1 Turn the power on and boot (start) Windows 95. 2 Insert EtherDisk diskette 2 in drive A. 3 Click Start in the Windows 95 taskbar, and then click Run. 4 Enter: a:\pnpdsabl.bat The DOS PNPDSABL screen appears, as shown in Figure 5-6.

Figure 5-6 DOS PNPDSABL Screen

5 Click the X in the upper right corner of the screen to close the DOS screen and return to Windows 95. Plug and Play is now disabled on the NIC. 6 Remove the diskette from drive A. 7 Shut down the PC and turn the power off. 8 Turn the PC power back on. The NIC is not detected by Windows 95 when the PC reboots. Now you must conﬁgure the NIC for the non–Plug and Play PC, as described in the next section. 5-8 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

Conﬁguring the NIC for Non–Plug and Play This section describes installing NIC software and conﬁguring the NIC when Plug and Play has been disabled on the NIC.

Follow these steps to install the NIC software and conﬁgure the NIC: 1 Double-click the My Computer icon, double-click the Control Panel icon, and then double-click the Add New Hardware icon. The Add New Hardware Wizard starts and displays the ﬁrst screen. 2 Click Next. You are prompted to let Windows 95 search for your new hardware. 3 Select No, and then click Next. The Add New Hardware Wizard displays the Hardware Types list box. 4 Select Network adapters and click Next. Windows 95 updates the driver database and then displays the Select Device screen, as shown in Figure 5-7.

Figure 5-7 Select Device Screen Windows 95 Setup for Custom Installation 5-9

5 Insert EtherDisk diskette 1 in drive A and click Have Disk. The Install from Disk screen appears, as shown in Figure 5-8.

Figure 5-8 Install from Disk Screen

6 If it is not already displayed in the Copy manufacturer’s ﬁles from entry box, type: a:\ 7 Click OK. The Select Device screen shown in Figure 5-9 appears, with 3Com EtherLink III ISA (3C509/3C509b) in ISA mode selected.

Figure 5-9 Select Device Screen 5-10 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

8 Click OK. Windows 95 copies the required ﬁles and updates the driver database. The Add New Hardware Wizard displays a screen showing the I/O range assigned to the NIC, as shown in Figure 5-10.

Figure 5-10 I/O Range Screen

9 Write down the I/O range setting displayed in the list box (or click Print, if you are connected to a printer), and then click Next. When you configure the NIC using the 3Com Installation Wizard, you must make sure that this setting matches the value displayed on the NIC Configuration Settings screen. See Figure 5-12. Windows 95 copies the required files to your hard disk. The 3Com Installation Wizard starts. CAUTION: I/O base address 0x110 is reserved for system resources. If this address is assigned to a hardware device in your PC, you need to change the I/O base address for that device. See “Configuring the NIC” on page 5-13. The next step is to use the 3Com Installation Wizard to install NIC software and configure the NIC. Go to “Starting Custom Installation,” on page 5-12. Windows NT Setup for Custom Installation 5-11

Windows NT Setup This section describes how to set up your Windows NT 3.51 or 4.0 system for Custom environment to install the NIC using the 3Com Installation Wizard Custom Installation installation option.

Follow these steps to install and conﬁgure the NIC under Windows NT: 1 Install the NIC in your PC. See Chapter 2. 2 Boot (start) Windows NT. 3 Double-click the My Computer Icon, double-click the Control Panel icon, and then double-click the Network icon. The Network screen appears. 4 Click the Adapters tab, click Add, and then click Have Disk. The Insert Disk screen appears. 5 Insert EtherDisk diskette 1 in drive A. 6 Make sure that the path to drive A appears in the entry box, and then click OK. The Select OEM Option screen appears. 7 If not already selected, select 3Com EtherLink III (3C509) ISA Adapter and click OK. The 3Com EtherLink III (3C509) ISA Adapter Bus Location screen appears. 8 Make sure that Bus Type: ISA and Bus Number: 0 appear in their respective selection boxes, and then click OK. Windows NT Setup copies the required ﬁles to your hard disk. The 3Com Installation Wizard starts.

The next step is to use the 3Com Installation Wizard to install the NIC software and conﬁgure the NIC. Go to the next section. 5-12 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

Starting Custom Custom installation begins with the ﬁrst 3Com Installation Wizard screen Installation (Figure 5-11). The way you reach this screen depends on your PC operating system and BIOS (Plug and Play versus non–Plug and Play):

■ In the last step of the Windows 95 setup procedure for conﬁguring a NIC in a Plug and Play PC on page 5-6, clicking Next starts the 3Com Installation Wizard.

■ In the last step of the Windows 95 setup procedure for conﬁguring a NIC in a non–Plug and Play PC on page 5-10, clicking Next starts the 3Com Installation Wizard.

■ In the last step of the Windows NT setup procedure for conﬁguring a NIC in the preceding section, clicking OK starts the 3Com Installation Wizard.

The ﬁrst 3Com Installation Wizard screen is shown in Figure 5-11.

Figure 5-11 Selecting Custom Installation Screen

Follow these steps to perform a Custom installation: 1 Select the Custom Installation radio button, shown in Figure 5-11. 2 Click Next. Starting Custom Installation 5-13

Configuring the NIC The NIC Configuration Settings screen appears, as shown in Figure 5-12. The list box displays recommended configuration settings for the NIC. You can either accept the recommended settings or change one or more to suit your operating environment.

Figure 5-12 NIC Conﬁguration Settings Screen

For Windows 95 non–Plug and Play PCs, make sure that the I/O Base Address value shown in the list box under Current Value is the same value that you wrote down when you conﬁgured the NIC for non–Plug and Play (Figure 5-10). Also make sure that the Interrupt Request Level (IRQ) value is one of the available values that you wrote down during “Preinstallation” in Chapter 2.

To Accept Configuration Settings Follow these steps to accept the recommended configuration settings: 1 On the NIC Configuration Settings screen (Figure 5-12), click Next. 2 Go to “Testing the NIC and the Network Connection” on page 5-14. 5-14 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

To Change Configuration Settings Follow these steps to change NIC configuration settings in a Windows 95 non–Plug and Play PC: 1 Under Network Parameter, select I/O Base Address. 2 In the Set Value selection box, click the scroll arrow to select the I/O range setting that you wrote down when you configured the NIC for non–Plug and Play (Figure 5-10). 3 Under Network Parameter, select Interrupt Request Level. 4 In the Set Value selection box, click the scroll arrow to select an interrupt request level that matches one of the available IRQs that you wrote down during “Preinstallation” in Chapter 2. (See Figure 2-1 on page 2-2.) 5 When you’ve finished changing the settings, click Next. The next step is to test the NIC and the network connection.

Testing the NIC and It is recommended that you test the NIC and then the network to verify the Network that each is working properly before you continue the installation. Connection The NIC Test screen appears, as shown in Figure 5-13.

Figure 5-13 NIC Test Screen Starting Custom Installation 5-15

Follow these steps to test the NIC and the network connection: 1 Click Perform NIC Test. While the test is running, an indicator shows test progress. If the test fails, a message indicates the error type. Click the Help button in the error message screen to obtain more information. Appendix C provides additional troubleshooting help. A message conﬁrms that the NIC is functioning correctly. 2 Click Next. The Network Connection Test screen appears, as shown in Figure 5-14.

Figure 5-14 Network Connection Test Screen

3 Click Perform Network Connection Test to verify that the network is functioning correctly. While the test is running, an indicator shows test progress. If the test fails, a message indicates the error type. Click the Help button in the error message screen to obtain more information. Appendix C provides additional troubleshooting help. A message conﬁrms that the network is functioning correctly. 5-16 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

4 Click Next. For Windows NT — Go to “Conﬁguring DynamicAccess Software” on page 5-23. For Windows 95 — The TCP/IP Inquiry screen appears, as shown in Figure 5-15.

Figure 5-15 TCP/IP Inquiry Screen

Installing TCP/IP Installing and conﬁguring TCP/IP to obtain Internet access is optional. Under Windows 95 ■ If you plan to access the Internet with this PC, you must install TCP/IP. Go to “To Install TCP/IP.”

■ If you don’t plan to access the Internet with this PC, you don’t need to install TCP/IP. Go to “To Not Install TCP/IP.”

To Not Install TCP/IP Follow these steps if you don’t want to install TCP/IP: 1 On the TCP/IP Inquiry screen (Figure 5-15), select the No radio button. 2 Click Next. Go to “Identifying Your PC on the Network” on page 5-22. Starting Custom Installation 5-17

To Install TCP/IP Follow these steps to install and configure TCP/IP: 1 On the TCP/IP Inquiry screen (Figure 5-15), select the Yes radio button. 2 Click Next. The TCP/IP Configuration screen appears, as shown in Figure 5-16. The next step is to configure TCP/IP, as described in the next section.

Figure 5-16 TCP/IP Conﬁguration Screen

Conﬁguring TCP/IP There are two ways to assign a TCP/IP address (commonly known as an Under Windows 95 IP address). You can obtain an IP address automatically or specify an IP address manually. If you’re attaching to an existing large network, your network administrator will specify which method to use, and if required, provide an IP address for you.

To Obtain an IP Address Automatically Follow these steps to obtain an IP address automatically: 1 On the TCP/IP Conﬁguration screen (Figure 5-16), select the Obtain an IP address automatically radio button. This option dynamically assigns a new IP address each time you connect to the network. 5-18 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

2 Click Test IP Connection to test the DHCP server connection. While the test is running, an indicator shows test progress. If the test fails, a message indicates the error type. Click the Help button in the error message screen to obtain more information. Appendix C provides additional troubleshooting help. A message conﬁrms that the connection to the DHCP server is functioning. 3 Click Next. Go to “Conﬁguring DNS” on page 5-19.

To Specify an IP Address Manually Follow these steps to specify an IP address manually: 1 Select the Specify an IP address manually radio button. 2 Click Next. The Specify an IP Address screen appears, as shown in Figure 5-17.

Figure 5-17 Specify an IP Address Screen

3 Enter your PC’s IP address. 4 Enter your PC’s subnet mask. 5 Enter your PC’s new gateway address. At least one gateway must appear in the Gateways list box before you can advance to the next screen. Starting Custom Installation 5-19

6 Click Add New Gateway to add the new gateway conﬁguration. The gateway is listed in the Gateways list box.

7 Click Test IP Connection to verify that the gateway connection is functioning. While the test is running, an indicator shows test progress. If the test fails, a message indicates the error type. Click the Help button in the error message screen to obtain more information. Appendix C provides additional troubleshooting help. A message confirms that the IP address is valid and functioning. 8 Click Next. The DNS Configuration screen appears, as shown in Figure 5-18. The next step is to configure DNS, as described in the next section.

Conﬁguring DNS Dynamic Name Server (DNS) converts a World Wide Web URL to an actual IP address. You can conﬁgure DNS either automatically or manually depending on how your network is set up.

When you click Next in the preceding section, the DNS Conﬁguration screen appears, as shown in Figure 5-18.

Figure 5-18 DNS Conﬁguration Screen 5-20 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

To Obtain a DNS Address Automatically Follow these steps to obtain a DNS address automatically: 1 On the DNS Configuration screen (Figure 5-18), select the Obtain a DNS address automatically radio button. This choice gives you a new DNS address each time you log on to the network. 2 Click Test DNS Connection to verify that the connection to the DNS server is functioning. While the test is running, an indicator shows test progress. If the test fails, a message indicates the error type. Click the Help button in the error message screen to obtain more information. Appendix C provides additional troubleshooting help. A message confirms that the DNS connection is functioning. 3 Click Next. The Network Identification screen appears, as shown in Figure 5-20. The next step is to identify your PC on the network. Go to “Identifying Your PC on the Network” on page 5-22.

To Specify a DNS Address Manually Follow these steps to specify a DNS address manually: 1 Select the Specify DNS manually radio button if you’re using a permanent DNS address. See Figure 5-18.

■ If DNS has been previously configured on your PC, the fields on this screen may already be filled in, as shown in Figure 5-19.

■ If DNS hasn’t been previously configured on your PC, these fields are blank and you must fill them in to enable DNS. Starting Custom Installation 5-21

Figure 5-19 Specifying a DNS Address Screen

2 Enter the host and domain data in their respective fields. 3 To configure a new server, enter the new server address, and then click Add New Server. The new server appears in the Servers list box. 4 Click Test DNS Connection to verify that the connection to the DNS server is functioning. While the test is running, a progress bar indicates test progress. If a test fails, a message indicates the error type. Click the Help button in the error message screen to obtain more information. Appendix C provides additional troubleshooting help. A message confirms that the DNS connection is functioning. 5 Click Next. The Network Identification screen appears, as shown in Figure 5-20. The next step is to identify your PC on the network, as described in the next section. 5-22 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

Identifying Your PC When you click Next in the preceding section, the Network Identiﬁcation on the Network screen appears, as shown in Figure 5-20. This screen lets you identify your PC on the network. The screen shows the PC’s current identiﬁcation if you’ve already entered this information through Windows 95 (see Figure 5-4).

Figure 5-20 Network Identiﬁcation Screen

Follow these steps to enter field data: 1 Type the name of your computer. There can be many PCs and other devices on a network—each one must be uniquely identified. This name identifies your PC on the network. The name can have up to 15 characters. Spaces are not allowed; however, you can use hyphens. 2 Type your workgroup name. This name identifies the group to which your PC belongs. This group will include most of the network resources that you use. This name can have up to 15 characters. 3 Click Next. The DynamicAccess Software Inquiry screen appears, as shown in Figure 5-21. The next step is to configure DynamicAccess software, as described in the next section. Starting Custom Installation 5-23

Conﬁguring The optional DynamicAccess feature set optimizes network performance DynamicAccess for large networks. Software When you click Next in the preceding section, the DynamicAccess Software Inquiry screen appears, as shown in Figure 5-21.

Figure 5-21 DynamicAccess Software Inquiry Screen

This screen lets you identify applications running on your PC that you wish to support using PACE software. Conﬁguring DynamicAccess software is optional.

■ If you’re installing a small peer-to-peer network, go to “To Not Conﬁgure DynamicAccess Software.”

■ If you’re using your kit to attach to an organization’s existing large network controlled by a network administrator, go to “To Conﬁgure DynamicAccess Software.”

DynamicAccess software includes PACE™ Interactive Access technology, dRMON (distributed RMON) support, Efﬁcient Multicast Control, and PACE real-time and multimedia application support.

To Not Conﬁgure DynamicAccess Software Follow these steps if you don’t want to conﬁgure DynamicAccess software: 1 On the DynamicAccess Software Inquiry screen (Figure 5-21), click Next. 2 Go to “Repeating a Previous Installation” on page 5-24. 5-24 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

To Configure DynamicAccess Software Follow these steps if you want to configure DynamicAccess software: 1 Double-click the 3Com PACE Config icon shown in Figure 5-21. The PACE Support Setup screen appears, as shown in Figure 5-22.

Figure 5-22 PACE Support Setup Screen

2 Select the Enable PACE Support radio button. 3 Select the check box next to each application that you want to conﬁgure. 4 Click OK to return to the DynamicAccess Software Inquiry screen. 5 Click Next. The Repeat Last Installation screen appears, as shown in Figure 5-23. Go to the next section.

Repeating a Previous You can save the conﬁguration settings and test options that you selected Installation during this installation for use in future installations for a large network. Saving settings is optional.

■ If you’re installing a small peer-to-peer network, go to “To Not Save Installation Settings.”

■ If you’re using your kit to attach to a large network, go to “To Save Installation Settings.” Starting Custom Installation 5-25

When you click Next in the preceding section, the Repeat Last Installation screen appears, as shown in Figure 5-23.

Figure 5-23 Repeat Last Installation Screen

To Not Save Installation Settings Follow these steps if you don’t want to save these conﬁguration settings: 1 On the Repeat Last Installation screen (Figure 5-23), select the No radio button, and then click Next. The Installation Complete screen appears, as shown in Figure 5-26. 2 Click Finish. Go to “Completing NIC Software Installation” on page 5-28.

To Save Installation Settings Follow these steps to save these conﬁguration settings for future installations: 1 On the Repeat Last Installation screen (Figure 5-23), select the Yes radio button, and then click Next. The Conﬁrm Installation Settings screen appears, as shown in Figure 5-24. 5-26 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

Figure 5-24 Conﬁrm Installation Settings Screen

2 Select the check boxes for tests that you want to run in future installations, and then click Next. The Save Installation Settings screen appears, as shown in Figure 5-25.

Figure 5-25 Save Installation Settings Screen Starting Custom Installation 5-27

3 Enter the path for the EtherDisk diskette that you’re using. The EtherDisk diskette is ﬁrst copied to a temporary directory, and then that ﬁle is copied to the drive that you indicate. If you’re saving the settings to a diskette, insert a blank, formatted diskette in drive A. Upon completion, remove the diskette from the drive. You can use this diskette to perform future installations. Otherwise, enter the name of the drive (for example, C:\) where you want to save the installation settings. 4 Click Next. The Installation Complete screen appears, as shown in Figure 5-26. 5 Click Finish.

■ Go to “Completing Installation for Windows 95” in the next section if you’re running Windows 95 on your PC.

■ Go to “Completing Installation for Windows NT” on page 5-30 if you’re running Windows NT on your PC.

Figure 5-26 Installation Complete Screen 5-28 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

Completing NIC Procedures for completing the installation and conﬁguration differ for Software Windows 95 and Windows NT. Installation

Completing This section describes how to complete the NIC installation and Installation for conﬁguration under Windows 95 after you close the 3Com Windows 95 Installation Wizard, as described in the preceding section.

The Insert Disk dialog box appears, prompting you for the Windows 95 CD. 1 Insert the Windows 95 CD in the CD-ROM drive and click OK. The Copying Files screen appears (Figure 5-27).

Figure 5-27 Copying Files Screen

If your PC is running OEM Windows 95 (version B), then the screens that appear are slightly different from those shown in this section. Follow the displayed directions and insert the appropriate diskette or CD when prompted. 2 Type or use the pull-down menu to replace the A:\ entry in the Copy files from field with the following entry: d:\win95 The CD-ROM drive is usually the D drive, but your CD-ROM drive may be different. Enter the appropriate drive letter. If you have Windows 95 diskettes instead of a Windows 95 CD, remove the EtherDisk diskette, insert the appropriate Windows 95 diskette (Windows verifies your choice), and select the appropriate diskette drive, such as the A drive. 3 Click OK. Windows copies files from the Windows 95 CD (or diskettes) to the PC hard drive. Windows then prompts you to restart the PC. Completing NIC Software Installation 5-29

4 Remove the EtherDisk diskette (or Windows diskette) from drive A and click Yes to restart. (You can also remove the Windows 95 CD.) Your PC may display a message regarding a missing DHCP server upon restart. If you’re installing a small peer-to-peer network, your network doesn’t require a DHCP server. Ignore the message and continue. Windows 95 restarts and prompts you for a network password (Figure 5-28).

Figure 5-28 Enter Network Password Screen

5 Type your user name (unless one is already displayed). If you haven’t previously entered a user name for this PC, the User name ﬁeld is empty. Type your user name now. 6 Type the network password and click OK. Conﬁrm the password if the system prompts you to do so. When the Windows 95 desktop is displayed, note that it now shows a Network Neighborhood icon.

Congratulations! Your Networking Kit is now installed. 5-30 CHAPTER 5: CUSTOM SOFTWARE INSTALLATION FOR WINDOWS 95 AND WINDOWS NT

To effectively use your network, you need to conﬁgure Windows 95 or Windows NT to allow resource sharing. Sharing resources for Windows 95 is described in Chapter 4, “Enabling File and Printer Sharing Through Windows 95.”

Verify that all existing installed hardware devices are still working. Typical devices to check include a sound card, CD-ROM drive, analog modem, LPT port to a printer, and game ports. If any devices are not working, go to Appendix C or the Windows Troubleshooting Help system.

Completing Clicking Finish on the Installation Complete screen (Figure 5-26) closes Installation for the 3Com Installation Wizard. Windows NT then displays the Adapters Windows NT tab of the Network screen. The next step is to conﬁgure TCP/IP according to the instructions in your Windows NT documentation.

This chapter describes how to install NIC software and conﬁgure the NIC if your PC’s operating system is DOS, Windows 3.1, or Windows for Workgroups. If your PC is running Windows 95, see Chapter 3 for Plug and Play PCs, or see Chapter 5 for non–Plug and Play PCs. If your PC is running Windows NT, see Chapter 5. To install the network drivers for Windows 3.1x, Windows for Workgroups, or DOS in a non-NetWare environment, see the appropriate text ﬁles in the HELP directory on EtherDisk diskette 2.

Installing NetWare This section describes how to use the 3Com AutoLink™ program to install Drivers for DOS, client and driver software for DOS environments and Novell NetWare 3.1x Windows 3.1, and or 4.1x under Windows 3.1 and Windows for Workgroups. Windows for Workgroups If a 3Install account has been installed on your server, the AutoLink program logs on to the server and updates the client software. AutoLink creates a new AUTOEXEC.BAT file and saves the old file as AUTOEXEC.3CM. AutoLink also creates a new CONFIG.SYS file and saves the old file as CONFIG.3CM.

AutoLink The AutoLink program includes an installation program. To use the Requirements AutoLink program, your PC should have only one NIC installed and a minimum of 1 MB of available hard disk space.

Running the AutoLink To run the installation program to conﬁgure the NIC, follow these steps: Install Program 1 Install the NIC and connect it to the network, as described in Chapter 2. 2 Reboot to DOS. 3 Insert EtherDisk diskette 2 in drive A. 6-2 CHAPTER 6: SOFTWARE INSTALLATION FOR DOS, WINDOWS 3.1, AND WINDOWS FOR WORKGROUPS

4 Run the installation program. At the DOS prompt, enter: a:install The main menu is displayed, as shown in Figure 6-1.

EtherDisk for the EtherLink III Adapter Family v5.1 ESC=Cancel F1=Help MAIN MENU

Installation Tips (ReadMe) ... Microsoft Windows Installation Auto Install and Config for NetWare (Autolink) Driver Installation and Update ... Configuration and Diagnostic Program Release Notes

This option displays a directory of help on relevant topics

Figure 6-1 Main Menu of the DOS Installation Program

5 Select Auto Install and Config for NetWare (AutoLink) and press Enter. The AutoLink program menu is displayed. 6 Select DOS, Windows 3.1x, or Windows for Workgroups 3.11 and follow the prompts. 7 When the auto installation process is finished, remove EtherDisk diskette 2 from drive A and reboot the PC. If you’re running Windows 3.1x, after you connect to the NetWare server, run the NetWare WSINSTALL utility for full Windows support. If problems occur only when using the AutoLink program, display or print the AUTOLINK.LOG file to see a list of all events occurring during the AutoLink installation and configuration process.

■ To display the ﬁle, enter: type autolink.log | more

■ To print the ﬁle, enter: print autolink.log Installing Other Supported Network Drivers 6-3

Obtaining NetWare You can obtain current NetWare Loadable Modules (NLMs) for the Loadable Modules NetWare servers listed in Table 6-1 from the Novell Web site, www.support.novell.com. Table 6-1 NetWare NLMs

NetWare Server NLM Name NetWare 3.12 ETHERTSM.NLM NBI31X.NLM MSM31X.NLM NetWare 4.11, 4.1 ETHERTSM.NLM NBI.NLM MSM.NLM

The Networking Kit NIC no longer supports NetWare 3.11 and 4.0x servers.

Installing Other Table 6-2 provides the text ﬁle names and driver names for other drivers Supported Network supported by the NIC. Text ﬁles for all supported network operating Drivers systems are included in the HELP directory on EtherDisk diskette 2. Table 6-2 Network Driver Text File Names

Network Operating System Text File Name Network Driver Name Banyan VINES BANYAN.TXT ELNK3.DOS Microsoft LAN Manager LANMAN.TXT ELNK3.DOS IBM LAN Server (DOS) LANSRV.TXT ELNK3.DOS IBM LAN Server (OS/2) LANSRV.TXT ELNK3.OS2 Artisoft LANtastic LANTASTK.TXT ELNK3.DOS DEC PATHWORKS PATHWORK.TXT ELNK3.DOS DEC PATHWORKS PATHWORK.TXT 3C5X9.COM (for NetWare ODI-compatible) Windows for Workgroups WFWNETWR.TXT 3C5X9.COM (NetWare) Windows for Workgroups WFWNDIS2.TXT ELNK3.DOS (NDIS 2) Windows for Workgroups WFWNDIS3.TXT ELNK3.386 with ELNK3.DOS (NDIS 3) Windows 95 NDIS 2 16-bit W95NDIS2.TXT ELNK3.DOS network driver (continued) 6-4 CHAPTER 6: SOFTWARE INSTALLATION FOR DOS, WINDOWS 3.1, AND WINDOWS FOR WORKGROUPS

Table 6-2 Network Driver Text File Names (continued)

Network Operating System Text File Name Network Driver Name NetWare Client 32 CLIENT32.TXT 3C5X9.LAN NetWare 3.12 Server NETWARE.411 3C5X9.LAN NetWare 4 Server NETWARE.411 3C5X9.LAN NetWare OS/2 NWOS2ODI.TXT 3C5X9.SYS Packet driver NOSs PACKET.TXT 3C5X9PD.COM

Configuring the NIC This section describes how to configure the NIC after you install it in your PC. If only one NIC is installed and you’re running Novell NetWare, use the AutoLink program to configure the NIC and load the appropriate driver, as described earlier in this chapter.

To configure the NIC, follow these steps: 1 Install the NIC (see Chapter 2) and the network driver (earlier in this chapter). 2 Reboot to DOS. 3 Insert EtherDisk diskette 2 in drive A. 4 Run the installation program. Enter: a:install The main menu is displayed, as shown in Figure 6-1. 5 Select Configuration and Diagnostic Program. If you have more than one NIC installed in the PC, select the NIC you want to configure. Tab to the Select button and press Enter. 6 Select Configure NIC and press Enter. The NIC Configuration screen is displayed, as shown in Figure 6-2. Configuring the NIC 6-5

Configuration and Diagnostic Program Version 3.2 QuitInstall Test View Select F1=Help NIC Configuration EtherLink III NIC Configuration I/O Base Address 300h Interrupt Request Level 10 Boot PROM N/A Transceiver Type On-board TP (RJ-45) Network Driver Optimization Windows or OS/2 Client Maximum Modem Speed 9600 Baud Plug and Play Compatibility Enabled Full Duplex Disabled

Auto Configure Modify File Options OK Cancel

[ENTER]= Automatically Configures the NIC [Alt]+=Execute Function [TAB]=Next Field [SHIFT+TAB]=Previous Field [F1]=Help [ESC]=Cancel

Figure 6-2 NIC Conﬁguration Screen

7 Select Auto Configure and press Enter. The I/O base address, interrupt request level (IRQ), and transceiver type are automatically configured to settings that don’t conflict with other devices in your PC. To change settings, follow the steps in “Changing Configuration Settings,” the next section. If you encounter a problem with the Auto Configure option, press F1 for help. The OK button is selected when configuration is completed. 8 Press Enter to accept the configuration parameters. The NIC is now configured. 6-6 CHAPTER 6: SOFTWARE INSTALLATION FOR DOS, WINDOWS 3.1, AND WINDOWS FOR WORKGROUPS

Changing You should change the default settings of a NIC only if a conflict with Configuration another device or NIC exists. Figure 6-2, the NIC Configuration screen, Settings shows the current configuration settings for the installed NIC. You can change the default settings to:

■ Disable Plug and Play

■ Optimize driver performance for a speciﬁc operating system

■ Optimize driver performance for operation on a DOS Client, Windows or OS/2 client, or on a server

■ Change the speed of a modem

Table 6-3 lists each software option, the default setting for that option, and other available settings for that option. For more information about an option, select the option and press F1. Table 6-3 Option Settings

Option Default Setting Supported Settings I/O Base Address 300h 200h, 210h, 220h, 230h, 240h, 250h, 260h, 270h, 280h, 290h, 2A0h, (N/A for Plug and 2B0h, 2C0h, 2D0h, 2E0h, 2F0h, Play PCs) 300h, 310h, 320h, 330h, 340h, 350h, 360h, 370h, 380h, 390h, 3A0h, 3B0h, 3C0h, 3D0h, 3E0h, EISA, ISA Interrupt 10 3, 5, 7, 9, 10, 11, 12, 15 Request Level (N/A for Plug and Play PCs) Boot PROM N/A or Disabled Disabled (Does not apply for 3C509B-TPO.) Transceiver Type On-board TP On-board TP (RJ-45) (RJ-45) Network Driver Windows or OS/2 DOS Client, Windows or OS/2 Client, Optimization Client Server Maximum 9600 Baud No Modem, 1200, 2400, 9600, Modem Speed 19200, or 38400 Baud (fastest modem installed) Plug and Play Enabled Enabled, Disabled Capability Full-Duplex Disabled Enabled, Disabled Changing Configuration Settings 6-7

If you’re using a PC that supports Plug and Play, the IRQ and I/O base address values are set by Plug and Play. To disable Plug and Play, go to “Conﬁguring a NIC in a Non–Plug and Play PC” on page 5-7.

Follow these steps to change the configuration settings: 1 When the main menu shown in Figure 6-1 appears, select Configuration and Diagnostic Program. The next screen shows the Install menu bar item selected and the Configure NIC option is already selected. 2 Press Enter. The Configuration dialog box appears. 3 Press the Tab key several times to highlight the first option in the main dialog box. Then use the arrow keys to select the parameter option you want to change and press Enter. The NIC Configuration screen is displayed, as shown in Figure 6-2 on page 6-5. 4 Use the arrow keys to scroll through the list of settings for that option. Select a setting and press Enter. 5 Continue this procedure for any of the other parameter options that you want to change. See the online help (using F1 when the option is selected) for more information about each of the settings. 6 Press Tab to select OK. Press Enter. You must select OK and press Enter to save the new settings to the NIC. If you want to use the same settings on other NICs, you can save the configuration settings to a file. Select Save under File Options in the NIC Configuration dialog box. For example, enter: d:\config\3c5xx.set where xx represents the last two digits of the NIC number. This saves the settings to the default file 3C5XX.SET in the CONFIG directory in drive D. See to the online help (using F1) for more information. 6-8 CHAPTER 6: SOFTWARE INSTALLATION FOR DOS, WINDOWS 3.1, AND WINDOWS FOR WORKGROUPS

Reconﬁguring If your PC has an EISA bus, it comes with an automatic conﬁguration the NIC for EISA program that allocates resources to each installed hardware device in the PC.

When you put the NIC into EISA mode, the EISA conﬁguration program that came with your computer can conﬁgure the NIC with correct settings for operating in an EISA PC.

You can conﬁgure an ISA NIC for EISA mode only if the NIC is installed in an EISA slot.

If you have conﬁgured an ISA NIC for an EISA PC, the PROTOCOL.INI ﬁle looks for the parameter SLOT=number rather than the I/O base address. The SLOT number is required only if you have multiple NICs installed.

The following procedures are general. If you require more detail, see the conﬁguration documentation that accompanied your PC.

Changing NIC Follow these steps to configure the NIC for an EISA PC: Configuration from ISA to EISA 1 Run the installation program as described in “Configuring the NIC” on page 6-4. 2 From the main menu of the installation program, select Configuration and Diagnostic Program. A screen appears that lists the NICs installed in your PC. 3 If you have more than one NIC installed, use the arrow keys to select the NIC you want to configure. Tab to the Select button and press Enter. A screen identifying the NIC is displayed with the Test menu bar item selected. 4 Use the arrow keys to select Install. The Configure NIC option is selected. Press Enter. 5 When the NIC Configuration dialog box is displayed, select Modify and press Enter. The I/O Base Address field is selected. An I/O Base Address dialog box appears. 6 Use the arrow key to select EISA and press Enter. The I/O base address setting is changed. Reconfiguring the NIC for EISA 6-9

7 Select OK to save the new configuration setting and press Enter. 8 Exit the program and remove EtherDisk diskette 2 from drive A. 9 Insert the EISA configuration utility diskette provided with your PC in drive A. 10 Turn the power off. Wait 10 seconds, and then turn the power on. 11 Follow the instructions accompanying your EISA PC to run the EISA configuration program. When the program prompts you for .CFG files to copy, insert EtherDisk diskette 2, press Enter, and select !TCM5095.CFG. If you are prompted for the wrong !TCM file: a Turn the power off and remove the NIC. b Clean the edge connectors on the NIC. c Reinsert the NIC in the slot. Make sure that the NIC is fully seated in the slot. d Turn the power on.

You should now be prompted for the correct !TCM ﬁle.

If your PC is running Windows 95 or Windows NT, see Chapter 5 for NIC software installation instructions.

Changing NIC To reconfigure the NIC to ISA mode, the NIC must be installed in an Configuration from EISA slot. EISA to ISA Follow these steps to reconfigure the NIC for an ISA PC: 1 Run the installation program as described in “Configuring the NIC” on page 6-4. 2 From the main menu, select Configuration and Diagnostic Program. A screen appears that lists the NICs installed in your PC. 3 If necessary, use the arrow keys to select the NIC you want to configure. Tab to the Select button and press Enter. 4 A screen identifying the NIC is displayed with the Test menu bar item already selected. 5 Select Install and press Enter. 6-10 CHAPTER 6: SOFTWARE INSTALLATION FOR DOS, WINDOWS 3.1, AND WINDOWS FOR WORKGROUPS

6 When the NIC Configuration dialog box appears, select Modify and press Enter. The I/O Base Address field is selected. An I/O Base Address dialog box appears. 7 Use the arrow keys to select ISA and press Enter. The I/O base address setting is changed. 8 Select OK to save the new configuration setting to the NIC and press Enter. 9 Remove EtherDisk diskette 2 from drive A. 10 Insert the PC configuration program diskette for your PC in drive A and reboot the PC. A SPECIFICATIONS

This appendix lists the speciﬁcations for both the hub and the NIC. For the NIC, it includes connector pin assignments and cable requirements.

Hub Speciﬁcations Physical Dimensions Length: 8.7 in (22 cm) Width: 5.3 in (13.5 cm) + 0.6 in (1.52 cm) for coaxial port on the Hub 8/TPC Height: 1.4 in (3.58 cm) Weight: 1.2 lb (550 g) (Hub 8/TPC) 1.1 lb (500 g) (Hub TP4) Environmental Operating Range Operating temperature: 0˚ to 50 ˚C (32˚ to 122 ˚F) (Hub 8/TPC) 0˚ to 40 ˚C (32˚ to 105 ˚F) (Hub TP4) Humidity: Up to 90% noncondensing Power Requirements Operating voltage: 12 VA (Hub 8/TPC) 2 VA (Hub TP4)

NIC Speciﬁcations Network Interface Ethernet IEEE 802.3i 10BASE-T Physical Dimensions Length: 6.14 in (15.59 cm) Width: 2.5 in (6.35 cm) Environmental Operating Range Operating temperature: 0˚ to 70 ˚C (32˚ to 158 ˚F) Humidity: 10% to 90% noncondensing A-2 APPENDIX A: SPECIFICATIONS

Power Requirements Operating voltage: +5 V ± 5% @ 150 mA max +12 V ± 5% @ 0.5 A max

RJ-45 Connector Figure A-1 shows the RJ-45 connector pin assignments. Pin Assignments

8 7 RD- 6 5 4 RD+ 3 TD- 2 TD+ 1

8 Figure A-1 RJ-45 Connector Pin Assignments

Cable Specifications In order to maintain compliance with the limits of a Class B or Class A digital device, 3Com requires that you use quality interface cables when connecting the EtherLink III ISA NIC or the OfficeConnect Hub TP4 or Hub 8/TPC. Changes or modifications not expressly approved by 3Com could void your authority to operate this equipment. Examples of supported cable types are as follows:

■ For unshielded twisted-pair (UTP) connections: Unshielded twisted-pair (UTP) (100 ohm):

■ Category 3 LAN and high-speed data cable, for example, Anixter® CM-00424BAG-3 or equivalent

■ Category 5 extended distance LAN cable, for example, Anixter CM-00424BAG-5 or equivalent

■ For thin coax connections: RG58 A/U or C/U (50 ohm ± 4) B DESIGNING YOUR NETWORK

After reading the ﬁrst chapter in this guide, you should have a basic understanding of networking and the various components that make up a network. Are you ready to design your own network so you can enjoy the beneﬁts provided through networking?

By using 3Com’s OfﬁceConnect Networking Kit, you should be able to design a network that allows you to meet your current networking needs and prepares you to meet your future networking goals as your needs grow and develop.

Determining Before your network can accomplish the desired results, you should Network determine what you want the network to do for you. Consider the Requirements following list of questions to help deﬁne your network requirements.

■ What do you want to do with the network (data and printer sharing, multiuser applications, and so forth)? Who needs the network?

■ How many computers and other devices do you want to connect on the network?

■ What level of performance do you expect of your network?

■ What computers will share resources with network users? What resources need to be shared (printers, ﬁles, and so forth)?

The following sections address each of these questions. As you discover your answers, you might want to record them on the checklist at the end of this appendix. B-2 APPENDIX B: DESIGNING YOUR NETWORK

Purpose of the Determining the purpose of your network helps to specify many factors. Network For example:

■ Does more than one person need access to certain ﬁles, such as proprietary information or accounting spreadsheets?

■ Do you want to store data ﬁles in one common location so that other users can access them?

■ Do you want to have a printer available for all users on the network?

■ Will more than one person need to access a common application program, such as a customer database, an accounting program, or a desktop publishing system?

Making a decision about these capabilities can help you decide the characteristics of each of the computers on the network. It can also help you focus on how you want to use the number of devices on the network.

Performance Factors Working in a network environment can help you to be more productive. The following factors can affect the speed or type of network performance that you can expect:

■ Network operating system (NOS) — Each NOS supports a different type of performance. One NOS may be better suited to your performance requirements than another. Before you invest in a particular NOS, refer to the documentation that’s supplied with the NOS or contact the manufacturer to determine if it suits your networking needs.

■ NIC throughput — For example, if sharing a printer is your network’s primary purpose, the NIC supplied with the Networking Kit provides adequate speed for this situation.

■ File sharing — If ﬁles and data are to be shared with other users on the network, performance is an issue. However, by using the Networking Kit, which supports the Ethernet suite of protocols, you can achieve 10 Mbps data speed at relatively low cost and gain high performance. Determining Network Requirements B-3

Sharing Resources Resource sharing is one of the more common tasks that is enhanced by a network. PCs that control resources, such as printers, databases, and directories for use by other computers are often conﬁgured as servers. When acting as a server is all they do, those computers are dedicated servers. When a PC acts as both a workstation and a server, then it’s a nondedicated server. For most smaller networks, using nondedicated servers is appropriate.

You need to determine which PCs will share resources and which won’t. For those PCs that you plan to use as any type of server, you may want to consider adding additional memory or hard disk storage.

As you consider the implications of sharing resources, you need to determine whether you need your network to be a server-based (client/server) or peer-to-peer network.

Peer-to-Peer Network In a peer-to-peer scheme, a two-way networking relationship exists between two or more “like” computers. Each PC may or may not make portions of its software or attached printers available to other PCs on the network. The determination of what to share is made on each individual PC.

Some sample NOSs that support peer-to-peer networking are:

■ Microsoft Windows for Workgroups (Windows 3.11)

■ Microsoft Windows 95

■ Novell NetWare

■ Artisoft LANtastic

A peer-to-peer network provides:

■ The capability to share resources on any computer in the network — In a server-based network you can share only the resources that are on a dedicated server.

■ Flexibility in sharing resources — Setting up shared resources may involve more repetition of tasks than in a server-based network. In a server-based network, sharing is speciﬁed from the server, not each computer.

■ Use of nondedicated equipment — The network does not require a dedicated server and works with your existing equipment. B-4 APPENDIX B: DESIGNING YOUR NETWORK

Client/Server Network In a client/server network, a one-way relationship exists between two or more PCs, where one or more computers act as a server. The other PCs in this environment are clients and connect to the server to utilize its resources. The server is usually conﬁgured with large disk drives for application and data sharing as well as storage, and with local or remote attached printers for print sharing. A server-based network requires more complex management than a peer-to-peer network. The determination of who is allowed to log in or share server resources is made from the server.

Some examples of client/server NOSs are:

■ Microsoft Windows NT

■ Novell NetWare

■ Microsoft Lan Manager

■ Banyan VINES

A client/server network provides:

■ Focus on the dedicated server that shares its resources with workstations (or clients) — The workstations (clients) can access the shared resources on the server but cannot access any resources on other workstations.

■ An opportunity for better performance — Since the dedicated server does not function also as a workstation, the network usually provides better performance.

■ Greater control over resources — Permission to use the server is administered through the server, rather than at each workstation.

■ Reliance on the server — Also, the network usually is more expensive to implement because it requires a dedicated server. Network Checklist B-5

Network Checklist Now that you’ve examined the purpose of your network, you probably have an idea of what you want to build. Take a few moments and use Table B-1 to write down the computers you want to network and the printers and other devices you want to make available. Table B-1 Network Component Checklist

Put on the network? Use as a server? Component Name Description Y/N If so, for what? Primary user name Computer 1

Computer 2

Computer 3

Computer 4

Computer 5

Computer 6

Computer 7

Computer 8

Printer 1

Printer 2

Fax/modem

Other device

Software application

Directories and files

C TROUBLESHOOTING

This appendix explains how to isolate and solve problems that may occur when you install the NIC in a PC running Windows 95, Windows NT, or Windows 3.x. It also describes how to interpret your hub’s LEDs to identify network problems.

Checklist If you experience problems installing the NIC, ﬁrst check these items:

■ Check the NIC LED, as described in “NIC Link LED” in Chapter 2.

■ Check the connectors. Examine the cable for obvious signs of damage, wear, or crimping. Substitute a known working cable.

■ Try removing the NIC software and reinstalling it as described in this appendix.

■ Make sure the drivers installed are correct for the network operating system you’re running (see “Installing Other Supported Network Drivers” in Chapter 6).

If the problem persists, go to related procedures in this appendix or see Appendix E, “Technical Support.”

Resolving Follow these steps to resolve hardware resource conflicts (I/O base address Hardware Conflicts or interrupt request level) if your PC is running either Windows 95 or in Windows 95 and Windows NT. Windows NT 1 From the Start menu, select Help. The Help window is displayed. 2 Select the Contents tab, and then select Troubleshooting. 3 Double-click If you have a hardware conflict. 4 Click Start the Conflict Troubleshooter and follow the instructions. C-2 APPENDIX C: TROUBLESHOOTING

Changing the If you have a resource conﬂict, you can change the I/O base address or I/O Base Address the interrupt request level (IRQ). If you’re adding new hardware to your or the Interrupt system, you may need to change a resource assignment to avoid a Request Level conﬂict. The following procedures describe how to change resource allocations for your Windows 95 or Windows NT PC.

Windows 95 Follow these steps to change the IRQ level assignment or the I/O base address in a Windows 95 PC: 1 Double-click the My Computer icon, double-click the Control Panel icon, and then double-click the System icon. The System Properties window is displayed. 2 Select the Device Manager tab, double-click Network adapters, and then double-click 3Com EtherLink III ISA Adapter. 3 Select the Resources tab. 4 Depending on the type of conflict that you have, select either Input/Output Range or Interrupt Request. 5 Select the resource that you want to change (IRQ or Input/Output Range) and select Change Settings. (If these options appear dimmed, clear the Use automatic settings check box.) 6 Scroll to a value that you know is available, and then click OK. You recorded available IRQ values during the Windows 95 preinstallation procedure. See “Preinstallation” in Chapter 2. Before you reboot Windows 95, make sure that the value that you assign to a resource matches the value for the same resource in the NIC Configuration Settings screen (similar to that shown in Figure 5-12) in the 3Com NIC Diagnostics program. 7 Close all open windows and restart the PC. The hardware conflict should be resolved. Windows 95 and Windows NT Troubleshooting C-3

Windows NT Follow these steps to change the IRQ level assignment or the I/O base address in a Windows NT PC: 1 Double-click the 3Com icon in the taskbar tray. The General tab of the 3Com NIC Diagnostics program appears. 2 Select the Conﬁguration tab. 3 Select the resource (I/O base address or interrupt request level) that you want to change in the Network Parameter column of the list box. The current value for that parameter appears in the Set Value entry box. 4 Scroll to the value that you want to assign, and then click OK. 5 If you change the I/O base address, before you restart Windows NT, make sure that the address that you assign matches the I/O base address on the Adapters tab screen. Follow these steps to verify the base addresses: a Double-click the My Computer icon, double-click the Control Panel icon, double-click the Network icon, and then select the Adapters tab. 3Com EtherLink III (3C509) ISA Adapter is selected. b Click Properties. The I/O Port Address value appears in the scroll box on the 3Com EtherLink III Adapter Card Setup screen. Ensure that this value matches the value set in step 4. To change this value, scroll to the matching value, and then click OK. c Click OK to close the 3Com NIC Diagnostics program. 6 Restart the PC. The hardware conﬂict should be resolved.

Windows 95 and A comprehensive section on troubleshooting tips and techniques is Windows NT provided in the online Help. To access the online Help, double-click the Troubleshooting 3Com icon in the taskbar tray, go to the Support tab of the 3Com NIC Diagnostics program, and click Release Notes. C-4 APPENDIX C: TROUBLESHOOTING

Diagnostic Testing The 3Com NIC Diagnostics program for Windows 95 and Windows NT is Under Windows 95 installed on your hard disk when you install the NIC software using the and Windows NT 3Com Installation Wizard.

Starting the 3Com You can start the program by double-clicking the 3Com taskbar tray icon NIC Diagnostics or by selecting 3Com NIC Doctor in the Windows Explorer. Program For Windows 95 or Windows NT, follow these steps to run the 3Com NIC Diagnostics program if the 3Com icon does not appear in your taskbar tray: 1 Click Start in the taskbar, and then select Run. The Run dialog box appears. 2 In the Open entry box, type: tcaudiag 3 Click OK. Table C-1 shows the various tab screens that are available within the 3Com NIC Diagnostics program.

. Table C-1 3Com NIC Diagnostics Program Tab Screens

Tab Description General The General tab is the first screen to appear when you start the diagnostics program. This screen identifies the NICs installed in your PC and lets you get information that is specific to the selected NIC. This screen also provides check boxes for adding the diagnostics program icon to the taskbar tray of your PC and enabling the PC as an auto echo server system on the network. Click NIC Details to display a screen that lists detailed information about the selected NIC. Configuration The Configuration tab is used to change NIC configuration settings. Statistics The Statistics tab provides network traffic information that is updated by the NIC driver several times a minute. Diagnostics The Diagnostics tab provides access to the 3Com NIC Diagnostics program that lets you test the NIC or change configuration settings. DynamicAccess The DynamicAccess tab is used to identify applications running on your PC that you wish to support using PACE software. (continued) Diagnostic Testing Under Windows 95 and Windows NT C-5

Table C-1 3Com NIC Diagnostics Program Tab Screens (continued)

Tab Description Support The Support tab provides five buttons, each of which provides different support-related information or options.

■ Diagnostics The Diagnostics button provides buttons for two tests that verify network and NIC functionality.

■ Release Notes The Release Notes button provides information about known problems with specific vendor models.

■ BBS Information The BBS Information button provides information for obtaining the latest 3Com software drivers.

■ http://www.3com.com The http://www.3com.com button takes you to the 3Com home page on the 3Com Web site.

■ Problem Report The Problem Report button displays forms for submitting a trouble report to 3Com through e-mail.

Running Tests Two tests help you troubleshoot problems with the NIC: the NIC test and the network test.

NIC Test Run the NIC test to determine that the NIC is working correctly. Be sure to run this test after you have veriﬁed that the network is functioning.

Follow these steps to run the NIC test: 1 Click Run NIC Test to begin the test. A progress indicator appears. Results are displayed when the test is completed. 2 Click OK. C-6 APPENDIX C: TROUBLESHOOTING

Network Test Run the Network test ﬁrst if you are experiencing problems with the NIC. This tests the ability of the NIC to transmit and receive data while connected to the network.

Follow these steps to run the Network test: 1 Click Run Network Test. The Network Connectivity Test screen is displayed. 2 Click Start to begin the test. The PC on the network acting as the receiver in this test is identiﬁed on the right side of the screen. Results are displayed when the test is completed. To run the test continuously, select the Continuous check box. 3 Click Close.

Uninstalling the If you have problems installing NIC software, allow the 3Com Installation NIC Software for Wizard to ﬁnish. The installation cannot be canceled once it is started. Windows 95 or Windows NT CAUTION: Before attempting to reinstall 3Com NIC installation software, you must ﬁrst perform the uninstallation process.

Follow these steps to uninstall the NIC software in a PC running Windows 95 or Windows NT. 1 Double-click the My Computer icon, double-click the Control Panel icon, and then double-click the Network icon. 2 Select the NIC.

■ For Windows 95 — On the Conﬁguration tab, select the 3Com EtherLink III ISA NIC.

■ For Windows NT — On the Conﬁguration tab, select Network adapters, and then select the 3Com EtherLink III ISA NIC. 3 Click Remove. 4 Click OK. The System Settings Change screen appears, prompting you to restart your PC. 5 Click Yes. The NIC is no longer recognized by your operating system. All NIC software is removed from your PC. Uninstalling the NIC Software for DOS, Windows 3.1, or Windows for Workgroups C-7

Uninstalling the EtherDisk diskette 2 includes an uninstallation program to remove the NIC Software for NIC software. DOS, Windows 3.1, or Windows for To run the uninstallation program, at the DOS prompt, enter: Workgroups un3c509.exe

The NIC software is removed from your PC.

Reinstalling NIC When an event such as a hard disk crash occurs, the original conﬁguration Software ﬁle written to the PC’s hard disk may be lost or damaged. In this case, you must reinstall the NIC software for the NIC to be operational:

■ To reinstall 3Com NIC software, follow the procedure speciﬁed in Chapter 3 for Plug and Play PCs and Chapter 5 for non–Plug and Play PCs.

■ To reinstall 3Com NIC software using saved settings from a previous installation, go to the next section.

If you are unable to reinstall the NIC or the NIC software successfully, refer to the appropriate troubleshooting sections in this appendix.

Performing This section describes how to install and conﬁgure the NIC when you Automated want to perform multiple installations automatically or when you must Installations reinstall the NIC software because it has been lost or corrupted.

This procedure uses conﬁguration settings saved from a previous installation.

Installing from Follow these steps if the saved configuration settings are in a file on your the Hard Disk hard disk: 1 Click Start in the taskbar, click Run, and then enter the path to the file that contains the saved configuration settings that you want to use to reinstall the NIC. 2 Click OK. The 3Com Installation Wizard starts and displays the first screen. 3 Click Install. 3Com Installation Wizard screens appear sequentially, displaying the settings saved in the original installation. C-8 APPENDIX C: TROUBLESHOOTING

Installing from Follow these steps if the saved configuration settings are in a file on a a Diskette diskette: 1 Insert the diskette containing the saved configuration settings in drive A. 2 Click Start in the taskbar, click Run, and then enter: a:\ 3 Click OK. The 3Com Installation Wizard starts and displays the first screen. 4 Click Install. The 3Com Installation Wizard screens appear sequentially, displaying the settings saved in the original installation.

Diagnostic Testing The Configuration and Diagnostic Program, on EtherDisk diskette 2, for DOS, includes the diagnostic program used for DOS, Windows 3.x, and Windows 3.x, and Windows for Workgroups. Windows for Workgroups You can run the diagnostic tests after installing one or more NICs, or you can run them when a fault is suspected. If the tests in their default configuration don’t isolate the problem, you can change the test parameters to meet specific situations.

If the NIC passes both tests successfully, hardware failure is ruled out. If a problem still remains, look at cabling, software, and other issues that affect functionality on the network.

Don’t run diagnostic tests with device drivers or memory managers installed.

Boot (start) your PC to DOS (use a DOS diskette) to avoid installing device drivers or memory managers.

If you’re using DOS 6.x in a plain DOS environment, you can bypass the CONFIG.SYS and AUTOEXEC.BAT ﬁles by holding down the right Shift key while starting the computer. If you’re running under DOS 6.2, pressing F5 while starting the computer will also bypass the same two ﬁles. If you’re using an earlier version of DOS, start your computer from a DOS diskette containing no device drivers. Diagnostic Testing for DOS, Windows 3.x, and Windows for Workgroups C-9

Diagnostic tests are divided into three groups, of which two apply to the NICs supplied with your kit:

■ The Group 1 tests check the physical components, connectors, and circuitry on the NIC.

■ The Group 2 Network Loopback Test (You can ignore this test. It doesn’t apply to the NICs supplied with your kit.)

■ The Group 3 test (the Echo Exchange Test) tests to see if the NIC can transmit and receive data while on the network.

If the NIC passes the group tests successfully, the NIC is functioning correctly. If the problem remains, look at cabling, software, driver conﬁguration, and issues that can affect network functionality.

Starting the DOS Follow these steps to run the Configuration and Diagnostic Program: Configuration and Diagnostic Program 1 Boot to DOS. (Use a DOS diskette.) 2 Insert EtherDisk diskette 2 in drive A. 3 Run the installation program. Enter: a:install The main menu is displayed, as shown in Figure 6-1. 4 Select Configuration and Diagnostic Program and press Enter. If multiple NICs are installed, each NIC is listed. 5 Select the NIC you want to test and press Enter. You can also run the tests from the command line. At the system prompt, enter: 3c5x9cfg run

Running the Group 1 tests evaluate the physical components of the NIC. A Group 1 Group 1 Tests test failure can indicate a faulty NIC.

For a description of each Group 1 test, press F1 to access Help. In the Help screen, tab to the Index button and press Enter. Use the arrow keys to move through the Index listings. Select Test Deﬁnitions and press Enter. C-10 APPENDIX C: TROUBLESHOOTING

Follow these steps to run the Group 1 tests: 1 From the Test menu, select Run Tests and press Enter. The Run Tests dialog box appears with the Start button already selected. 2 Press Enter to start the tests. Group 1 tests run 10 times (default setting) unless you specify otherwise. The test results are displayed in the Results column. To run the tests continuously, go to the Repetitions box on the Test Setup screen and select Continuous (and deselect Halt on Error in the Errors box). To access the Test Setup screen, select Test in the menu bar and then select Test Setup in the drop-down menu. Press Enter.

Running the The Group 3 test is the Echo Exchange Test. It tests to see if the NIC can Group 3 Test transmit and receive data while connected to the network. If you have successfully run the Group 1 tests, a failure in the Group 3 test usually indicates a cabling, hub, or network problem.

CAUTION: Don’t use an active network to run the Group 3 test.

To run the Group 3 test on the network, you need a second PC to serve as an echo server, and it must have a 3Com NIC installed. The echo server receives packets from and echoes packets back to the NIC being tested. The diagnostic program provided with the NIC supports the NIC echo server diagnostic program.

Setting Up an Echo Server To set up an echo server, follow these steps: 1 Insert the EtherDisk diskette 2 for the echo server NIC in drive A of the echo server. 2 Start the diagnostic program on the echo server. At the DOS prompt, enter the diagnostic program name for the NIC: a:\3c5X9cfg.exe The main window of the diagnostic program is displayed. 3 From the Test menu, select Echo Server, and then click Start. A message conﬁrms that your PC is now set up as an echo server. Diagnostic Testing for DOS, Windows 3.x, and Windows for Workgroups C-11

Starting the Group 3 Test To run the Group 3 test on the NIC, follow these steps: 1 Start the Conﬁguration and Diagnostic Program on the PC in which the NIC to be tested is installed. 2 From the Test menu, select Test Setup. 3 Enable the Group 3 test. Select OK and press Enter. 4 Go to the Run Tests dialog box to start the tests. 5 After the test is completed: a Exit the program on the echo server. b Exit the Conﬁguration and Diagnostic Program. 6 Reboot your PC.

Getting Help If a If a diagnostic test fails, the NIC may not be defective. The problem may Test Fails be incorrect conﬁguration settings, settings that conﬂict with other NICs, or improper installation.

For more information about a failed diagnostic test:

■ Select the test that failed in the Run Tests dialog box and press Enter. or

■ Select the Zoom button and press Enter.

CAUTION: Make sure to turn the power off before inserting or removing the NIC from the PC.

To test the NIC further, follow these steps:

■ Make sure the NIC is seated correctly in the slot. Check the NIC installation by reviewing the installation instructions in Chapter 2.

■ Inspect all cables and connections.

■ Check for speciﬁc hardware problems, such as broken traces or loose/broken solder connections. If you’re using thin Ethernet cable, make sure that you have a T-connector attached to the NIC and all other NICs on the network. Make sure that the thin Ethernet segment is terminated at both ends with a 50-ohm terminator. C-12 APPENDIX C: TROUBLESHOOTING

■ Make sure that you started your computer under DOS version 3.1 or later, and that no device drivers or memory managers are loaded.

■ If you’re running the Group 3 test, make sure that the NIC is connected to a properly cabled and inactive network and that an echo server is set up on the network.

■ Make sure that the settings for the NIC’s options are not the same settings used in the system or on any other NIC installed in the computer.

■ Install the NIC in another slot and run the diagnostic tests again. The original slot may be defective.

■ Replace the failed NIC with a working NIC and run the diagnostic tests again. Use the same option settings as those used on the failed NIC. If the working NIC passes all tests, the original NIC is probably defective. Refer to Appendix E for information on repair procedures.

■ If your ISA NIC has been previously configured to work in an EISA computer, reconfigure it to work in an ISA computer. See “Reconfiguring the NIC for EISA” in Chapter 6.

■ Check the version of the PC’s BIOS. You may need to upgrade it.

■ Make sure that you’ve installed the correct driver for the network operating system you’re running.

■ Install the NIC in another functioning computer and run the tests again. Your computer may be defective. If the NIC passes the tests in the second computer, contact the reseller or manufacturer of the original computer. If you experience problems that occur only when using the AutoLink program, display or print the AUTOLINK.LOG file. The AUTOLINK.LOG file contains a log of all the events that occurred during the AutoLink installation and configuration process.

■ To display the ﬁle, enter: type autolink.log | more

■ To print the ﬁle, enter: print autolink.log Diagnostic Testing for DOS, Windows 3.x, and Windows for Workgroups C-13

■ Check the A:\HELP directory for ﬁles with information about most common problems. If a problem persists, see Appendix E for instructions on getting technical assistance.

■ If you’ve installed the NIC correctly and you still experience problems, check the software.

Changing the To change the test parameters, follow these steps: Test Setup 1 Choose Test Setup from the Test menu in the main window of the Configuration and Diagnostic Program or use the Test Setup button in the Run Tests dialog box. 2 Press the Tab key to highlight any of the fields within the Test Setup dialog box. 3 To change a setting in any field, follow these steps: a In the Group Select box, use the arrow keys to select a test group. For more information on the diagnostic tests, see the appropriate sections earlier in this appendix. b In the Group X Tests box, use the arrow keys to highlight a test. Press the spacebar to enable or disable an individual test. c In the Repetitions box, specify the number of times you want to run the tests, or use the arrow keys to select the Continuous option. d In the Errors box, press the spacebar to select or deselect the Halt on Error parameter. 4 When you’re satisfied with the new test setup, select the OK button and press Enter. 5 To run the tests, choose Run Tests from the Test menu and select the Start button. CAUTION: Don’t use an active network to run the Group 3 test. C-14 APPENDIX C: TROUBLESHOOTING

Using the Help EtherDisk diskette 2 includes a Help library with general information and Library speciﬁc procedures on loading drivers and setting up a networking environment for your PC.

To use this information, you must know:

■ What type of operating system (OS) you are running; for example, Windows 95 or Windows for Workgroups

■ What kind of network operating system you will be connecting to; for example, NetWare (which requires ODI drivers) or Microsoft Networks (which requires NDIS drivers)

Opening the There are two ways of opening the Help library: EtherDisk Diskette ■ Change to drive A, run the Install program from DOS, and select Help Library Installation Tips (ReadMe).

■ Change to drive A and run the Help program from DOS. Depending on your PC and work environment, you can boot DOS, open a DOS window, or exit to DOS from a windowing environment.

To run the Help program from DOS, do the following: 1 Put EtherDisk diskette 2 in drive A. 2 Change to drive A by entering: a: 3 To run the Help program, enter: help The Help menu opens. Select a topic or family of topics and press Enter. For a brief description of a menu item, select it and press F1. Troubleshooting the Hub C-15

Troubleshooting The more complex your network setup becomes, the greater the possibility the Hub of small problems along the way. The LEDs on the front of the hub can provide you with some basic information.

The Power and Port Status LEDs provide speciﬁc troubleshooting information, as detailed in Table C-2. Table C-2 LED Troubleshooting Indicators

Symptom Cause Solution Power LED doesn’t glow steady The hub is defective. Contact your supplier or 3Com representative. green after the power-on tests have been completed. COAX LED glows yellow. The hub detects partitioning* Make sure that you’ve connected the (Hub 8/TPC only) on the coax (BNC) port. If the MDI/MDIX port on one hub to an RJ-45 port is not in use, the status (10BASE-T)† port on the other hub. Don’t is OK. connect two MDI/MDIX ports or two non-MDI/MDIX RJ-45 ports together. Port Status LED glows yellow. An installed NIC or the hub is Check cable connections. Confirm that the NIC defective. A loop may be or hub is not defective. Make sure that you’ve present because of illegal connected the MDI/MDIX port on one hub to cabling. A cable connector may an RJ-45 port on the other hub. Don’t connect not be properly seated. two MDI/MDIX ports or two non-MDIX/MDI RJ-45 ports together. Make sure that the segment is properly terminated (Figure D-4). The hub automatically enables the port and the LEDs glow green when the fault is corrected.

* Partitioning means that the port is shut off and no data can be transmitted. † 10BASE-T indicates that the port supports 10 megabit per second transmission over UTP cable.

The other LEDs on the panel indicate the status of each port, as described in Table 2-2 on page 2-11.

D EXPANDING YOUR NETWORK

As you become more familiar with networking and as your business needs grow, you may want to add more PCs or other devices to your network, as detailed in this appendix. If you outgrow your ﬁrst hub, you can easily add more.

You can connect up to eight PCs and peripheral devices to a single 3Com OfﬁceConnect Hub 8/TPC (and up to four PCs and peripheral devices to a single Hub TP4), as well as buy additional hubs and connect them together to expand your network.

You need one NIC for each PC added to the network.

Understanding The following deﬁnitions will help you better understand how to connect Connection OfﬁceConnect hubs together: Concepts ■ MDI/MDIX port (Media Dependent Interface/MDI with internal crossover) — The IEEE 10BASE-T standard for the UTP cable interface. The port farthest to the left on the hub’s rear panel is switchable between MDI and MDIX modes. (See Figure D-1.) The switch that controls the MDI/MDIX port is located to the left of the MDI/MDIX port. (See Figure D-2.) Table D-1 describes how to use the MDI/MDIX switch. Table D-1 MDI/MDIX Switch Positions

Position Meaning Out (MDIX) The MDI/MDIX port is used to connect one PC or peripheral device to the hub. The MDI/MDIX port is configured just like the other 10BASE-T RJ-45 ports when set to MDIX. This is the standard setting for small networks using just one hub. All of the hub’s nonswitchable RJ-45 ports are permanently set to MDIX mode. In (MDI) The MDI/MDIX port is used to connect the hub to another hub. D-2 APPENDIX D: EXPANDING YOUR NETWORK

■ Coaxial port — Can be used to connect the hub to another OfﬁceConnect hub or equipment with 10BASE2 cabling.

■ Straight-through cable — Pins 1, 2, 3, and 6 on one RJ-45 connector correspond to the same pins on the other RJ-45 connector.

■ Crossover cable — Pins 1, 2, 3, and 6 on one RJ-45 connector correspond to pins 3, 6, 1, and 2, respectively, on the other RJ-45 connector, thus crossing transmit and receive signals in the cable itself.

In order for two 10BASE-T devices to communicate with each other, the transmit signals on each device must be connected to the receive signals on the other device. The hub’s nonswitchable RJ-45 ports are permanently set to MDIX mode. MDIX ports cross transmit and receive signals internally. When you connect devices such as servers, workstations, or printers to MDIX ports, you must use a straight-through cable like the ones provided in the Networking Kit.

Connecting You can connect hubs to the network using either UTP cable or coaxial Additional Hubs Ethernet cable (also known as thinnet).

You can connect two OfﬁceConnect Hub 8/TPCs or other OfﬁceConnect units together using UTP cabling or coax cabling, but not both at the same time. For example, when connecting multiple hubs, either use a straight-through UTP cable to connect on RJ-45 port on one hub to the MDI/MDIX port on the next hub, or use coaxial cabling and the BNC coax connectors on the back of each hub.

Using UTP Cable If you use UTP cabling, you can connect up to four hubs together. To network two hubs, as shown in Figure D-1, connect one end of the UTP cable to a nonswitchable RJ-45 port on the ﬁrst hub and the other end of the cable to the MDI/MDIX port on the second hub.

When you use the port farthest to the left on the hub rear panel, be sure to have the MDI/MDIX switch (Figure D-2) depressed (in) if you are connecting to a hub.

Continue this type of connection to add two more hubs for a maximum of four hubs. Connecting Additional Hubs D-3

CAUTION: Use only a straight-through cable to connect a nonswitchable RJ-45 port to an MDI/MDIX port, or vice versa.

+ COAX

+ MDI/MDIX port COAX

RJ-45 port Figure D-1 Connecting Two Hubs Using UTP Cabling

The MDI/MDIX switch is located to the left of the MDI/MDIX port. When the switch button is extended (out), the port becomes an MDIX port, as shown in Figure D-2.

+ COAX

MDI/X 8

MDI

MDIX

Figure D-2 MDI/MDIX Switch D-4 APPENDIX D: EXPANDING YOUR NETWORK

Four Hub 8/TPC units connected by UTP cabling can support up to 26 computers, as shown in Figure D-3.

Hub number 4

MDI/MDIX port MDIX port

10–30 VDC 1A MAX – + COAXMDI/X 8 1X

Hub number 3

10–30 VDC 1A MAX – + COAXMDI/X 8 1X

Hub number 2

10–30 VDC 1A MAX – + COAXMDI/X 8 1X

MDI/MDIX switch (in) Hub number 1

10–30 VDC 1A MAX – + COAXMDI/X 8 1X

Figure D-3 Network with Four OfﬁceConnect Hub 8/TPCs Connecting Additional Hubs D-5

Using Coaxial If you use coaxial Ethernet cable, you can connect up to 30 hubs together. Ethernet Cable Such a network would provide up to 240 ports (one server and 239 client computers). Using coaxial Ethernet cable leaves more ports free for device connection.

Depending on the software applications used, such a network may be restricted to fewer than 240 network devices.

To build a network using coaxial Ethernet cabling, follow these steps: 1 Attach a coaxial T-connector to the BNC connector (see Figure D-4) located on the hub’s rear panel. (You can obtain a coaxial T-connector through your computer supplier.) Repeat this step for each hub that you want to connect to the network backbone. 2 Connect thin Ethernet cabling to the two sides of the T-connector. Contact your network supplier for the thin Ethernet cable and the BNC 50-ohm terminators that you may need. 3 Continue by connecting the thin Ethernet cable to the other T-connectors. 4 Attach the terminators and ground lead, as shown in Figure D-4. Each end of the coaxial cable trunk requires a terminator, and one end requires a ground lead.

+ COAX

Ground lead BNC connector with terminator

+ COAX

T-connector

+ COAX

BNC connector with terminator

Figure D-4 Connecting Three Hubs Using Coaxial Ethernet Cable D-6 APPENDIX D: EXPANDING YOUR NETWORK

5 Connect the ground lead to an available ground point. Contact a qualiﬁed electrician to make sure there is a proper ground. 6 Connect each hub to a power source with a hub power adapter.

Your network is now working.

CAUTION: You can’t connect hubs that are connected with UTP cabling to hubs connected with coaxial Ethernet cabling.

Positioning the Hub When installing your OfﬁceConnect hub, be sure that:

■ It’s out of direct sunlight and away from sources of heat.

■ Cabling is away from power lines, fluorescent lighting fixtures, and sources of electrical noise such as radios, transmitters, and broadband amplifiers.

■ Water or moisture cannot enter the case of the unit.

■ Air ﬂow around the unit and through the vents in the side of the case is not restricted. It is recommended that you provide a minimum of 1 in. (25.4 mm) clearance.

Using the Your Networking Kit includes four self-adhesive rubber feet that can Nonskid Feet prevent your hub from sliding on a desk surface. Attach the feet to the marked areas at each corner of the hub’s underside.

Stacking Multiple Your Networking Kit includes four stacking clips that you can use to stack Hubs your OfficeConnect units together securely. You can stack up to a maximum of four units. To stack your units, secure the clips on one side and then on the other. Use the following method to secure each side: 1 Place your existing unit on a flat surface. Your clips fit in the positions on the side of the unit, as shown in Figure D-5. 2 Position a clip over one of the holes, as shown in Figure D-6, and push it in until it clicks into place. Repeat this for the other clip position on the same side. 3 Keeping the front of the units aligned, rest the bottom of the new unit on the clips’ spikes. Push the clips firmly into the new unit until they click into place, as shown in Figure D-7. Positioning the Hub D-7

! PWR Alert PKT Port Status COLL 1 green = link OK, off =2 link fail, yellow = partition. 3 4

OFFICE CONNECT

Hub TP4

Figure D-5 Holes for the Stacking Clips

Figure D-6 Positioning a Clip

Figure D-7 Clipping the Hubs Together D-8 APPENDIX D: EXPANDING YOUR NETWORK

4 Repeat step 1 through step 3 to secure the other side of the hub.

To remove a clip, hold the units firmly with one hand and hook the first finger of your other hand around the back of the clip. Use reasonable force to pull it off.

Wall-Mounting Two slots on the underside of the OfﬁceConnect hub are used for wall the Hub mounting. You can mount the hub with the LEDs facing upward or downward.

When wall-mounting your hub, make sure that it’s within reach of the power socket.

You need two suitable screws. Make sure that the wall you’re going to use is ﬂat, dry, and sturdy. Make two screw holes that are 5.9 in. (150 mm) apart. Fix the screws into the wall, leaving their heads 0.12 in. (3 mm) clear of the wall surface.

Remove any connections to the hub and position it over the screw heads. When in line, gently push the hub on to the wall and move it downwards to secure. When making connections, be careful not to push the hub up and off the wall.

CAUTION: You can only wall-mount single hubs. Do not wall-mount stacked hubs.. E TECHNICAL SUPPORT

3Com provides easy access to technical support information through a variety of services. This appendix describes these services.

Information contained in this appendix is correct at time of publication. For the very latest, 3Com recommends that you access the 3Com Corporation World Wide Web site.

Online Technical 3Com offers worldwide product support 24 hours a day, 7 days a week, Services through the following online systems:

■ World Wide Web site

■ 3Com FTP site

■ 3Com Bulletin Board Service (3Com BBS)

■ 3ComFactsSM automated fax service

World Wide Web Site Access the latest networking information on the 3Com Corporation World Wide Web site by entering the URL into your Internet browser: http://www.3com.com/

This service provides access to online support information such as technical documentation and software library, as well as support options ranging from technical education to maintenance and professional services. E-2 APPENDIX E: TECHNICAL SUPPORT

3Com FTP Site Download drivers, patches, and software across the Internet from the 3Com public FTP site. This service is available 24 hours a day, 7 days a week.

To connect to the 3Com FTP site, enter the following information into your FTP client:

■ Hostname: ftp.3com.com (or 192.156.136.12)

■ Username: anonymous

■ Password:

A user name and password are not needed with Web browser software such as Netscape Navigator and Internet Explorer.

3Com Bulletin Board The 3Com BBS contains patches, software, and drivers for 3Com Service products. This service is available through analog modem or digital modem (ISDN) 24 hours a day, 7 days a week.

Access by Analog Modem To reach the service by modem, set your modem to 8 data bits, no parity, and 1 stop bit. Call the telephone number nearest you:

Country Data Rate Telephone Number Australia Up to 14,400 bps 61 2 9955 2073 Brazil Up to 14,400 bps 55 11 5181 9666 France Up to 14,400 bps 33 1 6986 6954 Germany Up to 28,800 bps 4989 62732 188 Hong Kong Up to 14,400 bps 852 2537 5601 Italy Up to 14,400 bps 39 2 27300680 Japan Up to 14,400 bps 81 3 3345 7266 Mexico Up to 28,800 bps 52 5 520 7835 P.R. of China Up to 14,400 bps 86 10 684 92351 Taiwan, R.O.C. Up to 14,400 bps 886 2 377 5840 U.K. Up to 28,800 bps 44 1442 438278 U.S.A. Up to 28,800 bps 1 408 980 8204 Support from Your Network Supplier E-3

Access by Digital Modem ISDN users can dial in to the 3Com BBS using a digital modem for fast access up to 56 Kbps. To access the 3Com BBS using ISDN, use the following number: 1 408 654 2703

3ComFacts The 3ComFacts automated fax service provides technical articles, Automated Fax diagrams, and troubleshooting instructions on 3Com products 24 hours a Service day, 7 days a week.

Call 3ComFacts using your Touch-Tone telephone: 1 408 727 7021

Support from Your If additional assistance is required, contact your network supplier. Many Network Supplier suppliers are authorized 3Com service partners who are qualiﬁed to provide a variety of services, including network planning, installation, hardware maintenance, application training, and support services.

When you contact your network supplier for assistance, have the following information ready:

■ Product model name, part number, and serial number

■ A list of system hardware and software, including revision levels

■ Diagnostic error messages

■ Details about recent conﬁguration changes, if applicable

If you are unable to contact your network supplier, see the following section on how to contact 3Com.

Support from 3Com If you are unable to obtain assistance from the 3Com online technical resources or from your network supplier, 3Com offers technical telephone support services. To ﬁnd out more about your support options, please call the 3Com technical telephone support phone number at the location nearest you. E-4 APPENDIX E: TECHNICAL SUPPORT

When you contact 3Com for assistance, have the following information ready:

■ Product model name, part number, and serial number

■ A list of system hardware and software, including revision levels

■ Diagnostic error messages

■ Details about recent conﬁguration changes, if applicable

Below is a list of worldwide technical telephone support numbers:

Country Telephone Number Country Telephone Number Asia Paciﬁc Rim Australia 1 800 678 515 New Zealand 0800 446 398 China Singapore 800 6161 463 From anywhere in China: 86 21 6350 1590 S. Korea From Shanghai: 10 800 3656 From anywhere in S. Korea: 82 2 3455 6455 Hong Kong 800 933 486 From Seoul: 00798 611 2230 India 61 2 9937 5085 Taiwan 0080 611 261 Indonesia 001 800 61 009 Thailand 001 800 611 2000 Japan 0031 61 6439 Pakistan 61 2 9937 5085 Malaysia 1800 801 777 Philippines 1235 61 266 2602 Europe From anywhere in Europe, +31 (0)30 6029900 phone call: +31 (0)30 6029999 fax From the following European countries, you may use the toll-free numbers: Austria 06 607468 Netherlands 0800 0227788 Belgium 0800 71429 Norway 800 11376 Denmark 800 17309 Poland 0800 3111206 Finland 0800 113153 Portugal 05 05313416 France 0800 917959 South Africa 0800 995014 Germany 0130 821502 Spain 900 983125 Hungary 00800 12813 Sweden 020 795482 Ireland 1 800 553117 Switzerland 0800 55 3072 Israel 177 3103794 U.K. 0800 966197 Italy 1678 79489 Latin America Argentina 541 312 3266 Colombia 571 629 4847 Brazil 55 11 523 2725, ext. 422 Mexico 01 800 849 2273 North America 1 800 NET 3Com (1 800 638 3266) Returning Products for Repair E-5

Returning Products Before you send a product directly to 3Com for repair, you must ﬁrst for Repair obtain a Return Materials Authorization (RMA) number. Products sent to 3Com without RMA numbers will be returned to the sender unopened, at the sender’s expense.

To obtain an RMA number, call or fax:

Country Telephone Number Fax Number Asia, Pacific Rim 65 543 6342 65 543 6348 Europe, South Africa, and 011 44 1442 435860 011 44 1442 435718 Middle East From the following European countries, you may call the toll-free numbers; select option 2 and then option 2: Belgium 0800 71429 Denmark 800 17309 Finland 0800 113153 France 0800 917959 Germany 0130 821502 Hungary 00800 12813 Ireland 1800553117 Israel 177 3103794 Italy 1678 79489 Netherlands 0800 0227788 Norway 800 11376 Spain 900 983125 Sweden 020 795482 U.K. 0800 966197 Austria 06 607468 Poland 00800 3111206 Portugal 05 05313416 South Africa 0800 995014 Switzerland 0800 55 3072 Latin America 1 408 326 2927 1 408 764 6883 U.S.A. and Canada 1 800 876 3266, 1 408 764 7120 option 2

GLOSSARY

10BASE2 The IEEE standard for a 10 megabit per second baseband network on thin coaxial cable.

10BASE-T The IEEE standard for a 10 megabit per second baseband network on twisted-pair cable. application software A program designed to perform a speciﬁc task, such as accounting, e-mail, or desktop publishing.

backbone The main transmission medium used to interconnect the workgroup areas of a network. The media type is usually coaxial or ﬁber cabling.

base address Also called I/O base address. The ﬁrst address in a series of addresses in memory, often used to describe the beginning of a network interface card’s I/O space.

BIOS Basic input/output system. An internal set of instructions in an IBM PC (or IBM-compatible PC) that controls basic hardware functions such as interactions with the keyboard, diskette drives, and hard disk drives.

BNC A type of bayonet-lock coaxial cable connector used for video and communications.

bus An electronic pathway along which signals are transmitted from one area of a PC to another.

CAT 3 Category 3 balanced cable. Balanced 100-ohm and 120-ohm cables and associated connecting hardware whose transmission characteristics are speciﬁed up to 16 MHz. Used by 10BASE-T and 100BASE-T4 installations.

CAT 5 Category 5 balanced cable. Balanced 100-ohm and 120-ohm cables and associated connecting hardware whose transmission characteristics are speciﬁed up to 100 MHz. Used by 10BASE-T and 100BASE-T installations. 2 GLOSSARY

client-server network A type of LAN that has at least one computer that is designated the host PC for some or all of the network’s applications. This type of LAN supports a networking relationship in which one or more PCs function as a “server,” providing application, data sharing, and storage capabilities. Other networked PCs, called “clients,” use the resources available from a server. See also peer-to-peer network.

coax, coaxial cable The copper-wire cable consisting of an outer braided wire that acts as a ground and an inner conductor used to carry signals. The outer and inner wires are separated from each other by insulating material. This type of cable can carry a much higher bandwidth than a wire pair. Coaxial cable uses the 10BASE2 Ethernet protocol.

collision A condition that results from concurrent data transmissions from multiple sources on the same data channel. When two devices transmit simultaneously, a collision occurs and the colliding devices delay their retransmissions for a random length of time. A sudden sustained increase in the number of collisions can indicate a problem with a device, particularly if it is not accompanied by a general increase in trafﬁc. On coaxial segments an increase in collisions can also indicate faulty cabling.

conﬁguration The software settings that allow different hardware components of a computer system to communicate with one another.

configuration files A group of files on the EtherDisk diskettes that contains configuration information and troubleshooting diagnostics specific to the functioning of the NIC with various network operating systems (NOSs).

crossover cable A patch cable wired to route the receive signals from one device to the transmit signals of another device, and vice versa.

device A component of the system’s hardware conﬁguration. Examples include the modem, printer, mouse, sound card, or disk drive.

device driver Software that controls how a PC communicates with a peripheral device, such as a printer, mouse, or NIC. Each operating system contains a standard set of device drivers for the keyboard, the monitor, NIC, and so forth. A network device driver is a program, usually resident in server or workstation memory, that controls the network hardware (such as adapters or controllers) or implements the protocol stacks through which higher-level applications communicate with the network hardware. GLOSSARY 3

DHCP server Dynamic Host Conﬁguration Protocol server. A server that automatically assigns a temporary TCP/IP address to a network PC upon startup, to allow that PC to access an Internet service. When the PC is turned off, it gives up its TCP/IP address so that the address can be used for another network PC. Dynamic IP addressing prevents duplication of addresses and the need for holding a large number of addresses in reserve.

Ethernet A local area network (LAN) standard deﬁning a physical medium and its method of placing data, or packet signaling, on a cable; a packet technology that operates at 10 Mbps over twisted-pair or coaxial cable and allows network devices such as workstations and hosts to communicate with each other.

EISA Extended Industry Standard Architecture. A PC bus system.

hub A device that connects network devices. Hubs serve as trafﬁc cops for managing network data. They restore signal amplitude and timing, detect collisions, and broadcast signals to network devices.

IEEE Institute of Electrical and Electronics Engineers. Committees that develop and propose computer standards, such as the 802 protocols, which deﬁne the physical and data link protocols of communication networks. Members represent an international cross section of users, vendors, and engineering professionals. input/output (I/O) The method, medium, or device (such as a keyboard, monitor, ﬂoppy disk, hard disk, NIC, or printer) used to transfer data to a computing system or from the computing system back to a device, a network, etc.

interrupt A signal that a device sends to the PC when the device is ready to accept or send information. Also used when a device needs the PC’s attention.

I/O base address See base address.

IRQ Interrupt Request Level or Interrupt Request Line. Hardware line over which devices can send interrupt signals. Each device connected to the PC usually uses a different IRQ.

ISA Industry Standard Architecture. A 16-bit extension of the original IBM PC bus architecture. The IBM Personal Computer AT bus. 4 GLOSSARY

LAN Local area network. A communications network within a limited physical area such as a building that provides high-speed data transmission. The basic components of a LAN are the NICs that plug into each PC to connect it to the network, cabling, server hardware, and software for network control.

LED Light-emitting diode. A diode that converts voltage to light and that is commonly used in digital displays.

loop See network loop.

Mbps Megabits per second.

network A group of computers and associated devices such as faxes and printers (peripherals) connected by a communications channel (cables and connectors) capable of sharing ﬁles and other resources among several users. The network size or type can range from a peer-to-peer (client-to-client) network, connecting a small number of users in an ofﬁce or department, to a local area network (LAN) connecting many users or groups in a relatively small area or campus, to a metropolitan area network (MAN) or wide area network (WAN) connecting users on several different networks spread over a wide geographic area.

network interface See NIC. card

network loop A condition that occurs when two pieces of network equipment are connected by more than one path. The hub detects this condition and partitions (isolates) one of its ports to break the loop. network operating See NOS. system

NIC Network interface card. A printed circuit board installed in a PC that allows network stations to communicate with each other; also called a network adapter card.

node A point in a network where one communicating device (such as a hub) is linked to the network and where information can be sent or received.

NOS Network operating system. A program running on each network PC that allows users to share ﬁles and network devices. The internal set of commands and instructions that directs a network’s activities. Windows NT, Novell NetWare, Banyan VINES, and Microsoft LAN Manager are examples of client-server NOSs. GLOSSARY 5

packet The unit of information transmitted over the network, consisting of a preamble, a destination address, a source address, the data being transmitted, and a code that allows testing for correct transmission.

partition A hub function that isolates a particular port from the network because of an excessive number of collisions. Once the problem causing the collisions is corrected, the port is reactivated. peer-to-peer network A network (usually with just a few PCs) in which each PC is set up to share its resources with every other PC on the network, and use the shared resources of every other PC on the network. No central server is required to administer sharing; however, peer-to-peer networking can still occur when a server is present on the network. See also client-server network.

Plug and Play (PnP) A standard that defines automatic techniques for making PC configuration simple and straightforward. Read-only memory (ROM) chips with unique identification numbers are added to each NIC, and the NIC can then arbitrate conflicts with interrupts, input/output ports, and memory.

segment The length of Ethernet cable connected to a port, whether this cable is 10BASE-T, 10BASE2 (coax), or other type. When you daisy-chain equipment together with 10BASE2 (coax) cable, all of the cable forms a single segment.

server A computer that provides disk space, printing support, ﬁle services, software applications, client/server networking. or other services to computers over a network.

STP Shielded twisted-pair. Shielded four-conductor electrical cable that offers high-speed transmission for long distances.

T-connector A cable adapter that attaches a PC with a network interface card to the network.

TCP/IP Transmission Control Protocol/Internet Protocol. A set of communications protocols that support peer-to-peer connectivity functions for both local and wide area networks. TCP/IP can be used to communicate to any PC using any desktop or network operating system anywhere in the world as long as it supports the TCP/IP suite of networking protocols. 6 GLOSSARY

twisted-pair Wiring similar to that found in the telephone system, consisting of two insulated wires loosely twisted around each other to help cancel out induced noise in balanced circuits. See also UTP.

UTP Unshielded twisted-pair. A cable consisting of two or more pairs of twisted copper wires that are not shielded. INDEX

changing Numbers configuration settings with DOS diagnostic 10BASE2 1-11 program 6-6 10BASE-T 1-9 I/O base address or IRQ C-2 3Com bulletin board service (3Com BBS) E-2 software options 6-6 3Com Installation Wizard 3-4, 5-12 client/server 3Com NIC Diagnostics program C-4 network B-4 3Com URL E-1 relationship 1-11 3ComFacts E-3 client-to-client relationship 1-11 clips for stacking hubs D-6 coax terminators D-5 A coaxial Ethernet cable D-5 adding the network printer to a PC’s Printers coaxial port D-2 folder 4-11 computer, components of 1-5 Artisoft LANtastic 6-3 CONFIG.SYS file C-8 AUTOEXEC.BAT file C-8 configuration and diagnostics program AutoLink program 6-1 DOS C-9 AUTOLINK.LOG file 6-2 Windows 3.x C-8 automated installation, creating file for C-7 Windows 95 C-4 Windows NT C-4 configuration settings B changing with DOS diagnostic program 6-6 backplate (NIC) 1-6, 1-8 list of 6-6 Banyan VINES 6-3 saving with 3Com NIC Diagnostics 5-25 BIOS Configuration tab C-4 non–Plug and Play 2-3, 5-7, 5-14 configuring Plug and Play 2-3 DNS 5-19 BNC DynamicAccess software 5-23 coaxial connector 1-11, D-5 EISA to ISA 6-9 terminators C-11, D-5 ISA to EISA 6-8 Boot PROM option 6-6 NIC bulletin board service E-2 DOS 6-1, 6-4 bus, definition of 1-6 in non–Plug and Play PC 5-7 in Plug and Play PC 5-3 Windows 3.x 6-1 C Windows 95 5-3, 5-7 cable Windows for Workgroups 6-1, 6-4 coaxial Ethernet cable D-5 Windows NT 5-11 crossover D-2 option settings 5-13, 6-6 requirements A-2 saving settings 5-27 specifications A-2 TCP/IP 5-17 straight-through D-2 thinnet D-2 twisted-pair D-2 UTP D-2 2 INDEX

connecting LAN Server 6-3 additional hubs D-2 LANtastic 6-3 using coaxial Ethernet cable D-5 Novell NetWare 6-1, 6-4 using twisted-pair cable D-2 packet 6-4 hubs Windows 3.1/DOS 6-1 using coaxial Ethernet cable D-5 Windows 95 3-1, 5-3, 5-7 using twisted-pair cable D-2 Windows for Workgroups 6-1 MDI/MDIX port to RJ-45 port D-2 Windows NT 5-11 NICs to the hub 2-7 DynamicAccess contents of the Networking Kit 1-2 NIC diagnostic tab C-4 conventions software 5-23 notice icons, About This Guide 2 text, About This Guide 2 CPU (central processing unit) See processor E crossover cable D-2 Echo Exchange Test C-10 Custom installation echo server C-10 Windows 95 5-2 EISA bus 1-7 Windows NT 5-11 EISA, reconfiguring to ISA 6-9 enabling file and printer sharing through Windows 95 4-4 to 4-17 D environmental operating range A-1 DEC PATHWORKS 6-3 EtherDisk diskette software categories 1-12 dedicated server B-3 EtherLink III ISA TPO NIC 1-7 designing the network B-1 Ethernet cable D-5 DHCP server connection, testing 5-18 expanding the network D-1 Diagnostic and Configuration Program, DOS C-9 expansion slots diagnostic program, Windows 95/Windows NT C-5 definition of 1-6 diagnostic test failure C-11 types 2-5 diagnostic testing Express installation 3-1 DOS C-9 Windows 3.x C-8 Windows 95/Windows NT C-4 F diagnostic tests fax service (3ComFacts) E-3 changing parameters C-13 file sharing through Windows 95 4-4 to 4-17 Group 1 C-9 Full-Duplex option 6-6 Group 3 C-10 Help C-11 Diagnostics tab C-4 G disabling Plug and Play on the NIC 5-7 General tab C-4 DNS granting access configuring 5-19 to PC hard drive 4-6 testing the server connection 5-20 to printer 4-8 domain name, entering 5-21 Group 1 tests C-9, C-10 DOS Group 3 test C-10, C-11 autoconfiguring the NIC 6-5 configuring the NIC 6-4 diagnostic program C-9 H installation program 6-1 hard disk drive, definition of 1-6 uninstallation program C-7 hardware conflicts in Windows 95 and Windows NT, drivers, installing supported resolving C-1 Banyan VINES 6-3 host name, entering 5-21 DEC PATHWORKS 6-3 LAN Manager 6-3 INDEX 3

hub connecting to another hub D-2 M connecting to NIC 2-7 Maximum Modem Speed option 6-6 definition of 1-8 MDI/MDIX port 1-10, 1-11, D-1, D-2 multiple D-6 MDI/MDIX switch 1-11, D-3 positioning D-6 memory, definition of 1-6 power adapter D-6 Microsoft LAN Manager 6-3 wall-mounting D-8 motherboard. See system board multiple hubs D-6 I installations I/O base address, changing C-2 making installation file for 5-27 IBM LAN Server 6-3 performing C-7 identifying PC on the network 5-22 installation file, making 5-27 installations, automated C-7 N installing NetWare drivers drivers 6-4 Banyan VINES 6-3 NLM files 6-3 DEC PATHWORKS 6-3 NetWare Loadable Modules (NLMs) 6-3 LAN Manager 6-3 network LAN Server 6-3 client/sever B-4 LANtastic 6-3 component checklist B-5 NetWare 6-1, 6-4 drivers 6-3 packet 6-4 expanding D-1 Windows 3.1/DOS 6-1 functions 1-3 Windows 95 3-1, 5-3, 5-7 identifying PC on 5-22 Windows for Workgroups 6-1 peer-to-peer B-3 Windows NT 5-1 purpose B-1 NIC 2-4 sample configuration 1-4 TCP/IP 5-16 system requirements 1-12 Interrupt Request Level option 6-6 testing the connection 5-15 IP address 5-17 Network Driver Optimization option 6-6 IRQs network interface card See NIC level, changing C-2 network interface specifications, NIC A-1 list of available 2-2 network operating system I/O Base Address option 6-6 Banyan VINES B-4 ISA (Industry Standard Architecture) bus 1-7 Microsoft LAN Manager B-4 ISA, configuring to EISA 6-8 Microsoft NT B-4 Novell NetWare B-4 network supplier support E-3 L network test C-6 LAN Manager 6-3 Networking Kit LAN Server 6-3 contents 1-7 LANtastic 6-3 software 1-11 LEDs system requirements 1-12 hub 2-10, 2-11, C-15 NIC 1-7 NIC 1-8, 2-9 backplate on 1-8 link LED 1-8 configuration, changing 6-6 connecting to hub 2-7 definition of 1-7 disabling Plug and Play 5-7 4 INDEX

installing 2-4 reinstalling software C-7 R removing installation software C-7 reinstalling NIC software C-7 testing 5-14 removing NIC software C-6, C-7 uninstalling NIC software C-6 repeating previous installation 5-24 NIC test C-5 resolving Windows 95 and Windows NT hardware nondedicated server B-3 conflicts C-1 non–Plug and Play BIOS 2-3, 5-7, 5-14 returning products for repair E-5 nonskid rubber feet D-6 RJ-45 connector, pin assignments A-2 rubber feet D-6 O OfficeConnect Hub 8/TPC 1-9 to 1-11 S OfficeConnect Hub TP4 1-8 to 1-11 saving configuration settings 6-7 OfficeConnect Networking Kit saving installation settings 5-25 contents 1-2 server system requirements 1-12 dedicated B-3 online technical services E-1 definition of 1-11 option settings nondedicated B-3 default 6-6 server address, entering the DNS 5-21 saving 6-7 server, DHCP, testing 5-18 OS/2 6-4 settings, changing configuration 6-6 sharing files and printers 4-4 to 4-17, B-3 software P installing PACE technology 5-23 Windows 95 5-3, 5-7 packet driver 6-4 Windows NT 5-11 PCI (Peripheral Component Interconnect) bus 1-7 network 1-11 peer-to-peer networking 1-11, B-3 reinstalling C-7 peripheral devices 2-8 uninstalling C-6, C-7 personal computer, components of 1-5 software option settings 6-6 physical dimensions A-1 stacking clips D-6 Plug and Play stacking multiple hubs D-6 configuring the NIC when disabled 5-8 Statistics tab C-4 determining presence of 2-3 straight-through cable D-2 disabling on the NIC 5-7 subnet mask, entering the 5-18 installing NIC software for 3-1 Support tab C-5 option setting 6-6 supported network drivers 6-3 positioning the hub D-6 system board, definition of 1-6 power LED 2-8, C-15 system requirements 1-12 power requirements adapter A-2 hub A-1 T preinstallation 2-2 T-connector C-11, D-5 printer sharing through Windows 95 4-4 to 4-17 TCP/IP in Windows 95 printing AUTOLINK.LOG file 6-2 configuring 5-17 problem report C-5 installing 5-16 processor, definition of 1-6 technical support 3Com URL E-1 bulletin board service E-2 fax service E-3 network suppliers E-3 product repair E-5 INDEX 5

terminators, BNC C-11, D-5 Windows 95 test changing I/O base address or IRQ C-2 DHCP server connection 5-18 diagnostic testing C-4 DNS server connection 5-20 installing NIC software 3-1, 5-1 failure C-11 performing automated installations C-7 gateway connection 5-19 Plug and Play Group 1 C-9 disabling 5-7 Group 3 C-10 installing NIC software for 3-1 network 5-14, C-6 reinstalling NIC software C-7 network connection 5-15 system requirements 1-12 NIC 5-14, C-5 uninstalling NIC software C-6 tests, diagnostic. See diagnostic tests Windows for Workgroups thin coax connection A-2 drivers, installing 6-1 thin Ethernet cable 1-11 NIC Transceiver Type option 6-6 auto configure 6-5 troubleshooting configuring 6-4 3Com NIC Diagnostics C-4 uninstalling software 6-4 diagnostic tests C-8 Windows NT DOS diagnostics C-9 changing I/O base address or IRQ C-3 hardware C-11 Custom installation 5-11 initial C-1 diagnostic testing C-4 resource conflicts C-1 performing automated installations C-7 tips C-11 reinstalling NIC software C-7 Windows NT C-1 uninstalling NIC software C-6 Windows 95 C-1 World Wide Web (WWW) E-1 twisted-pair cable 1-7, A-2, D-2 Z U Zoom button C-11 uninstalling NIC software C-6, C-7 unshielded twisted-pair connections A-2 URL E-1 UTP cable D-2

V verifying each PC’s identiﬁcation 4-2 network’s shared resources 4-18 VINES 6-3

W wall-mounting the hub D-8 Web site C-5 Windows 3.1/DOS diagnostic testing C-8 drivers, installing 6-1 NIC auto conﬁgure 6-5 conﬁguring 6-4 uninstalling software 6-4

3COM END USER SOFTWARE LICENSE AGREEMENT

IMPORTANT: Read Before Using This Product

YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING THIS PRODUCT. IT CONTAINS SOFTWARE, THE USE OF WHICH IS LICENSED BY 3COM CORPORATION (“3COM”) TO ITS CUSTOMERS FOR THEIR USE ONLY AS SET FORTH BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT USE THE SOFTWARE. USING ANY PART OF THE SOFTWARE INDICATES THAT YOU ACCEPT THESE TERMS. LICENSE: 3Com grants you a nonexclusive license to use the accompanying software program(s) (the “Software”) subject to the terms and restrictions set forth in this License Agreement. You are not permitted to lease, rent, distribute or sublicense the Software or to use the Software in a time-sharing arrangement or in any other unauthorized manner. Further, no license is granted to you in the human readable code of the Software (source code). Except as provided below, this License Agreement does not grant you any rights to patents, copyrights, trade secrets, trademarks, or any other rights in respect to the Software. The Software is licensed to be used on any workstation or any network server owned by or leased to you, provided that the Software is used only in connection with a 3Com adapter. You may reproduce and provide one (1) copy of the Software and supporting documentation for each such workstation or network server on which the Software is used as permitted hereunder. Otherwise, the Software and supporting documentation may be copied only as essential for backup or archive purposes in support of your use of the Software as permitted hereunder. You must reproduce and include all copyright notices and any other proprietary rights notices appearing on the Software and the supporting documentation on any copies that you make. NO ASSIGNMENT; NO REVERSE ENGINEERING: You may not transfer or assign the Software and/or this License Agreement to another party without the prior written consent of 3Com. If such consent is given and you transfer or assign the Software and/or this License Agreement, then you must at the same time either transfer any copies of the Software as well as the supporting documentation to the same party or destroy any such materials not transferred. Except as set forth above, you may not transfer or assign the Software or your rights under this License Agreement. Modification, reverse engineering, reverse compiling, or disassembly of the Software is expressly prohibited. However, if you are a European Community (“EC”) resident, information necessary to achieve interoperability of the Software with other programs within the meaning of the EC Directive on the Legal Protection of Computer Programs is available to you from 3Com upon written request. EXPORT RESTRICTIONS: You agree that you will not export or re-export the Software or accompanying documentation (or any copies thereof) or any products utilizing the Software or such documentation in violation of any applicable laws or regulations of the United States and the country in which you obtained them. TRADE SECRETS; TITLE: You acknowledge and agree that the structure, sequence and organization of the Software are the valuable trade secrets of 3Com and its suppliers. You agree to hold such trade secrets in confidence. You further acknowledge and agree that ownership of, and title to, the Software and all subsequent copies thereof regardless of the form or media are held by 3Com and its suppliers. UNITED STATES GOVERNMENT LEGEND: All technical data and computer software are commercial in nature and developed solely at private expense. The Software is delivered as “Commercial Computer Software” as defined in DFARS 252.227-7014 (June 1995) or as a “commercial item” as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in this License Agreement, which is 3Com’s standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-7015 (Nov. 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion of any legend provided on any licensed program or documentation delivered to you under this License Agreement. TERM AND TERMINATION: This license will expire fifty (50) years from the date that you first use the Software, if it is not earlier terminated. You may terminate it at any time by destroying the Software and documentation together with all copies and merged portions in any form. It will also terminate immediately if you fail to comply with any term or condition of this License Agreement. Upon such termination you agree to destroy the Software and documentation, together with all copies and merged portions in any form. GOVERNING LAW: This License Agreement shall be governed by the laws of the State of California as such laws are applied to agreements entered into and to be performed entirely within California between California residents and by the laws of the United States. You agree that the United Nations Convention on Contracts for the International Sale of Goods (1980) is hereby excluded in its entirety from application to this License Agreement. LIMITED WARRANTY; LIMITATION OF LIABILITY: All warranties and limitations of liability applicable to the Software are as stated on the Limited Warranty Card or in the product manual, whether in paper or electronic form, accompanying the Software. Such warranties and limitations of liability are incorporated herein in their entirety by this reference. SEVERABILITY: In the event any provision of this License Agreement is found to be invalid, illegal or unenforceable, the validity, legality and enforceability of any of the remaining provisions shall not in any way be affected or impaired and a valid, legal and enforceable provision of similar intent and economic impact shall be substituted therefor. ENTIRE AGREEMENT: This License Agreement sets forth the entire understanding and agreement between you and 3Com, supersedes all prior agreements, whether written or oral, with respect to the Software, and may be amended only in a writing signed by both parties. 3Com is a registered trademark of 3Com Corporation. 3Com Corporation, 5400 Bayfront Plaza, P.O. Box 58145, Santa Clara, CA 95052-8145. (408) 764-5000

3Com Corporation LIMITED WARRANTY

HARDWARE 3Com warrants its hardware products to be free from defects in workmanship and materials, under normal use and service, for the following lengths of time from the date of purchase from 3Com or its authorized reseller: Network Interface Cards Lifetime Other hardware products 1 year* *unless otherwise specified above Spare parts and spares kits 90 days

If a product does not operate as warranted above during the applicable warranty period, 3Com shall, at its option and expense, repair the defective product or part, deliver to Customer an equivalent product or part to replace the defective item, or refund to Customer the purchase price paid for the defective product. All products that are replaced will become the property of 3Com. Replacement products may be new or reconditioned. Any replaced or repaired product or part has a ninety (90) day warranty or the remainder of the initial warranty period, whichever is longer.

SOFTWARE 3Com warrants that the software programs licensed from it will perform in substantial conformance to the program specifications therefor for a period of ninety (90) days from the date of purchase from 3Com or its authorized reseller. 3Com warrants the media containing software against failure during the warranty period. No updates are provided. 3Com’s sole obligation with respect to this express warranty shall be (at 3Com’s discretion) to refund the purchase price paid by Customer for any defective software products, or to replace any defective media with software which substantially conforms to applicable 3Com published specifications. Customer assumes responsibility for the selection of the appropriate applications program and associated reference materials. 3Com makes no warranty or representation that its software products will meet Customer’s requirements or work in combination with any hardware or applications software products provided by third parties, that the operation of the software products will be uninterrupted or error free, or that all defects in the software products will be corrected. For any third party products listed in the 3Com software product documentation or specifications as being compatible, 3Com will make reasonable efforts to provide compatibility, except where the non-compatibility is caused by a “bug” or defect in the third party's product.

YEAR 2000 WARRANTY In addition to the Hardware Products Warranty and Software Products Warranty identified above, 3Com warrants that all Heritage 3Com products sold or licensed to Customer on and after January 1, 1998 that are date sensitive will continue performing properly with regard to such date data on and after January 1, 2000, provided that all other products used by Customer in connection or combination with the 3Com products, including hardware, software, and firmware, accurately exchange date data with the 3Com products, with the exception of those products identified at 3Com’s Web site, http://www.3com.com/products/yr2000.html, as not meeting this standard. A product is considered a “Heritage 3Com product” if it is a member of a product family which was manufactured by 3Com prior to its merger with US Robotics Corporation. This Year 2000 limited warranty does not apply to Heritage US Robotics Corporation products. If it appears that any such product does not perform properly with regard to such date data on and after January 1, 2000, and Customer notifies 3Com before the later of April 1, 2000, or ninety (90) days after purchase of the product from 3Com or its authorized reseller, 3Com shall, at its option and expense, provide a software update which would effect the proper performance of such product, repair such product, deliver to Customer an equivalent product to replace such product, or if none of the foregoing is feasible, refund to Customer the purchase price paid for such product. Any software update or replaced or repaired product will carry a Year 2000 Warranty for ninety (90) days or until April 1, 2000, whichever is later. OBTAINING WARRANTY Customer must contact 3Com’s Corporate Service Center or an Authorized 3Com Service Center within the SERVICE applicable warranty period to obtain warranty service authorization. Dated proof of purchase may be required. Products returned to 3Com’s Corporate Service Center must be pre-authorized by 3Com with a Return Material Authorization (RMA) number marked on the outside of the package, and sent prepaid and packaged appropriately for safe shipment, and it is recommended that they be insured. The repaired or replaced item will be shipped to Customer, at 3Com’s expense, not later than thirty (30) days after receipt of the defective product by 3Com. Dead- or Defective-on-Arrival. In the event a product completely fails to function or exhibits a defect in materials or workmanship within the first forty-eight (48) hours of installation but no later than thirty (30) days after the date of purchase, and this is verified by 3Com, it will be considered dead- or defective-on-arrival (DOA) and a replacement shall be provided by advance replacement. The replacement product will normally be shipped not later than three (3) business days after 3Com’s verification of the DOA product, but may be delayed due to export or import procedures. When an advance replacement is provided and Customer fails to return the defective product to 3Com within fifteen (15) days after shipment of the replacement, 3Com will charge Customer for the replacement product, at list price. 3Com shall not be responsible for any software, firmware, information, or memory data of Customer contained in, stored on, or integrated with any products returned to 3Com for repair, whether under warranty or not.

WARRANTIES EXCLUSIVE IF A 3COM PRODUCT DOES NOT OPERATE AS WARRANTED ABOVE, CUSTOMER’S SOLE REMEDY FOR BREACH OF THAT WARRANTY SHALL BE REPAIR, REPLACEMENT, OR REFUND OF THE PURCHASE PRICE PAID, AT 3COM’S OPTION. TO THE FULL EXTENT ALLOWED BY LAW, THE FOREGOING WARRANTIES AND REMEDIES ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER WARRANTIES, TERMS, OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING WARRANTIES, TERMS, OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND SATISFACTORY QUALITY. 3COM NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE OR USE OF ITS PRODUCTS. 3COM SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS TESTING AND EXAMINATION DISCLOSE THAT THE ALLEGED DEFECT IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY CUSTOMER’S OR ANY THIRD PERSON'S MISUSE, NEGLECT, IMPROPER INSTALLATION OR TESTING, UNAUTHORIZED ATTEMPTS TO REPAIR OR MODIFY, OR ANY OTHER CAUSE BEYOND THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE, LIGHTNING, OR OTHER HAZARD.

LIMITATION OF LIABILITY TO THE FULL EXTENT ALLOWED BY LAW, 3COM ALSO EXCLUDES FOR ITSELF AND ITS SUPPLIERS ANY LIABILITY, WHETHER BASED IN CONTRACT OR TORT (INCLUDING NEGLIGENCE), FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL, OR PUNITIVE DAMAGES OF ANY KIND, OR FOR LOSS OF REVENUE OR PROFITS, LOSS OF BUSINESS, LOSS OF INFORMATION OR DATA, OR OTHER FINANCIAL LOSS ARISING OUT OF OR IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE, USE, PERFORMANCE, FAILURE, OR INTERRUPTION OF ITS PRODUCTS, EVEN IF 3COM OR ITS AUTHORIZED RESELLER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND LIMITS ITS LIABILITY TO REPAIR, REPLACEMENT, OR REFUND OF THE PURCHASE PRICE PAID, AT 3COM’S OPTION. THIS DISCLAIMER OF LIABILITY FOR DAMAGES WILL NOT BE AFFECTED IF ANY REMEDY PROVIDED HEREIN SHALL FAIL OF ITS ESSENTIAL PURPOSE.

DISCLAIMER Some countries, states, or provinces do not allow the exclusion or limitation of implied warranties or the limitation of incidental or consequential damages for certain products supplied to consumers or the limitation of liability for personal injury, so the above limitations and exclusions may be limited in their application to you. When the implied warranties are not allowed to be excluded in their entirety, they will be limited to the duration of the applicable written warranty. This warranty gives you specific legal rights which may vary depending on local law.

GOVERNING LAW This Limited Warranty shall be governed by the laws of the State of California, U.S.A. excluding its conflicts of laws principles and excluding the United Nations Convention on Contracts for the International Sale of Goods.

3Com Corporation, 5400 Bayfront Plaza, Santa Clara, CA 95052-8145 (408) 764-5000 FCC DECLARATION OF CONFORMITY

We declare under our sole responsibility that the Model: Description: 3C509B EtherLink III ISA Network Interface Card

to which this declaration relates, is in conformity with the following standards or other normative documents: ■ ANSI C63.4-1992 Methods of Measurement ■ Federal Communications Commission 47 CFR Part 15, subpart B 15.107 (e) Class B Conducted Limits 15.109 (g) Class B Radiated Emissions Limits 3Com Corporation, 5400 Bayfront Plaza, P.O. Box 58145, Santa Clara, CA 95052-8145

FCC CLASS B STATEMENT

These devices comply with Part 15 of the FCC Rules. Operation is subject to the following two conditions: 1 These devices may not cause harmful interference, and 2 These devices must accept any interference received, including interference that may cause undesired operation. WARNING: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules, and the Canadian Department of Communications Equipment Standards entitled, “Digital Apparatus,” ICES-003. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: ■ Reorient or relocate the receiving antenna. ■ Increase the separation between the equipment and receiver. ■ Connect the equipment into an outlet on a circuit different from the one which the receiver is connected to. ■ Consult the dealer or an experienced radio/TV technician for help. The user may find the following booklet prepared by the Federal Communications Commission helpful: The Interference Handbook This booklet is available from the U.S. Government Printing Office, Washington, D.C. 20402. Stock No. 004-000-00345-4. NOTE: In order to maintain compliance with the limits of a Class B digital device, 3Com requires that you use quality interface cables when connecting to this device. Changes or modifications not expressly approved by 3Com could void the user’s authority to operate this equipment. Refer to the manual for specifications on cabling types.

VCCI CLASS 2 STATEMENT

This equipment is in the Class 2 category (Information Technology Equipment to be used in a residential area or an adjacent area thereto) and conforms to the standards set by the Voluntary Control Council For Interference by Information Technology Equipment aimed at preventing radio interference in such residential area. When used near a radio or TV receiver, it may become the cause of radio interference. Read the instructions for correct handling.