SOLVED Homegroups

[Tim Locke]

I have 3 PCs. Two are in the insider program and therefore use a Microsoft account to log in. The other one, my main machine uses a local account. I have been avoiding homegroups and decided to try one. Created it on the main machine got the password. Started up the Insider machines and could sign into the homegroup so that seemed OK.

I noticed that the display in file explorer showed two homegroups
My one as Joe and the other two machines as (e-mail address removed) the MS account. OK?

The MS account machines could see the shared folders but when I tried to access them on Joe insisted on a login to that machine....the MS account machines could share everything as the Homegroup is supposed to.
But then neither machine in Joe@email,com would allow any login to Joe or mapping a drive, insisted that the user name was wrong whether it was Joe or \\machinename\Joe.

So I went to the Joe machine and logged in as Joe@email , the MS account and it all worked.

I do not understand this behavior. I doubt it has anything to do with the use of an MS account. I think that it is a bug or a poorly done implementation of the Homegroup on W10.

Any thoughts out there?

 

[Saltgrass]

Before I check this, are all your W10 versions the same? Did you allow the same sharing options when you set up the second machine?

I will post back if I see anything but you might check the Credential Manager in the Control panel and see if anything shows the Local account as a Microsoft Account user and sets your Microsoft account login.

 

[Tim Locke]

No the versions are not the same. 2 11099 and 1 10586.63

When I set the main PC to be the MS account the homegroup all works. What I am saying is that the only thing that should matter is that I join the homegroup with the same password...i.e that it is the SAME homegroup.

As long as all the machines are the same login it all works.

 

[Saltgrass]

My understanding of a Homegroup would indicate it is for sharing computers between different users and not just ones which have the same user. What difference a Homegroup would see based of Microsoft Account user and Local account user I do not know.

My initial test was a little interesting. I created the Homegroup on my Local account system and then went to join it on the Microsoft Account system. The Microsoft system gave me the option to "Join" a Homegroup which meant it could see the Homegroup I had just created on the other system. After I joined on the Microsoft system, it indicated there were no other Homegroup systems available. If it couldn't see the other system, why did it not offer me the option to Create a Homegroup rather than to Join one?

I will be working with this to see if I can see what is happening but it may just be what we might consider a flaw with a Windows system.

 

[davehc]

It must be varying between computers - even more confusing.

But, I am wondering. First, did you have a password on the original?
If so, then, of course, you would have been asked to put this in when you joined from the second computer. You don't mention that?

I have never been in the situation, but, in my setup, between one MS account computer - the principal in the homegroup,. and three others on local accounts, I have not experienced any particular problems.

It could be that you need to turn off the option for a password?

 

[Tim Locke]

I tried both ways with a boot inbetween.