As has been
posted here recently, new Windows 10 updates have been interfering with connecting to the main computer in peer-to-peer setups. I egotistically started a new post to irk Bert.
The April 2018 update ("1803") is a large one, and has been rolling out gradually on my network. It finally bit me when the main computer updated this weekend.
The failure on my network was that AC didn't find the main computer database, or that during logon an error message appears "Storage Folders cannot be found" or "the version of AC on this computer is not the same as the main computer". When browsing your office network in File Explorer, the main computer with the AC databases does not appear, although it is possible to connect by using the intranet IP address (192.168.x.xxx).
What got me up & running initially was to use Amazing Utilities to reset paths, logon to AC & browse to the main computer by using the IP address.
However, since the update, several computers on my network still never appeared on the File Explorer Network window. I found this
Tech Republic article online describing several networking problems caused by the 1803 update. Problems discovering other networked computers are caused when the update resets Function Discovery services to start manually rather than automatic.
Go to Services (right-click Start, choose Run, then enter "Services.msc" to bring up the Services console) and see if these are set to "Manual" start:
Function Discovery Provider Host
Function Discovery Resource Publication
If these are set to manually start, right-click each, go to Properties and set the Startup type field to Automatic (delayed start). Then right click and start them both, then see if you can find other systems on the network.
Thanks to Microsoft for ruining my Memorial Day. It rained anyway.
.png "ACUF Donor I")