Hello! I am an IT guy and have found issues with Windows 10 1803. If you are doing filesharing and 1803 is on the Server and Client, then on occasion I run into problems accessing the server by the \\ComputerName and the error is Network Path not found.
This isn't a problem with Network Discovery, as others have complained about with 1803, which I wish Microsoft would also fix that as well. Where the computer shows up in the list on the Network and you have to enable services manually to get it to show up. What I am talking about is just accessing the computer by the UNC path.
If the server is 1709, and the clients are 1803, I don't seem to have issues. But if the server is 1803, then intermittently there is a problem with Network Path not found error coming from workstations. Rebooting the workstation may or may not fix it.
Not sure what the issue is, but I hope Microsoft gets down to the bottom of these issues and makes this as reliable as a Windows 7 Network. I don't care about the removal of Home Groups because I never use Home Groups... but having reliable filesharing is important.
Are you guys at Microsoft planning on fixing this stuff?
I also disabled SMB2\3 and put on SMB1 with the power shell scripts and sc config commands and that worked.. but not reliably. Same error.. Network Path not found on occasion.