samba - Oct 2015 - Replication Failing - NT_STATUS_IO_TIMEOUT

G'day Rowland,
> On 29/09/15 15:30, David Minard wrote:
>> I'm working on a brand new set of Samba DCs, as our University
changed it's domain name, so we thought we'd start from scratch. 
Working on 4.2.3 at the moment.
>>
>> I finally got the new DC to join, but I had to wait until things got
quiet (midnight-ish).
>>
>>
> Getting confused now, you originally posted this:
>
> I'm trying to commission another DC (number 5) in our production set
up,
> as we've opened up a new site.  All DCs are samba-4.0.25 self compiled.
> Yet now you say you are setting up a new domain, which is it ?
> If you are setting up a new domain, I hope you are not doing this in
> production.
     Sorry for the confusion.  I was just commenting to Marc that I am 
also running up a new set of samba servers, as he suggested moving to a 
supported version.    I'm loathed to jump up from this version to the 
latest on the production system.  Next, year, I hope the newer DCs I'm 
setting up with the new samba.domain will be in production, and the 
current production set will be retired.

     Our production version is 4.0.25, and this is the one with the 
problem described in this thread.

     I did end up getting samba4-05 to join, but even after a day or so, 
it did not have any of the domain users, groups, computers - just the 
standard stuff that comes with a new DC...  Strange.
>
> If you are setting up a new domain and self-compiling Samba, then you
> might as well use the latest version, this should reduce your chances of
> getting hit by a bug.
     Working on that.
>
> Rowland
>
-- 

Cheers,
David Minard.
Ph:    0247 360 155
Fax:    0247 360 770

School of Computing, Engineering, and Mathematics
Building Y - Penrith Campus (Kingswood)
Locked bag 1797
Penrith South DC
NSW 1797

[Sometimes waking up just isn't worth the insult of the day to come.]


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

On 01/10/15 05:22, David Minard wrote:
> G'day Rowland,
>
>> On 29/09/15 15:30, David Minard wrote:
>>> I'm working on a brand new set of Samba DCs, as our University 
>>> changed it's domain name, so we thought we'd start from
scratch.
>>> Working on 4.2.3 at the moment.
>>>
>>> I finally got the new DC to join, but I had to wait until things
got
>>> quiet (midnight-ish).
>>>
>>>
>> Getting confused now, you originally posted this:
>>
>> I'm trying to commission another DC (number 5) in our production
set up,
>> as we've opened up a new site.  All DCs are samba-4.0.25 self
compiled.
>> Yet now you say you are setting up a new domain, which is it ?
>> If you are setting up a new domain, I hope you are not doing this in
>> production.
>
>     Sorry for the confusion.  I was just commenting to Marc that I am 
> also running up a new set of samba servers, as he suggested moving to 
> a supported version.    I'm loathed to jump up from this version to 
> the latest on the production system.  Next, year, I hope the newer DCs 
> I'm setting up with the new samba.domain will be in production, and 
> the current production set will be retired.
>
>     Our production version is 4.0.25, and this is the one with the 
> problem described in this thread.
>
>     I did end up getting samba4-05 to join, but even after a day or 
> so, it did not have any of the domain users, groups, computers - just 
> the standard stuff that comes with a new DC...  Strange.
>
>>
>> If you are setting up a new domain and self-compiling Samba, then you
>> might as well use the latest version, this should reduce your chances
of
>> getting hit by a bug.
>
>     Working on that.
>
>>
>> Rowland
>>
>
I seem to remember that there was a problem with dns records and 
tombstones, have you tried searching for deleted dns records?

Rowland