[Samba] smbstatus shows no hostnames (3.5.1)
christo...@desy.de
I changed the samba version from 3.0.x to 3.5.1 and from that moment
something has changed with the nameresolving. The smbstatus mainly sjopws
IP adresses now:
[printserver] # smbstatus
Samba version 3.5.1
PID Username Group Machine
-------------------------------------------------------------------
14944 <uid> it 131.169.214.117 (131.169.214.117)
14944 <uid> it 131.169.214.117 (131.169.214.117)
Service pid machine Connected at
-------------------------------------------------------
IPC$ 14944 131.169.214.117 Mon Mar 22 11:43:05 2010
IPC$ 14944 131.169.214.117 Mon Mar 22 11:41:45 2010
I fiddled around with all the usual options with no success, DNS reverse
lookup works fine:
[printserver] # nslookup 131.169.214.117
Server: 131.169.40.200
Address: 131.169.40.200#53
117.214.169.131.in-addr.arpa name = zitpcx16179.desy.de.
When I go back to the 3.0.x version name resolution works fine again, what
am I missing ???
Any hints someone ?
cheers
~christoph
--
/* Christoph Beyer | Office: Building 2b / 23 *\
* DESY | Phone: 040-8998-2317 *
* - IT - | Fax: 040-8998-4060 *
\* 22603 Hamburg | http://www.desy.de */
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Christoph Beyer
by the way nmblookup looks fine, at the same time:
[printserver] /global/spool/samba_logs # nmblookup -T 131.169.214.117
querying 131.169.214.117 on 131.169.56.255
zitpcx16179.desy.de, 131.169.214.117 131.169.214.117<00>
????
Come on someone must have an opinion on this ?????
cheers
christoph
best regards
Volker Lendecke
> by the way nmblookup looks fine, at the same time:
>
> [printserver] /global/spool/samba_logs # nmblookup -T 131.169.214.117
> querying 131.169.214.117 on 131.169.56.255
> zitpcx16179.desy.de, 131.169.214.117 131.169.214.117<00>
>
> ????
You don't have those hosts in DNS?
Volker
christo...@desy.de
oc course I have I even did put thte one in question in '/etc/hosts' but
with no result :(
[printserver] # grep 131.169.214.117 /etc/hosts
131.169.214.117 zitpcx16179.desy.de zitpcx16179
[printserver] # nslookup zitpcx16179
Server: 131.169.40.200
Address: 131.169.40.200#53
Name: zitpcx16179.desy.de
Address: 131.169.214.117
[printserver] # nslookup 131.169.214.117
Server: 131.169.40.200
Address: 131.169.40.200#53
117.214.169.131.in-addr.arpa name = zitpcx16179.desy.de.
[printserver] /global/spool/samba_logs # grep -i dns /etc/nsswitch.conf
hosts: cluster files dns
cheers
christoph
On Wed, 24 Mar 2010, Volker Lendecke wrote:
> On Wed, Mar 24, 2010 at 12:02:47PM +0100, Christoph Beyer wrote:
>> by the way nmblookup looks fine, at the same time:
>>
>> [printserver] /global/spool/samba_logs # nmblookup -T 131.169.214.117
>> querying 131.169.214.117 on 131.169.56.255
>> zitpcx16179.desy.de, 131.169.214.117 131.169.214.117<00>
>>
>> ????
>
> You don't have those hosts in DNS?
>
> Volker
>
best regards
~christoph
--
/* Christoph Beyer | Office: Building 2b / 23 *\
* DESY | Phone: 040-8998-2317 *
* - IT - | Fax: 040-8998-4060 *
\* 22603 Hamburg | http://www.desy.de */
Volker Lendecke
> oc course I have I even did put thte one in question in '/etc/hosts' but
> with no result :(
Please send a debug level 10 log of smbd when such a client
connects.
Volker
christo...@desy.de
while debugging I observed something 'new' the name resolution works fine
on the samba server as long as I browse the server 'directly' on the
windows host (\\printserver)
It is not working when I look into a printerqueue etc on the windows host,
this goes along whith what I see in my working environment, a couple of
hostnames get resolved but very few.
So you can find to debug logfiles here, one with working name resolution
and one without working name resolution:
https://www.desy.de/~chbeyer/public/smbd_log_d10_working.tar
https://www.desy.de/~chbeyer/public/smbd_log_d10.tar
Thansk for the support !
cheers
christoph
On Wed, 24 Mar 2010, Volker Lendecke wrote:
> On Wed, Mar 24, 2010 at 12:16:27PM +0100, christo...@desy.de wrote:
>> oc course I have I even did put thte one in question in '/etc/hosts' but
>> with no result :(
>
> Please send a debug level 10 log of smbd when such a client
> connects.
>
> Volker
>
best regards
~christoph
--
/* Christoph Beyer | Office: Building 2b / 23 *\
* DESY | Phone: 040-8998-2317 *
* - IT - | Fax: 040-8998-4060 *
\* 22603 Hamburg | http://www.desy.de */
Volker Lendecke
> while debugging I observed something 'new' the name resolution works fine
> on the samba server as long as I browse the server 'directly' on the
> windows host (\\printserver)
>
> It is not working when I look into a printerqueue etc on the windows
> host, this goes along whith what I see in my working environment, a
> couple of hostnames get resolved but very few.
>
> So you can find to debug logfiles here, one with working name resolution
> and one without working name resolution:
>
> https://www.desy.de/~chbeyer/public/smbd_log_d10_working.tar
>
> https://www.desy.de/~chbeyer/public/smbd_log_d10.tar
>
> Thansk for the support !
Compared the logs, I don't see any difference in the
relevant pieces of them. I'm lost at this point. Someone
with Samba knowledge needs to look at the box itself.
Sorry,
Volker
Günter Kukkukk
I assume "hostname lookups = Yes" is set in smb.conf
During the last months i was also wondering about smbstatus output
regarding hostnames or simple IPs - i had the impression that somewhat
randomly some hostnames were not shown anymore, only their IP addresses.
I'm often running/testing very different samba versions - and the (different)
output of smbstatus didn't hit my interest/attention at all.
I'm now doing some further tests on the git master branch.
smbstatus e.g. relies on info stored in "sessionid.tdb" and "connections.tdb" ... ,
and the DNS related entries seem to be not properly collected and/or passed
over to the calling function (inside the server).
smbstatus just displays what the server previously has collected...
Cheers, Günter
Günter Kukkukk
did a lot of debugging and testing (using a recent samba git master branch).
I was not able to catch any misbehavior regarding samba's (reverse) DNS lookup.
More info is needed ...