drsauced wrote:Jumbo frames won't help if the switches don't support it. That would pretty rare this day and age, however. Jumbo frames allows for larger packets so there's less overhead in the protocol stack, which means more faster speed captain!
Flatland_Spider wrote:@bigjohn888jb: How did you team the NICs? If the teaming requires LACP and the switch doesn't support it then that could be the problem.
Usually, but not always in my experience. I've had situations where enabling checksum offloading and/or defragmentation to the NIC destroyed performance. Disabling it defintely loaded up the CPU, but performance increased dramatically overall with fewer unexplained glitches/stalls. (In that case, I trashed the NIC.)Flatland_Spider wrote:but other stuff is questionable.
curtisb wrote:As for maxing out a GigE link, a GigE Windows 7 or Windows 8 client going to a GigE Server 2008 R2/2012/2012 R2 server can most definitely max out a single GigE link if transferring large files.
Usacomp2k3 wrote:Unless you are maxing out the gigE, I'm betting you don't need the additional headroom.
homerdog wrote:Seconded. A single GigE link should suffice.
If you do want LACP, we've been using D-Link Web Smart switches with great success for the last few years. They support all the niceties that you would expect from a much more expensive HP or Cisco model, and I don't recall ever having one fail. Also quite easy to manage. Did I mention cheap?
We sell loads of these:
http://www.neweggbusiness.com/Product/P ... 06160741:s
Buub wrote:First question: how do you know this is a network problem, and not something else like a DNS resolution issue, an active directory problem, or something else?
homerdog wrote:If you do suspect wanky DNS you could set the server as primary DNS and try (if it isn't already).
Users browsing this forum: No registered users and 1 guest