winbind trouble, maybe PDC too.

[Jeremy Allison]

On Tue, Nov 27, 2001 at 02:09:14PM -0800, Hans Rasmussen wrote:
> A quick preamble.  SAMBA 2.2.2, Redhat 6.2, Mandrake 8.1 Windows NT4.0sp6a
> PDC
> 
> Here is an excerpt from my winbind log.
> 
> Sending a packet of len 50 to (192.168.1.255) on port 137
> Received a packet of len 62 from (192.168.1.20) port 137
> nmb packet from 192.168.1.20(137) header: id=5433 opcode=Query(0)
> response=Yes
>     header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=Yes
>     header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
>     answers: nmb_name=DOMAIN<1c> rr_type=32 rr_class=1 ttl=300000
>     answers   0 char ......   hex E000C0A8000A
> Got a positive name query response from 192.168.1.20 ( 192.168.1.20 )
> bind succeeded on port 0
> Sending a packet of len 50 to (192.168.1.20) on port 137
> Sending a packet of len 50 to (192.168.1.20) on port 137
> could not find any domain controllers for domain DOMAIN
> 
> 
> 
> NMAP shows ports 137,138 and 139 as being open on both my client machine and
> my NTsp6a PDC.  smbpasswd -j DOMAIN -r PDC -U blahblah woked alright, it
> said i joined the domain.  If in my smb.conf file that I have password
> server = *, then nothing works and the log say DOMAIN PASSWORD SERVER NOT
> FOUND.  password server = PDC works though.  It appears that my PDC is not
> responding to requests from the my samba box.  Broadcast, LMHOSTS, and WINS
> have all been tried.  Everytime my PDC's IP is resolved, followed by the
> message of not being able to find any domain controllers.  Any clues out
> there??

I've just fixed this bug in the 2.2 and HEAD CVS sources.

The problem it seems is that a PDC seems sometimes not to respond
to a node status request on the '*#0' name (which we use to get the
"real" NetBIOS name of the PDC/BDC). I changed the lookup
code to request on the DOMAIN#1b name instead and it will respond
to a node status on this name.

Jeremy.