New
#21
Read here3, may be a possible fix for this. Accessing other computers on the network...Help!
Not a secure fix but for a home network it should be okay.
Can't access Windows shares after 1803 update
-
-
New #22
Yeah, I hate unresolved issues so went on hunting this one even after reverting 1803 to 1709 and also came across that. Kicking myself for not taking an image of 1803 while it was up as it means hours going through the upgrade process once again to check it out. I'll probably do it though. Thanks
-
New #23
Add that to this fix list for sharing: https://answers.microsoft.com/en-us/...7-1ef360e9ffdf
-
New #24
Sadly that reg key does not exist in Win 10 Pro 32 bit and creating it didn't work either. I've also been through all the settings from your link in #23 with no success though I feel pretty sure it is just a settings issue. I can't even access the system by IP. All of this worked faultlessly in 1709.
-
New #25
Hmmm, if you enter
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters"
from a command prompt, what do you see? Should be something like this:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
EnablePlainTextPassword REG_DWORD 0x0
EnableSecuritySignature REG_DWORD 0x1
RequireSecuritySignature REG_DWORD 0x0
ServiceDll REG_EXPAND_SZ %SystemRoot%\System32\wkssvc.dll
ServiceDllUnloadOnStop REG_DWORD 0x1
AllowInsecureGuestAuth REG_DWORD 0x0
-
New #26
I use Regedit, but it has the same result. The key is not there, neither with a lowercase nor uppercase I in Insecure. But I've had quite enough of this - I've imaged 1803 as it is and reverted once again to 1709, blocking the 1803 upgrade. Thanks for your efforts.
-
New #27
I have been reading this stuff for years and came to one conclusion : Everything posted is just a guess and no one really knows a how to fix this stuff, Microsoft included
I use flash sticks to move things around. Of course I try every few months hoping for a miracle.
-
New #28
I'll throw this in here, at least for my experience, the only computer that is inaccessible (and also the only computer that cannot access shares on other computers) is the computer on which the homegroup was setup on. My other 3 computers can see and access each others' shares, but the 4th computer, on which the Homegroup was originally setup, can neither access nor be accessed.
-
-
New #29
I've never used Homegroup and have this problem on multiple computers sometimes. It comes and goes and seems to depend on which computer is booted first.
-
New #30
I'd put next month's wages on the faulty removal of Homegroup as the cause here, but that apart I've not had problems with my network over the last few years, largely helped by always using fixed IPs IMO.
Quote
Related Discussions
