We have several samba printservers and fileservers with
security=server validating against several PDC with ldap (samba 2.2.6).
I found a lot of ldap request like:
(uid=SAMBATESTPSERVER04)
beating the ldap servers: one before *each* validation in every print
job or share session.
I found this
On Thu, Oct 31, 2002 at 11:33:15AM +0100, Ignacio Coupeau wrote:
We have several samba printservers and fileservers with
security=server validating against several PDC with ldap (samba 2.2.6).
I found a lot of ldap request like:
(uid=SAMBATESTPSERVER04)
beating the ldap servers: one
Andrew Bartlett wrote:
On Thu, Oct 31, 2002 at 11:33:15AM +0100, Ignacio Coupeau wrote:
We have several samba printservers and fileservers with
security=server validating against several PDC with ldap (samba 2.2.6).
I found a lot of ldap request like:
(uid=SAMBATESTPSERVER04)
beating the
On Thu, Oct 31, 2002 at 12:20:25PM +0100, Ignacio Coupeau wrote:
Andrew Bartlett wrote:
On Thu, Oct 31, 2002 at 11:33:15AM +0100, Ignacio Coupeau wrote:
We have several samba printservers and fileservers with
security=server validating against several PDC with ldap (samba 2.2.6).
I
Andrew Bartlett wrote:
You could, but you really don't want to. Security=server
is really nasty. Fix whatever is causing Samba to pick the
wrong DC for secruity=domain. You can still specify the
server to use.
fixed (a wrong path :), we are using security = domain in the print
servers now.