Intel(R) PRO Network Connections Software Version 10.0 Release Notes
===================================================================

March 9, 2005

This release includes software and drivers for Intel(R) PRO/100,
Intel(R) PRO/1000, and Intel(R) PRO/10GbE adapters and integrated 
network connections.

Contents
========

- What's New in This Release
- User Guides
- Intel(R) PROSet for Windows* Device Manager
- Intel Fiber Optic Adapters
- Saving and Restoring Adapter Settings
- Teaming Notes
- Intel(R) PRO/1000 PM Network Connection Notes
- Microsoft* Windows* XP x64 and Windows Server* 2003 x64 Notes
- Microsoft Windows XP Notes
- Microsoft Windows 2000 Notes
- Microsoft Windows NT* 4.0, Windows 98, and Windows Me Notes
- Intel(R) PRO/10GbE Adapter Notes
- Intel(R) Quad Port Server Adapter Installation Notes
- Known Issues
- Customer Support


What's New in This Release
==========================

- Support for the Intel(R) PRO/1000 PM Network Connection
- Support for the Intel(R) PRO/1000 GT Quad Port Server Adapter
- Support for the Intel(R) PRO/1000 GT Dual Port Server Adapter
- Support for Intel(R) Extended Memory 64 Technology


User Guides
===========

Several user guides for Intel Network Connections are available for 
this product.  You may access them in the following ways: 
- On Windows-based systems, start the autorun program on the Intel CD, 
  then click "View User Guides".
- Double-click "index.htm" located in the root of the Intel CD.
- Go to http://support.intel.com. 


Intel(R) PROSet for Windows* Device Manager
===========================================

Intel PROSet functionality is now integrated with the Windows Device 
Manager. To configure Intel PRO/100, Intel PRO/1000 and Intel PRO/10GbE 
adapters on Windows 2000 systems or newer, open the Windows Device Manager.
Do not open adapter, team, or VLAN properties from the network control 
panel as you may be prompted to reboot your system.

You must have administrator rights to install or use Intel PROSet for 
Windows Device Manager. 


Intel Fiber Optic Adapters
==========================

Caution: The fiber optic ports may utilize Class 1 or Class 1M laser 
devices. Do not stare into the end of a fiber optic connector 
connected to a "live" system.  Do not use optical instruments to 
view the laser output. Using optical instruments increases eye hazard.  
Laser radiation is hazardous and may cause eye injury.  To inspect a 
connector, receptacle or adapter end, be sure that the fiber optic 
device or system is turned off, or the fiber cable is disconnected 
from the "live" system. 

The Intel PRO/1000 and PRO/10GbE adapters with fiber optic connections
operate only at their native speed and only at full-duplex.  Therefore
you do not need to make any adjustments.  Use of controls or
adjustments or performance of procedures other than those specified
herein may result in hazardous radiation exposure.  The laser module 
contains no serviceable parts.  


Saving and Restoring Adapter Settings
=====================================

You can save and then restore adapter settings through the script 
SavResDX.vbs.  Intel PROSet is required for SavResDX.vbs to function 
correctly.  

When you save and restore the settings for an adapter in a team, the 
preferred primary adapter setting is not saved or restored.  You must 
change the preferred primary adapter setting after restoring the team.


Teaming Notes
=============

Team setup requirement
----------------------
Before creating a team, make sure each adapter is configured similarly. Check
each adapter's settings in Intel PROSet. Settings to check include QoS Packet
Tagging, Jumbo Frames, and the various offloads. If team members implement 
Advanced features differently, the team will align the settings with the least 
capable adapter. 

Changing Offload Settings for an Adapter in an ANS Team
-------------------------------------------------------
When you disable an offload setting for an adapter in an ANS team, the team
reloads and the team capabilities are recalculated. As a result, the offload 
setting is disabled for the remaining adapters in the ANS team. 

Intel PROSet does not reflect the fact that the offload setting is disabled 
for the remaining adapters in the team.

If you re-enable the offload setting for the original adapter in the team,
the team reloads and the setting is automatically re-enabled for the 
remaining adapters.

Intel(R) Active Management Technology
-------------------------------------
If Intel(R) AMT is enabled on an adapter, you will not be able to add it to 
a team. When you create or modify a team, the adapter will not be displayed 
in the list of available adapters. The adapter will not have a Teaming tab 
on its Device Manager property sheet.

