This worked for me too!
Thx
1 Like
I should add that I’d already created a Windows credential, and it stopped working. I deleted it and samba still wouldn’t respond. But when I created a new credential, it worked. The fix might just be re-creating the credential after a Windows update introduced this problem. I think I used the same system name, but I’m not sure; what’s working for me now is “homeassistant” - with no backslashes - and of course the name and password I specified over in HA.
Ty. Worked for me.
I have found a solution, go to:
Control Panel → User Accounts → Credential Manager → Windows Credentials → Add a Windows credential
Add the hostname or ip, without ****, then user and password, with that you will be able to access the HA folders without problems.
5 Likes
Thanks, worked for me!
super un bon moment que je galère merci pour cette solution
fonctionne super bien
English please.
This worked for me too! Good job!
Thanks a bunch! Worked for me too!
I have a Windows username with a space in it, as I would guess many Windows users do.
Has anyone gotten this to work without changing the Windows user credential ?
I feel it should be possible to fix on the HAOS side, and do the user mapping there, rather than on the Windows client.
On a Ubuntu server, you can do this mapping for samba shares in the smbusers file.
Not sure how you would do the same under HAOS, though.
You don’t need to authenticate with your windows username.
I’m aware. I just prefer not to have any login popups show up.
When I set my Linux samba servers to do the mapping, I can just browse the shares from the Windows box, without ever being prompted to authenticate.
A publishing service is also necessary, wsdd, in order for the Linux boxes to show us in the Windows network tab.
Mine only popped up once and I entered the details.
Map it as a network drive. Otherwise you’ll have to add credentials every time.
Yes, because you saved the details that time, and it never asked you again.
I want it to pop up zero time.
I don’t want to enter any credentials from the Windows side at all, whether through drive mapping or through pop-up. This works fine if the Samba share on the HAOS side uses the same credentials as the Windows credentials.
The Samba add-on doesn’t properly support spaces in the username. It just writes whatever you put into the GUI into smb.conf . But that doesn’t work because Samba itself won’t support spaces in the username that way.
The solution is for the add-on to automatically create an smbusers file when there is a space in the username. That would make it work seamlessly with Windows.
Then use your windows credentials. You have a username in windows with a user id, pull the user id and use that. You can see what your user id is based on what directory is created under c:\users for your login. The user id won’t have spaces btw.
I installed Samba with samba username and samba passwd, In Windows Map:network_drive(first time) click “change account” ADD (samba)credential, after authenticated(the Correct way) i created a shortcut on windows desktop, on all my 3 laptops \ipnumber\ … gets automatisk a cool Icon on desktop … doubleclick and i have all Shares
he doesn’t want to do that
ok, i guess he can do the same as in ubuntu … find the “sambausers” file and make an alias there … as samba in ubuntu hardly accept a name with space in it, either ( as well as Linux )
Edit:
Question that arise in my head is, what will HA+OS say to a “name with space(or an alias)” … maybe there is “another” way to “Map” name with space in on “Ubuntu/Samba on Ubuntu” that im not aware of
My user name in Windows does indeed have space. It’s “Firstname space Lastname”.
And yes, the directory under C:\Users has a space in it as well. I would surmise that a very high percentage of Windows users have a space in their Windows username.