Windows 10: Home network issue - one pc cannot be accessed from all others

Thanks you got me hooked up again.

 

Hey churin,
If you shares are still not showing up, you can run the following on each PC. We're just making sure that SMBv1 & SMBv2 Server/Client are enabled, their services are auto starting and the browser is auto starting.

Open PowerShell as Administrator
Set-SmbServerConfiguration -EnableSMB1Protocol $true
Set-SmbServerConfiguration -EnableSMB2Protocol $true
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb10 start= auto
sc.exe config mrxsmb20 start= auto
sc.exe config browser start= auto

Reboot PC

 

The third one returned "[SC] ChangeServiceConfig FAILED 1059"

 

Hey churin,
I've not seen that command, fail with that error before. Did you copy/paste or type them in ?

Note: Some people think that bowser is a typo and change it to browser which is wrong. It is bowser.
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi

 

I did copy/paste on the two PCs this time and one success and one failure.

 

You have to open/run PowerShell as Administrator. In your first screen shot, PowerShell is not running as Administrator.

 

I ran PowerShell as Administrator and it succeeded.
Still only a PC started first is getting shares listed under "Network"
I wonder what I did wrong?

 

Your probably didn't do anything wrong ... Windows is just being a PITA and I'm not sure why, right now.

Edit: You did restart PC after running the commands successfully ?

 

I figured you did *Smile

If you want, you can run the following on ALL Win10 PC's and you can compare their SMB settings. It makes NO changes and is for information purposes only. It creates a PCNAME-SMB-CHECK.txt on your desktop. It can be a bit hard to decipher, so if you need/want help with the output, then zip up all 3 txt files and attach them to your post.

Open/Run PowerShell as Administrator and copy/paste the following, making sure to hit enter after the last line.

$(
"$(get-date -format g)"
"$($env:computername)"
get-windowsoptionalfeature -online -featurename SMB1Protocol
get-smbserverconfiguration | select EnableSMB1Protocol, EnableSMB2Protocol
sc.exe query mrxsmb10
sc.exe qc mrxsmb10
sc.exe query mrxsmb20
sc.exe qc mrxsmb20
sc.exe query browser
sc.exe qc browser
Get-ItemPropertyValue -Path HKLM:SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters -Name SMB1,SMB2
Get-ItemPropertyValue -Path HKLM:SYSTEM\CurrentControlSet\Services\LanmanWorkstation -Name DependOnService
) > "$($env:userprofile)\Desktop\$($env:computername)-SMB-CHECK.txt"

 

Eagle51,

As far as networking is concerned, present situation with W10 v.1709 reminds me of Windows 95 days. Since Windows 2000, I have had hardly any home networking problem. I temporarily switched the OSes for all networked PCs to W8.1, and sure enough the good old day came back again: Network shares are listed on every PC on the network, which I have gotten used to.

Allow me to back track on this thread: What do the following do or is supposed to do? You do not have to get too deep into it, which may be beyond my ability to comprehend.

Set-SmbServerConfiguration -EnableSMB1Protocol $true
Set-SmbServerConfiguration -EnableSMB2Protocol $true
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb10 start= auto
sc.exe config mrxsmb20 start= auto
sc.exe config browser start= auto

 

Those commands enable SMBv1 and SMBv2 for both Server/Client and are taken from this link - https://support.microsoft.com/en-us/...in-windows-and

Note: They assume that SMBv1 is installed ... if it's not then it will throw errors.

 

That is a lot of reading for me. It appears MS started changes about SMB even with W7. As I stated previously on this thread that I do not see any problem if W8.1 is running on networked PCs. Could you summarize why the problem is if the OS is W10v.1709? Is it simply because SMBv1 is not installed by default on W10v1709? Isn't it that I installed it manually by following your suggestion?

 

If it's of any help, I've had ongoing problems with my network since the early days of Windows 10. It would appear that it's my own doing though. All PCs in the house are set to 'use user accounts and passwords to connect to other computers' in the Network and Sharing' centre. There are 10x Windows 10 machines all running 1709 build 16299.214, plus 1x Windows 7 SP2.

That's my personal network layout, but my point is that i had disabled two services based on the fact that i don't use the Homegroup feature. These are: HomeGroup Listener and HomeGroup Provider. Once i re-enabled these and restarted all the PCs i could once again access all shares from all W10 PCs. The only remaing issue was the W7 machine. For this one i had to enter user details in the Credentials Manager Control Panel applet. This MAY be required for any machine not using a common username and/or password.

 

I have never used HomeGroup either. What I am doing to not use the HomeGroup is to select at Advanced Sharing/HomeGroup connection, "Use user accounts and passwords to . . . " I never pay attention to the "two services" you mentioned. Or should I?

 

Yes, see this link for more info on Win10 1709 and SMBv1 - https://support.microsoft.com/en-us/...r-version-1709

Note: HomeGroups has been deprecated by MS and has already been removed in the Insider Preview starting with 17063. If you don't use HomeGroups you can disable those two services HomeGroup Listener and HomeGroup Provider. I have them disable and have no issues with networking sharing.