samba - May 2003 - Sudden disconnect

hi all, just finished upgrading to 2.2.8a and things went well and without any
sign of a glitch. I was able to log in from windows to my FreeBSD box as root
just like before the upgrade.
but then, all of a sudden, the box was no longer available from windows 
no sign of anything going on with the FreeBSD computer 
I can putty into it and it seems fine 
nmbd and smbd show up in top 
what could have changed suddenly 
any thoughts? 

Tamir

Upgrading to 2.2.8a from what previous version?  Are the nmbd and smbd
running the ones from 2.2.8a?  "but then, all of a sudden, the box was
no longer available from windows" ... So it was working with 2.2.8a for
windows clients and then stopped?  What do you mean no longer available
from windows, do windows clients get an error message of some kind?

~ Daniel



On Thursday, May 01, 2003 1:54 AM, Tamir Halperin wrote:
> 
> hi all, just finished upgrading to 2.2.8a and things went 
> well and without any sign of a glitch. I was able to log in 
> from windows to my FreeBSD box as root just like before the upgrade. 
> but then, all of a sudden, the box was no longer available 
> from windows 
> no sign of anything going on with the FreeBSD computer 
> I can putty into it and it seems fine 
> nmbd and smbd show up in top 
> what could have changed suddenly 
> any thoughts? 
> 
> Tamir
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
> 
> 
-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.

> -----Original Message-----
> From: daniel.jarboe@custserv.com [mailto:daniel.jarboe@custserv.com]
> Sent: Thursday, May 01, 2003 12:55 PM
> To: Tamir Halperin; samba@lists.samba.org
> Subject: RE: [Samba] Sudden disconnect
> 
> 
> Upgrading to 2.2.8a from what previous version?
I believe it was 2.2.8_1, according to FreeBSD's pkg-version information.
> Are the nmbd and smbd
> running the ones from 2.2.8a?
I can't answer that for the abundance of my ignorance.
> "but then, all of a sudden, the box was
> no longer available from windows" ... So it was working with 
> 2.2.8a for windows clients and then stopped?
Yes!
> What do you mean no longer available from windows, do windows clients get
an
> error message of some kind?
No. I am prompted for a username and password, I provide the right ones and
I'm immediately prompted again.

I learned how to Tail the log file and this is what I got:

1. When the system boots the following is added to /var/log/messages -
May  1 00:45:33 john nmbd[140]: [2003/05/01 00:45:33, 0]
nmbd/nmbd.c:terminate(59)
May  1 00:45:33 john nmbd[140]:   Got SIGTERM: going down...
May  1 00:45:36 john syslogd: exiting on signal 15

2. When I browse enough of the Network Neighborhood to the point where I see the
FreeBSD box I get the following from /var/log/log.smbd:
[2003/05/01 21:46:46, 0] smbd/password.c:domain_client_validate(1558)
  domain_client_validate: could not fetch trust account password for domain
BROBUS
[2003/05/01 21:46:46, 0] passdb/pdb_ldap.c:ldap_open_connection(201)
  LDAPS option set...!
[2003/05/01 21:46:46, 0] passdb/secrets.c:fetch_ldap_pw(264)
  fetch_ldap_pw: no ldap secret retrieved!
[2003/05/01 21:46:46, 0] passdb/pdb_ldap.c:ldap_connect_system(308)
  ldap_connect_system: Failed to retrieve password for  from secrets.tdb
[2003/05/01 21:46:46, 0] passdb/pdb_ldap.c:ldap_open_connection(201)
  LDAPS option set...!
[2003/05/01 21:46:46, 0] passdb/secrets.c:fetch_ldap_pw(264)
  fetch_ldap_pw: no ldap secret retrieved!
[2003/05/01 21:46:46, 0] passdb/pdb_ldap.c:ldap_connect_system(308)
  ldap_connect_system: Failed to retrieve password for  from secrets.tdb
