Troubleshooting

If the adapter can’t connect to the network, read this section and review the Frequently Asked Questions (FAQ) and the PCI Troubleshooting section below.

Make sure the cable is installed properly.

The network cable must be securely attached at both RJ-45 connections (adapter and hub). The maximum allowable distance from adapter to hub is 100 meters. If the cable is attached and the distance is within acceptable limits but the problem persists, try a different cable.

Check the LED lights on the adapter.

The following table describes the LEDs for the Intel^® PRO/100+ and PRO/100 S adapters, and the PRO/100 VE, and VM Desktop Adapters and Network Connections.

LED	Indication	Meaning
ACT/LNK	On	The adapter and switch are receiving power; the cable connection between the switch and adapter is good.
	Off	The adapter and switch are not receiving power, or you have a driver configuration problem.
	Flashing	The adapter is sending or receiving network data. The frequency of the flashes varies with the amount of network traffic.
100TX	On	Operating at 100 Mbps.
	Off	Operating at 10 Mbps.

The following table describes the lights for the PRO/100+ Dual Port Server adapter (with three LEDs per port).

LED	Indication	Meaning
LNK	On	The adapter and switch are receiving power; the cable connection between the switch and adapter is good.
	Off	The adapter and switch are not receiving power; the cable connection between the switch and adapter is faulty; or you have a driver configuration problem.
ACT	On or flashing	The adapter is sending or receiving network data. The frequency of the flashes varies with the amount of network traffic.
	Off	The adapter is not sending or receiving network data.
100	On	Operating at 100 Mbps.
	Off	Operating at 10 Mbps.

The following table describes the lights for the PRO/100 S Dual Port Server adapter (with 64 bit PCI Connector).

LED	Indication	Meaning
ACT/LNK	On	The adapter and switch are receiving power; the cable connection between the switch and adapter is good. NOTE: if only one port appears to be operating, go into the Network control panel (Windows) or a configuration file for other operating system, and check the status of the second port.
	Off	The adapter and switch are not receiving power, or you have a driver configuration problem.
	Flashing	The adapter is sending or receiving network data. The frequency of the flashes varies with the amount of network traffic.
100TX	On	Operating at 100 Mbps.
	Off	Operating at 10 Mbps.

Make sure you’re using the correct drivers.

Make sure you’re using the drivers that come with this adapter or newer ones from the Intel support web site. The driver file name always contains the letter B (for example, E100BODI.DOS). Check the web site on a regular basis.

Make sure the switch port and the adapter have the same duplex setting.

If you configured the adapter for full duplex or autonegotiate, make sure the switch port is also configured for full duplex or autonegotiate, respectively. If you mismatch between forced duplex and autonegotiate, you may degrade performance, cause data loss, or result in lost connections.

Testing the Adapter (Diagnostics)

Test the adapter by running diagnostics. For DOS, run the Diag100.EXE diagnostics program on the PRO/100 S adapter disk. For Windows NT*, Windows 95 and Windows 98, run PROSet by double-clicking the PROSet icon in the Windows Control Panel. To run diagnostics, select the adapter and click the Diagnostics tab, then click Run Tests. For additional information, click Help in the PROSet window.

Frequently Asked Questions (FAQs)

The server hangs when the drivers are loaded.

Change the BIOS interrupt settings. See PCI Installation Tips for more information.

If you are using EMM386, it must be version 4.49 or newer (this version ships with MS-DOS 6.22 or newer).

Diagnostics pass, but the connection fails or errors occur.

At 100 Mbps, use Category 5 wiring and make sure the network cable is securely attached.

At 100 Mbps, connect to a 100BASE-TX hub/switch (not 100BASE-T4).

For NetWare, make sure you specify the correct frame type in your NET.CFG file.

Make sure the duplex mode setting on the adapter matches the setting on the switch.

The Wake on LAN feature is not working. (NOTE: Only the PCI 2.1 bus requires a WOL cable. The PCI 2.2 bus does not have a cable.)

Make sure the WOL cable is attached and that power is being applied to the computer.

Check the BIOS for its WOL setting. Some computers may need to be configured for WOL using the BROW utility in the \BootAgnt directory on the CD. On server adapters, the WOL setting is Off by default.

Make sure the network cable is fully attached to the adapter.

If none of these works, check the Late-breaking News document that came with the adapter or check the Intel support Web site. See Support page in this guide for information on connecting to Intel's online services.

PCI Configuration Troubleshooting

Some PCI computers require additional steps to configure a PCI adapter. Try the following if you are having problems configuring the adapter:

