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

Well, this is crazy I just turned on HomeGroup Listener and HomeGroup Provider and Joy all 3 computers are seeing each other again. MS is is killing me trying to keep a P2P network up and running.

So just in the last 2 week, we had to install SMBv1 that got me working until I installed 8258 so yesterday and today I struggled again did everything in this thread on all computer and couldn't get one to see the other 2 no matter what I did. I even spent some time on my Router and insured my IP's were Static ran an updated firmware.
This evening I see this HomeGroup Listener and HomeGroup Provider, I go into services and started them set them to start automatically. i have never used home group just continued my P2P, Boom all three are seeing all three the 4th my wife's HP all in one on 8.1 has always been available on all computer?? when its turned on.

So I guess in a couple of days MS will screw something else for us.

 

That's interesting about the HomeGroup Listener and HomeGroup Provider, but hey whatever works ... as it sure seems MS does a good job of making simple file sharing ... not so simple *Sad

I think the main reason I don't have any network sharing issues is that I've always used my Routers (old netgear wndr4000) USB File Sharing. This makes my router the SMBv1 Server/Master Browser and only need the SMBv1 Client (along with SMBv2 Server/Client) running on my Win10 PC's. I also did the registry hack for the Browser > MaintainServerList = No, which keeps my Win10 PC's from trying to be the Master Browser ... When SMBv1 goes away for good, I'll have to buy a new router *Sad

Here are what my SMB Settings look like....

FeatureName : SMB1Protocol
State : Enabled
FeatureName : SMB1Protocol-Client
State : Enabled
FeatureName : SMB1Protocol-Server
State : Enabled
FeatureName : SMB1Protocol-Deprecation
State : Disabled

EnableSMB1Protocol : False
EnableSMB2Protocol : True

SERVICE_NAME: mrxsmb10
STATE : 4 RUNNING
START_TYPE : 2 AUTO_START
SERVICE_NAME: mrxsmb20
STATE : 4 RUNNING
START_TYPE : 2 AUTO_START
SERVICE_NAME: browser
STATE : 1 STOPPED
START_TYPE : 3 DEMAND_START
SMB1 : 0
SMB2 : 1
DependOnService : {bowser, mrxsmb20, nsi}

Here are a couple of share connections and their dialect ...
ServerName ShareName Dialect
---------- --------- -------
DESKTOP ShareFiles 3.1.1 <- SMBv3
SHARE ShareDrive 1.5 <- SMBv1 (Router USB File Share)

 

I know it's crazy but....that's the way it is. I could not get my networking to work on any W10 machine without those Homegroup services enabled! This was checked and rechecked multpile times buy enabling, then disabling, restarting inbetween etc. Microsoft sure seem to have made a mess of this feature.

There is a possibility of some sort of conflict with different router models i suppose?

 

Anything is possible, but I don't think so. I guess, an exception would be that your router has USB File Sharing or Media Server (DLNA) ... then it has some version of SMB and if enabled might could be an issue.

 

My experience is the same. my Router Asus U68 it does have USB support turn off and Through it all, I did notice
1. My wife's 8.1 Pro never lost connection to any of the computers she has an Account on.
2 All my media devices connected Smart TV DirecTV DVRs, BR player, Printers were showing up.

Its beginning to look like I'm going to have to set and a full server-client network, it seems MS does not want us to have a P2P network and they have dropped the HomeGroup Scheme. I fully refuse to use One Drive or any of that cloud crap. Each of my computers has a purpose and do not share software or desktops and do share and back up each other for some files.
At the same time, I can't keep spending hours every time WU screws up my Network.

Thanks for letting me jump into your all's thread I have been experiencing the same issue so I thought I could add something to it while getting my own system up and running again.

We certainly can't be the only ones experiencing this issue?