similar to: Q: winbindd, unqualfied users, & name conflicts (a.k.a "Death to 'winbind use default domain'!")

My opinion: Local users should always take precedence. People should specifically refer to local users as <SambaHostName>\localuser, if that is the form the SMB client insists on sending. Tacking on default domains and/or stripping domains to/from user names and "trying them out" is playing fast and loose with user identity and is a breeding ground for potential security holes.

I have a file server with two shares accessible to 2 different groups. After the last update ( from debian 2:3.2.5-4 to 2:3.3.2-1 ) i cannot any more access ONLY ONE of the two shares and I can't understand the reason! Can anyone hel me? I'm getting mad! Thanks Giorgio from smb.conf: [documenti_movi] path = /home/documenti_movi valid users = @staffmovi read

Hi, When I use "valid users" in smb.conf to limit access on my share, I have this message with smbclient : [global] workgroup = MYDOM domain master = no local master = no security = user passdb backend = ldapsam:ldap://x.x.x.x:389 ldap admin dn = cn=admin,dc=company,dc=com ldap suffix = dc=company,dc=com ldap user

Hi, We have been running samba file server about 2 years without this problem. The problem appeared at the same time on our debian and centos servers. Not sure if it's related to any updates on our windows AD servers. Debian Squeeze sernet-samba-3.5.8-27 Centos 5.5 samba3-3.5.5-43.el5 Use Active Directory for user login authentication Use uid/gid from ldap The reason we still want winbind

hello, I'm trying to migrate a rather simple configuration from a Samba 2.0.6 to Samba 2.2.8 , on an AIX system. smb.conf stays exactly the same & checked with testparm. File sharing works fine again, but not printing : smbd meets an internal error when a NT box tries to launch a print job. Sample of logfile : [2003/03/19 16:42:56, 10] lib/username.c:user_in_list(456) user_in_list:

Hi, I want to switch from 'security = server' to 'security = ADS'. Kerberos is working and I can login to the server. With Samba 3.0.22 I was able to restrict access to shares with the 'valid users' directive. ve is local unix group. valid users = +ve And force the group ownership with the 'force group' directive. force group = +ve [foo] comment = foo

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Some people might find this discussion about upcoming changes in 3.0.22 interesting. It might also be helpful to get some feedback from the field on the ramifications of the changes. cheers, jerry ===================================================================== I live in a Reply-to-All world ----------------------- Samba

Hi, after upgrading samba from 4.1.17 to 4.1.19 on OpenSuSE 13.2, any shares offered by this machine can nolonger be accessed, when these shares contain an entry "force group" which specifies a local unix group and when there exists a unix user with the same name. Here's an excerpt from smb.conf: [FactWork] comment = FactWork-Downloadportal path =

We had to power down all servers today for electrical maintenance in the building and for some reason I began having access problems related to the valid users lists when power was restored. The dialog from the 'Samba-3.0.23 broke my network' thread seemed as if it might be related even though I had not performed any software upgrade so I tried adding the group mappings as discussed in

Hi, I am trying to use squid proxy with validation on win 2003 active directory to filter internet navigation and for it I installed an ubuntu 10.04 server 64 bit with samba. My installation looks ok, the server is joined to the AD, ntlm is able to validate user, wbinfo report corret information and squid works good. The problem arise after some hours: winbind become not able to resolv info

Hi all, I seem to be having a problem identical to this bug: https://bugzilla.samba.org/show_bug.cgi?id=3940 in Samba 3.0.28, however the bug is supposed to be fixed by now. I have a Fedora 7 box joined as a member to Windows 2003 domain. All my Windows users have accounts on the Samba machine, with the same user name in Windows and in Unix. I have a share with valid users = +group, where

>Submitter-Id: current-users >Originator: Alex Vasylenko >Organization: >Confidential: no >Synopsis: [patch] net/rsync: problems in client name lookup code >Severity: non-critical >Priority: low >Category: ports >Class: sw-bug >Release: FreeBSD 4.8-RELEASE-p16 i386 >Environment: System: FreeBSD 4.8-RELEASE-p16 >Description: rsync does reverse name

I am attempting to get a Debian box running Samba 3.0.23d (latest from debian testing) to work with our shiny new Windows 2003 server PDC. I can join the domain. windbinds various wbinfo commands return all the groups and users, as does getent. I can access everything from the PDC. Effectively, everything works _except_ specifying a group to 'valid users'. My smb.conf[0] is run of the

Hi list, My case : Local UNIX user : ZTEST domain : uuq.ork domain user : UUQ\ztest smb.conf for standalone samba : /home/hywu/smb.conf [/home/hywu] # cat /home/hywu/smb.conf [global] passdb backend = smbpasswd workgroup = WORKGROUP security=user Smbpasswd fail to change local UNIX user password (ZTEST) when samba role is DC. I want to change password of local UNIX user "ZTEST" but

Hi Team, While Running rsync rsync://username at ip:873 , I am getting following error. rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(276) [Receiver=3.1.1] In Remote pc , i can see segmentation fault, dmesg gives following error. My remote PC using debian wheezy. rsync[9022]: segfault at 968

Hi! The problem lies in the "winbind separator" settings. If I use winbind separator = \\ everything goes well. I believe this is due to a bug. As I don't want to register to yet another bugzilla, please someone issue the report there. Explanation: winbindd_raw_kerberos_login uses parse_domain_user to generate the kerberos principal from state->request.data.auth.user at this

All; I am using the cobalt Qube 2 which uses a Cobalt OS with is supposedly a RedHat Linux 4.2 variant. I can not compile the new rsync version 2.5.7 as I always fail my make with the following error: clientname.c: In function `client_addr': clientname.c:72: warning: implicit declaration of function `getnameinfo' clientname.c:73: `NI_NUMERICHOST' undeclared (first use this function)

Am 23.02.19 um 22:23 schrieb Rowland Penny via samba: > On Sat, 23 Feb 2019 21:54:31 +0100 > Alexander Spannagel via samba <samba at lists.samba.org> wrote: > >> Am 23.02.19 um 15:48 schrieb Rowland Penny via samba: >>>>>>>>> If you have, as you have, 'files sss winbind' in the the >>>>>>>>> passwd & group line

Samba 2.2.8a, RH7.3 I have successfully connected machines running XP to the samba controlled domain. There are 3 XP machines, each with only one user designated as a power user (ie domain\username power user). Each can log into any of the three machines without a problem. Now I am trying to log a different person into any of these machines and I get the message "System Could Not Log

On Thu, 25 Jan 2024 18:27:48 +0800 hhyy ww via samba <samba at lists.samba.org> wrote: > Hi list, > > My case : > Local UNIX user : ZTEST > domain : uuq.ork > domain user : UUQ\ztest > smb.conf for standalone samba : /home/hywu/smb.conf > > [/home/hywu] # cat /home/hywu/smb.conf > [global] > passdb backend = smbpasswd > workgroup = WORKGROUP >