filecopy from xp to samba slow, copy to mounted share fast
 

I have an xp and a redhat box.

When I copy a file from the xp box to a samba share, it takes ages.

When I copy a file from my linux box to a mounted share on the xp box it goes super duper fast.

What does this mean? I have used the tool included in redhat, to make the samba shares user level security. This is all okay because I can connect, logon etc.

A friend said it was my UTP cable but I don't believe him, or is he right?

I fixed it ayeddy :)

It was the router that forced 100 full duplex on my cards. I put it on autonegotiate and al works fine now.

Thanks ;)

hi,
I'm having a similar problem, but the other way around:
XP to Linux is fast but Linux to XP is about 5k/s

Can you expalin what the duplex settings mean?

Duplex settings mean the speeds at wich your network cards communicate with one another. This is on a hardware level.

Some cards are 10mbit, some 10 mbit full duplex(wich actually means that it´s pumping data TO you as fast as it´s sending it FROM you - so full speed bidirectional traffic). Many cards just say they are 100mbit, and say nothing about the full duplex part.

So what you will have to do is check out your router settings and card settings, put everything on ´auto-negotiate´ and bob´s your uncle.

thx for the info, xtra.

My settings are on autonegotiate, so that's not the problem.

I was wondering: could it be the fact that on my Linux box, I have CAT5 e crossover cable that connects to the router but on my PC I have a CAT5 straight through cable that connects to the router.

Could that cause this kind of problem?

Well, yes!

The full duplex uses all 8 wires (as far as I know). Older connection types use the four in the middle. If the one pair of four is connected correct, and the other pair is missing one or two connections, it could quite well produce a problem like yours. I'm only not sure if the autonegotiate would not pick up on that...

The fact that your cable is crossover is quite funny... Normally you would not be able to connect anything. There are some routers that can sense the kind of cable and ignore the type, but I've only seen that on professional routers (ie, the really expensive ones).

Anyway, try a new cable (preferrably a straight one), it could solve the problem really quick, especially if all duplex settings are correct.

Hi xtra,

I did actually fix the problem the other day.
I was all out of ideas as to what it could be and I was trying random things in a vain hope of getting it working.
One thing I tried was to install a NIC on my Linux box instead of using the on board motherboard NIC.
Low and behold this cured the problem.
I can only assume that the on board motherboard NIC must have been faulty in some way.

Cheers
Ludwig