Skip to main content

Home  Bio  Contact  Events  Expertise  Partners  Blog   


From: Lee Benjamin
Sent: Monday, August 05, 2013 4:50 PM
Subject: ESBUG TechTips: Tribal Knowledge and Exchange Servers


Once upon a time IPv6 was brand new and it didn’t work so well. Newsgroups, listservs, and even product support are known to have suggested turning it off. The same is true of the Scalable Networking Pack (SNP); network drivers on servers were not able to make use of the feature correctly, and many ended up turning the features off (Receive-Side Scaling, Chimney Offload, NetDMA).


With last year’s release of Exchange 2013, the latest updates for Exchange 2013, 2010, and 2007, and updated networking drivers for Windows Server 2012 and 2008, it is now more important than ever to let go of the “tribal knowledge” we’ve gained along the way, and turn these things back on!


I’ve had a number of customers with issues after installing SP3 for Exchange 2010. SP3 seems to install just fine on separate CAS servers, but then clients start reporting connectivity problems. Running EXBPA on the CAS servers may show problems connecting to, or seeing, other Exchange servers, or DC/GC’s. Re-enabling IPv6, rebooting, and then re-installing SP3 usually clears up the problem.


Other issues have been reported with the Scalable Network Pack, and I’ll give you the MS Exchange Team Blog on the subject to read. Note that it is important to update the vendor’s network drivers to make use of the SNP features. Too many times I see EXBPA reports that say the network interface driver is over three years old. It seems that is one most of us just don’t want to touch. We should.





Lee Benjamin MVP

President: ExchangeGuy Consulting



Chairman, Exchange User Group...                              

Exchange Liaison, Windows Server Group...                

Advisory Board, VirtG Virtualization Group...              

Vice President, BUG (Many User Groups)...                  

Global Board Secretary, GITCA (Int'l IT Pro Groups)...