Table of Contents
Advertisement
Troubleshooting Information
Refer to this table and the information that follows the table to troubleshoot your Model FE116
hub.
Symptom
Cause
Amber Col
Data collision is
(collision) LED
normal on
blinks.
Ethernet
networks.
Amber Col LED
There is data
blinks excessively.
collision on the
network because
the network is
extremely busy or
defective devices
are connected on
the network that
cannot detect
network traffic or
collision.
Wrong or miswired
cables are used.
Amber Part LED
The connected
turns on.
port is partitioned
because of
excessive
collisions.
Green Link/Rx
The port is not
LED on the
detecting a
100BASE-T port
successful link or
is off when a cable
data transmission.
is attached or not
blinking when
there is data
transmission.
Make sure the network interface cards installed in the workstations are in working condition and
the software driver has been installed.
If required, verify the integrity of the hub by resetting it. Turn power to the switch off and then
back on. If the problem continues and you have completed all the preceding diagnoses, contact
NETGEAR Customer Support. For the phone number of the representative in your area, see
"Customer Support."
Model FE116 Fast Ethernet Hub Installation Giude
Solution
No action is required.
Make sure connected devices are operating in half-
duplex mode. The Model FE116 hub is not compatible
with devices that operate in full-duplex mode.
If you suspect that there might be a defective device on
the network, disconnect devices one at a time to isolate
the defective unit on the network.
If the network is extremely busy, you may have to
segment the network with a Fast Ethernet switch such as
the NETGEAR Model FS104 switch.
Make sure the correct UTP cables are used. See the
table in the installation section of this guide for cable use
and Normal/Uplink push button information. Note that
home telephone cables can cause a collision condition
and cannot be used in place of UTP cables.
The 100BASE-T RJ-45 port is partitioned after 32
consecutive collisions are detected. When the first good
packet without a collision is received, the port is
reconnected and the amber Partition LED turns off.
Check and correct causes listed in this table for
excessive collisions and make sure that:
•
The correct cable is used and the cable is not faulty.
•
There are no faulty connectors.
•
The network card in your PC is set to half-duplex
mode.
Check for a bad cable, cable pairs that are not correctly
wired, or loose connectors. Make sure that there is power
to the hub and the connected PC. Make sure the port has
not been partitioned.
Make sure the network card in the connected PC is
configured for 100 Mbps operation.
If the Green Link/Rx LED is on port 16, also check to
make sure the Normal/Uplink push button switch is set
according to the instructions in "Installation Procedures."
Advertisement
Table of Contents