[2003/05/01 21:46:46, 0] smbd/password.c:domain_client_validate(1558)
  domain_client_validate: could not fetch trust account password for domain
BROBUS
[2003/05/01 21:46:46, 0] passdb/pdb_ldap.c:ldap_open_connection(201)
  LDAPS option set...!
[2003/05/01 21:46:46, 0] passdb/secrets.c:fetch_ldap_pw(264)
  fetch_ldap_pw: no ldap secret retrieved!
[2003/05/01 21:46:46, 0] passdb/pdb_ldap.c:ldap_connect_system(308)
  ldap_connect_system: Failed to retrieve password for  from secrets.tdb
[2003/05/01 21:46:46, 0] passdb/pdb_ldap.c:ldap_open_connection(201)
  LDAPS option set...!
[2003/05/01 21:46:46, 0] passdb/secrets.c:fetch_ldap_pw(264)
  fetch_ldap_pw: no ldap secret retrieved!
[2003/05/01 21:46:46, 0] passdb/pdb_ldap.c:ldap_connect_system(308)
  ldap_connect_system: Failed to retrieve password for  from secrets.tdb

3. With each unsuccessful attempt to provide the correct username and password:
[2003/05/01 21:48:35, 0] smbd/password.c:domain_client_validate(1558)
  domain_client_validate: could not fetch trust account password for domain
BROBUS
[2003/05/01 21:48:35, 0] passdb/pdb_ldap.c:ldap_open_connection(201)
  LDAPS option set...!
[2003/05/01 21:48:35, 0] passdb/secrets.c:fetch_ldap_pw(264)
  fetch_ldap_pw: no ldap secret retrieved!
[2003/05/01 21:48:35, 0] passdb/pdb_ldap.c:ldap_connect_system(308)
  ldap_connect_system: Failed to retrieve password for  from secrets.tdb
[2003/05/01 21:48:35, 0] passdb/pdb_ldap.c:ldap_open_connection(201)
  LDAPS option set...!
[2003/05/01 21:48:35, 0] passdb/secrets.c:fetch_ldap_pw(264)
  fetch_ldap_pw: no ldap secret retrieved!
[2003/05/01 21:48:35, 0] passdb/pdb_ldap.c:ldap_connect_system(308)
  ldap_connect_system: Failed to retrieve password for  from secrets.tdb
> ~ Daniel
Please forgive my ignorance. I'm not in a position to become a Samba
administrator at this time. I have a mail server that has to go up in the next
few days and not being able to get files off of the FreeBSD box (via Samba to
other windows boxes) I'm dead in the water. As soon as the mail server goes
up I'll have a lot more time to study all the ins and outs of Samba and
become proficient. I look forward to monitoring the maillist and providing as
much assistance as I can back to this wonderful community. But, alas, not yet.

In the meantime I can tell you that during the upgrade, I saw the option for
incorporating support for LDAP. I want to have such support in Samba because
I'm building an LDAP authentication database for the mail server anyway.
Therefore, LDAP will very conveniently replace the NTAS AD I'm currently
using for authentication. But, alas, not yet. I get the feeling that Samba is
trying to rely on LDAP for authentication right now. It should not. I believe
the solution involves me learning how to turn LDAP authentication off for now
and then turning it back on when I have a live LDAP available for
authentication.
> 
> 
> On Thursday, May 01, 2003 1:54 AM, Tamir Halperin wrote:
> > 
> > hi all, just finished upgrading to 2.2.8a and things went 
> > well and without any sign of a glitch. I was able to log in 
> > from windows to my FreeBSD box as root just like before the 
> upgrade. 
> > but then, all of a sudden, the box was no longer available 
> > from windows 
> > no sign of anything going on with the FreeBSD computer 
> > I can putty into it and it seems fine 
> > nmbd and smbd show up in top 
> > what could have changed suddenly 
> > any thoughts? 
> > 
> > Tamir
> > -- 
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  http://lists.samba.org/mailman/listinfo/samba
> >