I have two users who wish to print to their printers attached to their
XP Pro workstations from our linux server.
After trying (And failing) to set it up via the CUPS interface, I
started tinkering at the lower level, doing things like:
$ smbspool smb://printuser:[EMAIL
OK, I'm trying to get Samba working with LDAP. And I have it... sort of.
I have a Samba server TESTBOX, and I can authenticate to it just fine.
It seems taht if I change the netbios name (which I was doing to
simulate connecting from some other samba server in our network), I
get:
$ smbclient
On Sunday, June 22, 2003, at 09:23 AM, Andrew Bartlett wrote:
Like many users before you, you have not run 'testparm'
This would have told you that your configuration was not valid, as
shown
above.
True, but in fairness, I copied the example off the samba.org site
verbatim changing only the
http://us1.samba.org/samba/devel/docs/html/Samba-HOWTO-
Collection.html#id2867008
contains a line:
passdb backend ldapsam:ldap://ahab.samba.org
which should, obviously in retrospect, be:
passdb backend = ldapsam:ldap://ahab.samba.org
--
To unsubscribe from this list go to the following URL
Hopefully, you can help me out.
I'm trying to figure out why I'm getting the error I get. From the
debug output, it looks like it's adding the objectClass to the user (so
they can get the sambaSID attribute attached to them), but it's not
actually happening.
The schema is, obviously, in the
I've only got LDAP configured as a passdb type in my smb.conf, but
samba appears to be completely ignoring that and creating an
/etc/samba/smbpass file (full output of that at the bottom)
my smb.conf has:
ldap admin dn = cn=Admin,dc=byramhealthcare,dc=com
ldap ssl = off
passdb backend
Is there any way to DISABLE password expiration in the Samba password
TDB/file?
We're handling password expiration externally, and would manually
change the password on the samba servers as needed by the centralized
password database.
Any thoughts? I thought it might be something client based
After a brief stint offlist (thanks Bradley), I'm closer to getting
SMB/LDAP working but now am encountering something very odd, which he
suggested I bring back to the list for further evaluation. :-)
$ smbclient //TESTBOX/testshare -U dballing
added interface ip=10.15.49.142
On Wednesday, September 25, 2002, at 06:59 PM, Andrew Bartlett wrote:
That's really up to you. It's often a matter of 'pick your day' on
CVS. Most days are pretty good, but the debian folks had horrible luck
and kept getting 'the bad days'...
tell me about it... I'm still trying to get
Using the 3.0CVS 8/29 package in debian, I see, when trying to do
smbpasswd -a dballing
(where dballing is a valid user, just not yet someone with an
objectclass of sambaAccount),
The relevant config bits are:
passdb backend = ldapsam:ldap://ldap.XX.com/
ldap admin dn =
10 matches
Mail list logo
