Seemingly minor and easily overlooked settings can still have profound security implications.
One final note: on the SP3, I had to enable SMB 1 following 1803. .As soon as one of the machines - either the one accessing the files or the one sharing them - uses a Microsoft account, it is no longer possible to access any files or folders on the other machines.Pauli, I don't mean to shout, but I'M SO happy! .In Windows 7 and Vista, I just.For troubleshooting purposes, I pulled all but 2 PCs, 1 Surface Pro 3, and a NAS from the LAN after the initial 1803 debacle after following.
I have a home network, with Windows.1 and Windows 10 machines, all in the same Workgroup.
Pauli, your steps through 5a worked really well for me - that's what made all the computers show up in File Explorer, Network, Computer. .
The problem seems to be the same in Windows 8 and in Windows.
Access to the SP3 is golden now - I've tested restarted tested restarted until I'm blue in the face, and it is all good! .
The most daunting part of upgrading to Windows Vista may be trying to figure out where in the layers of menus the networking and file-sharing options are hidden.
Andre's second response here didn't fix things, so now I just have to power the rest up edit the hosts table on those fix the sharing as you describe.I'm not sure why 1803 broke that (I recall having to do this on the PCs with the Fall Creator Update but it was working fine on the SP3 without SMB 1 being enabled until 1803.Changing the Microsoft account to a local account immediately fixes the problem, with no other configuration changes.Also, I'm going to try setting the Functional Discovery Services to automatic rather than automatic (delayed) as you suggest because on the SP3, I'm seeing the delay you mentioned - on the SP3, the SP3 is the last thing to appear in File Explorer, Network.When the PCs would access it (sometimes they could do so successfully but mostly not they only thing they could "see" was SP3UsersxxxoneDrive (which we don't use) nothing else. .Your steps helped me get that sorted.The final success was editing the host - table! .I almost have a fully functional LAN again with everything seeing having access to all again. .Don't use Microsoft accounts).Successfully implemented workarounds (not solutions Store the usernames/passwords to the other machines in the Credential Manager and give up the idea of sharing without password.Specifically, if the machine with the Microsoft account tries to access the machine with the local account, it will prompt for a username and password, and access will fail unless username and password of an actual user on the target machine are provided.Best use a common account for access.If I had to guess, my guess would be that the PCs laptops had originally been networked through Workgroup those shares were preserved in the bowels of Windows somehow.I want to be able to share individual folders on the network, by setting them to shared through File Explorer.