14.5 and 14.6 pop-up this error message for a directory - Z:\Bilder\Urlaube\Afrika\Madagaskar2022 - that does not exist on any of the 2 drives that it compares. See attached screenshot.
That does not make sense to me.
What's wrong there????
Unexpected Network Error for non-existent directory
- Posts: 27
- Joined: 10 Feb 2021
- Attachments
-
- FFS_strange_error_message.png (315.82 KiB) Viewed 126 times
- Posts: 323
- Joined: 13 Apr 2017
The two File explorer windows show the folders from the same drive F:
- Posts: 27
- Joined: 10 Feb 2021
Looks like I made a mistake here.
Anyway the problem seems to be that Windows Explorer doesn't immediately show all the directories on the NAS-share mounted as a drive. After some time - considerable time - the directly shown as missing in the error popup was shown in the Explorer, too.
Anyway the problem seems to be that Windows Explorer doesn't immediately show all the directories on the NAS-share mounted as a drive. After some time - considerable time - the directly shown as missing in the error popup was shown in the Explorer, too.
- Posts: 1221
- Joined: 8 May 2006
> Windows Explorer doesn't immediately show all the directories on the NAS-share mounted as a drive
Even though WE may not see it (the mapped drive letter - yet), are you able to type in the UNC path (into WE) & have it open it (immediately)?
(I hate [Windows] networking, & often when "Network" does not see a share, I can still plug in a UNC path & have that share come up.
Like right now, I can see NAS & SHERRY, but not NEIL.
But If I plugin \\NEIL\C, I can get right in.
And my last go-around with networking, & read, heh, something, that mentioned if certain setting was set [of which I've now forgotten] that it could cause extremely long Discovery times.
As it was I gave up on getting 10/11 machines to work & threw in a XP machine.)
Even though WE may not see it (the mapped drive letter - yet), are you able to type in the UNC path (into WE) & have it open it (immediately)?
(I hate [Windows] networking, & often when "Network" does not see a share, I can still plug in a UNC path & have that share come up.
Like right now, I can see NAS & SHERRY, but not NEIL.
But If I plugin \\NEIL\C, I can get right in.
And my last go-around with networking, & read, heh, something, that mentioned if certain setting was set [of which I've now forgotten] that it could cause extremely long Discovery times.
As it was I gave up on getting 10/11 machines to work & threw in a XP machine.)
- Posts: 4905
- Joined: 11 Jun 2019
I don't think therube's reply is relevant to this at all, since it refers to network discovery issues, which do exist very much. But OP's info shows a mapped Z: drive, so discovery or UNC access isn't going to play a part in this.
Sounds like FFS is waiting for access and doesn't receive it in time, reporting the error. File Explorer will wait, I think literally forever, for everything to show up. If data is taking that long to show up though, you have a critical problem on you NAS side that you need to address. Check the health of the drives. Also reboot and check for updates, but you'd likely have issues with all directories if these were the fix.
Sounds like FFS is waiting for access and doesn't receive it in time, reporting the error. File Explorer will wait, I think literally forever, for everything to show up. If data is taking that long to show up though, you have a critical problem on you NAS side that you need to address. Check the health of the drives. Also reboot and check for updates, but you'd likely have issues with all directories if these were the fix.
- Posts: 27
- Joined: 10 Feb 2021
I rebooted the NAS several time trying to find out what's going on (or, rather, not going on). And I don't think it is a general NAS issue as it's only a few directories that are so slow, from several in the same folder.
I rather believe it's a Windows issue, but I have no idea how to prove or disprove this belief, less so how to solve the problem.
Do you?
I rather believe it's a Windows issue, but I have no idea how to prove or disprove this belief, less so how to solve the problem.
Do you?
