Hi folks,
We're seeing an odd thing happening on about 8 out of 100 UNIX machines
running Samba 1.9.18p7. Mostly on HU-UX 10.20 systems, but at least once
on an IRIX 6.4 system.
The scenario:
- SAMBA up and running in this environment for about 2 years sharing UNIX
home directories with NT boxes.
- SAMBA set up to start via inetd.
- Had a plant shutdown over a weekend a month ago, all systems powered down
gracefully.
- When we started everying back up (with minimal hardware problems, if you
can believe that!!), about 8 of the systems would not start nmbd.
- Message in log.nmb was:
"bind failed on port 137 socket_addr=0.0.0.0 (Address already in
use)"
What we have done:
- Verified entries in /etc/services and NIS services map
- Verified entries in /etc/inetd.conf
- Could not find any other applications that are using port 137
Current workaround (/fix ?):
- Reboot system, cannot map drives from NT
- telnet to port 139 and then disconnect
- nmbd gets launched and all is well
- (now..here's the kick as a co-worker said) After that, all is well even
when
the machine is rebooted.
Might anyone have a clue as to what is going on here?
Thanks!
-Glenn
<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-<->-
<->-<->
Glenn J. Christman, WD8OMW, MCSE, MCP+I Email: gchristman@analysts-cle.com
Analysts International Phone: 330-796-1633
Cleveland, Ohio