Teaming Known Issues
--------------------

  Express Team may not respond if failover recovery occurs during standby
  -----------------------------------------------------------------------
  If an express team fails over from the primary to the secondary adapter, 
  and the link state on the two adapters reverses while the system is in 
  an S3 sleep state, the team will be unable to respond to network traffic.  
  This is because the S3 state prevents the reconfiguration of MAC 
  addresses on link state change.  

  Secondary member ports of an express team are visible in Device Manager
  -----------------------------------------------------------------------
  If your multiport adapter is installed in a hot-swap capable slot, the
  secondary member ports of an express team will be visible in Device 
  Manager. Changes made to the advanced properties of the secondary ports
  are ignored.
  
  Network Connections window shows the team as disabled or network
  cable unplugged
  ----------------------------------------------------------------
  After adding a VLAN to the team, this is normal.  The connection
  protocols are now bound to the VLAN on the team. You can configure the
  connection protocols in the Properties for the VLAN.

  Team name doesn't change in Device Manager
  ------------------------------------------
  If you modify a team name from the team property sheet, it may take
  several minutes for the name to change in Device Manager. Closing and
  opening Device Manager will load the new name.

  Removing a teamed adapter from a hot-plug system
  ------------------------------------------------
  When you physically remove an adapter that is part of a team or a VLAN, 
  you must reboot or reload the team/VLAN before using that adapter in the 
  same network. This will prevent Ethernet address conflicts. 

  Changing speed and duplex of adapters in a team
  -----------------------------------------------
  When you add an adapter to a Link Aggregation team using Intel PROSet, 
  make sure that the adapter is running at the same speed and duplex of 
  the other adapters in the team.

  Compatibility notes for Multi Vendor Teaming
  --------------------------------------------
  Attempting to hot-add a non-Intel adapter to a team may cause system 
  instability.  If you do hot-add a non-Intel adapter to a team, make sure 
  you restart the computer or reload the team. 

  Enabling GMRP with AFT Teaming May Create Multicast Group
  ---------------------------------------------------------
  If GMRP is enabled at the switch, with AFT teaming in a Windows environment, 
  you may find a new multicast group within all the ports connected to the 
  team members participating in it.  This occurs only in Microsoft Windows 
  XP and Server 2003.  The multicast address is used by IEEE 802.1x protocol, 
  which is supported by these operating systems. 

  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 an 802.3ad team connected to a Foundry switch, 
  make sure you maintain an even number of adapters in the team.

  QoS Load Balancing on ANS Teams without prioritizing packets is not
  Recommended
  -------------------------------------------------------------------
  Enabling QoS load balancing on ANS teams without prioritizing packets will
  result in reduced performance.

  Express Teaming Option is Unavailable for a Multi-port Adapter
  --------------------------------------------------------------
  If you install a multi-port adapter in a slot that previously contained an
  Intel adapter, Express Teaming may be disabled.  To resolve this, move the
  new adapter to a different PCI slot.  Or, reinstall the old adapter,
  uninstall the adapter from Windows Device Manager, and install the 
  new adapter.


Intel PRO/1000 PM Network Connection Notes
==========================================

Known Issues
------------

  Jumbo Frames
  ------------
  The Intel PRO/1000 PM Network Connection does not support jumbo frames.


Microsoft Windows XP x64 and Windows Server 2003 x64 Notes
==========================================================

Known Issues
------------

  Traffic interruptions when creating a VLAN or team
  --------------------------------------------------
  Creating a VLAN or a team temporarily interrupts traffic on all VLANs and
  teams on a Windows XP x64 or Windows Server 2003 x64 system.

  Newly teamed adapter is disabled
  --------------------------------
  If you add an adapter to a team with a VLAN, and the adapter has lower
  offloading capabilities than the team, then the adapter will appear 
  disabled.  Rebooting resolves this issue.


Microsoft Windows XP Notes
==========================

Microsoft Windows XP Known Issues
---------------------------------

  TCP Segmentation Offload is not supported
  -----------------------------------------
  TCP Segmentation Offload (Large Send Offload) has performance issues with
  Windows XP due to Microsoft issues.  The feature is disabled by default 
  upon install and upgrade regardless of previous settings.  This is only
  for Windows XP and is for all versions and service packs of Windows XP.
  For more information reference MS Knowledge base article 842264. 


Microsoft Windows 2000 Notes
=============================

Service Pack 4 Required for Microsoft Windows 2000
--------------------------------------------------
Windows 2000 Service Pack 4 is required for Intel network drivers 
and software to function correctly.

Unknown PCI Device and PCI Serial Port
--------------------------------------
Intel Active Management Technology is not supported on Windows 2000.  
Adapters with Intel AMT enabled will display two unknown devices in 
Windows Device Manager. This does not affect network traffic on the 
adapter.