You may need to change the Plug and Play setting in your computer's BIOS. See your computer's manual for instructions on how to access. For Windows 95, 98, and Me, set the Plug and Play OS option to YES. For Windows 2000, reverse the setting. For any other operating systems, set the Plug and Play OS option to NO..
Enable the PCI slot. In some PCI computers, you may need to use the BIOS Setup program to enable the PCI slot. This is especially common in PCI computers with the PhoenixBIOS.*
Enable the slot for busmaster. You must install the PRO/100 adapter in a busmaster slot. Some BIOS Setup programs require you to enable the slot for busmaster/master. Check your BIOS Setup program and the computer's documentation to make sure the slot is set for busmaster/master.
Configure the slot for level-triggered interrupts. The PCI slot the adapter is using must be configured for level-triggered interrupts instead of edge-triggered interrupts. Check your BIOS Setup program to make sure triggering is set up.
Reserve interrupts and/or memory addresses for ISA adapters. This prevents PCI cards from trying to use the same settings as ISA cards. Check your BIOS Setup program; there may be IRQ options such as Enable for ISA or Disable for PCI.

Here are some examples of BIOS Setup program parameters:

PCI slot #	Slot where the adapter is installed (1-3)
Master	ENABLED
Slave	ENABLED
Latency timer	40 - 80
Interrupt	Choose any one of several that the BIOS Setup provides.
Edge-level	Level

The exact wording of the parameters varies with different computers.

Common Problems and Solutions

Problem	Solution
Your computer can't find the adapter	Make sure the adapter is seated firmly in the slot. Try a different PCI busmaster slot. See your server's documentation to identify busmaster slots. Try a different PRO/100 adapter. If you add an adapter with a bridge chip (such as a dual-port adapter), uninstall and then reinstall all of the drivers for all installed adapters.
An adapter doesn't work after installing an adapter driver from Windows Me*	If you use the drivers that come with Windows Me, during an installation of Windows Me, the adapter may not function correctly. After Windows Me installs the default driver, you'll need to update all Intel adapters with the newer driver on the Intel CD. See Install the Network Drivers for instructions. If you use multiple adapters with Windows Me, you must upgrade all Intel adapters for any to function properly.
Diagnostics pass but the connection fails	Try running the Sender-Responder diagnostic test. Make sure the network cable is securely attached.
An adapter stopped working after you installed the PRO/100 adapter	Make sure the cable is connected to the adapters you intend to be connected to. Check for a resource conflict. See PCI Configuration Troubleshooting. Make sure both adapters are seated firmly in the slot. If you add an adapter with a bridge chip (such as a dual-port adapter), uninstall and then reinstall all of the drivers for all installed adapters. Check all cables.
The adapter stopped working without apparent cause	Try reseating the adapter. The network driver files may be damaged or deleted. Reinstall the drivers. Try a different PRO/100 adapter. Unload and reload all adapter drivers and try again. Unload the driver and switch slots of the adapters. Then reload drivers as in installing for first time. Try enabling or disabling the auto-negotiation setting on the link partner (this setting must be set the same on both the switch and the adapter). NOTE: The adapter's LNK LED may light even if communications between the adapter and its link partner have not been properly established. Proper configuration of link partners consists of both sides being set to either auto-negotiate or set with the same speed and duplex settings.
The Link LED does not light	Make sure the PC is receiving power. Make sure the adapter cable is attached at both ends. Make sure you've loaded the correct adapter driver. Check all connections at the adapter and the switch. Try another port on the switch. Make sure the duplex mode setting on the adapter matches the setting on the switch. Make sure you have the correct type of cable between the adapter and the hub. 100BASE-TX requires two pair. Try enabling or disabling the auto-negotiation setting on the link partner (this setting must be set the same on both the switch and the adapter).
RX or TX LED does not light	Make sure you've loaded the network drivers. Network may be idle; try logging in from a workstation. The adapter isn't transmitting or receiving data; try another adapter.
One port in a dual port adapter does not work	Upgrade the BIOS Check the interrupts and see if another is IRQ is available for the second port. Uninstall all drivers for all PCI adapters, reboot, and reinstall all drivers. This forces the PCI bus to re-enumerate and take into account the bridge chip on the dual port adapter. Note: Unattended installs work for one port only. Note: Boot agent works on the first port only.
In NetWare, the following message is displayed: "IPX received an incomplete packet from network 00001011:00A0C9AADFC3. 85 incomplete packets received."	This message occurs when NetWare's internal routing mechanism mistakes the Intel iANS driver's probe packets for NetWare RIP packets. To prevent this message from displaying, make sure that IPXRTR.NLM is loaded on every NetWare server on the LAN. For more information on IPXRTR, see Novell's documentation or their Support web site (support.novell.com).