2010/12/26 François Patte :
> As far as I understand from Chris blog, " map to guest = bad user" is to
> be used because the mode security=share is now deprecated. In my version
> of samba-swat (samba-swat-3.2.15-0.36) this security share mode is
> still there. Do I have to change the configuratio
On 07/12/2010 07:47 AM, t...@tms3.com wrote:
>
>>
>>
>> I also encounter this problem that
>> the user security mode work fine, but on share security level,
>> it always return NT_STATUS_WRONG_PASSWORD.
>>
>> Is SHARE on samba 3.4 deprecated ?
>> Can anybody give some advice?
>
> user = share is
I also encounter this problem that
the user security mode work fine, but on share security level,
it always return NT_STATUS_WRONG_PASSWORD.
Is SHARE on samba 3.4 deprecated ?
Can anybody give some advice?
user = share is like Windoze95/98 type file share.
Thanks.
--
View this message
I also encounter this problem that
the user security mode work fine, but on share security level,
it always return NT_STATUS_WRONG_PASSWORD.
Is SHARE on samba 3.4 deprecated ?
Can anybody give some advice?
Thanks.
--
View this message in context:
http://old.nabble.com/security-%3D-SHARE-tp2
On Thu, 2010-07-08 at 02:44 +0200, José Puente wrote:
> Hello,
> Please, i need help with security mode = share.
> i want to configure security = share and the parameter "username = user"
> in a shared folder to avoid that everybody could access to it. f I have
> understood correctly the manual,
Hello,
Please, i need help with security mode = share.
i want to configure security = share and the parameter "username = user"
in a shared folder to avoid that everybody could access to it. f I have
understood correctly the manual, this configuration enables to access if
the password provided
Hello,
Please, i need help with security mode = share.
i want to configure security = share and the parameter "username = user" in
a shared folder to avoid that everybody could access to it. f I have
understood correctly the manual, this configuration enables to access if the
password provided mat
Le 30/03/2010 12:09, Cassian Braconnnier a écrit :
Le 29/03/2010 21:54, Jeremy Allison a écrit :
On Mon, Mar 29, 2010 at 09:45:06PM +0200, Cassian Braconnier wrote:
Hi,
in "Using Samba" by G. Carter, J Ts and R. Eckstein, 3rd edition, on
chapter 5, page 113, I ses that the security = share opt
Le 29/03/2010 21:54, Jeremy Allison a écrit :
On Mon, Mar 29, 2010 at 09:45:06PM +0200, Cassian Braconnier wrote:
Hi,
in "Using Samba" by G. Carter, J Ts and R. Eckstein, 3rd edition, on
chapter 5, page 113, I ses that the security = share option is
"deprecated". It is said that "there is a
On Mon, Mar 29, 2010 at 09:45:06PM +0200, Cassian Braconnier wrote:
> Hi,
> in "Using Samba" by G. Carter, J Ts and R. Eckstein, 3rd edition, on
> chapter 5, page 113, I ses that the security = share option is
> "deprecated". It is said that "there is a high chance that ... will be
> removed
Hi,
in "Using Samba" by G. Carter, J Ts and R. Eckstein, 3rd edition, on
chapter 5, page 113, I ses that the security = share option is
"deprecated". It is said that "there is a high chance that ... will be
removed from Samba at some future time".
I find that security = share is extremely us
Hi,
I have several servers in separate networks currently running samba
2.2.5. Each server can have aliases and I'm using the %L macro in share
path, so that each appear as a separate 'virtual' server - depending on
how the client calls it. There is at least one SMB users defined in
'smbpasswd' f
I've expirienced strange problem with unix group login in samba recently. This
is
unusuall because users given in "username" pramater in share can log into it,
but if I
add group of users that group cant log in to share. I'm using FreeBSD 6.2
Stable,
samba version is 3.0.25.a. Sample smbd log
> [images]
> public = yes
>
> It is not prompting for a password, what am I missing?
public=yes means anyone can connect to the share. You will notice from
your logs that the user authentication fails, and here you would
normally get an error message - but because of public=yes, Samba jus
[global]
workgroup = SCL
netbios name = ODIN
security = share
log level = 2
interfaces = eth*
bind interfaces only = yes
socket options = IPTOS_LOWDELAY TCP_NODELAY
[images]
comment = ODIN
path = /odin/images
browseable = yes
Hi list,
the security=share setting does not behave as many admins expect. Access
to all shares are mapped to the guest account and if the underlying unix
permissions don't permit that access you get errors and the access
doesn't work as expected.
Also is security=share a global parameter. This g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| Well, unfortunately, my users don't have the inclination
| to migrate from Win9x (which is what security=share was
| patterned after, right?) so they don't have an option to
| supply a separate username when logging into a sha
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Carlos Knowlton wrote:
>
> | I'm having trouble migrating from Samba2 to Samba3. I'm
> | trying to make a share that allows some users
> | read-only access, and others read-write. In version 2.2
> | this worked, but not in version 3.
> |
> |
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carlos Knowlton wrote:
| I'm having trouble migrating from Samba2 to Samba3. I'm
| trying to make a share that allows some users
| read-only access, and others read-write. In version 2.2
| this worked, but not in version 3.
|
| I'm pretty sure it's
Hi,
I'm having trouble migrating from Samba2 to Samba3. I'm trying to make
a share that allows some users read-only access, and others
read-write. In version 2.2 this worked, but not in version 3.
I'm pretty sure it's my configuration, but I ran into this link on the
samba bugzilla site, a
Hi,
How can I set the restrictions on my shares if I want to make them read
only or permit to write on it only to some users if I use security = share
option. (Samba 3). I have to use security=share due to different cases.
thanks., Sandor
--
...Fehér Sándor...---Sandor Feh
Using the following config file, the command
smbclient //share/name -U user
returns an error code of instead of working
tree connect failed: SUCCESS - 0
-
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0
I'm having a problem authenticating to my Samba server. I'm NOT using
winbind, and I have setup local users in the smbpasswd file. My w2k
workstation works as I would expect and when I connect I see the following
in the log.smbd.
[2002/05/14 10:38:23, 2] smbd/reply.c:reply_sesssetup_and_X(980)
23 matches
Mail list logo
