Full Version: weird file copying problem

From: milko [#1]
 14 Mar 21:01
To: ALL

My (win 7, 64bit) computer has odd problems copying files across the network or also to USB storage. Multiple devices tried so this seems to be at the computer end of things. If I'm copying a bunch of folders, it often fails on the first file in each, but will happily do the rest of the files. Later, when I copy the one leftover file again, it'll be fine. It says:
quote: windows

There is a problem accessing [destination drive]\[folder]\[subfolder]\[filename]

Make sure you are connected to the network and try again.

I am connected. Trying again does not work, though as I say if I go back later and do it again it'll be fine. It's always the first file in a folder. It's not always the same filetype or anything like that. SOME just-about-identical folders copy completely.

It's kind of fucking me off. My external drive died recently so I'm re-backing up a lot of stuff and this makes it need more input than it should as it interrupts and freezes the job each time. Grarggh.

Incidentally, the Netgear ReadyNAS is well smart. I now have a spare NSLU2 unit if anyone's interested.

Reply



From: ANT_THOMAS [#2]
 14 Mar 21:03
To: milko [#1] 14 Mar 21:19

Does it still do this if you copy using the command prompt?

Reply


From: milko [#3]
 14 Mar 21:19
To: ANT_THOMAS [#2] 14 Mar 21:31

I don't know. Gosh that sounds a bit fancy though. I'll try that next. If it doesn't, what does that mean? If it does, what does that mean?

Reply


From: ANT_THOMAS [#4]
 14 Mar 21:33
To: milko [#3] 14 Mar 21:39

No idea what it means to be honest, I just like suggesting these things to give other people ideas in case something odd happens :$

I usually prefer to do large amounts of copying using the command prompt with the xcopy command. I guess I've had too many "Not Responding" fuck ups when doing big copying jobs using Windows Explorer.

Reply


From: Matt [#5]
 14 Mar 21:57
To: ANT_THOMAS [#4] 14 Mar 21:59

quote:
I usually prefer to do large amounts of copying using the command prompt with the xcopy command


Ditto, except I use robocopy.

Milko: Is it the source file that it can't access or the destination file? I'm thinking anti-virus or some other anti-malware program that is locking the file and preventing Windows from reading or writing to it.

Reply


From: milko [#6]
 14 Mar 22:04
To: Matt [#5] 14 Mar 22:32

it's the destination, where of course the file doesn't yet exist. Only AV I have is MSE, if that's of any influence.

Reply


From: Matt [#7]
 14 Mar 22:35
To: milko [#6] 14 Mar 23:57

Have you tried turning off the real-time file protection and see if it still happens?

Reply


From: milko [#8]
 14 Mar 23:58
To: Matt [#7] 15 Mar 9:50

I got scared by the command line and installed Teracopy, which right now appears to be hitting the same trouble. I shall try MSE zapping!

Reply


From: milko [#9]
 15 Mar 9:48
To: Matt [#7] 15 Mar 9:50

Right, you win the prize, again. Disabling it seems to cure the problem. Any idea if there's a way to make it not have this trouble? Or a recommendation of AV to use instead?

Reply


From: Matt [#10]
 15 Mar 9:55
To: milko [#9] 15 Mar 11:00

Checked for an upgrade for it? Microsoft don't always update the main program automatically, just the definitions.

You might try submitting a support case or posting on the community forums, too: http://www.microsoft.com/security_essentials/support.aspx?mkt=en-us&s=3#mainNav

I still use NOD32, have done for last 3 or 4 years, but it's not free. MSE is easily the best you'll get for free, even if it does have weird problems with copying files to USB devices.

Reply


From: Radio [#11]
 15 Mar 10:17
To: Matt [#10] 15 Mar 10:30

I use Avast, which is still free.
I'm sure there's probably a reason I shouldn't, but I've had no problems with it - and its certainly not the memory hungry beast that AVG was.

Reply


From: Matt [#12]
 15 Mar 10:40
To: Radio [#11] 15 Mar 10:56

I used to install Avast on all the machines I supported, but I don't like what they've done to it recently.

The default interface looks like a car CD player and it absolutely kills older machines / those with limited memory. Admittedly the interface can be changed, albeit to the wrongly named "Simple User Interface" which if anything is more in-depth and complicated, and far from simple.

Started to switch to MSE which is much lighter on it's feet and gave new life to a neighbours AMD 3200+ which only has 512MB RAM.

Reply


From: milko [#13]
 15 Mar 11:03
To: Matt [#10] 15 Mar 11:04

It recently had itself a proper upgrade but I'm sure this was happening before that too. I'll go start a support case I guess.

Reply


From: milko [#14]
 15 Mar 22:45
To: ALL

hmm. Still getting problems. "The specified network name is no longer available" it says, whilst not doing anything more. It fucking is! I'm navigating around it right now wondering why my files aren't there!

Fucking computers and fucking especially fucking networks :C

Reply


From: Matt [#15]
 15 Mar 23:39
To: milko [#14] 15 Mar 23:44

http://home.bott.ca/webserver/?p=260 maybe?

Reply


From: milko [#16]
 16 Mar 0:18
To: Matt [#15] 16 Mar 9:06

heey. the update there seemed to fix that. Well done Matt! I guess next I try it with MSE enabled to see if it was involved in that somehow.

Reply


From: milko [#17]
 16 Mar 0:23
To: milko [#16] 16 Mar 0:23

no, that's still broke it looks like. Ho hum. Actually I think more tests needed for both things, possibly.

Reply


From: Kriv [#18]
 18 Mar 1:15
To: milko [#17] 18 Mar 11:00

Got the Readynas NV+ which is excellent.

I think the services on the device is pretty standard so the following may help as it's what I needed to do.

1. Autotune on Vista & Win 7. Had to disable this as it was causing a whole world of pain.

2. Services, found that there were a few turn on which were not necessary which caused issue. Leave on CIFS and NFS and turn off as many of the others as you can. This had a massive impact stopping the crippled copying. I think you have a Mac...? If so I don't know what will happen if you disable AFP.

3. Router. I found that my router was crippling transfer speeds, probably worth googling your router / ready nas combo to see if firmware is a cause.

4. Jumbo frames, If your router or NIC doesn't support it, disable. Causes loads of failed packets.

5. (not really pertanant to your issue) RAM. I think you can upgrade the RAM in the device. If you can get it stable then this is your next move. Get around a 10% - 15% performance increase.

6. If all else fails http://www.readynas.com/forum/ yoh-dah is pretty good at covering issues, but there is a great user base on there that can help.

Reply


From: milko [#19]
 18 Mar 11:01
To: Kriv [#18] 19 Mar 10:48

what's Autotune?

I have a Mac but only at work so I guess I don't need AFP enabled usually.

Reply


From: Kriv [#20]
 19 Mar 10:49
To: milko [#19] 19 Mar 11:26

http://www.kombitz.com/2007/02/14/vista-auto-tuning/

Reply


Show messages: All  1-20

Reply to All

Back to thread list | Login

© 2010 Project Beehive Forum