Networking Kit User Guide
Networking Kit User Guide
Networking Kit
®
User Guide
http://www.3com.com/
ii
CONTENTS
CONTENTS
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
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
A SPECIFICATIONS
Hub Specifications A-1
NIC Specifications A-1
RJ-45 Connector Pin Assignments A-2
Cable Specifications A-2
v
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 Conflicts 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 Configuration 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
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
vii
FCC DECLARATION OF CONFORMITY
viii
ABOUT THIS GUIDE
This guide describes how to set up your own network using the 3Com®
OfficeConnect® 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 Specific This table shows the location of specific 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.
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.
GETTING STARTED
1
The 3Com® OfficeConnect® 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
■ Configure the NIC on each network PC
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 defines 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.
!
Hub Alert PWR
PKT
COLL
green 1
Port Sta
tus
= link 2
OK, off 3
= link 4
fail, yell
ow = part
ition.
OF FIC
CONNECEE
NECTT
Hub TP4
Q
withuick Ste
Win ps to
N dow
s 95Network
Useretworkin
NICs Nonskid feet Guid g Kit
e
in g
Stacking
clips
Quick Steps Guide
User Guide
®
For
EtherDis
Configu the EtherL
NetWa ration
k
ink ®III
®
Version
PC (DOS 1.44
DOSOS/2 re ®2.x, and
Transceand ODI Drivers3.x, Diagnostics Card Family MB)5.0
Suppor nd ®OS/2 NDIS and 4.x DOS
83-070 Service ts both and SmartA2.01 and
5-000 s and PCPCMCIA gent Drivers
A:>INMultifunction
© 1995, STALL Card Service Release ™Driver
Card Standa
© 1994, 2.1 CardAgents
3Com
1995, Corporati
Novell,
s rd
Inc. on.
All All rights
rights reserved.
reserved
.
®
For
EtherDis
Configu the EtherL
NetWa ration ink ®III
® k
Version
PC (DOS 1.44
DOSOS/2 re ®2.x, and
Transceand ODI Drivers3.x, Diagnostics Card Family MB)5.0
Suppor nd ®OS/2 NDIS and 4.x DOS
83-070 Service ts both and SmartA2.01 and
5-000 s and PCPCMCIA
A:>INMultifunction gent Drivers
© 1995, STALL Card Service Release
Card Standa Driver
™
Cables
rights reserved.
reserved
.
NIC software
Hub power
adapter
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
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.
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 file 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 files 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
1A VDC
MA
– X
+
MD
I/X
8
1X
OfficeConnect Hub
Figure 1-2 Sample OfficeConnect Networking Kit Network
The next few sections briefly 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)
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 sufficient RAM and hard drive space.
1-6 CHAPTER 1: GETTING STARTED
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
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.
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 specifications 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.
Your Networking Kit contains one of the following hub types, depending
on the model:
■ OfficeConnect Hub TP4
■ OfficeConnect Hub 8/TPC
Understanding Networking 1-9
The OfficeConnect 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 Port St
Alert PKT
COLL atus
green 1
= link 2
OK, off 3
= link 4
fai l, yello
w= partit
ion.
OF FI
CONN CE
ECT
panel
! PWR
Alert
COLL Port St
1 atus
2
3
green 4
= link 5
OK, off 6
= link 7
fail, ye 8
llow = COAX Netw
partit ork Ut
ion. ilizatio
1%
2% n
3%
6% OF FI
12%
25% CONN CE
50% ECT
Hub 8/T
PC
LED display
panel
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/
Power input X
4
1X
RJ-45 ports
COAX
MDI/
X
8
Power input
BNC 1X
coaxial connector MDI/MDIX port
MDI/MDIX switch
RJ-45 ports
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).
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
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 configure 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.
Where to Go To get your network up and running, you first 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 configure 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.
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.”
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
■ Configure the NIC for a non–Plug and Play BIOS. (See “Configuring
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.
Screw
Backplate
Expansion slots
Figure 2-2 Removing the Backplate
.
EISA
ISA
PCI
Figure 2-3 PC Expansion Slot Types
If you can’t find 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.
■ Reconfigure the NIC from ISA mode to EISA mode. (See
“Reconfiguring 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.)
■ Configure the NIC for a non–Plug and Play BIOS. (See “Configuring
the NIC for Non–Plug and Play” on page 5-8.)
2-6 CHAPTER 2: INSTALLING YOUR NETWORK HARDWARE
Remove backplate
Insert 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
Connecting NICs This section describes connecting each installed NIC to the hub. Before you
to the Hub continue, finish installing all the NICs for your network, as described in the
preceding section.
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
1X
RJ-45 ports
MDI/MDIX switch
MDIX To NIC
When you’ve finished 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, confirming an active
connection.
When you first 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, first make sure that the hub is operational and
then check the LED on the NIC connected to the hub.
Hub LED Status The OfficeConnect 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.
When you’ve finished 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).
Under Windows 95, Plug and Play automatically configures 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 find 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 flag 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 finished
connecting the hub to the NICs in all the PCs to be networked, as
described in Chapter 2.
If you can’t find your Windows 95 CD or diskettes, you can still continue with
the procedure. Your hard drive may already have the required Windows files.
3-2 CHAPTER 3: EXPRESS SOFTWARE INSTALLATION FOR WINDOWS 95
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).
4 Make sure that the drive letter in the field corresponds to the diskette
drive containing the EtherDisk diskette. Click OK.
The system copies files 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 fill in the Network screen fields later,
as described in Chapter 4, “Enabling File and Printer Sharing
Through Windows 95.”
5 Click OK.
The Identification tab of the Network screen appears (Figure 3-4).
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).
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, configures 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 flexible 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 Configuration 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
10 Click Finish.
The system copies more files 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).
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 verifies your
choice), and select the appropriate diskette drive, such as the A drive.
13 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 (Figure 3-8).
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).
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.
However, before you can effectively use your peer-to-peer network, you
need to configure 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 final few tasks you need to perform before your
Windows 95 peer-to-peer network is functioning properly. It describes
how to enable (activate) file and printer sharing through Windows 95.
Although this chapter focuses on enabling file and printer sharing, you can
also use this method to enable sharing for other resources.
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 file 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
Identification opportunity to define 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.
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).
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 Configuration 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 Configuration 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 file 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 files 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).
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.
This completes the procedure for allowing users to share the files 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).
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 final 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).
The Add Printer Wizard starts and displays the welcome screen shown in
Figure 4-16.
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.
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.
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.
10 Select the printer displayed in the Browse for Printer screen, as shown in
Figure 4-21.
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
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.
Changing the name here only affects the name as it’s shown in this PC’s
Printers file. 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 confirm that
your network printer connection is working.
Adding the Network Printer to a PC’s Printers Folder 4-17
15 Click Finish.
Windows 95 sends a test page to the printer and asks you to confirm that
the test page printed correctly, as shown in Figure 4-26.
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.
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 configured properly.
2 Double-click Computer_2 in the Network Neighborhood window.
The Computer_2 window appears, as shown in Figure 4-28.
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 confirm that the instructions in this chapter are appropriate for your PC,
see Table 5-1.
Table 5-1 NIC Software Installation Roadmap
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
configuration 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:
■ Configure 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 configure 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 finished
connecting the hub to the NICs in all the PCs to be networked, as
described in Chapter 2.
If you can’t find your Windows 95 CD or diskettes, you can still continue
with the procedure. Your hard drive may already have the required
Windows files.
Windows 95 Setup for Custom Installation 5-3
Configuring 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.
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).
4 Make sure that the drive letter in the field corresponds to the diskette
drive containing the EtherDisk diskette. Click OK.
The system copies files 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 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 fill in the Network screen fields later,
as described in “Identifying Your PC on the Network” on page 5-22.
5 Click OK.
The Identification tab of the Network screen appears (Figure 5-4).
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).
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, configures 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 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
Configuring a NIC in a Each NIC in your kit is configured 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.
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 configure 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
Follow these steps to install the NIC software and configure 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 first 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.
8 Click OK.
Windows 95 copies the required files 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.
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 configure 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 files 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 configure 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 first 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 configuring 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 configuring 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 configuring a
NIC in the preceding section, clicking OK starts the 3Com Installation
Wizard.
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.
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 configured 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.
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.
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 confirms that the NIC is functioning correctly.
2 Click Next.
The Network Connection Test screen appears, as shown in Figure 5-14.
4 Click Next.
For Windows NT — Go to “Configuring DynamicAccess Software” on
page 5-23.
For Windows 95 — The TCP/IP Inquiry screen appears, as shown in
Figure 5-15.
Installing TCP/IP Installing and configuring 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 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.
Configuring 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.
Configuring DNS Dynamic Name Server (DNS) converts a World Wide Web URL to an
actual IP address. You can configure DNS either automatically or manually
depending on how your network is set up.
When you click Next in the preceding section, the DNS Configuration
screen appears, as shown in Figure 5-18.
Identifying Your PC When you click Next in the preceding section, the Network Identification
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 identification if you’ve
already entered this information through Windows 95 (see Figure 5-4).
This screen lets you identify applications running on your PC that you
wish to support using PACE software. Configuring DynamicAccess
software is optional.
■ If you’re installing a small peer-to-peer network, go to “To Not
Configure 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 Configure
DynamicAccess Software.”
Repeating a Previous You can save the configuration 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.
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.
3 Enter the path for the EtherDisk diskette that you’re using.
The EtherDisk diskette is first copied to a temporary directory, and then
that file 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.
Completing NIC Procedures for completing the installation and configuration differ for
Software Windows 95 and Windows NT.
Installation
Completing This section describes how to complete the NIC installation and
Installation for configuration 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).
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).
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. See Appendix C for more information about the 3Com
tray icon.
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 configure TCP/IP according
to the instructions in your Windows NT documentation.
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.
SOFTWARE INSTALLATION
6 FOR DOS, WINDOWS 3.1, AND
WINDOWS FOR WORKGROUPS
This chapter describes how to install NIC software and configure 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 files 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.
Running the AutoLink To run the installation program to configure 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
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 file, enter:
type autolink.log | more
■ To print the file, 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
The Networking Kit NIC no longer supports NetWare 3.11 and 4.0x servers.
Installing Other Table 6-2 provides the text file names and driver names for other drivers
Supported Network supported by the NIC. Text files 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
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.
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 specific 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
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
“Configuring a NIC in a Non–Plug and Play PC” on page 5-7.
When you put the NIC into EISA mode, the EISA configuration program
that came with your computer can configure the NIC with correct settings
for operating in an EISA PC.
You can configure an ISA NIC for EISA mode only if the NIC is installed in
an EISA slot.
If you have configured an ISA NIC for an EISA PC, the PROTOCOL.INI file
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
configuration 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
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.
SPECIFICATIONS
A
This appendix lists the specifications for both the hub and the NIC. For the
NIC, it includes connector pin assignments and cable requirements.
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
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)
DESIGNING YOUR NETWORK
B
After reading the first 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 benefits provided through networking?
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 define 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, files, and so forth)?
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 files, such as
proprietary information or accounting spreadsheets?
■ Do you want to store data files 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 files 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 configured 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.
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.
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 configured 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.
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
Other device
Software application
Software application
Software application
Checklist If you experience problems installing the NIC, first 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).
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 conflict, 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 conflict. 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 Configuration 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 conflict should be resolved.
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.
.
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
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 verified that the network is functioning.
Network Test
Run the Network test first 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.
Uninstalling the If you have problems installing NIC software, allow the 3Com Installation
NIC Software for Wizard to finish. 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 first perform the uninstallation process.
Reinstalling NIC When an event such as a hard disk crash occurs, the original configuration
Software file 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 specified 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 configure 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.
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.
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.
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 files 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 files. 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
configuration, 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.
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.
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.
Getting Help If a If a diagnostic test fails, the NIC may not be defective. The problem may
Test Fails be incorrect configuration settings, settings that conflict with other NICs,
or improper installation.
CAUTION: Make sure to turn the power off before inserting or removing
the NIC from the PC.
■ 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 file, enter:
type autolink.log | more
■ To print the file, enter:
print autolink.log
Diagnostic Testing for DOS, Windows 3.x, and Windows for Workgroups C-13
■ Check the A:\HELP directory for files 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.
Using the Help EtherDisk diskette 2 includes a Help library with general information and
Library specific procedures on loading drivers and setting up a networking
environment for your PC.
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.
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 other LEDs on the panel indicate the status of each port, as described
in Table 2-2 on page 2-11.
EXPANDING YOUR NETWORK
D
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 first hub,
you can easily add more.
Understanding The following definitions will help you better understand how to connect
Connection OfficeConnect 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
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).
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 first 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
COAX
RJ-45 port
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
Hub number 4
10–30 VDC
1A MAX
– + COAX MDI/X 8 1X
Hub number 3
10–30 VDC
1A MAX
– + COAX MDI/X 8 1X
Hub number 2
10–30 VDC
1A MAX
– + COAX MDI/X 8 1X
MDI/MDIX
switch (in)
Hub number 1
10–30 VDC
1A MAX
– + COAX MDI/X 8 1X
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.
COAX
Ground
lead BNC connector
with terminator
+
COAX
T-connector
COAX
BNC connector
with terminator
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 OfficeConnect 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 flow 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 Port St
Alert PKT
COLL atus
green 1
= link 2
OK, off 3
= link 4
fail, ye
llow =
pa rtition
.
OF FI
CONN CE
ECT
Hub TP
4
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 OfficeConnect 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 flat, 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.
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)
■ 3ComFacts automated fax service
SM
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/
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: <your Internet e-mail address>
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.
Support from Your If additional assistance is required, contact your network supplier. Many
Network Supplier suppliers are authorized 3Com service partners who are qualified 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 configuration 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 find 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 configuration changes, if applicable
Returning Products Before you send a product directly to 3Com for repair, you must first
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.
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.
base address Also called I/O base address. The first address in a series of addresses in
memory, often used to describe the beginning of a network interface
card’s I/O space.
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 5 Category 5 balanced cable. Balanced 100-ohm and 120-ohm cables and
associated connecting hardware whose transmission characteristics are
specified 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.
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 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 Configuration 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 defining 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.
hub A device that connects network devices. Hubs serve as traffic cops for
managing network data. They restore signal amplitude and timing,
detect collisions, and broadcast signals to network devices.
input/output (I/O) The method, medium, or device (such as a keyboard, monitor, floppy
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.
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.
LED Light-emitting diode. A diode that converts voltage to light and that is
commonly used in digital displays.
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 files 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 office
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 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.
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, file services,
software applications, client/server networking. or other services to
computers over a network.
T-connector A cable adapter that attaches a PC with a network interface card to the
network.
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.
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
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
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 identification 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 configure 6-5
configuring 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
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
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.