Back to Contents Page
Troubleshooting: Broadcom 440X 10/100 Integrated Controller
User Guide
Hardware Diagnostics
Checking Port LEDs
Troubleshooting Checklist
Checking if Current Drivers are Loaded
Testing Network Connectivity
Software Problems and Solutions
Hardware Diagnostics
Loopback diagnostic tests are available for testing the adapter hardware. These
tests provide access to the adapter internal/external diagnostics, where packet
information is transmitted across the physical link (for DOS, see DOS
Diagnostics; for Windows see Diagnostics).
See Network Link and Activity Indication
to check the state of the network link and activity.
The following checklist provides recommended actions to take to resolve problems
that you may encounter when using the Broadcom 440X 10/100 Integrated Controller.
LAN on Motherboard
- Inspect all cables and connections. Verify that the cable connections at
the network adapter and the switch are attached properly. Verify that the
cable length does not exceed the specified maximum (100 meters) and that the
cable is the proper type (Category 3, 4, or 5 UTP for 10BASE-T operation,
and Category 5 UTP for 100BASE-T operation).
- Check the properties settings and change them if they are in conflict with
another device.
- Verify that your computer is using the latest BIOS.
Network PCI Card
- Remove any metallic object or jewelry from your hands and wrists.
- Ensure to use only insulated or nonconducting tools.
- Verify that the system is powered OFF and unplugged before accessing internal components.
- Installation or removal of adapters must be performed in a static-free environment. The use of a properly grounded wrist strap or other personal antistatic devices and an antistatic mat is strongly recommended.
- Ensure the card is properly seated in a PCI card slot. Check for specific hardware problems, such as obvious damage to board components or the PCI edge connector.
- Try inserting the adapter in another slot. If the new position works, the original slot in your system may be defective.
- Replace the failed adapter with one that is known to work properly. If the second adapter works in the slot where the first one failed, the original adapter is probably defective.
- Install the adapter in another functioning system and run the tests again. If the adapter passed the tests in the new system, the original system may be defective.
- Remove all other adapters from the system and run the tests again. If the adapter passes the tests, the other adapters may be causing contention.
Checking if Current Drivers are Loaded
Go to Broadcom Advanced Control Suite 2 to
view vital adapter information, network status, and network connectivity.
Testing Network Connectivity
Use the ping command to determine if the network connection
is working.
 |
NOTE: Network connectivity can also be tested using the
Network Test feature in Broadcom Advanced
Control Suite 2. |
- Click Start, and then click Run.
- Type cmd in the Open box, and
then click OK.
- Type ipconfig /all to view the network connection
to be tested.
- Type ping IP address, and then
press ENTER.
The ping statistics that are displayed indicate whether the network connection
is working or not.
Software Problems and Solutions
Microsoft Remote Installation Service(RIS) Instructions for Windows RIS Servers
Problem: Microsoft Remote Installation Service (RIS) installation
fails for Windows 2000 and Windows XP.
Solution: Refer to the Microsoft Knowledge Base Article, "How
to Add Third-Party OEM Network Adapters to RIS Installations."
To deploy a Windows 2000 Image
- Verify that Windows Service Pack 3 or later has been installed on the Windows
2000 RIS server.
- Follow the steps described in the Microsoft Knowledge Base Article - 246184
at http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b246184.
- If Service Pack 3 or later has not been installed on the Windows 2000 RIS
server, modify the b44win.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 the [Manufacturer] section (see the following
example).
Original |
Revised |
[Manufacturer]
%V_BCM% = Broadcom, NTx86.5.1 |
[Manufacturer]
%V_BCM% = Broadcom |
- Follow the steps in the Microsoft Knowledge Base Article - 246184 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
- Follow the steps described in Microsoft Knowledge Base Article - 315279
at http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b315279.
- Modify the b44win.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 the [Broadcom] section (see the following example).
;------------Win2K and Win9x Device List-------------------------
[Broadcom]
; very generic Broadcom 4401 A1 NIC or LOM
%BCM4401.DeviceDesc% = BCM4401, PCI\VEN_14E4&DEV_4401
.
.
; MSI LOM
%BCM4401_msi_two.DeviceDesc% = BCM4401_msi_two, PCI\VEN_14E4&DEV_4401&SUBSYS_590C1462
;----------end of Win2k and Win9x Device List-------------
|
- Remove NTx86.5.1 in two locations (see the following
example).
Original |
Revised |
[Manufacturer]
%V_BCM% = Broadcom, NTx86.5.1
[Broadcom.NTx86.5.1] |
[Manufacturer]
%V_BCM% = Broadcom
[Broadcom] |
- Follow the steps in the Microsoft Knowledge Base Article - 315279
at http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b315279,
skipping step 1, as shown above.
Broadcom Boot Agent
Problem: Unable to obtain network settings through DHCP using PXE.
Solution: For proper operation make sure that the STP (spanning tree
protocol) is disabled or that portfast mode (for Cisco) is enabled on the port
to which the PXE client is connected. For instance, set spantree portfast 4/12
enable.
Back to Contents Page