Hello,
I am having problems getting nmbd to work as a WINS
server. nmblookup fails, as lookups from a PC.
If I turn the debugging way up, in the log.nmb, I see:
[1999/12/20 18:55:26, 4] libsmb/nmblib.c:debug_nmb_packet(109)
nmb packet from 160.101.120.62(44713) header: id=28190 opcode=Query(0)
response=No
header: flags: bcast=No rec_avail=No rec_des=No trunc=No auth=No
header: rcode=0 qdcount=1 ancount=0 nscount=0 arcount=0
question: q_name=YOSHIKO<00> q_type=32 q_class=1
[1999/12/20 18:55:26, 3]
nmbd/nmbd_incomingrequests.c:process_name_query_request(466)
process_name_query_request: Name query from 160.101.120.62 on subnet
UNICAST_SUBNET for name YOSHIKO<00>
[1999/12/20 18:55:26, 9] nmbd/nmbd_namelistdb.c:find_name_on_subnet(137)
find_name_on_subnet: on subnet UNICAST_SUBNET - name YOSHIKO<00> NOT
FOUND
[1999/12/20 18:55:26, 3]
nmbd/nmbd_incomingrequests.c:process_name_query_request(608)
UNKNOWN
[1999/12/20 18:55:26, 4] nmbd/nmbd_packets.c:reply_netbios_packet(918)
reply_netbios_packet: sending a reply of packet type: nmb_query
YOSHIKO<00> to ip 160.101.120.62 for id 28190
[1999/12/20 18:55:26, 4] libsmb/nmblib.c:debug_nmb_packet(109)
nmb packet from 160.101.120.62(44713) header: id=28190 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=YOSHIKO<00> rr_type=32 rr_class=1 ttl=0
This is a result of doing:
nslooup -U usagi yoshiko
Usagi is the samba server. It looks link nmb is never trying to lookup
the host. The global samba.conf parameter are:
[global]
workgroup = TIBCO-TKY
server string = Usagi Samba Server
update encrypted = Yes
log level = 9
log file = /local/samba/var/log.%m
name resolve order = host wins bcast
os level = 66
preferred master = Yes
wins proxy = Yes
wins support = Yes
unix realname = Yes
I am using Samba 2.0.6 on Solaris 2.6. Previously I was using 1.9.16p2
on SunOS 4.1.4. This suddenly started failing in a rather strange way,
after applying y2k patches to the OS. Sometimes lookups would work OK,
othertimes I would get back an IP of 0.0.1.16 or some such. Not sure
why that is either. I wanted to move away from SunOS anyway, so I'm
not to worried about that problem.
Thanks,
Andy
