Am 05. Oct, 2001 schwätzte Thomas Mondoshawan Tate so:
> On Fri, Oct 05, 2001 at 01:48:33PM -0700, der.hans wrote:
> > moin, moin,
> >
> > I'm babysitting our samba server today, so, of course, it's misbehaving :(.
> >
> > What services should be listening?
> >
> > lsof | grep LISTEN
> >
> > I only get:
> >
> > smbd 4642 root 7u IPv4 2730881 TCP *:netbios-ssn
> > (LISTEN)
> >
> > The rest aren't from samba. WE do have slapd on the same box. That's
> > actually the service that's not responding, but I'm told the error is due to
> > smb.
> >
> > ciao,
> >
> > der.hans
>
> AFAIK, slapd shouldn't have anything to do with Samba -- it's its own daemon
> and uses the standard LDAP ports for communication (port 389 to be exact),
> unless the LDAP database is on a mounted Samba share. Is that the case?
Nah, LDAP db is on ext2 partition. I know it mostly shouldn't matter that
they're on the same box, but just in case someone knew of issues with using
samba and ldap together, specifically when they're on the same box, then I
wanted to make sure that was in the problem description :).
> Samba only opens one port for listening on the machine it's running on. An
> exact replica of your command 'lsof |grep LISTEN' on my working samba system
> results in exactly the same line. smbd is the only thing listening.
OK, cool. That's what I needed to know. Danke.
> Just to make sure, might want to use smbclient to check the status of the
> Samba server.
Couldn't get the samba server to respond to anything, which is why I was
looking into it.
> Also, slapd supports a monitoring interface -- might want to take a look at
> the information returned by it just to make sure it's working properly. The
> exact command would be "ldapsearch -s base -b cn=monitor 'objectclass=*'"
ldap was working fine the whole time.
ciao,
der.hans
--
#
der.hans@LuftHans.com home.pages.de/~lufthans/
www.DevelopOnline.com
# It's up to the reader to make the book interesting.
# An author has only the opportunity to make it uninteresting. - der.hans
(text/plain)