Here is a problem which I hope someone can help me out on. We have three
SCO Unix Systems in our office. Two are running samba but the third keeps
on giving me core dumps. Here is a breakout of each computer.
Computer #1
Acer 1000 Computer running 486/50 CPU
Adaptec SCSI Controller
SCO ODT 5.0.4 Operating System
Samba 2.0.5a - compiled with SCO cc.
Computer #2
Acer 7000 Computer running Pentium CPU
Adaptec SCSI Controller
SCO ODT 5.0.2 Operating System
Samba 2.0.5a - compiled with SCO cc.
Computer #3
Acer 9100 Computer running Pentium II/266 CPU
Adaptec SCSI Controller
SCO ODT 5.0.4 Operating System
Samba 2.0.5a - compiled with SCO cc.
Computers 1 and 2 run samba with no problems at all. However, Computer 3
gives me a core dump when ever I run the SAMBA startup program. Below is
what I get from the samba log. The operating system on computer #1 and #3
are the same. The ifconfig and route and basiclly the same except for the
computers own IP number. All three computers are on a 8 port HUB with
Two NT Servers (one Pent and one 486/50) and two Windows 98 machines
(both
Pents).
[1999/07/28 13:47:16, 1] nmbd/nmbd.c:(684)
Netbios namerserver version 2.0.5a started.
Copyright Andrew Tridgell 1994-1998
[1999/07/28 13:47:16, 0] lib/util_sock.c:(886)
bind failed on port 137 socket_addr=0.0.0.0 (Address already in use)
Can anyone offer suggestions. Am I doing something wrong with Computer #3
or is there something about SCO 5.0.4 and Acer 9100 computer that SAMBA
doesn't like. I added gcc to Computer #3 and recompiled samba only to get
the very same results.
+-----------------------------+
| Donald Bennett |
| ARK Computer Services, Inc. |
| 8027 Leesburg Pike, LL-150 |
| Vienna, Virginia 22182 |
| (Voice) 703-448-8833 |
| (Fax) 703-448-9104 |
+-----------------------------+
