nmblookup bug in 3.0alpha24 ?

[Guillaume LACHENAL]

Hi,

We're running a 3.0alpha24 WINS (+PDC) server :

 > $ grep wins /etc/smb.conf
 > wins support = yes
 > name resolve order = wins

Querying "NT4PDC" (correctly registred in wins.dat) with
'net lookup host NT4PDC' is OK

 > $ net lookup host NT4PDC
 > 192.168.A.B

Querying this host with 'nmblookup' failed

 > $ nmblookup -d 10 -U localhost NT4PDC
(...)
 > querying NT4PDC on 127.0.0.1
 > Sending a packet of len 50 to (127.0.0.1) on port 137
 > read_udp_socket: lastip 127.0.0.1 lastport 137 read: 56
 > parse_nmb: packet id = 16887
 > Received a packet of len 56 from (127.0.0.1) port 137
 > nmb packet from 127.0.0.1(137) header: id=16887 opcode=Query(0) 
response=Yes
 >    header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes
 >    header: rcode=3 qdcount=0 ancount=1 nscount=0 arcount=0
 >    answers: nmb_name=NT4PDC<00> rr_type=32 rr_class=1 ttl=0
 > Negative name query response, rcode 0x03: The name requested does not 
 > exist.
 > name_query failed to find name NT4PDC

Our wins.dat is as follow :

 > $ cat wins.dat
 > VERSION 1 0
 > "__MSBROWSE__#01" 1055101688 255.255.255.255 e4R
 > "NT4PDC#00" 1055113567 192.168.A.B 64R
 > "NT4PDC#03" 1055113567 192.168.A.B 64R
 > "NT4PDC#20" 1055113567 192.168.A.B 64R
 > "SAMBAPDC#00" 1055072307 192.168.C.D 66R
 > "SAMBAPDC#03" 1055072307 192.168.C.D 66R
 > "SAMBAPDC#20" 1055072307 192.168.C.D 66R
 > "TESTDOMAIN#00" 1055113567 255.255.255.255 e4R
 > "TESTDOMAIN#1b" 1055072307 192.168.C.D 64R
 > "TESTDOMAIN#1c" 1055113567 192.168.C.D e4R
 > "TESTDOMAIN#1e" 1055072307 255.255.255.255 e4R

no bugreport found in bugzilla 3.0/HEAD, but I can fill up one if usefull
(as the 'net' utility is introduced in 3.0 let me think that 'nmblookup' 
will be soon deprecated/removed)

Best regards,

  -Guillaume-