In our environment, we have recently rolled out several Lenovo 7484-WWA model PCs.
We have noticed however that there are communication issues and customers noting issues with communications on the Lenovo boxes.
The Lenovos are running Windows XP SP3, and are using a Intel 82567LM-3 NIC and driver.
When we log into the model of switch that we use (an AT&T Netgate), we noticed that the Netgate is reporting differences in duplex settings versus what is set in the OS. All ports on the Netgate are at auto negotiate, and run at 10/100. For reference...Lenovo at 10Base-T Half = Netgate reports 10Base-T FullLenovo at 10Base-T Full = Netgate reports 10Base-T HalfLenovo at 100Base-T Half = Netgate reports 100Base-T HalfLenovo at 100Base-T Full - Netgate reports 100base-T HalfLenovo at Auto-Neg = Netgate reports 100Base-T Full We upgraded the NIC driver on the Lenovo to 8/8/2011 version located at this link - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18717&lang=eng&OSVersion=Windows%20XP... http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18717&lang=eng&OSVersion=Windows%20XP.... After upgrading the driver, we now see the following results: Lenovo at 10Base-T Half = Netgate reports 10Base-T HalfLenovo at 10Base-T Full = Netgate reports 10Base-T HalfLenovo at 100Base-T Half = Netgate reports 100Base-T HalfLenovo at 100Base-T Full - Netgate reports 100base-T HalfLenovo at Auto-Neg = Netgate reports 100Base-T Full We tried a different switch - a Motorola WS2000 - and could duplicate the issue, pointing directly to the NIC and it's Windows XP driver. We validated the health of both switches by cabling different equipment to them, such as an HP Desktop, an IBM PC, and an Apple MacBook Pro, and we do not experience the same duplex inconsistencies with those PCs. Has anyone else reported this, and if so, is there a fix available? We are currently in mid-rollout, and would like to have a fix in place for the pending devices that have yet to ship.
I got this from a colleague of mine.
"When one link partner is configured for "auto-Detect" that only means that the speed is autodetected. Duplex can not be autodetected. Our User documentation states that our device should have speed/duplex configured to be the same as the link partner. So either both link partners configured for "Auto-Detect", or both link partners forced to the same speed/duplex setting.
Please see the Intel® Gigabit Desktop Adapter Guide, Setup Speed and Duplex section on the Release 16.5 CD for more detail.
Let me know if this helps.