Microsoft Windows NT 4.0, Windows 98, and Windows Me Notes
==========================================================

Updating drivers and utilities on systems using IPSec
-----------------------------------------------------
If you have a Windows NT 4.0 or Windows 9x system and you are using IPSec,
upgrading drivers and utilities might cause changes to your security 
setting or potential mismatches with the adapter drivers or applications. 
If you want to continue using IPSec, Intel recommends that you NOT update 
to this software version. If you do not wish to continue using IPSec, 
uninstall the existing Intel IPSec software before installing this version.

Locally administered address (LAA) in Windows 98SE
--------------------------------------------------
If you want to use the default address after using a manually-assigned (LAA) 
address, perform one of these procedures:

  - From the Network Properties dialog box’s Advanced tab, select Locally 
    Administered Address and change its value to 0. Click OK to apply the 
    setting.

  - In Intel PROSet II, click the Advanced tab, then click Restore Default 
    or clear all characters from the Value field. Click OK to apply the 
    setting.

Microsoft Windows NT, Windows 98, and Windows Me Known Issues
-------------------------------------------------------------

  PRO1000 Receive Errors on Windows NT 4.0
  ----------------------------------------
  If you experience high received error counts on a Windows NT 4.0 system 
  with a PRO1000 adapter installed, increasing the Receive Descriptors 
  setting to 384 will alleviate the problem.

  No I/O Access for Older Adapters on Windows NT 4.0
  --------------------------------------------------
  Some older adapters do not support I/O. When these adapters are removed 
  with the hot plug lever on a Windows NT 4.0 system, the system no longer 
  functions. Before using the hot plug lever on a system running Windows NT
  4.0, make sure that the adapter supports I/O. If the adapter does not 
  support I/O, power down the system before removing the adapter.

  "PROSet Failed to Initialize" error on Windows NT 4.0
  -----------------------------------------------------
  Some Intel PRO/1000 MT Desktop Adapters and Intel PRO/1000 GT Desktop 
  Adapters do not function correctly while running on the following systems:
 
  Dell* Optiplex* GX280
  Dell Dimension* 8200
  Dell Precision* 530
  Dell XPS

  Windows 98 SE Driver Installation Issues
  ----------------------------------------
  When installing drivers on Windows 98 SE, the Hardware Installation
  Wizard is displayed. If you use the wizard, you must specify a
  location for the drivers. After checking the Specify a Location
  checkbox, browse to the Intel CD and then to the \PRO1000\WIN_98ME
  directory.  Similarly, for Intel PRO/100 adapters, go to the 
  \PRO100\WIN_98ME directory.

  Controller Information not available in Windows 98 and Windows NT
  -----------------------------------------------------------------
  In systems running Windows 98 and Windows NT, Intel PROSet does not 
  display controller information in the Adapter Details window. However, 
  Intel PROSet help indicates that this setting is available.

  Enabling/Disabling an adapter in Windows 98 SE and Windows Me 
  requires restart
  -------------------------------------------------------------
  Due to a technical limitation in Microsoft Windows 98 SE and Windows 
  Me, if you enable or disable an adapter, you must restart the 
  computer to ensure stable operation.  

  Windows 98SE - Wake On Directed Packets
  ---------------------------------------
  When trying to enable Wake On Directed Packets on Windows 98SE
  systems, the system does not instruct the driver to wake on
  directed packets. Due to this operating system limitation, this
  feature will not work properly with Intel PROSet.


Intel PRO/10GbE Adapter Notes
=============================

Intel PRO/10GbE Adapter Known Issues
------------------------------------

  Intel PRO/10GbE Incorrectly reported link speed in Windows 2000
  ---------------------------------------------------------------
  In Windows 2000, the link speed of the adapter may be incorrectly
  reported as 1.4Gbps. Windows Server 2003 will indicate the correct 
  link speed. 

  Intel PRO/10GbE Small Packet Transmit Failure in Windows 2000
  -------------------------------------------------------------
  In Windows 2000, the adapter may fail to transmit small packets in some 
  situations.  Typically, this only occurs when attempting many small 
  packets simultaneously.  This issue has been fixed in Windows 2000 
  Service Pack 4.  Windows 2003 Server is not affected. 

  Run "netstat -e" from a command line to determine if this problem is 
  occurring.  If the "Send Errors" counter is steadily increasing, it is 
  likely an indication of this issue. 


Intel Quad Port Server Adapter Notes
====================================

The Intel(R) PRO/1000 MT Quad Port Server Adapter operates in 3.3 volt 
PCI-X slots only. For best performance, this adapter should be installed 
in a 64-bit PCI-X slot. Refer to the detailed installation instructions 
in the User's Guide for additional requirements.

