similar to: Windows 2003 server unable to join a Samba PDC

---------------------------- Original Message ---------------------------- Subject: Windows 2003 server unable to join a Samba PDC From: "Christian" <christian@telemack.net> Date: Fri, August 18, 2006 3:26 pm To: samba@lists.samba.org -------------------------------------------------------------------------- Hello, I have been trying for hours to make a Windows 2003

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 #

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

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

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:

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

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

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

hello when I try to install samba 3.0.23b I get this error error: Failed dependencies: perl(Unicode::MapUTF8) is needed by samba-3.0.23b-1 is this perl module required since 3.0.23b? and why? can you use 3.0.23b without it? werner Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

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

Hi All, Just upgraded a test box to 3.0.23b and discovered some changes that cause a panic. I had an smb.conf with passdb backend = tbdsam guest The guest bit now causes panic action. log.smbd complains ... "No builtin nor plugin backend for tdbsam guest found" Either the build options have changed or the guest operative has issues. Works OK without guest, but it's been

I installed a PDC some days ago for some 15 users/PCs (w98,2000,xp), with samba 3.0.23b-1 and valid users wasn't working. I'm going to update to 3.0.23c which solves that problem. I'm using smbpasswd passdb backend. In /etc/group I have only two groups. I don't understand very well the changes related to primaryGroupSID and RID commented in previous posts. Please, is it

I'm compiling samba-3.0.23b as I write this. However, after studying the documentation, I have some serious concerns about installing it. The WHATSNEW file says that the method of mapping unix-native uids and gids to SIDs has changed since 3.0.22. As I read this, this would imply that upgrading Samba will cause much breakage because domain users will no longer be able to access files they

hi, iam using samba winbind with ntlm_auth for squid authentication. i have 200 ntlm_auth clients activated in squid.conf, don't know really how many i need. I have about 200 internet users. my winbind crashed and i have the following in my winbind log .. [2006/08/25 11:39:13, 0] nsswitch/winbindd.c:process_loop(822) winbindd: Exceeding 200 client connections, no idle connection found

Hi All, I'm running samba-3.0.23b compiled on a Solaris 10 system compiled against MIT kerberos. I am experiencing odd behaviour where joining the machine to the domain using 'net rpc join' seems to break the kerberos principal tickets and regular user authentication via kerberos ceases to work. My smb.conf is fairly minimal; [global] use kerberos keytab = yes unix

Hi, We've recently upgraded a network from Win2k to 2k3 SBS. We were using samba with security = domain (which I believe stopped working - I was on vacation at the time the upgrade was done) and are now using security = ads. We're using samba-3.0.23b-0.1.35 on SuSE Enterprise Linux Server 9 SP3 x86_64 The samba machine has been sucessfully joined to the domain with: kinit

An old problem has started to reappear with our Solaris (2.8) Samba (3.0.23b). This was after an upgrade from 3.0.22 in which the problem was worse. Occasionally an smbd process will go "rogue" and start consuming CPU cycles until killed. I did a truss of the process and got back this tight loop. fcntl(27, F_SETLKW64, 0xFFBEEF98) = 0 fcntl(27, F_SETLKW64, 0xFFBEF010)

I am running samba-3.0.23b-2 On both my server and laptop. I can't for the life of me write to the mounted shares. I have tried every possible combination to mount the shares and still cannot write to them. Also, I keep getting an error at boot: mounting cifs filesystem error 13 opening credentials file. But it doesn't complain about it if I mount the shares manually after the

I portupgraded my samba domain server and domain member to 3.0.23b from 3.0.23 and found that the domain member was not accessible from workstations. The error message: \\HOSTNAME is not accessible. There are currently no logon servers available to service the logon request. In the log.winbindd of the domain member, I found: [2006/08/23 22:52:00, 0] nsswitch/winbindd.c:request_len_recv(517)