• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Improving Gigabit lan performance...

Insomniator

Diamond Member
Hey guys I have a Gigabit switch connected to my 10/100 wireless router. I have two machines on the switch and only average about 10MB/s when transferring files (large videos).

I read that traffic will not travel through the router so I am good there (assuming that is correct). Both machines read connected at 1 Gbps.

Are there anyways to get better? I think I was getting at least 20MB/s a while ago... I'd be happy with that again. Shorter/better cables?

This is 2 Win 7 x64 machines in a homegroup.

Thanks!
 
First thing I would do is check cables. If those all pass (via a tester or known good swap) I would begin looking at the switch.
 
What is your measuring device? (i.e. what tool is telling you the transfer rate?)



What kind of switch is it too, sometimes you can configure for something like jumbo frames or rate limiting.
 
What is your measuring device? (i.e. what tool is telling you the transfer rate?)



What kind of switch is it too, sometimes you can configure for something like jumbo frames or rate limiting.

I am just going by windows 7 transfer details. It is a cheap trendnet 5 port switch from newegg.. was like 15 bucks. I'm going to bring home two cat6 cables and a Netgear GS108 (should be a better switch) switch from work today and give em a try.
 
Is that one of the Green switches? I have their 8 port switch and I'm getting about 40 MB/s to/from my WHS2 box and my Win7 computers.
 
disable ipv6 on all machines. these switches can not handle it.

ipv6 is default on all vista/win7 machines and causes endless problems.

properties on the network/wireless card. uncheck ipv6. apply.

also make sure you are on the same subnet (duh) otherwise the router will be routing your packets.

also make sure you disable windows firewall service ( services.msc windows filewall - disable - stopped takes up more resources than disabled).

Make sure you do not use jumbo frames on a mixed environment

Update your lan drivers - intel/realtek especially - configure advanced and make sure you play with the interrupts setting. disable flow control (!!) you do not want this.

(duh) make sure the cables are good
(duh) use a spare pci-e (rosewill) gig-e card to make sure its just not a sucky nic. i've got a on-board nic that has a poor quality connector and generates alot of errors. i hate when folks yank cables.
 
^ What Emulex said. Also, turn "Interrupt Request" to disabled if you are using a Broadcom or Intel-based NIC. All Windows machines have it enabled by default. If you do not see it in your NIC driver details, make sure you are not using the built-in Windows driver. Get your manufacturer-specific driver and install it & reboot. Then you should see it. This made a huge increase in network file transfer speed on my corporate LAN at the expense of ~5-10% more CPU utilization during large file transfers. With today's multi-socket & multi-core machines, what's a bit more CPU utilization?
 
Wow guys I don't know exactly what did it but I changed all of the settings mentioned and now get 45MB a second!

thank you!

Edit- actually getting 60MB on some transfers... crazy. Gonna try and figure out which setting did it exactly..
 
Last edited:
Turning IPv6 back on made everything go back to snail speeds. I wonder how many computers still have that enabled for no reason...
 
all products based on the windows server 2008 (aka vista) and 2008 R2 (win7) have this default on.

The most obvious evidence is issues with dns or extremely long page load times.

Flow control should not be enabled either.

I believe the theory is if the routers and switches were all cisco/procurve and modern they would not have issues with ipv6. But that is not the world we live in.

The nasty part is the 2008+ systems boot dhcp and acquire ipv6 and ipv4 addresses so in a Active directory scenario you can create local dns entries just by powering up the system/vm; I always disconnect the ethernet then disable ipv6. Then i power up the operating system. This prevents the obvious: Devices believing there is hardware present on ipv6 by dns/arp once you disable ipv6.

Try to remember this someday it will be helpful until we are ready for ipv6
 
Back
Top