New
#1
That annoying 0x800704cf error...
This is something I see with every fresh installation of Windows 8 and later.
I have a file server, called FILES, which is a Windows 8.1 Pro machine with a bunch of shared folders. I use several Windows 10 Pro machines to connect to these shares over Ethernet or WiFi (Netgear R8000 router).
I use basic password-based authentication. I.e. all machines have the same set of user accounts with identical passwords. All machines belong to default WORKGROUP. Homegroups are disabled. Windows Firewall is disabled on all machines as well. The network is designated as private.
Now, once I log into my Windows 10 user account, I open File Explorer, hit 'Network' and see FILES listed as a machine on my network. This means that network discovery works fine.
I double click on FILES icon and see the full list of all available shares on FILES. So this part works fine as well.
But then, when I click on a specific share (say, 'Storage'), I get an error message
Trying to click on the same share (or other shares) produces the same error. But it happens only for about 20-40 seconds after the first click. After that, the next click suddenly successfully opens the share and everything works fine after that. All other shares on FILES also begin working perfectly.
However, if I leave FILES alone for a while and then return back to it, the same behavior happens again. First click of FILES shares generate 0x800704cf error, but after a short while everything starts working again.
What is the reason for this annoying error? I see it mentioned on the Net quite a few times, but no definitive answer.