1. Intel_LAN_72_NW_A00.exe Driver
2. readme.txt File Contents

readme.txt Driver File Contents (Intel_LAN_72_NW_A00.exe)

Intel(R) Network Adapter Software 7.2 Release Notes
===================================================


Contents
========

- Viewing the user guide
- Repairing installation of utilities
- Team setup requirement
- IEEE 802.3ad teaming with Foundry switches
- Service Pack 4 for Windows* 2000
- Procedure for installing and upgrading drivers and utilities
- Updating drivers on Windows 2000 and Windows Server 2003
- FORCELOM keyword for DOS ODI driver
- Changing Boot Agent settings in Intel PROSet
- Network connectivity test
- Assigning multiple IP addresses in Windows
- File and driver Versions
- Known limitations
- Customer support


Viewing the user guide
=======================

Additional information can be found in the User's Guide. To access it, click 
"View User Guides" from the autorun screen or navigate to the MANUAL directory
and double-click index.htm. 


Repairing installation of utilities
===================================

When attempting to repair the installation of DMI or the WMI NIC provider, 
you must uninstall and reinstall the utility. To uninstall a utility:

  1. Run the Intel PROSet Installer.
  2. In the Program Maintenance dialog box, select Modify.
  3. In the Custom Setup dialog box, click the graphic next to the utility 
     you would like to uninstall. Click the option Do not install this 
     feature. 
  4. Follow the onscreen directions to finish the installation.

After completing the uninstall, use the Intel PROSet Installer to reinstall 
the utility. 


Team setup requirement
======================

Before adding an adapter to a team, make sure each adapter is configured the
same as other adapters in the team. For team members to successfully 
implement teaming functionality, each team member must be configured 
similarly. To check team member configuration, view each team member's 
settings in the Advanced tab in Intel PROSet.  Settings to check include QoS 
Packet Tagging, Jumbo Frames, and the various offloads. If team members 
implement Advanced features differently, failover and team functionality are
affected.  


IEEE 802.3ad teaming with Foundry switches
==========================================

Foundry switches require an even number of ports in an aggregated link. If 
you remove an adapter from a 802.3ad team connected to a Foundry switch, 
make sure you maintain an even number of adapters in the team.


Service Pack 4 for Windows 2000
===============================

For the driver and software to function correctly on Windows 2000, it is 
recommended that you install Service Pack 4 or later.


Procedure for installing and upgrading drivers and utilities
============================================================

Intel does not recommend installing or upgrading drivers and Intel(R)
PROSet software over a network connection. Instead, install or upgrade
drivers and utilities from each system.


Updating drivers on Windows 2000 and Windows Server 2003
========================================================

When adding new Intel PRO/1000 adapters to a system, use one of these
methods to update drivers of Intel PRO/1000 adapters that are already 
in the system and using older drivers.
- Click Install Base Drivers on the CD autorun
- Use setupbd.exe (see the User Guide for more information)

If you use Windows' Update Driver feature, the new Intel adapters 
you add to the system will not operate correctly until you restart 
the system or disable then re-enable the Intel adapters.

If you use Setupbd.exe to update the drivers and are using files from a 
source other than the installation CD, you must update the Setupbd.ini 
file so it refers to the correct location of the .inf file.
 
Setupbd.ini is located in the ...\SETUP\SETUPBD\W2KWS03 directory.


FORCELOM keyword for DOS ODI driver
===================================
 
The FORCELOM keyword allows you to specify the driver to load on an integrated network 
connection, or LAN On Motherboard (LOM). To specify a LOM on a Dell server, use this 
command:
 
FORCELOM 1028

Changing Boot Agent settings in Intel PROSet
============================================

If you are logged in to a Windows system with Administrator rights, the Apply Settings 
button on the Boot Agent tab in Intel PROSet will be grayed out until you change a 
setting. After you have changed the setting, click Apply Changes.

You do not need to press CTRL+S before you are able to change the settings. 

If you are not logged in with Administrator rights, you will not be able to change
settings on the Boot Agent tab.
 

Network connectivity test
=========================

