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 > likely be different). Part of me is thinking about upgrading the existing > 3.3.4 in place to a later 3.x -series version that might clean up such a > problem, *then* try the migration. > > Just don't want to disable the existing, working domain in the process - > which would more or less defeat the purpose of the exercise in the first > place :) > > > > > > > -- > View this message in context: http://samba.2283325.n4.nabble.com/Problems-in-SAMBA-3-3-to-4-0-migration-tp4680653p4680722.html > Sent from the Samba - General mailing list archive at Nabble.com.If you can upgrade to a later version, then this would be a wise move. It would also be wise to try anything else on a test machine, the last thing you need is a broken domain. Rowland
No broken domains!! That's for sure. Actually, I am leaning toward abandoning the "migration" effort as much as just replacing the server (as noted in the upgrade section of the Samba Guides) by manually copying the relevant files to the new SAMBA server. I'm beginning to realize that if whatever is broken is actually broken on the server I plan to retire, then time spent fixing it is in some measure wasted other than in gaining the knowledge of what went wrong. I will still spend some time on the migration tonight, but wholesale, manual replacement isn't far off the horizon. :) -- View this message in context: http://samba.2283325.n4.nabble.com/Problems-in-SAMBA-3-3-to-4-0-migration-tp4680653p4680726.html Sent from the Samba - General mailing list archive at Nabble.com.
One thing I discovered that may or may not be an element of some of these problems... I was inspecting the contents of my secrets.tdb file, and was observing the values stored in the AUTH_USER and AUTH_PASSWORD entries. The AUTH_PASSWORD stored is not correct for that AUTH_USER on that machine, which obviously is a potential problem. However, my reading indicates that these values generally relate to the value stored for LDAP updates, and there is no LDAP component in my situation. So, while it's wrong, I'm not sure it's relevant. Are there other situations where this user/pw combination is used? -- View this message in context: http://samba.2283325.n4.nabble.com/Problems-in-SAMBA-3-3-to-4-0-migration-tp4680653p4680730.html Sent from the Samba - General mailing list archive at Nabble.com.
* 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 *existing* 3.3.4 box to a later Samba incarnation. That *might* solve what I think now is a dependency issue that's subsequently caused wbinfo to stop working entirely. It *might* also solve whatever SMB signing issue is preventing net rpc vampire from working on the BDC. * Given the age of the setup, are there recommended "increments" for upgrading a 3.3.4 setup? Or should I be able to go to at least 3.6 (the last 3.x series release) directly in place without much risk? -David -- View this message in context: http://samba.2283325.n4.nabble.com/Problems-in-SAMBA-3-3-to-4-0-migration-tp4680653p4680750.html Sent from the Samba - General mailing list archive at Nabble.com.