similar to: Truncated username error?

Hello I am running a Samba file server (Version 3.0.22) with 'security = share'. Here is one of my share definitions: [archive] path = /var/smb/archive writeable = Yes username = @staff valid users = @staff First question: In the manpage for smb.conf, it is mentioned that '+group' expands to the Unix group named 'group'. But that does not

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've uploaded the *final* 3.0.23c roll up patch to http://samba.org/~jerry/patches/patch-3.0.23b-3.0.23c-gwc-2.diffs.gz. I've already cut the 3.0.23c tarballs so unless there is a major problem, this will be the final change set. Please report *any* bugs that you find. I'd like to wrap this one up and do the public 3.0.23c

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm watching the logs, and Samba is trying the following combinations for _Get_Pwnam() with the name UserName in the domain DOMAIN: domain+username DOMAIN+UserName DOMAIN+USERNAME and then it trys: username UserName USERNAME however, all 6 fail because what getent passwd shows is DOMAIN+username. Is there a configuration change that can fix

Not for all users but for some. I'm using samba 3.0.20 running on Fedora Core 3. Security = ADS, winbind works and getent passwd returns local unix accounts plus the domain accounts as expected. It also returns a lot of entries like: 6811ff15281f4d19bdc:x:18004:10000:Anel Susana Esquivel:/export/private/6811ff15281f4d19bdc:"/sbin/nologin" I suspect these are accounts in a

Can anybody tell me please, what isn't correct? What should I change in config? /var/samba/log/log.XP-CLIENT-IP: [2006/06/22 08:24:54, 1] smbd/sesssetup.c:reply_spnego_kerberos(303) Username DOMAIN\XP-CLIENT-NAME$ is invalid on this system all works in general, but the error above is listed in every /var/log/samba/log.CLIENT Thanks Steffen ---------------------------------------------

I have aix with 3.0.21c samba with the following smb.conf: [global] workgroup = MYDOMAIN realm = MYDOMAIN.COM server string = User management Server security = ADS password server = ad.mydomain.com idmap backend = rid:MYDOMAIN=100000-200000 allow trusted domains = No log level = 0 log file = /usr/local/samba/var/log.%m

Hi there Just a couple of questions to help me understand. When I upgrade from 3.0.22 to 3.0.23c the access restrictions on my shares on the member server no longer work. I read in the Changes file "Since Samba 3.0.8, it has been recommended that all domain accounts listed in smb.conf on a member server be fully qualified with the...." So far so good I know what I have to do still I

Gerry, all: HELP! On mandriva, I compiled samba from source and got it running, but I cannot connect from windows. (see my post from earlier "[Samba] Compiling and Configuring Samba for Mandrival") I think this relates to the group/SID changes discussed in the release notes. However, I'm not smart enough to figure it out. The tarball compiled and installed fine. It

Yesterday evening I upgraded my FreeBSD 5.5-RELEASE Server from Samba 3.0.22 to 3.0.23. This gave me a LOT of work today... :-( This is what I found so far: My Samba-Server is member of a large ADS-Domain. After the upgrade, file based Usermapping didn't work anymore... better: it worked TWICE. (I once opened a PR for that a few years ago :-). So, with LogLevel 3:

I portupgraded my working 3.0.23b PDC on FreeBSD 5.5 to 3.0.23c and found that all workstations could not login. The log file reads: get_md4pw: Workstation PC01$: no account in domain I ran pdbedit -L, and it returned nothing. I use tdbsam backend; all user accounts show up fine with 3.0.23b. Now they are missing. I deinstalled 3.0.23c and switched back to 3.0.23b. Everything is then back

Have been running samba successfully authenticating to a windows 2003 domain since 3.0.1. Starting in 3.0.23 and 3.0.23b I can't do a "net ads join" on a HPUX itanium server running 11.23 ia64. I can kinit just fine w/ this userid. Samba was built with gcc 4.1.1. See below: root@serv00 # kinit jjurich_wa Password for jjurich_wa@DIVMS.UIOWA.EDU: root@serv00 #

Greetings list, I'm using samba 3.0.23a on a Fedora Core 5 system in a member server role in an Active Directory domain (security ads). My problem is that, although wbinfo -u and -g work great and can pull user and group lists respectively from AD, getent passwd and getent group do not. I've configured passwd: files winbind and group: files winbind in nsswitch.conf, and have

Hi All, I havent heard a response back to my previous posts so I am now trying from a "broader" topic. What I have is the following: A 2 Form Factor Token Authentication system similar to RSA SecureID A Linux SAMBA 3.0.14a-Debian I've got the two systems authenticating against each other with RADIUS via PAM support. When I tell SAMBA to use this PAM support as well, I see the

-----Original Message----- From: M. D. Parker [mailto:mike.parker@ga.com] Sent: Thursday, August 10, 2006 9:02 AM To: 'samba@lists.samba.org' Subject: HELP -- Problem with access list on samba 3.0.23b but not on 3.0.20c PDC I am using samba with NO windbind and a configuration file that has worked for years stopped working at 3.0.23b. The affect was that my [netlogon] area was not being

I have several groups in /etc/groups on my samba server. I upgraded to samba 3.0.23b and then users couldn't connect to any shares they were groups on in /etc/groups (shares used valid users = @groupname) but could connect to shares where valid users = their_username. I did some reading and saw the group mapping change at

Hi list, Using Samba 3.0.22 on a Debian box. Samba is using security = ADS and is a member server. Winbind, kerberos works as expected. BUT If I look at the security tab in windows I always see the Everyone entry. I think this is because the POSIX "other" entry in the FS on the debian box, correct? Can I remove it? If so how? Thanks, Henrik

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, We are discussing removing the capability to chaining passdb backends. It's a decent idea but overly complicates things IMO and unless it has wide spread use, we'll probably axe it soon (voting is starting up on the samba-tecnnical ml now). To give you an example of what I mean, is anyone using something like: passdb backend =

Does *anyone* have info on how I can authenticate to Active Directory using dotted usernames from a Linux machine? I'm running Fedora Core 4 with samba-3.0.14a-2, and when I mount a share using a "normal" (dot-free) username everything works fine. My situation sounds pretty much exactly like the following, but there's no response:

Hi All, Yesterday, I've upgraded my Samba server from 3.021c to 3.023 through yum upgrade samba*. I'm running Fedora Core 4 Kernel 2.6.17-1.2142 on this server. After upgrade has been completed, I lost the attributes of ownership and groups. I noticed that the uids/gids have changed for all AD accounts. This means that users can't have total access for their files and no access

Hallo! I am running samba-3.0.10-1.4E.11 on centOS. I want to enable the automatic printer download feature, but are running into problems. I have tried to work it out from samba by example, but since the automatic driver download is bundeled togehter with ldap (which I am not using), this does not get me anywhere. Can anyone direct me to a good howto on this - one that will make things work! I