similar to: ***SPAM*** Re: Configure Samba with non-standard OpenLDAP location

Try the configure format below: LDFLAGS='-L/usr/local/openldap/lib' CPPFLAGS='-I/usr/local/openldap/include' ./configure --prefix=/usr/local/samba-3.0.12pre1 --with-ldap --with-ads --with-winbind --with-krb5=/usr/local/krb5-1.3.5 --with-libiconv=/usr/local/libiconv-1.9.1 That's from my own compile. Change the LDFLAGS as applicable. -----Original Message----- From:

Tony Earnshaw: > Schlomo Schapiro: > > >> read the recent thread on vampire, there we discussed the question, if >> usernames with spaces work on Linux. For example useradd "hello world" >> won't work on any Linux system around me here (various SuSE). So maybe >> you just have bad luck (sorry to tell you, but having usernames with >> spaces can

Before I lay out the problems I am currently suffering from let me describe my environment: Dell OptiPlex GX270 2.6Ghz 512MB Ram RedHat Linux Fedora Core 3 with all current updates. Samba compile is version 3.0.20 stable. Uname -a: Linux theo.hq.navis.net 2.6.12-1.1378_FC3 #1 Wed Sep 14 04:24:31 EDT 2005 i686 i686 i386 GNU/Linux Everything was running fine until my last YUM update.

Compiling version 3.0.20 from source on RedHat Fedora Core 4 everything seems to go smoothly. However upon trying to join a 2000 domain with the following command "net ads join -U Administrator%Password 'OU'" I get the following error: [2005/08/26 09:43:56, 0] utils/net_ads.c:ads_startup(191) ads_connect: No such file or directory I have checked my smb.conf file with

Hi, especially John H. T :) I'm yet again plodding through chapter 14 of the Samba-HOWTO-Collection.pdf. Not because I can't make what's in it work for me, I did that long ago, I found out for myself, because a great deal of what's in it is wrong. I just got fed up with trying to get Nagios to work - I gave up, for various reasons and started on the Samba doco. At the risk of

I'm trying to use the LDAP backend for the idmap database but I just can't seem to get it to work. There really is rather pathetic documentation out there on how to implement this. I've basically got my ldap server setup with an OU called smb and another OU under it called idmap. Here is my smb.conf file: [global] workgroup = HQ server string = Theo's Samba Server

Base: Red Hat RHAS3, PDC security = user Samba 3.0.14a Cups 1.1.17 Windows XP Pro Epson C42UX (cheap inkjet) USB to the server I was looking for an alternative to the immensely complicated Add Printer Wizard procedure (APW) detailed in chapter 19.6 of the Samba HOWTO guide. The following is a method that works for me, I don't necessarily expect it to work for others, and I'd value any

List, both on RHAS3 update3, update 4, Samba source code 3.0.9 thru 11 gives SIGSEGVs on make check. Installing the buggers and trying to run them gives the same. *THOUGH*. The Red Hat beta 3.0.9 srpm at fr2.rpmfind.net comples and runs "like a little sun" ("net als een zonnetje", in Dutch). Anyone compiled Samba 3.0.11 on Red Hat RHAS3/RHEL3? Not "how", just

Johan B, please let it through+ The headers are needed. I live in the Netherlands, where the police contacts for this sort of thing are grey and unknown to me. The Metropolitan Police (London only) in England is 100% on the ball, but they're under resourced and I don't live in their "manor" (London slang for area). I'd like to push it out to as powerful an organization

Hi, It's (possible|probable) that the above was included in the list postings in February last; at that time I hadn't even begun with Samba (use it in production now :). If so,please point me at the archives, if not, could someone please comment? >From the last SANS NewsBites (apologies for the line break in the URL for those using 76-character text MMUAs): WORMS, ACTIVE EXPLOITS,

List, Thanks tremendously to JC and JHT for guiding (nay, kicking) me toward getting ACLs to work on RHAS3. Reading the RH sysadmin guide about ACLs and searching elsewhere, as well as thinking for myself, were also a pre. Now for something completely different: High school in Amsterdam Netherlands: - RHAS3 - Samba 3.0.11 RPC, not ADS (no way we're upgrading while the bug reports keep

List, from the Dutch "Computable" paper ICT tabloid and daily ICT subscribable mailing-list and so-called verwittigingsbrief/ad hoc news letter, partly translated into English by me ;) Dutch readers only: http://www.computable.nl/nieuws.htm?id=524000 "Manage Windows clients from Linux servers" blahblahblah Zenworks 7, the latest release of Novell's sysadmin suite".

To answer my own question of a week or so ago, as to whether RHAS3 users had got 3.0.11 to compile and execute (I had a plethora of errors): The Red Hat 3.0.11 SRPM from the Samba site compiled cleanly and runs fine (daemons and utilities) on my RHAS3 test rig, and on a RHAS3 update 4 production NAS server doubling as a Samba 3 server with 1150+ users of Unix/Linux and soon PDC Windows services.

People have been experiencing problems with the subject line. AFAICS most of them haven't bothered to follow selected bits of the HOWTO. However, the former excludes all references to the idealx scripts, which I cannot use, since my DIT is set up completely differently from the idealx concept. I write my own, disjointed, shell and awk OpenLDAP scripts. Neither on my RHAS3 test rig (config as

Samba 3.0.11, 3.0.14a, 3.0.15pre1 on Red Hat RHAS3 Samba server is an NT4 PDC (no ADS) passdb backend = ldapsam I could try it out for myself, since I've a test machine besides my regular site. But I'd really rather have a definitive answer. I have POSIX ACLs working fine. In smb.conf I set "nt acl support = yes" (default anyway). Let's presume that I go and put all

People, I came to Samba 3 or 4 weeks ago and now have a successful ldapsam 3.0.11 PDC installation for 1150+ users (around 80 Win 2000 and XP workstations) running together with a DHCP server as an "afterthought" service on a RHAS3 NAS server. I adopted/adapted my already existent Openldap (2.2.17) DSE at that site) and wrote to this list about my experiences. For example I

Means "acclaim" in both Norwegian languages (there are new official rules out today for writing both of the 2 Indo-European Norwegian languages). What made me write this acclaim is the number of postings I've seen about Samba's instability - i.e. run-away processes, profiles going wrong, ACL problems and more. My (high school) site with around 80 w2k workstations, of which

I have been trying in vain to get ADS domain authentication working. I can't figure out what is wrong and have read the docs and looked through the mailing lists. I'm not sure why better documentation hasn't been written on the web site for the ADS feature since it's pretty spectacular to be able join a Samba server natively to an AD domain. I have successfully joined the samba

List, documenters; I'd like to exchange notes about the official Samba 3 LDAP doco. I'd like to do this off list, since doing it on list would simply confuse and confound users wit perfectly working systems. Background: Me, Samba relative newbie, though I can get *everything* Samba-orientated to work simply by using umpteen years Unix experience. Many years as Openldap admin. With

List, No, no questions, no complaints. Just compliments to the Samba team. Samba 3.0.11 (Red Hat RHAS3) running as (one of 5 diverse Linux servers) PDC for all (75+) wk2000 and XP professional workstations on top of an 1,560+ OpenLDAP 2.2.17 backend at Barlaeus Gymnasium ("gymnasium" means "sort of high school for over-intelligent pupils whose parents just might happen to have