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: which prove that I'm not alone, but other than that, don't really help. I tried to e-mail the poster (Karl Irvin) but alas, his e-mail address is no longer valid. (Mr. Irvin, if you're out there... did you ever get this issue resolved?)
If any of you out there have any thoughts on this matter, I'd love to hear from you!
----------------------------
Additional info:
- 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).
5 comments:
I don't know from .mdb files or the Norton suite. Could the files you're having trouble with be sparsely allocated? Sometimes when you're reading such a file over the network, you end up fetching blocks and blocks of zeroes which aren't actually stored in the original source file. That could lead to the "can't copy" messages cited by Mr. Irvin, and maybe it'd give you the symptoms you've seen.
'Course, it looks like this issue has probably gone dormant for you by now.
Welcome, Tuxedo and thanks for spelunking in the archives! The issue is still active and I'm swapping e-mails back and forth with some tech support folks at pcdatasheet.com.
Hrm.... hadn't considered the sparsely allocated file scenario. I have, however, been able to copy said files across the network to System C (and to a USB drive) so I'm guessing I could rule that out...
Any additional thoughts you may have would be greatly appreciated!
Having exactly the same problem. Discovered that the copy even is OK when I use a cross cable instead of a switch. Other types of files are no problem (entire service packs, no problem). No solution yet.
Hi Miche,
I read your post and I have the same problem on my company network.
Did you solve the problem at least?
Thank you in advice,
Luca Giornetti
Lucia,
Sadly, still no solution. Current work around involves USB drives and sneakerNet. (Walking the USB drive from one location to the other.)
Post a Comment