New
#31
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
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
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)