http://blogs.isaserver.org/shinder/2006/10/15/beware-nic-and-switch-autonegotiation/ Written by Dr Thomas W Shinder, consultant to Microsoft, HP and many Fortune 500 companies on ISA firewall and Web proxy deployments this blog is where administrators get information about ISA Server Universal Threat Management firewalls. Topics include how to manage, deploy, and troubleshoot ISA Server as a network firewall, Web proxy/Web cache, remote access VPN server and VPN gateway to provide a high level of network security for all corporate computers. Fri, 5 Sep 2008 22:42:50 +0000 http://wordpress.org/?v=MU http://blogs.isaserver.org/shinder/2006/10/15/beware-nic-and-switch-autonegotiation/#comment-14876 Wed, 18 Oct 2006 12:58:51 +0000 http://blogs.isaserver.org/shinder/2006/10/15/beware-nic-and-switch-autonegotiation/#comment-14876 [...] I just thought I would share this with you guys, I know there was some confusion on this a while back and Tom just posted on his blog regarding “Beware NIC and Switch Autonegotiation” . Most network engineers are under the impression that you should always force or manually configure links for the designated speed/duplex. Unfortunately with the advent of 1000B-TX that is no longer an option. Although Cisco in their infinite wisdom decided to still make it an option in the IOS, it still does the autoneg because it has to. At least according to the IEEE standard. Below is some decent documentation that I found on a Sun site believe it or not. Let me know if you still have questions. [...] […] I just thought I would share this with you guys, I know there was some confusion on this a while back and Tom just posted on his blog regarding “Beware NIC and Switch Autonegotiation” . Most network engineers are under the impression that you should always force or manually configure links for the designated speed/duplex. Unfortunately with the advent of 1000B-TX that is no longer an option. Although Cisco in their infinite wisdom decided to still make it an option in the IOS, it still does the autoneg because it has to. At least according to the IEEE standard. Below is some decent documentation that I found on a Sun site believe it or not. Let me know if you still have questions. […]

]]>