Here are my findings. Keywords for Google and for those who, like me,
did not find useful references: create user domain ldap active
directory ad linux rpcclient net ads rpc account enable enabled login
bind.
Background: we're migrating users from AD to OpenLDAP; for a period
the two have to coe
I'm migrating an AD service over to OpenLDAP. There will be a
transitional period where logins will still be served by AD, but
address book/mail/etc. will be authenticated against OpenLDAP, so I'd
like to provide the AD admins with a way of creating users in OpenLDAP
and having the change replica
First of all, sorry, this must have been discussed before but I
couldn't come up with a good set of keywords for googling. Feel free
to slap with a msgid or an URL. :-)
I successfully set up a PDC that authenticates a small Win 2k/XP LAN.
It fetches auth info from a LDAP server and also serves ho
> The 2000 machines also write a profile dirctory in that share, and
> copy the entire desktop contents to it each time the user logs
> off. For most of the users, this isn't a problem, but some users
> have a gig of video files on their desktop, and it writing all that
> crap to the sever is
On Tue, Oct 15, 2002 at 02:48:34PM +0200, Peter Lustig wrote:
> is it, and how - possible to add an Win2K/XP Client to a Samba-Server (PDC)
> without encrypted passwords ?
On a related note: is it possible to put the whole auth conversation
between the Windows client and the Samba PDC in SSL, i
On Sun, Oct 13, 2002 at 02:17:39PM +0200, Massimiliano Mirra wrote:
> (I'm staying with alpha18 for now because, for some reason, with
> alpha20 the PDC just vanishes from the domain.)
I solved this, and in case someone else had the same problem, here's
the fix:
s
I've read on usenet about using `smbpasswd -S' from the latest 2_2 to
get the MACHINE.SID of an existing PDC into the secrets.tdb of a
soon-to-become BDC. I've also noticed `net setlocalsid SID' in
alpha20. Is there any way to do the same on alpha18?
(I'm staying with alpha18 for now because, fo
I am configuring two identical PDCs so that, if one goes down, the
other can start to serve logins.
The first PDC, a Debian 3.0 with Samba 2.999+3.0cvs20020723-1, works
fine.
The second PDC, that I bring up after killing manually smbd and nmbd
on the first one, is a Red Hat 7.3 with Samba compil
the current one can't be accessed?
Massimiliano Mirra
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba