New
#11
With password sharing off I still get prompts for credentials. Interesting to know what is different in our setups but that we will never find out!
With password sharing off I still get prompts for credentials. Interesting to know what is different in our setups but that we will never find out!
Hi there
@Kari
I'm afraid for once you *could* be in error
When accessing on a Lan to a computer with an Ms account - at least in my case the user name doesn't include the email part that you see on the original Windows logon screen when the computer is started.
The easiest way to find the actual user name you should use is to browse the Users folder and look for a name other than public or all users. This is the name you should use.
The password of course is the password of the Ms account.
You might or might not need to prefix your computer with computername e.g \computername\user
From my Centos system to connect to an Ms account computer I don't actually need to prefix the computer with the computer name
I'm having problems currently getting W10 computers to even recognize THEMSELVES - although networking devices such as Chromecast, media servers such as PLEX and squeezebox server plus squeezeboxes, smart TV's etc are seen as devices.
From a computer with an Ms account o another computer with a LOCAL account - the last time it worked --previous release you need to logon with \lomputername\user as the username and use your local password. The computer name in this case is the computer WITH the MS account -- not the target computer. I haven't tried between TWO computers with Ms accounts though.
From a Local signed on computer TO a W10 computer with an ms account just username should work with your password (ms account password).
Note though - if you are using a simple LAN - not domains etc beware that the default has changed
You need to go into control panel ==>system==>network Id ==>change
This setting seems randomly to switch back to the first one --so it's worth checking.
After re-booting W10 computers could see each other -- and other windows computers -- stll no joy though on them seeing Samba shares although SAMBA can see them. Might be something to do with SAMBA versions and IPV4/6 stuff -- that's another issue though.
Cheers
jimbo
Cheers
jimbo
Last edited by jimbo45; 03 Jan 2016 at 03:53.
I tried everything that was posted in this thread. Nothing worked for me.
Then I read truker's recommendation and it worked.
Unfortunately, after I was able to get into my homegroup computers, none of the files matched. Everything is screwed up. There is nothing under "Homegroup" and instead, the computers are listed under "Network". However, the files shown in the three computers when viewing the other computers don't match up and many are missing.
And when I finally get on the Homegroup, one Win 7 machine sees the other machines, but does not see itself.
And one other thing: when I click on another computer's files/folders, I get the message that "Windows cannot access..."despite having all of those files set to share in the homegroup.
Beats the heck outta' me.
Anyway, thanks truker.
Oh, one other thing: Microsoft's "Homegroup" system really is terrible. Been at it for a few years now and it never works properly.....at least not for me.