Bug 1288 - libnss_wins do not resolve everything but the server (NAME#20)
libnss_wins do not resolve everything but the server (NAME#20)
Product: Samba 3.0
Classification: Unclassified
Component: libsmbclient
All Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Depends on:
  Show dependency treegraph
Reported: 2004-04-22 16:11 UTC by German Marchenko
Modified: 2005-11-14 09:29 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description German Marchenko 2004-04-22 16:11:21 UTC
Linux-machines can not resolve several names (ping name) via libnss_wins 
("hosts: wins" in nsswitch.conf). Simultaneously Windows-machines can to 
resolve this several names (ping name). WINS-server provided by Samba and file 
wins.dat for this several names does not contain the servername (NAME#20), but 
always contains the machinename (NAME#00). And there are no shared resources 
(files and printers) on this several machines.
Comment 1 Gerald (Jerry) Carter 2004-04-22 17:38:53 UTC
This is a design decision.  It's an easy change but not one that 
I'm convinced we should make.  search for 0x20 in wins.c and change 
that to 0x00.

Mail me directly if you want to try to convince me that we should
change the current behavior.  I'm closing this one as won't fix for 
Comment 2 German Marchenko 2004-04-23 13:06:51 UTC
According to Samba documentation "it will be possible to ping any MS Windows 
machine by its NetBIOS  machine name, as long as that machine is within the 
workgroup to which both the Samba machine and the MS Windows machine belong".
Please clarify me such desing decision.
Comment 3 Gerald (Jerry) Carter 2004-04-24 06:56:17 UTC
reopening for more discussion.
Comment 4 German Marchenko 2004-04-26 21:33:50 UTC
As I know, all Windows-machines register it's NAME#00, and only servers
(stations with shared files and/or printers) register it's NAME#20.
Not all Windows-machines have file and/or printer services. By default
Windows resolve NAMES#00 and can ping any machine. But libnss_wins can
not resolve Windows-machines without shares. I think it is strange.
I don't know why there was such design decision.
Please explain me this.
Comment 5 Gerald (Jerry) Carter 2004-04-27 06:09:40 UTC
<0x20> was chosen for historical reasons based on the DNS 
lookups in smbd.

But I'll give on this.  Never felt really good about 
it anyways.  Will fix for 3.0.3.
Comment 6 Gerald (Jerry) Carter 2005-08-24 10:18:51 UTC
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.
Comment 7 Gerald (Jerry) Carter 2005-11-14 09:29:14 UTC
database cleanup