help- network slow 1 way only

yyz

Junior Member
Nov 15, 1999
12
0
0
I have a tcp/ip network between my desktop and laptop. Transferring a 5mb file from desktop to laptop takes 10 seconds while transferring the identical file from laptop to desktop takes over 2 min. Why?

I pinged both and the results are identical: 0% lost packets w/ avg = 2ms. Where's the bottleneck?:frown:
 

emjem

Golden Member
Apr 7, 2000
1,516
0
0
Are these files one and the same file, or two files of the same size?

As you know, two different files of 5 meg each can each use different amounts of hdd space, and thus processing time.

There could be some caching and bus speed issues, but it seems to me that your most viable fix is to defrag both hdds. Not to say that won't equalize things, but I've never seen THAT kind of improvement from defragging.
 

GoldServe

Member
Oct 10, 1999
49
0
0
I dunno wut to tell you! ehe...i know if you ahve win2k and any other operating system it is slower to drag a feil from win2k 's exporer into the other os's drive and faster if you do it vice versa....hrm...maybe the pair of wires on for your cable that is responsible for send is slightly damaged...alot of cross talk or something...dat's the only other reason i can think so,...try swapping a cable first..good luck!
 

yyz

Junior Member
Nov 15, 1999
12
0
0
thanks all. the files are identical so there shouldn't be a difference. i did defrag the drives and there was a definite improvement but there is still a large difference. The laptops hard drive definitely seems to be the bottleneck tho. It seems to pause for several seconds before resuming the upload.
 

emjem

Golden Member
Apr 7, 2000
1,516
0
0
It sounds like your notebook hdd is FASTER than your desktop hdd.

Since a typical hdd can read data 20+% faster than it can write data, the writing is always the bottleneck in moving data. In your example, the data is being written faster on the notebook hdd (re 10 seconds) than on the desktop hdd (re 2 minutes). More evidence, the notebook is pausing while waiting for something to happen -- probably the desktop hdd to write the data.

I don't know how caching impacts data movement times, so I guess there is still that as a potential cause. But with this huge time difference I'm thinking hdd differences are key.