samba - Jun 2017 - Lowest functional level 2000 (4.6.4)

Unfortunately its an old setup that I’ve inherited from someone else.

From what i understand there was originally a windows sbs server and this samba
dc has replaced that. It was done when samba 4 was in early beta.

Thanks for the link i found that thread but as you say it doesn’t help.

Failing any kind of fix is there a way to import users/computers into a fresh
database?

On Mon, 5 Jun 2017 15:09:41 +0100
Danny Tipple <danny at trials-forum.co.uk> wrote:
> Unfortunately its an old setup that I’ve inherited from someone else.
> 
> From what i understand there was originally a windows sbs server and
> this samba dc has replaced that. It was done when samba 4 was in
> early beta.
> 
> Thanks for the link i found that thread but as you say it doesn’t
> help.
> 
> Failing any kind of fix is there a way to import users/computers into
> a fresh database?
Not sure if there is anything to dump the database, it would probably
need something like the classicupgrade tool that is used to upgrade an
NT4 domain.

You may be able to work around this, it all depends on what schema
version you have, see here to find out:

https://wiki.samba.org/index.php/AD_Schema_Version_Support

If you have schema version 47, then it may just be a case of
adding/changing a few attributes (I don't know which) and then running
samba_upgradedns and then tidying AD.

Of course this is very simplistic and may not work, I think somebody
like Andrew needs to jump in here, he definitely knows more about this
than I do ;-)

Rowland

Thanks Rowland.  I just checked the schema version and its 30.  So way old.

Ive been battling this some more today.

I setup a win2003 server and used ‘adprep’ from 2008r2 to update the schema to
version 47 and all works ok.

Problem is i then can’t replicate that back to the samba server due to lack of
proper DNS as far as i can tell. Replication works samba > windows but not
the other direction (can anyone provide a list of DNS records that should get
added samba side when i add a new domain controller?). I added a few DNS entries
manually which i saw were failing then got the following:

"the following error occurred during the attempt to synchronize naming
context”
"The remote system is not reachable by the transport”"

Does making the windows server the primary (how do you initialise the DNS
server?), retiring the current samba server, then adding a new one back, then
retiring the windows box seem like a sensible option?
> On 5 Jun 2017, at 16:00, Rowland Penny via samba <samba at
lists.samba.org> wrote:
> 
> On Mon, 5 Jun 2017 15:09:41 +0100
> Danny Tipple <danny at trials-forum.co.uk> wrote:
> 
>> Unfortunately its an old setup that I’ve inherited from someone else.
>> 
>> From what i understand there was originally a windows sbs server and
>> this samba dc has replaced that. It was done when samba 4 was in
>> early beta.
>> 
>> Thanks for the link i found that thread but as you say it doesn’t
>> help.
>> 
>> Failing any kind of fix is there a way to import users/computers into
>> a fresh database?
> 
> Not sure if there is anything to dump the database, it would probably
> need something like the classicupgrade tool that is used to upgrade an
> NT4 domain.
> 
> You may be able to work around this, it all depends on what schema
> version you have, see here to find out:
> 
> https://wiki.samba.org/index.php/AD_Schema_Version_Support
> 
> If you have schema version 47, then it may just be a case of
> adding/changing a few attributes (I don't know which) and then running
> samba_upgradedns and then tidying AD.
> 
> Of course this is very simplistic and may not work, I think somebody
> like Andrew needs to jump in here, he definitely knows more about this
> than I do ;-)
> 
> Rowland
> 
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba