Happy new year! I know, I was lazy during the last weeks. However I published at least one new guide last night: https://wiki.samba.org/index.php/Standalone_server I think most of the docs linked on https://wiki.samba.org/index.php/User_Documentation are meanwhile rewritten and a good basis for most of the users. Next I will finally focus on the results of my Samba user survey from last year (https://www.samba.org/~mmuehlfeld/) and see where to enhance the existing docs with missing pieces. Regards, Marc PS: Thanks to Rowland for reviewing the new standalone server guide.
Hai Marc,
First best wishes and happy new year.
This one looks great, but your missing one thing imo.
You can do the same without a local user when you change
map to guest = Bad User
to
map to guest = Bad Password
Which gives also the advantage, that you dont need to have a local user on a
windows system, which popups up with a password and where lots of peoople have
problems with.
And offcourse the share needs 777 and not 775,
or rights forced from share ( which i use at home )
So my suggestion
2A) A basic smb.conf ( which user rights/acl, proceed to chapter 3 )
2B) A basic smb.conf ( a open server, no rights, all mapped to nobody )
You can still use the acl on linux to force rights, but a use mapping must be
possible between windows and samba. So windows and samba user/pass must be the
same.
When do you use something like this.
For example my kodi server has open shares.
Like :
\\kodi\media ( open share. )
\\kodi\backup ( open share with acl. )
I have a match user/pass for this one.
And just a question, have you tried to access the server from win7+
With only \\servername
I bet you get a popup to authenticate.. user Guest is disabled in windows.
So the user mapping between the pc and samba goes wrong.
Just my thoughts.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Marc Muehlfeld
> Verzonden: maandag 4 januari 2016 20:44
> Aan: samba at lists.samba.org; samba-technical at lists.samba.org
> Onderwerp: [Samba] Wiki: Standalone server
>
> Happy new year!
>
> I know, I was lazy during the last weeks. However I published at least
> one new guide last night:
>
> https://wiki.samba.org/index.php/Standalone_server
>
> I think most of the docs linked on
> https://wiki.samba.org/index.php/User_Documentation are meanwhile
> rewritten and a good basis for most of the users. Next I will finally
> focus on the results of my Samba user survey from last year
> (https://www.samba.org/~mmuehlfeld/) and see where to enhance the
> existing docs with missing pieces.
>
>
> Regards,
> Marc
>
>
> PS: Thanks to Rowland for reviewing the new standalone server guide.
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
On 05/01/16 08:10, L.P.H. van Belle wrote:> Hai Marc, > > First best wishes and happy new year. > > This one looks great, but your missing one thing imo. > > You can do the same without a local user when you change > map to guest = Bad User > to > map to guest = Bad Password > > Which gives also the advantage, that you dont need to have a local user on a windows system, which popups up with a password and where lots of peoople have problems with.I thought that 'Bad User' mapped unknown users to the guest account, but 'Bad Password' mapped users, that gave an incorrect password, to the guest account, or to put it another way, if a user known to Samba typed a wrong password, they get silently mapped to guest. I suggest we stick to 'Bad User'.> > And offcourse the share needs 777 and not 775, > or rights forced from share ( which i use at home ) > > So my suggestion > > 2A) A basic smb.conf ( which user rights/acl, proceed to chapter 3 ) > 2B) A basic smb.conf ( a open server, no rights, all mapped to nobody ) > You can still use the acl on linux to force rights, but a use mapping must be possible between windows and samba. So windows and samba user/pass must be the same. > > When do you use something like this. > For example my kodi server has open shares. > Like : > \\kodi\media ( open share. ) > \\kodi\backup ( open share with acl. ) > I have a match user/pass for this one.If you are using 'Bad Password' and you type the password incorrectly, your user will get mapped to guest.> > And just a question, have you tried to access the server from win7+ > With only \\servername > I bet you get a popup to authenticate.. user Guest is disabled in windows. > So the user mapping between the pc and samba goes wrong. >I thought the mapping is done on the Samba server, so what has guest being disabled on win7+ have to do with this ? Rowland> Just my thoughts. > > Greetz, > > Louis > > >
>I thought the mapping is done on the Samba server, so what has guest being >disabled on win7+ have to do with this ?Because of the windows Pass through authentication, and guest on windows is disabled.. Result, authentication popup. map to guest = Bad User was the online setting which got it working for me. I really suggest we have a look at this again. Check the archlinux also for this one. https://wiki.archlinux.org/index.php/Samba/Tips_and_tricks see example Sample Passwordless configuration. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Rowland penny > Verzonden: dinsdag 5 januari 2016 11:53 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Wiki: Standalone server > > On 05/01/16 08:10, L.P.H. van Belle wrote: > > Hai Marc, > > > > First best wishes and happy new year. > > > > This one looks great, but your missing one thing imo. > > > > You can do the same without a local user when you change > > map to guest = Bad User > > to > > map to guest = Bad Password > > > > Which gives also the advantage, that you dont need to have a local user > on a windows system, which popups up with a password and where lots of > peoople have problems with. > > I thought that 'Bad User' mapped unknown users to the guest account, but > 'Bad Password' mapped users, that gave an incorrect password, to the > guest account, or to put it another way, if a user known to Samba typed > a wrong password, they get silently mapped to guest. I suggest we stick > to 'Bad User'. > > > > > And offcourse the share needs 777 and not 775, > > or rights forced from share ( which i use at home ) > > > > So my suggestion > > > > 2A) A basic smb.conf ( which user rights/acl, proceed to chapter 3 ) > > 2B) A basic smb.conf ( a open server, no rights, all mapped to nobody ) > > You can still use the acl on linux to force rights, but a use mapping > must be possible between windows and samba. So windows and samba user/pass > must be the same. > > > > When do you use something like this. > > For example my kodi server has open shares. > > Like : > > \\kodi\media ( open share. ) > > \\kodi\backup ( open share with acl. ) > > I have a match user/pass for this one. > > If you are using 'Bad Password' and you type the password incorrectly, > your user will get mapped to guest. > > > > > And just a question, have you tried to access the server from win7+ > > With only \\servername > > I bet you get a popup to authenticate.. user Guest is disabled in > windows. > > So the user mapping between the pc and samba goes wrong. > > > > I thought the mapping is done on the Samba server, so what has guest > being disabled on win7+ have to do with this ? > > Rowland > > > Just my thoughts. > > > > Greetz, > > > > Louis > > > > > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Hello Louis, Am 05.01.2016 um 09:10 schrieb L.P.H. van Belle:> You can do the same without a local user when you change > map to guest = Bad User > to > map to guest = Bad Password > > Which gives also the advantage, that you dont need to have a local > user on a windows system, which popups up with a password and > where lots of peoople have problems with."Bad password" maps you directly to the guest account if you enter a wrong password. I think it's not a good idea and the manpage tells you why:> Note that this can cause problems as it means that any user > incorrectly typing their password > will be silently logged on as "guest" - and will not know the > reason they cannot access files they think they should - there will > have been no message given to them that they got their password > wrong. Helpdesk > services will hate you if you set the map to guest parameter this > way :-).> And just a question, have you tried to access the server from win7+ > With only \\servername > I bet you get a popup to authenticate.. user Guest is disabled in windows. > So the user mapping between the pc and samba goes wrong.I can't confirm this. My standalone in my test environment uses the same config than in the guide. Win7 Pro is in the same workgroup ("workgroup") than the Samba host. If I connect to \\ip or \\servername I see the two shares without being asked for username/password. Regards, Marc