Michael Lueck wrote: > > Atrox wrote: >> Michael Lueck wrote: >>> So, how do you know Samba can not find itself? >> >> Well, server doesn't answer to nmblookup by broadcast: >> $ nmblookup -B 192.168.1.255 frontier >> querying frontier on 192.168.1.255 >> name_query failed to find name frontier >> >> If I query Samba via unicast, it answers OK: >> $ nmblookup -U frontier frontier >> querying frontier on 192.168.1.31 >> 192.168.1.31 frontier<00> >> >> For lo0 interface I get the error: Packet send failed to >> 127.255.255.255(137) ERRNO=Operation not permitted >> >> Should it be that way? > > What are you actually trying to do? I know nmblookup by name, but never > have to use it. >
The error "Operation not permitted" occures when I nmblookup without any flag, ie. "nmblookup frontier". Nmblookup queries lo0 as I have specified it in "interfaces" parameter. $ nmblookup frontier querying frontier on 192.168.1.255 querying frontier on 127.255.255.255 Packet send failed to 127.255.255.255(137) ERRNO=Operation not permitted name_query failed to find name frontier > <><><><><><> > > About logs, what is your smb.conf logging configuration? Ours is: > > log file = /var/log/samba/log.%m > Yep, I have the same. > which generates a separate log for each machine. First by IP address > (log.IPADDR) until the computer name of the host is learned. Then it > starts writing to log.machinename from then on. > > So I was asking do you get errors in the Samba logs that you are trying to > understand? > Yes, I understood. But I don't see anything unusual nor any errors there (in log.smbd, log.nmbd, log.frontier, log.192.168.1.31) when I do nmblookup.. -- View this message in context: http://www.nabble.com/Samba-can%27t-find-its-hostname-via-broadcast-tf4633404.html#a13358113 Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