The Intel(R) PRO/1000 GT Quad Port Server Adapter operates in 3.3 volt 
and 5.0 volt PCI-X slots. For best performance, this adapter should be 
installed in a 64-bit PCI-X slot. Refer to the detailed installation 
instructions in the User's Guide for additional requirements.

Hot Plug operations are not supported by Intel quad port server adapters.

Wake on LAN is not supported on the Intel PRO/1000 MT Quad Port Server 
Adapter. Trying to enable this feature with IBAUTIL.EXE will not have any 
effect. Wake on LAN is supported on port A of the Intel PRO/1000 GT Quad 
Port Server Adapter.

Intel quad port server adapters support Intel Boot Agent functionality on 
ports A and B, however it is disabled by default. To enable and use the 
Intel Boot Agent, refer to the User's Guide and other information in the 
\APPS\BOOTAGNT\ directory.

Intel Quad Port Server Adapter Known Issues
-------------------------------------------

  Multiple Intel quad port adapters in one system
  -----------------------------------------------
  Installing more than two Intel quad port server adapters in the same 
  system is not recommended. Many systems are unable to support the power 
  requirements for more than two of these adapters. 

  Use only in a PCI-X Slot
  ------------------------
  Reduced performance has been observed when the Intel PRO/1000 MT Quad 
  Port Server Adapter is installed in a slot other than a PCI-X slot.

  Shared Interrupt Limitation 
  ---------------------------
  In some systems, the BIOS and OS assign the same interrupt number to 
  two or more different ports on the Intel PRO/1000 MT Quad Port Server 
  Adapter. If this occurs, these ports do not function properly. To 
  address this issue, reassign the system resources so that each port 
  of the adapter has its own unique interrupt number or disable one of 
  the ports sharing the same interrupt number. 

  Downshifting
  ------------
  When connecting to any Gigabit switch via a faulty CAT 5 cable where 
  one pair is broken, the adapter does not downshift from 1 Gig to 
  100Mbps. For the adapter to downshift, it must identify two broken 
  pairs in the cable.
  
  Installing the Base Driver on systems running Windows XP 
  or Windows Server 2003
  --------------------------------------------------------
  After inserting the adapter in the system, you must install the base
  driver. This is true even if you previously installed base drivers
  for other Intel Ethernet adapters.

  Intel PRO/1000 MT Quad Port Server Adapter Not recommended 
  for use on some systems
  ----------------------------------------------------------
  The Intel PRO/1000 MT Quad Port Server Adapter does not function 
  correctly in the following systems:
 
  Dell* PowerEdge* 2500
  Dell PowerEdge 6400
  Dell PowerEdge 6450
  Dell PowerEdge 6650SC
  Intel Saber, Saber-R, and Saber-Rx Systems
  SuperMicro* 370DE6
  SuperMicro P4DP6
  IBM* eServer* xSeries* 365
 
  Using the Intel PRO/1000 MT Quad Port Server Adapter in these 
  configurations is not recommended.

  Heavy traffic may cause system reboot in some systems
  -----------------------------------------------------
  Using an Intel PRO/1000 MT Quad Port Server Adapter may cause a reboot 
  in systems with the Intel Profusion chipset including: Intel OCPRF100 
  and SRPM8 server systems; Compaq* ProLiant* 8000, 8500, ML750, DL760; 
  Dell PowerEdge 8450, 6300, 6350; IBM* x370.  Using the Intel PRO/1000 
  MT Quad Port Server Adapter in these configurations is not recommended.


