[Samba] No responses, not a one?

[Linux Addict]

On Tue, Jul 28, 2009 at 11:45 AM, Wikked one <wikked1 at hotmail.com> wrote:

>
>
>
>
>
>
>
> Presently we are not using SSL and this parameter once again restored
> access to
> the shares.
> However when I make an attempt to access another Samba server I get the
> following error on the PDC.
> [2009/07/28 11:42:02, 0]
> passdb/passdb.c:pdb_increment_bad_password_count(1477)
>   pdb_increment_bad_password_count: pdb_get_account_policy failed.
>
>
>
>
> > Date: Tue, 28 Jul 2009 11:19:07 -0400
> > Subject: Re: [Samba] No responses, not a one?
> > From: drescherjm at gmail.com
> > To: wikked1 at hotmail.com
> > CC: samba at lists.samba.org
> >
> > On Tue, Jul 28, 2009 at 11:14 AM, Wikked one<wikked1 at hotmail.com> wrote:
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Good Morning List,
> > >                    After an upgrade to 3.3.6 on my CentOS 5.3 system I
> now cannot access the share at all. I get the following console error
> message :
> > > [2009/07/26 08:35:52,  0] lib/smbldap.c:smb_ldap_start_tls(656)
> > >  Failed to issue the StartTLS instruction: Connect error
> > >
> > > I looked for this parameter in the smb.conf file (Start TLS) but I
> think it's an LDAP config file
> > > (slapd.conf ?) If some can save me the trouble ,at any rate I can't
> access this system with any client....(hopefully it's related to the TLS
> option?)
> > > Thanks
> > >
> >
> > It should be. I mean if samba can not talk to ldap your shares should
> > not work. Do your other systems use SSL to connect to the ldap
> > servers? If not then
> >
> >
> >   ldap ssl = off
> >
> > John
>
> _________________________________________________________________
> NEW mobile Hotmail. Optimized for YOUR phone.  Click here.
> http://windowslive.com/Mobile?ocid=TXT_TAGLM_WL_CS_MB_new_hotmail_072009
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>


*"pdb_increment_bad_password_count*: pdb_get_account_policy failed. "

Obviously this has something to do with password policies. Did you make any
changes recently.

Set the log level to 10 and try accessing share. It will give you enough
information to see what is going on.