New
#41
Unbelievable it took a hosts file edit to fix this. I am glad your issue is fixed. Thanks for marking the thread solved.
side note: Way to go MS with 1803 and home networking.
EDIT: Your very welcome Beerlord. :)
Unbelievable it took a hosts file edit to fix this. I am glad your issue is fixed. Thanks for marking the thread solved.
side note: Way to go MS with 1803 and home networking.
EDIT: Your very welcome Beerlord. :)
The PC name in the hosts file must match exactly what the computer name is on the PC itself. Also I would check the posts earlier in this thread to make sure all services, shares and permissions are set correctly.
Also I would edit the pic you posted with the MAC addresses on them.
EDIT: you won't need to put the MAC address in the hosts file. It reads the IP and name
This is easy to verify by replacing the other machine's name with its IP address. Typically with IP instead of name everything begins to work perfectly, indicating that this is not a permissions issue, but rather some sort of name resolution issue.
This name resolution issue is specific to LAN share access only, since Remote Desktop and "ping" command to other LAN machines typically continue to work "by name" without any problems at all.
This 1803 bug is very similar to the one we had in the first version of Windows 10. In fact, this has been an ongoing issue with various versions of Windows for quite a while. How come they can't get it to work for all this time is beyond me.
I remember that adding manual mappings to HOSTS file kinda helped in previous cases as well. But at the same time I remember that it was only a temporary fix. After a few reboots the network would begin to run into the same error again even when HOSTS file entries were present and IPs were static.
Last edited by AndreyT; 12 May 2018 at 14:31.
Uh Oh! This morning I'm back to where I was where access is denied again. Seems the hosts files had the # in front of the IP addresses on both computers even though they were saved. Fix it and I'm back but why does it keep changing?
Dang Microsoft! <pulls hair out but already nearly bald>
I had to reboot yesterday because I could not see either PC on here when opening the network in File Explorer. Worked fine after a reboot. I bet the same happened to yours. This has happened twice to me since I found the fix with the services.
And if your router gave them a new IP after sleep that would affect it as well. (hosts file edit you did)
Yes I agree. I did not do that for my network. It was suggested by another user and he tried it. I have another suggestion he try. That is to open Computer Management, expand the Shares on the left. Then right click the share that is failing, click stop sharing. After that, right click in the space there and click on New Share. Follow through the wizard sharing the folder he wants and pay attention when it asks about permissions. Click on customize permissions and then make sure all permissions and security are set correctly from within the wizard. Once done click Finish. See if it works then.