I did that already and it was samba (the hanging one)

Eric Jansen
> -----Original Message-----
> From: Michael L Gueterman [mailto:[log in to unmask]]
> Sent: Monday, July 09, 2001 9:59 AM
> To: Jansen, Eric; [log in to unmask]
> Subject: RE: [HP3000-L] samba unreachable from some pc's and not from
> others
>
>
> Eric,
>
>   I'm not sure what is causing the lock-out situation that
> you describe, but the error message shown in the log.smb file
> is saying that something other than that iteration of SMBD has
> already grabbed port 139 on your HP 3000.  If that "something"
> happens to be other than a prior occurrence of SMBD (maybe
> the older HP Resource Sharing product?), then that would cause
> a similar set of problems.  The next time that occurs, you can
> use NETTOOL.NET.SYS (after it starts, hit 'C') and look for
> port 139.  See what it is that is holding it open.  Maybe that
> will give you a hint.
>
> Regards,
> Michael L Gueterman
> Easy Does It Technologies LLC
> http://www.editcorp.com
> voice: 888.858.EDIT or 573.368.5478
> fax:   573.368.5479
> --
>
> Eric wrote:
> <snip>
>
> >After some time of working fine; sometimes weeks, sometimes
> hours; samba is
> >unreachable from some pc's.
> >We don't really see a certain scenario in which it happens
> neither do we
> >have problems with certain pc's, they differ every time.
> >
> >
> >log.smb error:
> >-------------
> >Added interface ip=<system ip> bcast=<bcast addr> nmask=<nmask>
> >07/06/01 15:05:12 loaded services
> >standard input is not a socket, assuming -D option
> >Unsupported Samba/iX 0.7 by [log in to unmask] 4/97
> >07/06/01 15:05:12 staying in job mode on MPE
> >bind failed on port 139 socket_addr=0 (Address already in use)
> <snip>
>
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *