search for: samsync

...running in a VM now, and just some > minor tweaks are needed going forward. Thanks to all who at least read and > certainly to Rowland for the help. Hope I can return the favor sometime. 'net rpc vampire' will never work against a Samba DC. We never implemented a sever-side for the SamSync (NETLOGON replication between and NT4-style PDC and BDC) protocol. This is different to AD replication which uses DRSUAPI, and that we do implement client and server side. Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, S...

Hello!! A customer of mine recently experienced a catastrophic failure of their PDC, and their BDC is not running as stable as we'd like. They've agreed to move PDC/BDC schema to Linux (currently they run NT4). So the question is: having ONLY a BDC available for SAM database, how do I extract that so I can replicate that to Samba and do a "transparent" upgrade (if possible)?

...effort, TP4 includes the work to better understand and implement the DRSUAPI replication protocols. By better understanding the needs of replication now, we can structure our databases so that their format will have to change less in future. We hope to use this replication function to replace the SamSync based Vampire process so effectively demonstrated since TP1, and to eventually join an Active Directory domain, as a replicating partner. Behind the scenes, much of the core infrastructure of Samba4 continues development: In Kerberos, we have continued to track the development of the Heimdal...

dear redhat, i examined a friend's system today, to help him configure it. assuming that he just "installed" from scratch the samba package, it appears that you have provided a default smb.conf file for redhat 6.1 that puts samba private configuration files in /etc. the suggested options, for example show "smbpasswd file = /etc/smbpasswd". this is REALLY bad. 1) you

Hola folks, After a few years of slowly phasing in various Linux and BSD platforms, the company I work for is willing to take a hard look at replacing its existing Windows NT domain controllers with a Linux/Samba combination. We only have about sixty people in our main office, but most of my experience is with smaller deployments. I'm not looking for step-by-step instructions, that's

...de(ad_dc) samba3.rpc.samr.passwords.lockout(ad_dc) samba3.rpc.bench-schannel1(nt4_dc) samba3.rpc.bench-schannel1(ad_dc) samba4.ldap.bench-cldap(ad_dc_default) samba4.rpc.samba3.sharesec on ncalrpc with seal,padcheck(ad_dc_ntvfs:local) samba4.rpc.samsync on ncacn_np with seal,padcheck(ad_dc_ntvfs) samba4.rpc.samba3-sessionkey on ncacn_np with seal,padcheck(ad_dc_ntvfs) samba4.rpc.samba3-getusername on ncacn_np with seal,padcheck(ad_dc_ntvfs) samba4.rpc.samba3-lsa on ncacn_np with seal,padcheck(ad_dc_ntvfs) samba4...

...ot; has been removed. The NT4-based commands were accidentially broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...ot; has been removed. The NT4-based commands were accidentially broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...henticate3 include and parser file - fix for difference in strsep and strtok semantics in nmbd - Ensure we don't change to a user that we can't get an NT_TOKEN for - Put back in BDC support in set_server_role() - added a 'net rpc samdump' command for dumping the whole sam via samsync operations (as a BDC) - don't use spnego in the client unless enabled in smb.conf - Added some new delta types discovered by Ronnie from ethereal - Cope with negative cache dns entries better - do not expose special files, only files, directories and links - attempts to simplify Samba'...

...ot; has been removed. The NT4-based commands were accidentially broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...ot; has been removed. The NT4-based commands were accidentially broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...ot; has been removed. The NT4-based commands were accidentially broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...ot; has been removed. The NT4-based commands were accidentially broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...NOTRUN, not implemented WinbinddDest NOTRUN, not implemented PidDest OK SelfDest OK BadDest OK BadCmd OK Debug OK ForceElection OK SamSync OK SamRepl OK DmallocMark OK DmallocChanged OK Shutdown OK DrvUpgrade OK CloseShare OK Ping OK Debuglevel OK P...

I am migrating an old but functional Samba 3.3.4 smbpasswd-based PDC to a new Samba 4.0-based VM. I planned to build the 4.0 as a BDC and then simply dcpromo it to my PDC, and then retire the old server. But I've come across two problems for which I'm needing some guidance. I've built the 4.0 box, extracted the original domain SID, and joined the machine to the domain. I can log into

...uot; has been removed. The NT4-based commands were accidentally broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...uot; has been removed. The NT4-based commands were accidentally broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...uot; has been removed. The NT4-based commands were accidentally broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...uot; has been removed. The NT4-based commands were accidentally broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...

...uot; has been removed. The NT4-based commands were accidentally broken in 2013, and nobody noticed the breakage. So instead of fixing them including tests (which would have meant writing a server for the protocols, which we don't have) we decided to remove them. For the same reason, the "samsync", "samdeltas" and "database_redo" commands have been removed from rpcclient. "net rpc vampire keytab" from Active Directory domains continues to be supported. vfs_aio_linux module removed ---------------------------- The current Linux kernel aio does not match...