Clicking the Advanced button on the Diagnostics tab in the Windows 
version of Intel PROSet launches the Network Connectivity Test. 
This test sends test messages to another Ethernet adapter on the 
network to verify network connectivity.


Assigning multiple IP addresses in Windows
==========================================
 
If you assign multiple IP addresses to a single network connection in a Windows 2000 
or Windows Server 2003 system, you must create a new DWORD value in the Registry:
 
1. Using the Registry Editor, browse to this registry key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}
2. Under this key you will see multiple instances of four-digit incrementing numeric values, 
   i.e. 0000, 0001, 0002, etc. Click on each of the values within this key and find the key(s)
   of the Intel adapter(s) in the system. You can identify the Intel adapters by checking 
   the value of the DriverDesc string value.
3. Add a new DWORD value in the key for each Intel adapter that will use multiple IP addresses. 
   (Click Edit > New > DWORD Value.)
4. Name the new DWORD "WaitAutoNegComplete".
   This DWORD is case-sensitive.
5. Set the WaitAutoNegComplete value to 1.


File and driver versions
========================

Windows base drivers
--------------------
Windows 2000 Fast Ethernet (e100bnt5.sys): 7.0.26.0
Windows 2000 Gigabit Ethernet (E1000nt5.sys): 7.2.19.2
Windows Server 2003 Fast Ethernet (e100b325.sys): 7.0.26.0
Windows Server 2003 Gigabit Ethernet (E1000325.sys): 7.2.19.2

Windows ANS drivers
-------------------
Windows 2000 (iansw2k.sys): 6.25.1.0
Windows Server 2003 (ianswxp.sys): 6.25.1.0

Windows applications
--------------------
Intel PROSet for Windows (proset.exe): 6.4.3.8
Intel Priority Packet (priority.exe): 2.28.0.0
Intel SNMP agent (ILanSnmp.dll): 1.52.0.0

Red Hat Linux base drivers
--------------------------
Fast Ethernet (e100.o): 2.3.30
Gigibit Ethernet (e1000.o): 5.2.17.10

Red Hat Linux ANS driver
------------------------
Linux iANS Driver (ians.o): 2.4.13

Red Hat Linux applications
--------------------------
Intel Linux LAN Adapters PROCfg Command Line Tool (procfg): 1.8.6d
Intel Linux* LAN Adapters PROCfg Daemon (procfgd): 1.8.8a
Intel PROSet for Linux (xprocfg): 1.8.7
SNMP for Linux (inic-snmp): 1.6.9

NetWare base drivers
--------------------
Fast Ethernet (ce100b.lan): 7.03.02
Fast Ethernet Client 32 (ce100b32.lan): 7.03.02
Gigabit Ethernet (ce1000.lan): 7.34.01

NetWare ANS driver
------------------
NetWare iANS (ians.lan): 7.36.10

NetWare applications
--------------------
NetWare SNMP agent (LANAgent.lan): 1.17.00

DOS base drivers
----------------
Fast Ethernet NDIS2 (e100b.dos): 4.48
Fast Ethernet DOS ODI (e100bodi.com): 4.05
Gigabit Ethernet NDIS2(e1000.dos): 3.46
Gigabit Ethernet DOS ODI (e1000odi.com): 2.39


