Windows 10 1803 Server and Clients, problems with SMB. Network Path not found.

Give this a try, It should help you.

Photos and an actual real setup.

https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/connecting-pcs-and-users-for-sharing/fb92e439-5dbc-4367-9857-1ef360e9ffdf

Tried this already... Not reliable. Network path not found intermittently. 

EDIT: And we shouldn't be having to do stuff like that anyways... When you think about it. ;)

I would like to say, that with 1803 and Windows 7 clients no issues at all.

SMB2 seems to be working. Too bad we can't disable SMB3 without disabling SMB2 as well. There doesn't seem to be a way.

Because MS made changes to Win v1803 that caused issues for PC's to resolve link between IP and Hostname in peer-to-peer networks.

I have solve this issue by using hosts -table (step 6.2 on my example), to create link between IP and Hostname. (Not very handy on large networks.)

It's old historic way back from 60's in ARPANET, the predecessor of internet, long time before DNS was invented.

https://answers.microsoft.com/en-us/windows/forum/windows_10-files/homegroup-removed-how-to-get-network-sharing-work/01277332-2916-4a68-853a-116696b20743

"Are you guys at Microsoft planning on fixing this stuff?"

To get your concern to MS dev engineers you have to use Feedback Hub.

uh, yes it does work every time. I have did about 300 PC's since v1803 on numerous Home and Business networks.

Instead of using  \\Computer Name

you have to create shortcuts to them using

 \\Computer IP ADDRESS

Then you connect to each PC using the IP ADDRESS shortcut, not through network folder.

Then if you have the connection issue between PC's and having to connect by

 \\Computer IP ADDRESS

you will need to go into each PCs C:\ drive>>properties>>security>>advanced

and add network user in the list with full permissions.

then when you select to share anything, EVERYONE user is there by default. then you add NETWORK in the list, set the permissions for both the same.

It is all explained in my article midway down with photos.

Resolving the computer by IP is... just... this whole thing is broken. I suppose I can do try that at an office. But... even if it does work, we need to be letting MS know that this is not.. satisfactory.. not at all.

Windows 2000 6 Month MCSE course... is my background...  

This 1803.. ain't right... Having to enable services for automatic just to get the computer name to show up in the network list.. isn't good.