Re: nmbd problem?

[Michael Heldebrant <hmike@portalofevil.com>]

On Sat, 2001-12-29 at 15:39, Russ Cook wrote:
> Attached is an excerpt from the syslog of one
> of my Debian boxes.  It is the gateway for
> my home LAN, consisting of two Debian boxes
> and two Windows boxes.  P633 is one of the
> Windows boxes.  Can anyone tell me what
> the syslog excerpt indicates?
> ----
> 

> Dec 29 06:28:04 p75 nmbd[11564]: connect from p633
> Dec 29 06:28:05 p75 inetd[3527]: /usr/sbin/tcpd: exit status 0x1
> Dec 29 06:28:05 p75 nmbd[11565]: connect from p633
> Dec 29 06:28:05 p75 inetd[3527]: /usr/sbin/tcpd: exit status 0x1
> Dec 29 06:28:05 p75 nmbd[11566]: connect from p633
> Dec 29 06:28:05 p75 inetd[3527]: /usr/sbin/tcpd: exit status 0x1
> Dec 29 06:28:05 p75 nmbd[11567]: connect from p633
> Dec 29 06:28:05 p75 inetd[3527]: /usr/sbin/tcpd: exit status 0x1
> Dec 29 06:28:05 p75 nmbd[11568]: connect from p633
> Dec 29 06:28:05 p75 inetd[3527]: /usr/sbin/tcpd: exit status 0x1
> Dec 29 06:28:05 p75 nmbd[11569]: connect from p633

I get this every now and then.  Check your hosts.allow and hosts.deny
files with tcpdchk to see if you have any problems.  Then once you've
twiddled to your liking restart inetd and kill all nmbd processes and
let them respawn automatically.  For some reason nmbd goes nuts every
now and then and starts either looping or getting these types of
errors.  Perhaps a more enlightened samba guru can provide the reasons
why.

--mike