similar to: Account Flag X -Password Never Expires Problem

I'm helping a school district set up Samba for staff/student shares. The PDC/BDCs are running NT4. Samba is v 3.0.23a on Fedora Core 5 boxes. winbind is mapping the users. Access to shares through Windows clients or smbclient works perfectly. There is a desire to have some faculty access the server using, e.g., an ssh client (mostly for remote file access). When I try to log in

Hello all, I'm running samba3 as domain controller. I have upgraded samba from 3.0.22 to 3.0.23b and faced an issue with groups display: samba does not see any groups. "net rpc group -U Administrator" returns empty set. usrmgr.exe does not show any groups also. Groups are present in ldap, nss_ldap works fine: # id asv uid=2005(asv) gid=513(Domain Users) groups=513(Domain Users),

I just installed Samba 3.0.23a from the sources on a Slackware 10 server kernal version 2.4.26. I didn't get any errors during installation. When I try to start the Samba daemon by smdb -D nothing happens. Here is a snippet from log.smbd: [2006/07/28 20:22:27, 0] smbd/server.c:main(847) smbd version 3.0.23a started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2006/07/28

Since upgrading to Samba 3.0.23a, mounting a Samba share using mount.cifs generates the following errors in the Samba server's logs: Aug 7 17:45:08 pccentos4 smbd[5345]: [2006/08/07 17:45:08, 0] libsmb/smb_signing.c:srv_check_incoming_message(720) Aug 7 17:45:08 pccentos4 smbd[5345]: srv_check_incoming_message: BAD SIG: seq 2 wanted SMB signature of Aug 7 17:45:08 pccentos4 smbd[5345]:

hello the passdb backend no longer accepts multiple backends in a chaining configuration since samba 3.0.23a . question: will the following confi still work? passdb backend = ldapsam://ldapserver1 ldapsam://ldapserver2 ? the idea is to use 2 ldap servers werner Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

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

Using Samba 3.0.23a-1.fc5.1 When I try to add XP workstation to the domain using Network ID wizard (from XP) it fails. add machine script is: /usr/sbin/useradd -d /dev/null -g 500 -s /bin/false -M %u What happens is a unix account (in passwd file) is created with LOWER-CASE username. Account is added to smbpasswd in UPPER-CASE. XP reports error "A device attached to the system is not

Okay guys, Im trying to get samba 3.0.23a to join a Windows Domain (no suprise right) Anyways, i ran "net rpc join -U [adminaccount]", it asked for the password to [adminaccount] and said the domain was joined. Then i ran "net ads join -U [adminaccount]", it asked for the passsword to [adminaccount] and after typing it in, it says [2006/08/07 10:35:56, 0]

I'm not sure that the problem is with net ads join but I'm in desperate need of help either way. Using smb Version 3.0.23a-1.fc4.1 I do a net ads join I get the below error: [root@mustang tmp]# net ads join -U exservice@MACHINEVISIONPRODUCTS.COM exservice@MACHINEVISIONPRODUCTS.COM's password: Using short domain name -- MVP Failed to set servicePrincipalNames. Please ensure that the

Hi, I'm running Samba 3.0.23a on Linux. One of my share is a USB disk with a FAT32 filesystem. When copying large files from my Windows XP machine to this share, smbd seem to "reserve" (by using ftruncate()) the space needed on the USB disk before actually doing any copying. This ftruncate() operation takes quite a while when the file is large. It may even cause the client to time

We have a Linux user and group with the same name (username prox, group name prox) and a Samba share with "force user = prox" set. Since upgrading from Samba 3.0.21b to Samba 3.0.23a, that share no longer works. smbclient gives the following error when connecting to the share: tree connect failed: NT_STATUS_NO_SUCH_USER The Samba server logs the following error: [2006/08/07 09:38:26,

I had the same problem after upgrading to 3.0.23a. I have one samba PDC running a basic setup back to the smbpasswd file, and one that runs OpenLDAP. The former did exactly as yours, and I ended up rolling back to version 3.0.23. On the latter, the smb process refused to run, reporting that it could not contact the database. I ended up having to remove all the database files and reinstall

Greetings, I am in the process of testing Samba 3.0.23a with our own passdb plugin. As part of mytesting I am trying to join the domin so here are the steps I take... 1 - get local sid /usr/local/samba/bin/net getlocalsid SID for domain JAZZY is: S-1-5-21-1016995387-3159270912-1426853295 2 - create group mappings [paulg@jazzy ~]$ /usr/local/samba/bin/net groupmap list Domain Users

All, I fear I''ve become a pita with this, but windbind periodically dying on one of my machines is really starting to cause grief, and I have no idea what might be causing it, especially as the same config is used on several similar boxes which do not exhibit the problem. While I've posted the problem previously, I thought that maybe this latest log entry after winbind dies

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

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

-----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

I've got an issue with roaming profiles with samba 3.0.23a and an LDAP backend. I can use the ldap to authenticate an NT and a local user, and I know alot about PAM, NSS, and general linux. BUT, I can't get ANY roaming profiles to work. Other than my domain name changed for security purposes, the following is my smb.conf file. (I first used SWAT, then did more customization)

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 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