I have the following
     PDC:  Samba 3.0.37 on Solaris 10
     BDC1: Samba 3.0.37 on Solaris 10
PDC is configured to be the WINS server for everything, including XP Pro 
clients and other Samba machines.
PDC# testparm -v | grep master
Load smb config files from /etc/sfw/smb.conf
...
Server role: ROLE_DOMAIN_PDC
...
Press enter to see a dump of your service definitions
         preferred master = Yes
         local master = Yes
         domain master = Yes
PDC#
BDC1# testparm -v | grep master
Load smb config files from /etc/sfw/smb.conf
...
Server role: ROLE_DOMAIN_BDC
...
Press enter to see a dump of your service definitions
         preferred master = No
         local master = No
         domain master = No
BDC1#
I accidentally have BDC1 "local master = yes" initially but fixed
that.
I have not since restart smbd or nmbd on either machine.
On a windows machine, in the network neigborhood, I can rt click on both 
PDC and BDC1, and select properties and verify that the machine is 
showing as a Primary or Backup.
However, nbtstat on XP and nmblookup on Solaris do NOT show BDC1 as a 
domain controller.  Specifially I am looking for
     "MYDOMAIN <1c>  BDC1", to indicate that BDC1 is a domain
controller.
PDC# nmblookup -A PDC
Looking up status of .....
...
         ..__MSBROWSE__. <01> - <GROUP> H <ACTIVE>
         MYDOMAIN <1c> - <GROUP> H <ACTIVE>
         MYDOMAIN <00> - <GROUP> H <ACTIVE>
         MYDOMAIN <1d> -         H <ACTIVE>
         MYDOMAIN <1e> - <GROUP> H <ACTIVE>
         MYDOMAIN <1b> -         H <ACTIVE>
         MAC Address = 00-00-00-00-00-00
PDC# nmblookup -A  BDC1
Socket opened.
Looking up status of ...
         BDC1 <00> -         H <ACTIVE>
         BDC1 <03> -         H <ACTIVE>
         BDC1 <20> -         H <ACTIVE>
         MYDOMAIN <00> - <GROUP> H <ACTIVE>
         MYDOMAIN <1e> - <GROUP> H <ACTIVE>
         MAC Address = 00-00-00-00-00-00
As expected, the PDC shows up a domain controller and the primary domain 
controller ("<1b>.")
Nbstat under XP gives similar results.
The samba how-to documentation indicates that XP clients should choose a 
bdc  in preference to the pdc, which they never do.    Presumably if I 
shut down my PDC, XP clients will not be able to login to the network.
I am not sure whether wins.tdb is generated from wins.dat or vice 
versa.    If I delete BDC1 from wins.dat, the file will shortly be 
automatically recreated with the missing entries restored.
I don't know if I can or should add a static entry in WINS.DAT.  It 
would seem unnecessary since BDC1 is a WINS client of PDC.
Thanks
Actually, restarting nmbd on BDC1 does seem to have fixed this.
-------- Original Message --------
Subject: 	Samba BDC does not register in WINS as BDC
Date: 	Mon, 16 Nov 2009 15:52:25 -0500
From: 	Gaiseric Vandal <gaiseric.vandal at gmail.com>
Reply-To: 	gaiseric.vandal at gmail.com
To: 	samba at lists.samba.org
I have the following
     PDC:  Samba 3.0.37 on Solaris 10
     BDC1: Samba 3.0.37 on Solaris 10
PDC is configured to be the WINS server for everything, including XP Pro
clients and other Samba machines.
PDC# testparm -v | grep master
Load smb config files from /etc/sfw/smb.conf
...
Server role: ROLE_DOMAIN_PDC
...
Press enter to see a dump of your service definitions
         preferred master = Yes
         local master = Yes
         domain master = Yes
PDC#
BDC1# testparm -v | grep master
Load smb config files from /etc/sfw/smb.conf
...
Server role: ROLE_DOMAIN_BDC
...
Press enter to see a dump of your service definitions
         preferred master = No
         local master = No
         domain master = No
BDC1#
I accidentally have BDC1 "local master = yes" initially but fixed
that.
I have not since restart smbd or nmbd on either machine.
On a windows machine, in the network neigborhood, I can rt click on both
PDC and BDC1, and select properties and verify that the machine is
showing as a Primary or Backup.
However, nbtstat on XP and nmblookup on Solaris do NOT show BDC1 as a
domain controller.  Specifially I am looking for
     "MYDOMAIN<1c>   BDC1", to indicate that BDC1 is a domain
controller.
PDC# nmblookup -A PDC
Looking up status of .....
...
         ..__MSBROWSE__.<01>  -<GROUP>  H<ACTIVE>
         MYDOMAIN<1c>  -<GROUP>  H<ACTIVE>
         MYDOMAIN<00>  -<GROUP>  H<ACTIVE>
         MYDOMAIN<1d>  -         H<ACTIVE>
         MYDOMAIN<1e>  -<GROUP>  H<ACTIVE>
         MYDOMAIN<1b>  -         H<ACTIVE>
         MAC Address = 00-00-00-00-00-00
PDC# nmblookup -A  BDC1
Socket opened.
Looking up status of ...
         BDC1<00>  -         H<ACTIVE>
         BDC1<03>  -         H<ACTIVE>
         BDC1<20>  -         H<ACTIVE>
         MYDOMAIN<00>  -<GROUP>  H<ACTIVE>
         MYDOMAIN<1e>  -<GROUP>  H<ACTIVE>
         MAC Address = 00-00-00-00-00-00
As expected, the PDC shows up a domain controller and the primary domain
controller ("<1b>.")
Nbstat under XP gives similar results.
The samba how-to documentation indicates that XP clients should choose a
bdc  in preference to the pdc, which they never do.    Presumably if I
shut down my PDC, XP clients will not be able to login to the network.
I am not sure whether wins.tdb is generated from wins.dat or vice
versa.    If I delete BDC1 from wins.dat, the file will shortly be
automatically recreated with the missing entries restored.
I don't know if I can or should add a static entry in WINS.DAT.  It
would seem unnecessary since BDC1 is a WINS client of PDC.
Thanks