[Samba] net ads and wbinfo are painfully slow -- but they work

[Chris Stankevitz]

On Tue, Jan 31, 2017 at 2:45 PM, Rowland Penny via samba
<samba at lists.samba.org> wrote:
>> /etc/resolv.conf:
>> root at nickel:~ # cat /etc/resolv.conf
>> nameserver 192.168.11.5
>> nameserver 192.168.1.4
>> domain mydomain.local
>>
>
> I take it at least one of the above nameservers is the AD DC, is the
> other another AD DC ? If it isn't, then remove it. If they are both
> DCs, try changing the order.

They are both DCs.  I will try changing the order.  Is it possible for
me to restrict winbindd so that it attempt to only contact one of the
two DCs?  Once DC is local and another DC is remote (goes through a
firewall and is 80 ms ping time away).

> I would also change the 'domain mydomain.local' to 'search
> mydomain.local'

I will try.

> Is a firewall getting in the way ?

Possibly.  Winbind seems to prefer using the DC that is through a
firewall (see my comment above).

>> /etc/hosts:
>> 127.0.0.1               localhost localhost.mydomain.local
>> 192.168.11.3            nickel.mydomain.local nickel
>> 192.168.1.2             iron.mydomain.local iron
>
> I take it the machine has a fixed IP and as you are relying on dns to
> find the DC (as you should), you do not need the line that starts
> '192.168.1.2'

Yes, I agree.  I will remove it.

> Can you ping the DC from 'nickel', both by IP and name ?

Yes

> Is winbind actually running ?

Yes

Thanks again,

Chris