Rebooted my PCs a couple of times, looks like this is issue is permanently fixed for me. Interesting reading, @Barman58. I'm worried about WannaCry ransomware, but I also need to access files among my three PCs (two laptops and one PC) often. I never use a third-party solution when there's a native one on Windows that works properly, and because I'm very lazy as well, so I don't have much of a choice unless turning SMBv1 protocol, even with its security flaws.
You could try without the SMBv1 enabled if you are only looking at windows devices (No TVs or media centres or NAS drives) as windows should then use SMBv2 or SMBv3 which are not susceptible to Wannacry.
Make sure that Function Discovery Provider Host & Function Discovery Resource Publication as set to Automatic (Delayed Start) and you should be good to go
To be honest, if all your systems are Windows 10 and you update your systems as prompted by windows you are safe for the Wannacry vulnerability and adding any of the better known Security Suites, even free versions should add that extra bit of confidence when surfing the web
This is so damn frustrating. I've gone through security settings, network settings, etc. All settings are the same as my computers that are working. The only thing I haven't done is looked at the registry. Guess that's next.
Well, I found it. I was using my laptop to transfer files from my desktop to my server while I worked.
There were some minor differences in the registry since I have different programs on each machine and my laptop is W10 Home and my desktop is W10 Pro. But, the fix was...
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInse cureGuestAuth -> change 0 to 1.
Thanks to everyone for the help/suggestions.
The purpose of that key gives a clue to the actual fault causing the issue - The permissions are not set correctly to give a secure connection between devices so they would normally be rejected "Silently" and thus the network would appear, not to work. (Silent rejection gives no indication of the rejection so the potential attack has no data to work with)
Checking the actual sharing and NTFS permissions should indicate some slight error, but as long as you are happy there should not be major consequences of not fully securing access on a home system
Microsoft's detail on he Key is here ...
AllowInsecureGuestAuth | Microsoft Docs
As you mentioned, with it being on a home network, I'm not too concerned about it. Interestingly enough, none of my other Windows 10 machines (Home or Pro) even have it.The purpose of that key gives a clue to the actual fault causing the issue - The permissions are not set correctly to give a secure connection between devices so they would normally be rejected "Silently" and thus the network would appear, not to work. (Silent rejection gives no indication of the rejection so the potential attack has no data to work with
Checking the actual sharing and NTFS permissions should indicate some slight error, but as long as you are happy there should not be major consequences of not fully securing access on a home system
Microsoft's detail on he Key is here ...
AllowInsecureGuestAuth | Microsoft Docs
I'm going to try this at the shop MOnday. I have been fighting this problem for months now and if this fixes it I'll be overjoyed! Thank you.
Hijacking this thread again, I'm just posting to say that network browsing still works on all PCs after disabling SMBv1, thank you once more. As you said, I lost access to my TV on my network, but as I never access any media from it, i don't care. So, with SMBv1 disabled,Windows always updated and Windows Defender enabled, I believe all my machines are protected against WannaCry, right? Looks like those two services are essential, thus I wonder if re-enabling TCP/IPv6 will break things, but I believe it won't.
Quote
