> I'm not sure how to do this. The nic on the dell is on the back of the
> computer. The one on the laptop is visible and has 3 lights, but I don't
> know what they indicate.
>>I'm not sure how to do this. The nic on the dell is on the back of the
>>computer. The one on the laptop is visible and has 3 lights, but I
[quoted text clipped - 5 lines]
> The fd/col and 10/100 lights are steady green, the link/act blinks green
> rapidly (on the laptop).
That's as it should be. I'm curious what happens as a copy fails --
e.g. does the link light go off? At the same time the disk light comes
on? How long from when the lights stop flashing until the error is
signaled on the screen? etc.
I suspect your transfer is proceeding fine until the receive buffers
fill, then (as it's necessary to dump the data to disk on the receiving
end in order to proceed), the sending machine times out. Unfortunately,
there are MANY reasons that might happen, from faulty software/drivers
to misconfiguration. No chain is stronger than its weakest link.
I detect from your response that you might be using a crossover cable.
FWIW, I've found use of such cables (i.e. no switch/hub) to be more
troublesome than a "normal" connection. Switches can be had for under
10 bucks; that would be a cheap thing to try in order to eliminate one
possible source of difficulty. A store-and-forward switch will help
manage the protocol and perhaps get you past this problem.

Signature
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.
CJT - 21 Nov 2005 03:02 GMT
>>> I'm not sure how to do this. The nic on the dell is on the back of the
>>> computer. The one on the laptop is visible and has 3 lights, but I
[quoted text clipped - 24 lines]
> possible source of difficulty. A store-and-forward switch will help
> manage the protocol and perhaps get you past this problem.
Re-reading this, I realize I didn't notice before that you say the
"fd/col" light is steady green. You might want to read the
documentation for your laptop and see if that's normal. It might
be indicating near-constant collisions.

Signature
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.
*selah* - 21 Nov 2005 23:51 GMT
I tried mapping the network drive as F: and copying the files from dos
and they all copied with no problems.
Seems the problem is with windows somewhere.
CJT - 22 Nov 2005 02:28 GMT
> I tried mapping the network drive as F: and copying the files from dos
> and they all copied with no problems.
>
> Seems the problem is with windows somewhere.
Sure sounds like it. Is copying them that way an option? Or do you
still need to find a solution?

Signature
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.