Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
Well, this is confusing.as hell.
For "Microsoft Account" users, you have to give access both in "Share..." (don't know why it's greyed for you) AND in "Advanced Sharing..."
The logic behind it evades me but it works for me.
Note that I used the account first name to connect, not the email address and special chars in the pwd worked.
Posts: 260
Joined: Sep 2011
Reputation:
6
2015-07-06, 21:31
(This post was last modified: 2015-07-06, 21:37 by LazerBlue.)
I think it's greyed out because I already have it shared.
Let me try the account first name on my end
Edit: Yup, just entering my first name associated with my account in the username and typing my password worked. That is the weirdest thing.
Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
I think the first name is the actual user ID for Windows.
Just go to the "Users" folder and you'll see that the user folders have that name.
Posts: 52
Joined: Nov 2012
Reputation:
3
windows installations having activated/in use more authorities available to authorise new session many times appreciated a hint, what is the authoritative "domain".
so in case of a local user account the username was created as WINDOWSMACHINENAME\username . it was clearly visible on NT4DOM or ADS bonded systems, but in general it is not specific only to this - specially if Windows is (able) using other types of external authentication mechanisms.
it is worth trying.
Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
Well, we used to use an antiquated version (3.0) that we bumped to 3.6
No idea why it worked with the email address before, the first name has always been the user ID in win8, AFAIK.
Posts: 117
Joined: Feb 2015
Reputation:
6
I've always used the email address in Kodi and other software (including Windows itself, on other computers) for SMB shares. Seems like it should work in Isengard too, but if this new method works.....
Posts: 10
Joined: Nov 2008
Reputation:
0
2015-10-22, 16:15
(This post was last modified: 2015-10-22, 17:32 by Mistar Muffin.)
I found a thread where Koying commented that SMB 3.6 was merged on 4/4/15 so I went looking for the newest build before that date. I found Isengard 15.0-Alpha2 from 4/1/15 and it has no issues connecting to my SMB share. I know SMB 3.6 brings many benefits to a lot of different users so I know it is not going to be reverted but I'm hoping if we can figure out what is pissing it off maybe I can make an adjustment on my server side to fix it.
I am NOT a SMB expert but I know the OI SMB stack for ZFS is their own in-kernel implementation. I want to say it's a bit dated and is SMB1 ONLY. Could this cause the issue? I will also add that I enabled guess mode and gave Everyone full access to the share and it made no difference. At this point I'm just thinking out loud.
Posts: 5
Joined: Apr 2016
Reputation:
0
Just commenting this still seems to be an issue. I just got a ShieldTV and was trying to get into SMB to watch the vids located on my Win10 pc. Kept getting the login would just kick back with no errors. My Windows login was my email address, so I changed it to just my name and then it worked immediately. Seems the Kodi SMB login can't handle the "@" symbol still.
Posts: 1
Joined: Aug 2016
Reputation:
0
This drove me nuts. It's worked for years, then didn't work last week. I can't tell you the number of hours I spent on it. My fix was simple - all of a sudden Kodi won't accept 'administrator' as username. No, it requires 'Administrator' because all of a sudden it's gone all case-sensitive on me. Yes, obvious I know...
