http://bugzilla.novell.com/show_bug.cgi?id=584710
http://bugzilla.novell.com/show_bug.cgi?id=584710#c18
James McDonough changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
InfoProvider|Joachim.Reichelt@helmholtz- |
|hzi.de |
Resolution| |INVALID
--- Comment #18 from James McDonough 2010-04-18 10:27:16 UTC ---
There is nothing wrong with libnss_wins. This is intended to be for client
systems doing wins/netbios broadcast lookups on the network of windows hosts,
generally. It is normal to send out a broadcast packet and wait to see if
anyone responds.
If you really need wins lookups to a wins server without broadcasts, look at
"name resolve order" in smb.conf. If you need broadcast lookups without
repeatedly trying after the first round of failures (the first attempt will at
least always wait a bit to see if there is a response), then use nscd to cache
negative lookups.
Perhaps you might not want wins lookups at all, or maybe directly wins server
lookups.
FYI the "unexpected.tdb" reads are checking to see if an unexpectedly receieved
packet matches, because there have been a number of broken microsoft systems
that return packets on the wrong port (answered by smbd instead of nmbd).
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.