samba - Jul 2017 - Samba ADS-member-server: FQDNs in /etc/hosts

Am 2017-07-11 um 11:43 schrieb Rowland Penny:
> On Tue, 11 Jul 2017 10:21:37 +0200
> "Stefan G. Weichinger via samba" <samba at lists.samba.org>
wrote:
> 
>> Am 2017-07-11 um 09:34 schrieb Stefan G. Weichinger via samba:
>>
>>> [2017/07/11 09:31:17.790046,  2]
>>>
../source4/dns_server/dns_query.c:1019(dns_server_process_query_send)
>>>   Not authoritative for 'SERVER', forwarding
>>> [2017/07/11 09:31:17.826966,  2]
>>>
../source4/dns_server/dns_query.c:1019(dns_server_process_query_send)
>>>   Not authoritative for 'SERVER', forwarding
>>>
>>> Note: the old netbios name of the DM server is "SERVER",
and that is
>>> what all the users use in their UNC paths.
>>>
>>> For some it works, for others not.
>>>
>>> I checked /etc/resolv.conf on DC and DM:
>>>
>>> nameserver 192.168.16.205 # IP of DC
>>> domain my.tld
>>
>> is it
>>
>> search my.tld
>>
>> or
>>
>> domain my.tld
>>
>> ?
>>
>> Should "dig server" work on both DC and DM, right?
>> It does not right now.
> 
> dig 'shorthostname' works on my DC, but I have to use dig FQDN on a
> Unix domain member

search
or
domain

?


// I set "guest OK" now and let the guy there connect the problematic
PCs.

maybe relevant:

DC: debian 9, samba 4.6.5
DM: debian 8.8, samba 4.5.10

On Tue, 11 Jul 2017 11:59:24 +0200
"Stefan G. Weichinger" <lists at xunil.at> wrote:
> Am 2017-07-11 um 11:43 schrieb Rowland Penny:
> > On Tue, 11 Jul 2017 10:21:37 +0200
> > "Stefan G. Weichinger via samba" <samba at
lists.samba.org> wrote:
> > 
> >> Am 2017-07-11 um 09:34 schrieb Stefan G. Weichinger via samba:
> >>
> >>> [2017/07/11 09:31:17.790046,  2]
> >>>
../source4/dns_server/dns_query.c:1019(dns_server_process_query_send)
> >>>   Not authoritative for 'SERVER', forwarding
> >>> [2017/07/11 09:31:17.826966,  2]
> >>>
../source4/dns_server/dns_query.c:1019(dns_server_process_query_send)
> >>>   Not authoritative for 'SERVER', forwarding
> >>>
> >>> Note: the old netbios name of the DM server is
"SERVER", and that
> >>> is what all the users use in their UNC paths.
> >>>
> >>> For some it works, for others not.
> >>>
> >>> I checked /etc/resolv.conf on DC and DM:
> >>>
> >>> nameserver 192.168.16.205 # IP of DC
> >>> domain my.tld
> >>
> >> is it
> >>
> >> search my.tld
> >>
> >> or
> >>
> >> domain my.tld
> >>
> >> ?
> >>
> >> Should "dig server" work on both DC and DM, right?
> >> It does not right now.
> > 
> > dig 'shorthostname' works on my DC, but I have to use dig FQDN
on a
> > Unix domain member
> 
> 
> search
> or
> domain
> 
> ?
I use 'search'
> 
> 
> // I set "guest OK" now and let the guy there connect the
problematic
> PCs.
> 
> maybe relevant:
> 
> DC: debian 9, samba 4.6.5
> DM: debian 8.8, samba 4.5.10
One way to find out, upgrade the DM with Louis's 4.6.5 packages

Rowland

Am 2017-07-11 um 12:05 schrieb Rowland Penny:
>>>> is it
>>>>
>>>> search my.tld
>>>>
>>>> or
>>>>
>>>> domain my.tld
>>>>
>>>> ?
> I use 'search'
thanks, me too
>> maybe relevant:
>>
>> DC: debian 9, samba 4.6.5
>> DM: debian 8.8, samba 4.5.10
> 
> One way to find out, upgrade the DM with Louis's 4.6.5 packages
sure... I have ~10 users working right now and ~5 waiting to connect to
their shares ... not exactly the best point in time. Maybe when they
have lunch ...