Disconnects mapped NAS, freezes

[gtandzi]

Hi, I have an ongoing problem with FFS getting half way through a synchronization and then stopping, with an error message:

ERROR_UNEXP_NET_ERR: An unexpected network error occurred. [CopyFileEx]

If I then go to Windows Explorer, I find that the mapped NAS that holds the destination folders is no longer accessible. And when I try to close FFS, it's locked, and I can only close it using Task Manager.

I'm running Windows 11 - the most recent update - on (not that this should matter) a very powerful computer.

[therube]

If I then go to Windows Explorer, I find that the mapped NAS that holds the destination folders is no longer accessible.

To me, that would then appears to be a network/NAS issue.

when I try to close FFS, it's locked, and I can only close it using Task Manager

Since FFS is throwing up an error message, you would think it would allow an abort (to the sync), returning control to FFS itself, allowing for an orderly close of the program. Why it might not be doing that... ?


If you were to attempt a similar type of copy, from source to NAS, but through Windows itself (instead of FFS), would that also fail mid-way?
(I would assume that to be the case, which would further reinforce the thought of a network/NAS issue.)

[xCSxXenon]

Agreed that it sounds like a network/NAS issue. FFS freezing when it disconnects is more likely to be because of how Windows reacts to network resources disconnecting. These hangs happen with File Explorer native transferring also

[gtandzi]

Any suggestions on how I track that down? It's the only example I've come across (so far) where I've had any problems accessing the NAS - I can easily transfer any of the files manually, and I regularly access the NAS via Windows Explorer