similar to: Problems in SAMBA 3.3 to 4.0 migration

On Thu, 2015-02-19 at 22:06 -0800, soonerdave wrote: > ***** SUCCESS ***** > > After nearly a week of wrangling with this annoying and frustrating issue, > I'm delighted to report that I finally have EVERYTHING working. I was on the > cusp of giving up, but some diligent reading, lots and lots of testing, and > some long evenings finally paid off. I know this thread is

On 15/02/15 04:41, soonerdave wrote: > Update > > I did update my Samba 3.3.4 PDC to 3.6.24 after MUCH grief, overcoming (at > least) two library incompatibilities PLUS recalling the dusty old memories > that if you start with Slackware, you use Slack's samba installer, not the > source from Samba itself. > > I've fixed two library problems with libtalloc and

***** SUCCESS ***** After nearly a week of wrangling with this annoying and frustrating issue, I'm delighted to report that I finally have EVERYTHING working. I was on the cusp of giving up, but some diligent reading, lots and lots of testing, and some long evenings finally paid off. I know this thread is kinda buried now by virtue of its age, but I wanted to highlight the problems I had and

* sigh * this is becoming an exercise in frustration. * Performing a direct migration of my Samba 3.3.4 box by copying .tdb and related files to the new machine looks like a non-starter, as the group_mappings file went from an ldb to a .tdb format, and it appears the only conversion occurs during an in-place version upgrade. * The next step, it appears, looks to be some sort of upgrade to the

On 11/02/15 17:42, soonerdave wrote: > 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

On 12/02/15 18:42, soonerdave wrote: > I'll certainly give that a try this evening, Rowland. Thank you for the > suggestion and review. > > What concerns me about the wbinfo issue on the existing PDC is that there's > really no rationale for it *not* to work. Almost makes me wonder if there's > some red herring at hand, a mismatched library (granted the failure would

Hello According to NT4 Migration Using tdbsam Backend http://samba.org/samba/docs/man/Samba-Guide/ntmigration.html#id2604610 I would like to transfer PDC settings (users,groups sids) to BDC and later make from BDC PDC machine. I have Fedora Core 7 PDC(hostname serwer) and Centos 5.4 BDC (hostname serwer2) both on tdbsam backends. I have copied smb.conf, passwd,group,shadow,secrets.tdb files

Hi All, Hope someone here can help me ? *See end for background and system information... I'm looking for advice or links to clear documentation on the use and configuration of "net vampire" and it's ability to download PDC accounts with passwords intact. I have successfully used "net vampire" to synchronize my Samba BDC -- with my companies PDC. I've switched

John, We previously corresponded on our testing of Samba 3.0.0 RC4. Since then, we have downloaded the Samba 3.0.0 Release version for testing with some interesting results. The Setup Major Networks: Solaris (NIS), Windows Native NT4 Domain Our Test Plan We are testing Samba 3.0 as a candidate for replacing the old NT4 Domain. Being a complex production networking environment, we replicated

I'm helping out a small office upgrade their NT 4 PDC to Samba. It's a small office of 6 people, so tdbsam is being used. They keep having tape backup issues and other problems, so one of the reasons for the Samba migration is to allow me to SSH into their box and remotely administer it from home on evenings/weekends. Currently I'm testing the move using two dummy machines, and

I am replacing an old NT4.0 Server with a debian 4.0R1 etch Linux server (samba 3.0.24). This was with a completely fresh install of debian. My smb.conf is pretty simple: [global] workgroup = BUTLER netbios name = STAR3 passdb backend = tdbsam domain master = No domain logons = Yes os level = 33 add user script = /usr/sbin/useradd -m '%u' delete

So finally I got the net vampire to work. I had to roll back to commit 62e0a74 bypassing all the updates done by mdw at samba.org for now. Now the replication PDC1 is the first domain controller created by provision PDC2 is the second is the second domain controller created by net vampire on PDC1 I added user using "net newuser testuser1" in few seconds it appeared on PDC2 using the

Hi, Rowland, and thanks for the reply. The PDC OS is Slackware 13. The BDC OS is Slackware 14. The choice to use Samba 4.0 was merely due to its inclusion on the Slackware 14 distro. I'll worry about upgrading that once I have the migration complete. I will post the two machine's respective smb.conf's later today. -- View this message in context:

I just did a clean install of Fedora 9 onto a Pentium 4 machine. It is actually running SELinux enforcing, but I haven't found any errors related to that so far. It is running Samba 3.2.3-0.20. I am trying to migrate a Windows NT 4.0 domain with about 30 users and 30 computers onto a pure Samba setup, using Samba as the PDC and tdbsam. I have read the HOWTO guide extensively, and

Greetings everyone I finally succeeded in doing the seemingly most difficult thing, "following directions." I got my act together configuring the smb.conf and migrating using net rpc vampire into tdbsam. There are issues with this migration in which computer netbios names which are obviously all uppercase were not being created in /etc/passwd. I put my C cap on and converted the computer

Hello I am running a net work with a NT4PDC a NT4 BDC and attent to add samba BDC. I am following the brief section 28 of the Samba-Howto collection for samba head/3.0. * Adding the samba server as a BDC from NT server manager seems OK * Getting, recording domain sid is ok (see below) > rpcclient NT4PDC -U Administrator password: > lsaquery domain IMAGERIE has sid blablabla > net

I've done the net rpc vampire and gotten all the user and machine accounts from the NT server, I've test logged in, checked permissions, set groups, tested some of our odd apps and it all looks good. The problem I'm having is switching the desktops, and keeping the (non-roaming) profiles. I'd like to have it so everyone reboots their computer after the Samba switch over, and then

Hello, I get this error message when i try to join my Samba4 server to an existing domain: """ >./net vampire domain.local -Uadmin --realm=domain.local Password for [WORKGROUP\admin]: Become DC [(null)] of Domain[DOMAIN]/[domain.local] Promotion Partner is Server[dc1.domain.local] from Site[Default-First-Site-Name] Options:crossRef behavior_version[2] schema

I currently have a pure samba domain running off a Suse 9.1 machine. When I installed this domain I wasn't really comfortable with linux or LDAP so I used a tdbsam password file, and as there are only 30 or so users it seemed the way to go in the small amount of time I had available. Well, now I want to add a BDC to the mix I find I need to move to an LDAP backend. I only have two boxes at

Hello and good day, we're in the middle of migrating an old samba (3.0.11) pdc server, to a new server (3.0.23d) i thought i could do a NET VAMPIRE to make the new server sync with the old one. but ofcoz' that doesn't work (NT error code 0x1c010002) is there an other way to make these servers sync ? ea. can I do pdbedit -e tdbsam:/dump.tdb on the old server, and pdbedit -i