Michael Lueck wrote: > > Atrox wrote: >> Ah, yes, it's plain-text :) > > rrrr??? Should be binary, yet readable with cat. > >> But there's only 1 IP for the server, but there are 8 lines for the >> server: > > Sounds good. Probably not the same problem as I had then. Yes, I recall > multiple entries for the server. > > 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? > Are you seeing messages in the nmbd log? > Nope. I can debug it a little with "-d 5", but don't see anything intresting there either: ... Socket opened. querying frontier on 192.168.1.255 Sending a packet of len 50 to (192.168.1.255) on port 137 Sending a packet of len 50 to (192.168.1.255) on port 137 Sending a packet of len 50 to (192.168.1.255) on port 137 name_query failed to find name frontier -- Silver -- View this message in context: http://www.nabble.com/Samba-can%27t-find-its-hostname-via-broadcast-tf4633404.html#a13337205 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