Known Issues
============

  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. To install or upgrade drivers
  and utilities, follow the instructions in the User Guide.

  Installing Intel PROSet and Intel PROSet for Windows Device Manager on 
  the same system
  ----------------------------------------------------------------------
  Intel Prevents installing both Intel PROSet and Intel PROSet for Windows
  Device Manager on the same system. When you install Intel PROSet for
  Windows Device Manager, prior versions of PROSet are uninstalled automatically. 

  Novell* Netware* support for PCI Express devices
  ------------------------------------------------
  PCI Express devices are not supported in Novell Netware 5.x. Please contact 
  Novell to resolve any issues.


  "Malicious script detected" warning from Norton AntiVirus during 
  PROSet Uninstall
  ----------------------------------------------------------------
  The Intel PROSet uninstall process uses a Visual Basic script as part of 
  the process.  Norton AntiVirus and other virus scanning software may 
  mistakenly flag this as a malicious or dangerous script. Letting the script 
  run allows the uninstall process to complete normally.

  "Test switch configuration" in PROSet fails when using Cisco 6500 switch
  ------------------------------------------------------------------------
  If you are connecting a team with GVRP support to a Cisco 6500 switch, and 
  then run the "test switch configuration" selection in PROSet, the test 
  will fail.  This is because the Cisco 6500 switch does not support 
  dynamic VLAN de-registration.  

  "The Location You Specified Does Not Exist or Cannot Be Reached" Error 
  during driver installation
  ----------------------------------------------------------------------
  This is a known issue with Windows Server 2003.  Please see Microsoft
  Knowledge Base article 819586 for workarounds and a possible patch.
  <http://support.microsoft.com/default.aspx?scid=kb;en-us;819586>

  "Out Of Disk Space" Message during Installation
  -----------------------------------------------
  The boot partition requires a minimum of 15 MB free space in order to install 
  Intel PROSet, regardless of which drive you specify for installation.  If 
  there is insufficient space on the partition you will see this error 
  message, and the product will not install.  

  Windows Code 10 Error Message on Driver Install or Upgrade
  ----------------------------------------------------------
  If you encounter a Windows Code 10 error message when installing or 
  upgrading drivers, reboot to resolve the issue.

  Throughput reduction after Hot-Replace
  --------------------------------------
  If an Intel gigabit adapter is under extreme stress and is hot-swapped,
  throughput may significantly drop.  This may be due to the PCI property
  configuration by the Hot-Plug software.  If this occurs, throughput can
  be restored by restarting the system.

  System Wakes-Up from a Removed VLAN
  -----------------------------------
  If a system goes into standby mode, and a directed packet is sent to the 
  IP address of the removed VLAN, the system will wake-up.  This occurs 
  because a directed packet bypasses VLAN filtering. 

  No settings available on the Intel(R) Boot Agent tab in Windows Device 
  Manager after flashing an EFI image
  ----------------------------------------------------------------------
  The settings have been hidden because the EFI environment does not make 
  use of them.

  ASF link loss after shutdown
  ----------------------------
  On some systems with an Intel(R) PRO/1000 CT Network Connection, shutting 
  the system down results in loss of link and loss of ASF functionality. 
  Set Link Speed and Duplex to Auto Detect or 10Mbps (half or full duplex) 
  to resolve the issue.

  Intel PRO Adapters ignore consecutive Wake Up signals while
  transitioning into standby mode
  -----------------------------------------------------------
  While sending a system into standby, occasionally a wake up packet 
  arrives before the system completes the transition into standby mode.
  When this happens, the system ignores consecutive wake up signals
  and remains in standby mode until manually powered up using the
  mouse, keyboard, or power button.

  Netware 5.1 (and later) with PRO/1000 adapters
  ----------------------------------------------
  When manually installing drivers in a Netware 5.1 (and later) environment, 
  there may not be enough resources for all adapters during installation, 
  so the parameter of all PRO/1000 adapters' RX buffer should be equal to 
  or lower than 32 (in multiples of 8). 

  Link Difficulties With 82541 or 82547 Based Connections
  -------------------------------------------------------
  The PROSet Advanced tab now contains a setting allowing the 
  master/slave mode to be forced. This improves time-to-link with 
  some unmanaged switches. For older adapters and controllers, you 
  may encounter difficulty with 82541 or 82547 based connections.

  Using Intel PRO/1000 XT or T Adapters and e1000ODI.COM Driver
  -------------------------------------------------------------
  In some cases, an Intel PRO/1000 T or PRO/1000 XT adapter or 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 IBAUTIL.TXT 
  file for more information (\APPS\BOOTAGNT directory).  

  Intel PRO/1000 Adapters (copper only) do not detect active link 
  during load time
  ---------------------------------------------------------------
  Some Intel PRO/1000 adapters, especially copper adapters, cannot
  detect an active link during load time. To resolve this issue, try
  the following workarounds.
  - Re-attach to the server without reloading the driver.
  - For DOS-based installations, add a delay of 4 to 5 seconds in the 
    batch file after the load driver command.
  - Load the configuration by manually entering commands.
  - Set adapter to link at 1000 Mbps only. 


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

- Main Intel web support site: http://support.intel.com

- Network products information: http://www.intel.com/network

- Worldwide access: Intel has technical support centers worldwide.  Many of
  the centers are staffed by technicians who speak the local languages. For
  a list of all Intel support centers, the telephone numbers, and the times
  they are open, visit http://www.intel.com/support/9089.htm.

- Telephone support: US and Canada: 1-916-377-7000 
  (07:00 - 17:00 M-F Pacific Time) 


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

Copyright (C) 1998-2005, 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.
