# Performance and Troubleshooting

This section contains the following topics:

- Common Problems and Solutions

- Multiple Adapters

- Bus Configuration Troubleshooting

- Other Performance Issues

- The entire bus will operate at the speed of the slowest PCI card installed in the bus.

## Common Problems and Solutions

In addition to the table below, review the product release notes.

Problem | Solution
--- | ---
The computer cannot find the adapter | Make sure the adapter is seated firmly in the slot. Download the latest drivers from the Intel support web site: http://www.intel.com/network Try a different PCI/PCI-X bus master slot. Check to see if your motherboard has the latest BIOS. Make sure your PCI slots are v2.3 compatible. Make sure your PCI-X slots are v1.0a compatible. Try rebooting the computer. Try a different Intel adapter.
Diagnostics pass but the connection fails | Check the responding link partner. Make sure that the cable is securely attached. Also, make sure that the cable is the proper type and does not exceed the recommended lengths. Try another cable. Try running the Sender-Responder diagnostic Test. Make sure the duplex mode and speed setting on the adapter matches the setting on the switch.
Another adapter is no longer working after you installed an Intel adapter | Make sure the cable is connections are correct. Make sure your BIOS is current. See Bus Configuration Troubleshooting. Check for interrupt conflicts and sharing problems. Make sure the other adapter supports shared interrupts. Also, make sure your operating system supports shared interrupts. Unload all PCI/PCI-X device drivers, then reload all drivers. Try reseating all adapters.
The adapter is no longer working without apparent cause | The network driver files may be damaged or deleted. Reinstall the drivers. Try reseating the adapter in its slot or different slot, if necessary. Try rebooting the computer. Try another cable. Try a different adapter. Run the adapter and network tests described under "Test the Adapter".
The Link indicator light is off | Check all connections at the adapter and the switch. Make sure the cable is securely attached. also, make sure that the cable is the proper type and does not exceed the recommended lengths. Run the adapter and network tests described under "Test the Adapter". Make sure that the adapter driver is loaded, and that the adapter is enabled. Try another port on the switch. Make sure that the link partner is configured to auto-negotiate (or forced to match adapter). If connecting to a 10GbE switch, verify that it is IEEE 802.3ae- compliant.
The link light is on, but communications are not properly established | Make sure the proper (and latest) driver is loaded. Both the adapter and its link partner must be set to either auto-negotiate or manually set to the same speed and duplex settings. The adapter's link indicator light may be on even if communications between the adapter and its link partner have not been properly established. Technically, the link indicator light represents the presence of a carrier signal but not necessarily the ability to properly communicate with a link partner. This is expected behavior and is consistent with IEEE's specification for physical layer operation.
RX or TX light is off | Make sure you've loaded the network drivers. Network may be idle; try creating traffic while monitoring the lights. Try another adapter.
The diagnostic utility reports the adapter is "Not enabled by BIOS" | The BIOS isn't configuring the adapter correctly. See Bus Configuration Troubleshooting. Try another PCI-X/PCI slot.
The computer hangs when the drivers are loaded | Try changing the BIOS interrupt settings. See Bus Configuration Troubleshooting.
Event viewer message: A device attached to the system is not functioning | If there is a BIOS setting for "Plug and Play OS", it should be set to YES.
In Windows* 2000, installer is prompting for Prodd.vxd and Prokddp.vxd files | If you use the Add/Remove Programs icon in the Windows Control Panel to remove an Intel adapter, and then try to install drivers from a later Intel CD, you may see a prompt asking for the following files: Prodd.vxd Prokddp.vxd This is because Windows is attempting to install the files associated with the earlier driver, which are not present on the later Intel CD. To resolve this problem, finish the installation and choose Skip when prompted for a missing file. Then, instead of removing the driver, update it with the later Intel CD. For instructions on updating the adapter driver, see the "Install the Network Drivers" section in this online guide.
After upgrading operating systems, Intel PROSet is no longer available | If you are upgrading Windows operating systems and you have Intel PROSet software installed, it will be deleted in the process. You will need to reinstall Intel PROSet.
In Windows Server 2003, IP addresses are lost or Intel PROSet becomes unstable with bridging enabled | With bridging enabled, Intel PROSet does not retain adapter IP address information. If changes are made to any Intel PROSet advanced feature after enabling bridging, the Intel PROSet software becomes unstable.
Terminal Server support | When using Terminal Server, make sure only one session of Intel PROSet is open at any one time. Simultaneous sessions are not supported in Intel PROSet.
The IPv6 protocol does not seem to work after updating adapter drivers on Windows 2000 Advanced Servers. | When using a Windows 2000 Advanced Server SP1 with IPv6 bound to the adapter, you must unbind the IPv6 protocol from the adapter before updating drivers. This is a result of the operating system implementation of the IPv6 protocol. To update an adapter using the IPv6 protocol: Unbind the IPv6 protocol from the adapter. To find the IPv6 setting, click Start > Settings > Control Panel > Network and Dial-Up connections > Local Area Connection <#>, where <#> is the connection number. Right-click the Connection number to open the Adapter Properties dialog box. Clear the IPv6 checkbox then click OK. Update drivers. Bind the IPv6 protocol to the adapter. In the Adapter Properties dialog box, click the IPv6 checkbox. See step one for detailed instructions on finding the IPv6 option.

