[Samba] diconnections when using roaming-profiles with samba4

[Rowland Penny]

On 06/09/14 14:36, steve wrote:
> On Sat, 2014-09-06 at 09:57 +0100, Rowland Penny wrote:
>> On 05/09/14 23:19, bugblatterbeast wrote:
>>> Am 06.09.2014 00:02, schrieb Rowland Penny:
>>>> On 05/09/14 22:46, bugblatterbeast wrote:
>>>>> Am 05.09.2014 23:21, schrieb Rowland Penny:
>>>>>> I would tend to agree with Greg here, I run S4, Bind9 and DHCP, all
>>>>>> on the same machine. From the client asking to renew its ip is only
>>>>>> microseconds, but I have seen instances (here on the list, not on
>>>>>> my setup) where windows clients have problems if they are allowed
>>>>>> to update their own records, that is why I asked how the OP had
>>>>>> setup DHCP.
>>>>> isc-dhcp-server with defaults (except for the recent changes in
>>>>> lease-time). The clients have dynamic addresses (default
>>>>> windows-configuration).
>>>> AH, so no reverse zone updates and probably the forward zone keeps
>>>> missing getting updated correctly, also don't add any Linux clients
>>>> or your problems will really start ;-)
>>>>
>>>> Rowland
>>>>
>>>>>> Rowland
>>>>> I think I'm fine for now and I will keep my eyes open. If you're
>>>>> still interested though, I could post the configuration files when
>>>>> I'm back at the office.
>>>>>
>>>>>
>>>>> nice regards, bbb
>>> Oh, thanks alot! If it's not too much trouble, could you discripe
>>> shortly, how you fixed the zone updates? Or are you using static ips?
>>> Take your time, I'll be off now.
>>>
>>> Nice regards, bbb
>> OK,
>> Short answer, see here:
>> http://blog.michael.kuron-germany.de/2011/02/isc-dhcpd-dynamic-dns-updates-against-secure-microsoft-dns/
>>
>> Rowland
> Hi
> I wonder if the dhcp topic is anything to do with where the dhcp box is
> situated? The only problem we have had with ddns updates is when we add
> a Linux client to the domain, and then only with the reverse zone[1].
> Our dhcp server sits between the domain and our internet connection. It
> also does wireless. All we have to configure is the start of the IP
> range and the number of IPs in the (what Cisco term) 'pool'. That's it.
> We never run out of IPs and the updates are transparent.
Thats how you set up any dhcp server
> [1]
> Our ddns updates are via sssd which in turn uses nsupdate -g. The only
> way to get the reverse zone updated is to delete the zone and then
> recreate it.

Do you mean that when a client updates its lease, all the reverse zone 
is deleted and then recreated ???

Rowland
> Just thinking out loud...
> Steve
>
>