samba - Feb 2012 - nmbd process and winbindd process can't start in multi network interface environement

Hello,
  Our OS is AIX 6100-06-05-1115 and SAMBA version is 3.3.12.0

  We have two network interfaces with different IPs. Now we restrict SAMBA
active in onf of the interface. SWAT and smbd can start. But nmbd and winbindd
processes can't start. And there is below warning info in log.nmbd and
log.winbindd. Please give your suggestions and thx.

pekwj42a-> # cat /usr/lib/smb.conf
# Samba config file created using SWAT
# from UNKNOWN (140.231.210.142)
# Date: 2012/02/09 12:45:34

[global]
        interfaces = eth6

[sap_capps]
        comment = sap AP1 interface
        path = /export/capps/AP1
        valid users = cn1wj026
        read only = No

[sap_interface]
        comment = sap AP1 interface
        path = /export/capps/AP1/Interface
        read only = No

[sap_edi]
        comment = sap AP1 edi
        path = /export/capps/AP1/edi
        read only = No
[sap_capps]
        comment = sap AP1 interface
        path = /export/capps/AP1
        valid users = cn1wj026
        read only = No
pekwj42a-> #


[2012/02/09 11:27:55,  0] nmbd/nmbd.c:main(850)
  nmbd version 3.3.12 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2012/02/09 11:27:55,  0] lib/interface.c:load_interfaces(546)
  WARNING: no network interfaces found
[2012/02/09 11:27:55,  0] nmbd/nmbd_subnetdb.c:create_subnets(206)
  create_subnets: No local IPv4 non-loopback interfaces !
[2012/02/09 11:27:55,  0] nmbd/nmbd_subnetdb.c:create_subnets(207)
  create_subnets: Waiting for an interface to appear ...
[2012/02/09 11:28:00,  0] lib/fault.c:fault_report(40)
  ==============================================================[2012/02/09
11:28:00,  0] lib/fault.c:fault_report(41)
  INTERNAL ERROR: Signal 11 in pid 7865238 (3.3.12)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2012/02/09 11:28:00,  0] lib/fault.c:fault_report(43)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2012/02/09 11:28:00,  0] lib/fault.c:fault_report(44)
  ==============================================================[2012/02/09
11:28:00,  0] lib/util.c:smb_panic(1673)
  PANIC (pid 7865238): internal error
[2012/02/09 11:28:00,  0] lib/util.c:log_stack_trace(1827)
  unable to produce a stack trace on this platform
[2012/02/09 11:28:00,  0] lib/fault.c:dump_core(231)
  dumping core in /var/cores/nmbd




[2012/02/09 12:42:59,  0] winbindd/winbindd.c:main(1130)
  winbindd version 3.3.12 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2012/02/09 12:42:59,  0] lib/interface.c:load_interfaces(546)
  WARNING: no network interfaces found
[2012/02/09 12:42:59,  0] lib/fault.c:fault_report(40)
  ==============================================================[2012/02/09
12:42:59,  0] lib/fault.c:fault_report(41)
  INTERNAL ERROR: Signal 11 in pid 8127146 (3.3.12)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2012/02/09 12:42:59,  0] lib/fault.c:fault_report(43)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2012/02/09 12:42:59,  0] lib/fault.c:fault_report(44)
  ==============================================================[2012/02/09
12:42:59,  0] lib/util.c:smb_panic(1673)
  PANIC (pid 8127146): internal error
[2012/02/09 12:42:59,  0] lib/util.c:log_stack_trace(1827)
  unable to produce a stack trace on this platform
[2012/02/09 12:42:59,  0] lib/fault.c:dump_core(231)
  dumping core in /var/cores/winbindd
Best Regards
Huang Hai Qing
No. 500 Dalian Road, Yangpu, Shanghai
200082, P.R. China
Softhandy: +86 21 38893546
Business E-mail: haiqing.huang at
siemens.com<blocked::blocked::mailto:haiqing.huang at siemens.com>

On 02/09/2012 06:14 AM, Huang, Hai Qing SLC CIT CMP SHA
wrote:
> Hello,
>    Our OS is AIX 6100-06-05-1115 and SAMBA version is 3.3.12.0
>
>    We have two network interfaces with different IPs. Now we restrict SAMBA
active in onf of the interface. SWAT and smbd can start. But nmbd and winbindd
processes can't start. And there is below warning info in log.nmbd and
log.winbindd. Please give your suggestions and thx.
>
> pekwj42a->  # cat /usr/lib/smb.conf
> # Samba config file created using SWAT
> # from UNKNOWN (140.231.210.142)
> # Date: 2012/02/09 12:45:34
>
> [global]
>          interfaces = eth6
Try en6 instead of eth6.

Cheers,
Christian

Good Morning Samba Team,

                We?ve been using Samba 3.4.8 and
OpenLdap as an NT domain PDC for a number of years, running on CentOS 5.7 64
bit.   In the
meantime I?ve been configuring other systems to use a multimaster OpenLdap
backend and implement TLS.  Obviously the
first system does not communicate with the other 2 systems (now registered as
BDC system on the same domain).

I have imported the user,group and computer groups into the
newer systems so that all password and user information is synchronized.  

We are also use Samba4Wins as our WINS server?..

Now my question:  I
can ?promote? the target system I want to as the PDC by making a few changes to
the smb.conf as well as the config file on the current PDC.  

When I use the old NT4 server manager tool the domain change
seems to take a few minutes to register, however many of the domain member
client systems (almost exclusively Windows XP Pro) are failing to recognize the
change and still use the old PDC to login.  


How can I force the client systems to recognize the new PDC
?Is this dependent on the WINS servers?


Thanks!