Problem solve Get help with specific problems with your technologies, process and projects.

Whenever I copy a file from one computer to another, I get an error "Network Busy," and the source

Whenever I copy a file from one computer to another, I get an error "Network Busy," and the source computer hangs. I changed the network card, and the driver but it didn't help. Can you think of something else to try?
The elimination process you have followed is very similar to what I would have proposed as usually a faulty driver or network card is the cause of such errors.

Assuming that you have correctly installed the new network card and driver, but the problem hasn't been rectified, you need to check a few more things in order to accurately identify the source of your problem.

You mentioned that the source computer hangs right after the error is displayed. Even though this might seem like it's a problem with the source computer, it might possibly also be a problem with the destination computer.

Since you didn't tell us if you have made any changes on the destination computer, I'd suggest you take a look at it and see if you can update the driver for its network card. If you have a 3rd pc, you can try to transfer files from that pc onto the destination computer and see if the problem is repeated, this will give you a good idea if the destination computer is the source of the problem.

Firewall.cx logo

Do you have questions about networking, VPN security or VoIP? Then visit Firewall.cx, one of the few websites recommended by Cisco Systems in its world class Cisco Academy program.

On another note, your problem might have nothing to do with the network card or drivers on either the source or destination computer. A bad sector on one of the hard drives might be enough to cause a network error simply cause data cannot be read or written on either computers, so a scandisk and possibly disk defragmentation might prove to be a good idea.

As a last idea, you can try to run a packet sniffer on your network and 'see' what's happening during the file transfers and right before the error pop's up and the computers stop transferring files. A packet sniffer will show you which machine sent a "reset" command (TCP header, RST flag), and this can prove to be valuable information to help you determine the cause or source of the problem. If you're running Windows NT, 2K or XP, check your event viewer for any errors that might be reported.

Troubleshooting these type of errors without physical access to the machines is quite difficult, but I'm sure by following the above advice, you will at least be able to identify the source of your problem. From there, with some research on the Internet, you should be able to find the solution to your problem.

This was last published in September 2003

Dig Deeper on Network management and monitoring

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.