The linked thread basically recommends updating Windows 10 to fix samba issues. Since this was a recent (clean) upgrade from Win8.1 I thought I was already up to date but did a check for updates anyway. There was an update, which I duly installed.
Which then broke everything worse!
My network was basically invisible, and even the "net use"/"net view" commands suggested above just returned error messages.
I eventually managed to sort this out by going to windows features and disabling samba and then re-enabling it (reboots required after each step).
I *think* the problem seems to be that Win10 doesn't like public/anonymous/guest access to shares. If you assign a log on and password I was able to get it to connect via the map network drive function in File Explorer. There wasn't/isn't a guest option.
This may have something to do with domains and homegroups (though I am not sure of the difference, exactly)? I set this notebook up using my Office 365 account rather than my Microsoft account. Apparently I have been assigned to a domain (the name of the notebook) and now can't set up a homegroup because I am a member of a domain? Not sure that makes sense though.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
Trusted