### Other Items to Check

- Use the drivers that came with your adapter, or download the latest ones from the Intel support web site.

- Make sure the cable is installed properly. The network cable must be securely attached at all connections. If the cable is attached but the problem persists, try a different cable.

- Make sure the link partners match or are set to auto-negotiate. Make sure the updated driver is loaded.

- Test the adapter. Run the adapter and network tests described in Test the Adapter.

- Check the Common problems table and try the recommended solutions

- The entire bus will operate at the speed of the slowest PCI/PCI-X card installed in the bus.

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

## Multiple Adapters

When configuring a multi-adapter environment, you must upgrade all Intel adapters in the computer to the latest software.

If the computer has trouble detecting all adapters, consider the following:

- If you enable Wake On LAN (WOL) on more than two adapters, the Wake on LAN* (WOL) feature may overdraw your system’s auxiliary power supply, resulting in the inability to boot the system and other unpredictable problems. For multiple desktop/management adapters, it is recommended that you install one adapter at a time and use the IBAUtil utility (ibautil.exe in \BootAgnt) to disable the WOL feature on adapters that do not require WOL capabilities. On most server adapters, the WOL feature is disabled by default.

- Adapters with Intel® Boot Agent enabled will require a portion of the limited start up memory for each adapter enabled. Disable the service on adapters that do not need to boot PXE or RPL.

## Bus Configuration Troubleshooting

If the adapter is not recognized by your OS or if it does not work you may need to change some BIOS Setup program settings. Try the following only if you are having problems with 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.

- Enable the PCI/PCI-X slot. In some computers, you may need to use the BIOS Setup program to enable the slot.

- You must install the network adapter in a bus master slot. Some BIOS Setup programs require you to enable the slot for bus master/master. Check your BIOS Setup program and the computer's documentation to make sure the slot is set for bus master/master.

- Configure the slot for level-triggered interrupts. The slot used by the adapter must be configured for level-triggered interrupts instead of edge-triggered interrupts. Check your BIOS Setup program to make sure triggering is configured properly.

- Reserve interrupts and/or memory addresses into the BIOS. This prevents adapter cards from trying to use the same settings as older ISA cards. Check your BIOS Setup program; there may be IRQ options such as 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.

## Other Performance Issues

Attaining gigabit speeds requires that many components are operating at peak efficiency. Among them are the following:

- Cable quality and length. (Do not exceed the maximum recommended length for your cable type. Shorter lengths provide better results. Straighten kinks and check for damaged sections of cable.)

- PCI/PCI-X Bus speed and traffic

- Processor speed and load

- Available memory

- Transmission frame size (see Jumbo Frames)

- Operating System (Features will vary by OS compatibility, such as offloading and multiprocessor threading.)

`Last modified on 8/25/04 5:44p Revision 1`