Troubleshooting: BroadcomNetXtreme? Gigabit Ethernet Adapter User’s Guide


  Microsoft Remote Installation Service (RIS) installation fails for both

  Windows 2000 and Windows XP.

  Solution: Refer to Microsoft’s

  Article Q246184 “How to Add Third-Party OEM

  Network Adapters to RIS Installations.”

  In the .inf file that is to be placed in the RemoteInstallSetupLanguageImagesDir_Namei386

  folder, remove NTx86.5.1 in two lines (see the following example).



  %V_BCM%=BROADCOM, NTx86.5.1










  Only use the .inf file provided by the vendor for this purpose.

  Problem: Able to create

  Broadcom LAC connections icons having same name under network properties



  In Windows 2000, each network adapter installed properly will have an icon

  in Network Properties window. The name of the icon is usually in the form

  of “Local Area Connection ##” and where ## is a number starting from 1.

  The names of icon can be changed by right clicking the icon and selecting

  rename. The name of the icon is only meaningful to the Network Properties

  window. Sometimes the system administrators will rename these icons to easily

  differentiate the network connections. When BASP is configured, BASP will

  create additional adapter icons and rename the icons. The naming convention

  is to allow end users to quickly identify the adapter with corresponding

  team and VLAN. The names of the icons created by BASP therefore are not

  recommended to be changed.

  Problem: Uninstalling

  the BASP software and user is prompted to reboot early


  In Windows 2000, after configuring BASP team, the system may sometimes prompt

  user to reboot. This is because Plug and Play on W2k may fail to commit

  any change in the network protocol binding. Users can choose not to reboot

  and continue configuring intermediate driver without having any side effect.

  When user has finished all the configuration, it is required to reboot.

  Problem: Cannot enable

  VLAN after it is disabled


  In Windows 2000, BASP creates additional network connections in “Network

  Connection and Dail-up” Window. Similar to physical network connections,

  these virtual connections can be disabled via the context menu. However,

  if these virtual connections are re-enabled, the system will report error

  as “connection failed!”. This is known problem with Windows 2000. When this

  happens, reboot the system will enable the virtual connection again.


  Able to configure Internet Connection Sharing (ICS) when there aren’t any

  unassigned adapters.


  Windows 2000 networking is shipped with the Internet Connection Sharing

  (ICS), which is designed to allow multiple computers accessing the Internet

  via a Windows 2000 system. To configure ICS, a user would need to select

  a network connection as “outside” connection, and another network connection

  as “inside” connection. Broadcom has observed that ICS allow any available

  network connection to be “outside” and “inside” connection, regardless of

  the BASP team configuration. Broadcom recommends that the user not select

  any network connection that is part of the BASP team to be “outside” and


  Problem: Team configuration

  is not retained when user goes back to edit.


  In configuring BASP team configuration, the actual changes of the configuration

  is not committed until the user click “OK” in “Network Properties” window.

  If a user chooses not click OK and instead goes back to the BASP team configuration

  window, all the previous uncommitted changes will be lost and user will

  need to reenter the configurations. As a workaround, the user should always

  click “OK” in “Network Properties” window after making changes.

  Problem: IP address

  is configurable on a member of the team.


  When a team is created, the TCP/IP properties for the adapters are unselected.

  The user can manually select and configure TCP/IP properties of the adapters

  and configure an IP address. This is a limitation of the Windows 2000 network

  installation paradigm, where this invalid configuration is still allowed.

  Problem: When creating

  64 VLANs, all virtual adapters show disconnected or one of the 64 VLANs

  show disabled.


  The maximum VLAN configurations are 63 tagged and one untagged VLAN ID 0.

  If 64 tagged VLANs are created, they are disconnected. A reboot is required

  and only 63 tagged VLANs show links, while a 64th is disabled.