0x800704cf network error

I receive an 0x800704cf error when attempting to access my FreeNAS 9.3 server via the file explorer. A dialogue box pops up and provides me with a 'diagnose' button. A couple of seconds after I click on the 'diagnose' button, access to the NAS is available (the windows shares appear). Sometimes, I actually am able to have the file explorer display the shares (without receiving the 0x800704cf error), but when select (via file explorer) one of the shares, I get the error dialogue box. In the latter case, I click on the 'diagnose' button and then am able to access any of the shares from that point forward. I have no idea what the 'diagnose' button launches, but whatever it is, clears the network access error. I have no idea how to debug this - any help would be welcomed. BTW, I have another Windows 10 system on the network which is not experiencing these errors.

Hi and welcome!
Try this:
Press the Windows Key > type cmd to search for the Command Prompt.
2.Right-click Command Prompt > Click Run as administrator
3.In the Command Prompt window, type sfc /scannow > Press Enter to run the command.

And uncheck IPv6 - this may help.

SFC ran cleanly with no integrity issues. I did uncheck the IPv6 property under the Network tab for the NIC a couple of days ago, and that didn't help.

clk1946 said:

SFC ran cleanly with no integrity issues. I did uncheck the IPv6 property under the Network tab for the NIC a couple of days ago, and that didn't help.

Hmm....I found this: http://www.kapilarya.com/error-0x800...ant-be-reached

When I unchecked 'Client for Microsoft Networks', File Explorer did not see my NAS, and File and Print sharing and Network Discovery were turned off. I was able to ping the NAS and reach it via the browser to log in, but could not get to the Windows shares (CIFS). I then went back to NIC properties and checked 'Client for Microsoft Networks', checked Network discovery and File and Print sharing on. I re-booted the system and the File explorer was able to display the NAS and shares. I was then able to click on one of the shares and get a list of files in that share and was able to open one of the documents in that share. I will do some additional testing before marking this solved.

I'm back to encountering the same sequence of events when trying to access my FreeNAS 9.3 server. Sometimes I get lucky and am able to access the server and Windows (CIFS) shares without problem, but most of the time I have to go through a litany of 0x'C000023C' errors, which eventually get resolved by clicking on diagnose button, which seems to 'clear' up some sort of networking condition that initially gives me the "The network location could not be reached" result. Thankfully, eventually I am able to access the server and the shares. However, this is a pain in the butt. I currently have two Windows 10 based computers and one Windows 8.1 based computer on the LAN with the FreeNAS server. The two Windows 10 systems experience the same networking problems, but the Windows 8.1 system runs flawlessly and has no issues getting to the FreeNAS server and shares everytime.

BTW, I have looked at several of the ETL files generated as a result of going through the network diagnostics (diagnose button). Most of the log files are 'clean', however some have error events generated by the SMBclient: 'session setup error, eventid 401', and 'create VNET Root error: 0x'C000023C'. I'm not sure if these reported errors reflect the initial problems encountered. My only 'take away' is that the diagnostics seem to clear up whatever problem is encountered initially when trying to access the FreeNAS server.