Known limitations
=================

  Removing an adapter when using teaming
  --------------------------------------
  When you remove an adapter from a system, do not put this adapter into 
  any system on the same network until you have rebooted the original 
  system. Otherwise, two identical Ethernet addresses appear in the 
  network.

  Diagnostics may inaccurately report cable length
  ------------------------------------------------
  When using PROSet's "Test Cable" feature, Intel gigabit adapters may 
  incorrectly report the length of a 110 meter cable as being over 140 
  meters. Other cable lengths are correctly reported.  

  WOL and Standby options not available when connecting to a Gigabit Only
  switch (copper adapters only)
  -----------------------------------------------------------------------
  When a copper media adapter is connected to a Gigabit-only switch, the 
  WOL and Standby features are unavailable. This is due to the power 
  consumption level of the adapter.

  The Intel PRO/1000 MF Server Adapter supports WOL, but uses fiber media.


  Team settings default to those common to all adapters in the team
  -----------------------------------------------------------------
  Team settings, or capabilities, are always set to the lowest common 
  denominator for each capability. When you make team changes, the team
  settings are updated when you click Apply in PROSet and the team is 
  reloaded.
  
  If through PROSet you add an adapter to a team that has lower capabilities 
  than the team itself, PROSet warns you that there is a compatibility
  mismatch. PROSet adds the adapter to the team and the new team settings are 
  set to the lowest common denominator. These settings take effect when you
  click Apply.

  All adapters in the team have to have the same capabilities or they will 
  default to the lowest denominator. This is true regardless of the team 
  member's status.
 
  Naming a team for an unattended installation
  --------------------------------------------
  As part of the unattended installation, you can set up one or more 
  teams. When naming teams, you must start the team name with
  the word Team. Examples of valid team names are Team One and Team1.

  Saving and Restoring Settings for Teams
  ---------------------------------------
  You can save and then restore settings for teams through Intel PROSet
  or through the script savres.vbs. When you save and restore the 
  settings for a team, the preferred primary adapter setting is not 
  saved or restored. You must change the preferred primary adapter
  setting after restoring the team.

  TCP Segmentation for Windows 2000
  ---------------------------------
  The advanced feature TCP segmentation is not supported in Windows
  2000 for Intel(R) PRO/1000 Server adapters.

  Windows Server 2003 does support this feature for Intel PRO/1000
  Server Adapters.  

  Intel PRO/1000 Adapter will not have Link when forced to operate at 
  10 or 100 Mbps with a link partner is also forced to the same state
  -------------------------------------------------------------------
  Unless copper Gigabit Adapters are set to auto-negotiate, they are not 
  MDI/MDI-X aware.

  When an Intel PRO/1000 Adapter is forced to operate at 10 or 100
  Mbps, the adapter will not have a link with the link partner under
  the following circumstances:
  - If a link partner is also forced to operate at 10 or 100 Mbps, is
    connected back to back, and is connected using a regular cable 
    instead of a crossover cable. 
  - If a link partner is also forced to operate at 10 or 100 Mbps, 
    connected to a switch, and connected using a crossover cable instead
    of a regular cable.

  Changing speed and duplex of adapters in a team
  -----------------------------------------------
  When you add an adapter to a Fast EtherChannel, Gigabit EtherChannel, 
  or Link Aggregation team, Intel PROSet makes sure that the adapters in
  the team are capable of operating at the speed assigned to the team.
  Intel PROSet does not force any adapter in the team to operate at that
  speed.

  LargeSendOffload and Intel PRO/100 adapters
  -------------------------------------------
  LargeSendOffload provides no perfomance benefits for Intel PRO/100 adapters, 
  so it should not be enabled.

  Linux SNMP: Set operation fails on RH 3
  ---------------------------------------
  Running the set operation using Red Hat 3 fails when using the
  net-snmp-5.0.8 package. This issue has been fixed in net-snmp-5.0.9 
  package.

  Using Intel PRO/1000 XT Network Connections and e1000ODI.COM driver
  -------------------------------------------------------------------
  In some cases, an Intel PRO/1000 XT Network Connection using the 
  e1000ODI.COM driver will not receive traffic. You can fix this problem 
  by disabling Wake On LAN (WOL) in the adapter hardware before connecting 
  to the network. 
 
  Use IBAUtil to disable WOL. For more information, see the Intel Boot 
  Agent User Guide on the installation CD.

  

  
Customer Support
================

- Main Dell web support site: http://www.dell.com


Legal / Disclaimers
===================

Copyright (C) 2002-2004, Intel Corporation.  All rights reserved.

Intel Corporation assumes no responsibility for errors or omissions in 
this document. Nor does Intel make any commitment to update the information 
contained herein.

* Other product and corporate names may be trademarks of other companies 
and are used only for explanation and to the owners' benefit, without intent 
to infringe.