I have 2 machines in front of me (System A and System B) both running XP Pro. They are connected through a local area network. They both have shared folders with wide open permissions and can see each other.
I can copy txt, pdf, doc, jpg, psd, gif, html and most xls files from System A to System B (and vice versa) without issue (files transfer quickly and effortlessly).
However, when I try to copy across an mdb file from System A to System B, things grind to a halt. 1MB files which should fly across, state in the copy status box, that it will take a total of 9 minutes to complete the transfer. And then, of course, the transfer fails ungracefully. (No, the mdb files aren't in use, either).
It almost looks like something on System B is scanning the mdb to see if it's dangerous and then preventing it from coming across when it can't be sure it's safe. However, when I borrow a USB drive, I can copy the mdb onto the drive from System A and then from the USB drive to System B without issue. So it's not an obvious System B thing. (Although I can copy effortlessly from B to A, so it's something to do with System B). It doesn't seem to matter whether I'm pushing from A or pulling from B.
A quick Google search reveals these articles:
If any of you out there have any thoughts on this matter, I'd love to hear from you!
- Rename foo.mdb to foo.jpg before copying it doesn't work when copying with xcopy or Explorer.
- Copy foo.mdb via the command line instead of Explorer doesn't work. It just times out.
- pkzip foo.mdb allows me to copy the file over just fine.
- I can copy mdb files from A to C and back again without issue. However, I can't pull the mdb file from C to B.
- This applies to ALL mdb files I've tried. (And one XLS)
- I don't think that the file is corrupted or on a soft spot on the disk. I've copied the file on the original disk to another folder (the original file remaining where it was) which should counter for that. I the fact I can copy from System A to USB drive would mean it's not a System A disk issue. And that I can copy other types of files to System B would mean that it isn't System B's disk.
- System B is running Norton Firewall and Antivirus. Both shut off at the application level and the service level.
- According to Task Manager on B when you trying to copy from A to B, SYSTEM IDLE PROCESS sucks up over 95% of the CPU. And then leaves me with a "network connection lost" error. (Which doesn't occur when I'm moving other files).