How long should file transfers take?

Do you think running some cat6 would help a little? Just curious.

No, unless you change out everything to CAT 6. I have everything CAT 5e and all systems except for 1 wireless laptop on 802.11N mini USB which is on XP Pro SP3, the others are on 802.11N or G running Windows 7 HOP 32-bit or 64-bit. on Gig. I usually transfer 300MB to and from. This should take less than 2 seconds over Gig to Gig connection from two different systems over 200FT from each other and done remote into one box. Check your cables, switches, ports, NIC adapters. These tend to fail or you might have ports that are duff. Instead of 1000mbps you get 100mbps. Terminate ends might not be made correctly in your cables if you got them from third-party. Have you ever used Qcheck for TCP testing? A free tool.

Yes, I have used qcheck. What kinds of speeds do you get with it?
All my cables tested out good with the tester I used.

That varies. I have moved 150GB data files, and media last night from single core onto a new quad core system. Prior it was 7 hours. There was a problem with the onboard Gig NIC. That's fix now. Added some tweaks to netsh feature in 7 to offload the CPU to the NIC PU and some DMA tweaks. Now it only took less than 4 hours on Gig to Gig about a bit more 200 feet of CAT 5e cabling.

Does Vista have those tweaks?

Well yes.. start by doing this run as administrator cmd prompt.
Type: netsh int tcp show global

Now look at: TCP Chimney Offload (disable on Vista but set to Automatic on 7)
offload enables Windows to offload all TCP processing for a connection to a network adapter.

Type: netsh int tcp set global chimney=enabled (set for both Vista and 7)
Reduces networking-related CPU overhead, enabling better overall system performance by freeing up CPU time for other tasks

Under XP it was called Offload, pretty much the same. But you need to change these commands under CMD. (old dos prompt)

Under 7 there is a feature not found in Vista. Direct Cache Access (DCA) More used on systems with Gig to Gig transfers: netsh int tcp set global dca=enabled Don't use it on wireless nor Vista though as it's not supported.

Non DSL networks Domain and Cable the MTU should be 1500 to check to see if yours is set correctly.
Type: netsh interface ipv4 show subinterface

To change it to 1500
Example I call my Gig connection (Gig Access)
Type: netsh interface ipv4 set subinterface Gig Access mtu=1500 store=persistent

If you have dual or quad core you might want to add this feature:
Type netsh int tcp set global rss=enabled (by default is should be enabled)

Also one more..
Type: netsh int tcp set global congestionprovider=ctcp for Add-on congestion Control Provider

The above can be done on wireless networkings also. Just make you follow the above. Everything could be put into a script and lauched as the admin to produce the same results.

hi

5,,,,or longer

Now, I am a little confused. The first one says to disable TCP chimney offload, then you say to enable it. Which should I do?????

No by default in Vista it's disabled. So you would want to enable it. Thus offloading the CPU and place it NIC Adapter processor. Thus freeing up the lag. Windows 7 users should force to be enabled always.

Yeah, I was just writing to say I re read it and that's what I figured.

It's okay, I know I am too technical. LOL! There are a few more tweaks though. Most involve to edit the registry. I use to use pre-define *.reg files, they should work. I do a lot remote into systems so I need the best throughput.

As you said there are many variables, but shortly I can say 10 GB is considered as high mass through network. Hours maybe days, it takes!

The measurement of how these transfer rates varies between the given ratio of how the 10/100/1000mbps are handled. Real-time 6/60/600mbps as if you use PCI should be able to move 30mb/s and PCI-E should do 50+mb/s. Again factoring in your system HDD controller, HDD cache and spin speed to and from both systems. So 10GB (6000GB). Most home users are stuck at 100 or 1000.