Can't copy from client/server.

I know that this sounds crazy, but did you do a virus scan? Possible...

Ypu might try locking down both cards to 10-baseT full duplex. You described one computer nic, but not the other; sometimes auto-sence does not consistently work between various manufacturer's nics.

I have a WinBook LXi (PII 266MHz with a 3com589d-tp pcmcia nic -- it's only 10-baseT -- it's an older computer), but it communicates better -- without interruption -- when I lock down the other 3com nic that is 10/100 to 10-BaseT.

Try turning off any virus scan (this slows down a copy because the files are being scanned). And try setting the NICs to half duplex. I know the 3c905 is a 10/100 card is the other one?

It would probably come from your setting of mirrored drive.

You should have an identical set of hard disks to allow for mirroring to work properly. Otherwise one drive would be slower in writing the information than the other.

This would cause an inconsistency in the data, which in turn would force the OS to resync the data first, prior to allowing any network request (system is busy anyway since resync would seem to lock/slowing system down).

Would you try to release your mirror and try copying your data without mirror to see if mirroring is the cause ??

set network cards to 10 mb and half duplex to eliminate speed negotiation isues if set to auto negotiation. also check for rights issues on files being copied to or from machines with windows 2000 or nt also check to make sure binding orders on protocols are same or try just running the ipx/spx protocal as this is the most reliable for its simplicity to set up. I dont believe some of the other posters know what you meen by a software mirror but he means he is running raid 1 on the drives that he set up using disk administrator and not on a hardware raid controller wich will not cause a problem also make sure your page file on the logical disk c: is lager than the amount of memmory you are useing nad larger than the file size you are tryingto copy over but allow for at least double the space on destination hard drives than the size of the files you are copying. also are you drag and droping or mapping a drive and useing a copy or xcopy command in a dos box try mapping a drive if you have not already. this is a weard problem for the siplicity of the operation you are trying to perform

Point value changed by question poster.

Ron, another explanation.

It seems that it come from your NIC. Apparently you used 3com NIC on one computer with other NIC brands on the other computer.

3Com 3C905b didn't work very well with other brand, yet it does its job very well with another 3C905b.

What I would suggest, try another NIC and replace this 3C905b with this NIC.

I came over this problem, when I used 3C905b as a NIC in a server. When I issued a dir command to this server, it only display parts of the directory contents. Replacing the network card (with DLINK 538TX) solved the problem. Yet I know, that the 3C905b is good and doesn't have any problem.

Hope it would help you.

Be carefull when cross-cabling two computers that may have different speeds, although they should be able to negotiate the correct speed, the auto sensing feature, many times arrise rare and strange problems.

The main problem here (hub included) may be the difference between speeds. AS you send packets to the network using a 100 mbps nic, they are saved into the buffer's hub memory, in order to be divided into 10mbps packets for example. As long as you send packets, the buffers hub memory may collapse, resulting in a network down message.
In order to check this out, make the highest speed nic computer, the receiver, and the lower nic speed, the sender.
Another issue may be memory. When copying files, specially with explorer, the machine will try to load all possible files into memory, make a transaction log if the move option is selected, etc, etc. This may lead the computer to an out of memory stage, which may result in an "xx" error.
In this case, consider making the large copy file trought a DOS, not windowed, box.
The third, but more strange condition may be some corruption or file in use, either in the file storage side or in the HD target side.

Hope it Helps!!!

You changed the nic in the winbook? I didn't know you could do that. If I read incorrectly, see if maybe the nic in the winbook is bad.

- Jason

This question was closed by the author