[Samba] netbios name resolution

[Tatar Kolos]

Hello,

> >I have a setting of log file = /var/log/samba/%m.log, and there are log 
> >files with netbios names and ip addresses too. (nbname.log, x.x.x.x.log).
> >
> This is the behavior by design (I believe) but at least it is 
> understandable once you know what is going on.  When a client connects, 
> the only thing you know about it is its IP address.  Even if the very 
> first thing it does is to query the network for naming related 
> information, or to be queried by the server for its name there is still 
> this name-less connection.  You should notice that most of these files 
> are 0 length.

The problem is that those files are not 0 length.

For example:
$ dig vendeg.[mydomain]
[..]
;; ANSWER SECTION:
vendeg.[mydomain]. 3600 IN      A       192.168.0.31
[..]

$ cat vendeg.log
[..]

[2005/04/14 15:15:57, 1] smbd/service.c:make_connection_snum(698)
  vendeg (192.168.0.31) connect to service install initially as user root 
(uid=0, gid=0) (pid 17536)
[2005/04/14 15:16:01, 1] smbd/service.c:make_connection_snum(698)
  vendeg (192.168.0.31) connect to service kolos initially as user kolos 
(uid=500, gid=100) (pid 17536)
[2005/04/14 15:16:08, 1] smbd/service.c:close_cnum(880)
  vendeg (192.168.0.31) closed connection to service install
::{2227a280-3aea-1069-a2de-08002b30309d}

[..]

$ cat 192.168.0.31.log
[..]

[2005/04/15 14:59:07, 1] smbd/service.c:make_connection_snum(698)
  192.168.0.31 (192.168.0.31) connect to service install initially as user 
root (uid=0, gid=0) (pid 2776)
[2005/04/15 14:59:15, 1] smbd/service.c:close_cnum(880)
  192.168.0.31 (192.168.0.31) closed connection to service install
[2005/04/16 18:38:24, 1] smbd/service.c:make_connection_snum(698)
  192.168.0.31 (192.168.0.31) connect to service install initially as user 
root (uid=0, gid=0) (pid 3346)
[2005/04/16 18:39:44, 1] smbd/service.c:close_cnum(880)
  192.168.0.31 (192.168.0.31) closed connection to service install

[..]

In these log snippets the services being connected to are "install" in 
both files, still one has the ip resolved and the other not.
Any ideas?

Thank you for the reply anyway.

> I know there was a better explanation of what is happening, but it came 
> down to  the fact that it was normal.

I understand, and this would make sense, but I suppose that's not the 
case.

Thanks,
-- 
Tatár Kolos
Archi-data Kft.