Back to Contents

Troubleshooting: Broadcom 440X 10/100 Integrated Controller User Guide

Hardware Diagnostics
Checking Port LEDs
Troubleshooting Checklist
Checking if Correct Drivers are Loaded
Testing Network Connectivity

Software Problems and Solutions


Hardware Diagnostics

Network connectivity diagnostic tests are available for testing the adapter hardware under Windows. These tests provide access to the adapter's internal/external diagnostics, where packet information is transmitted across the physical link (see Diagnostics in Broadcom Advanced Control Suite).

Back to Top


Checking Port LEDs

The adapter has two LEDs, one for Activity and one for Link speed. The Activity LED indicates data transfer status, and the Link LED indicates a connection (on at 100 Mbps, off connected at 10 Mbps). After the driver is loaded and the cables are connected properly, the appropriate LED is lit.

Before the port LEDs can provide troubleshooting information, the adapter must be connected to the network, and the network drivers for your particular operating system must be installed.

  1. Verify that the adapter driver software has been installed and that the adapter is connected to a network.

  2. Check to see that the controller status LEDs are operating correctly.
Note: For information about the LED interface for notebooks or tablet PCs, refer to the documentation included with your computer.

Back to Top


Troubleshooting Checklist

The following checklist provides recommended actions to take to resolve problems installing the Broadcom 440X 10/100 Integrated Controller, or running it in your computer.


Back to Top


Checking if Correct Drivers are Loaded

The following section describes how to check if the correct drivers are loaded for Windows.

The Broadcom Advanced Control Suite Vital Sign function allows for viewing vital adapter information, network status, and network connectivity. Active adapters are listed.

  1. From the Installed Adapters list in the Vital Sign window, select the Broadcom adapter to be tested.
Note: Information for non-Broadcom adapters is less comprehensive than information listed for Broadcom adapters.

  1. Click Refresh to display the driver status of the selected adapter.


Back to Top


Testing Network Connectivity

The following section describes how to test network connectivity for Windows.

Use the ping command to determine if network connectivity is working.

  1. Click Start, and select Run from the Windows menu to display the Run command window.
  2. In the Open field, type cmd.
  3. Click OK.
  4. Type ipconfig /all to display the command window.
  5. At the command line, type ping <IP address>; and then press Enter. This displays the network connectivity information.

Back to Top


Software Problems and Solutions

Microsoft Remote Installation Service(RIS) Instructions

Problem: Microsoft Remote Installation Service (RIS) installation fails for both Windows 2000 and Windows XP.

Solution: Refer to Microsoft Article Q246184 How to Add Third-Party OEM Network Adapters to RIS Installations

To deploy a Windows 2000 Image

  1. Verify that the Windows 2000 RIS server has Service Pack 3 or later installed.
  2. Follow the steps described in Microsoft Article Q246184 article at http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b246184.
  3. If the Windows 2000 RIS server does not have Service Pack 3 or later installed, modify the bcm4sbe5.inf file as described below. In the .inf file that is to be placed in the RemoteInstall\Setup\Language\Images\Dir_Name\i386 folder, remove NTx86.5.1 in two lines (see the following example).

    Original Revised

    [Manufacturer]
    %V_BCM% = Broadcom, NTx86.5.1

    [ControlFlags]
    ExcludeFromSelect = *

    [Broadcom]

    [Manufacturer]
    %V_BCM% = Broadcom

    [ControlFlags]
    ExcludeFromSelect = *

    [Broadcom]


  4. Follow the steps in the Microsoft Article Q246184 article at http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b246184, skipping step 1 as this has been done above.

To deploy a Windows XP Image

  1. Modify the bcm4sbxp.inf file.
  2. In the .inf file that is to be placed in the RemoteInstall\Setup\Language\Images\Dir_Name\i386 folder, remove NTx86.5.1 in two lines (see the following example).

    Original Revised

    [Manufacturer]
    %V_BCM% = Broadcom, NTx86.5.1

    [ControlFlags]
    ExcludeFromSelect = *

    [Broadcom.NTx86.5.1]

    [Manufacturer]
    %V_BCM% = Broadcom

    [ControlFlags]
    ExcludeFromSelect = *

    [Broadcom]

  1. Follow the steps in the Microsoft Article Q246184 article at http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b246184, skipping step 1, as this has been done above.

Back to Top

Back to Contents