Re: [Samba] Problem joining Samba 4 to an older Samba 4 alpha 17
On Fri, 2013-01-18 at 13:48 +0100, Daniel Hedblom wrote: 2013/1/18 Andrew Bartlett abart...@samba.org On Fri, 2013-01-18 at 10:11 +0100, Daniel Hedblom wrote: Hi there, Im trying to join a samba 4.0.1 server to an older samba 4 alpha 17 server. Whatever i do the join is interrupted but i dont know what goes wrong. Dns is double checked and correct as is most other stuff. How can i get a better view of what is happening than this? Can it be the source domain that contains erroneous objects? My goal is to move the old server to a new one, maybe there are a better way of doing this? Suggestions? Honestly, upgrading in place is the best way to do this. Backup the old DC, upgrade in place, and start the 4.0.1 release. The role transfer stuff isn't as reliable as we would like, whereas in-place is. Thanks for answering so fast. Im trying to move to a new hardware at the same time, and the server is not easily upgraded as its an Resara Server with their own packages of Samba4. Not so sure i would be successfull if i upgrade. I would very much prefer if i could move the machine and user accounts somehow without doing nasty stuff to the original server. OK, so what I would suggest is setting up a new server, with the data from Resara. The way I would do it is provision a new Samba4 install, but use the same hostname, SID, domain and realm as your old server. Use the --host-ip parameter to point at your old server's IP. Then copy all the samba files to the matching locations on the new server (the main purpose of the provision is to help you find all those locations). Files to look for include the private dir (all of it), the sysvol folder and your DNS zone. The run the commands suggested in the upgrade code: samba-tool dbcheck --fix samba-tool ntacl sysvolreset source4/scripting/bin/samba_upgradedns Finally give it the same IP (at the end of the process), and then start it up. It should work - if it doesn't, then power down the new machine, go back to your old Resara server while you work out what is wrong. This will configure Samba to use the internal DNS server (the new default) and hopefully will migrate your file-based DNS zone into the AD database. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Problem joining Samba 4 to an older Samba 4 alpha 17
Hi there, Im trying to join a samba 4.0.1 server to an older samba 4 alpha 17 server. Whatever i do the join is interrupted but i dont know what goes wrong. Dns is double checked and correct as is most other stuff. How can i get a better view of what is happening than this? Can it be the source domain that contains erroneous objects? My goal is to move the old server to a new one, maybe there are a better way of doing this? Suggestions? Error joining to domain: Schema-DN[CN=Schema,CN=Configuration,DC=sesam,DC=lan] objects[402/1550] linked_values[0/0] Schema-DN[CN=Schema,CN=Configuration,DC=sesam,DC=lan] objects[804/1550] linked_values[0/0] Schema-DN[CN=Schema,CN=Configuration,DC=sesam,DC=lan] objects[1206/1550] linked_values[0/0] Schema-DN[CN=Schema,CN=Configuration,DC=sesam,DC=lan] objects[1550/1550] linked_values[0/0] Analyze and apply schema objects Partition[CN=Configuration,DC=sesam,DC=lan] objects[402/1674] linked_values[0/0] Partition[CN=Configuration,DC=sesam,DC=lan] objects[804/1674] linked_values[0/0] Partition[CN=Configuration,DC=sesam,DC=lan] objects[1206/1674] linked_values[0/0] Partition[CN=Configuration,DC=sesam,DC=lan] objects[1608/1674] linked_values[0/0] Partition[CN=Configuration,DC=sesam,DC=lan] objects[1674/1674] linked_values[94/0] Partition[DC=sesam,DC=lan] objects[100/100] linked_values[79/0] Partition[DC=sesam,DC=lan] objects[502/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[904/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[1306/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[1708/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[2110/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[2512/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[2914/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[3316/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[3718/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[4120/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[4522/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[4924/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[5326/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[5728/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[6130/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[6532/6594] linked_values[0/0] Partition[DC=sesam,DC=lan] objects[6694/6594] linked_values[1338/0] Partition[DC=sesam,DC=lan] objects[6694/6594] linked_values[1500/0] Partition[DC=sesam,DC=lan] objects[6694/6594] linked_values[1500/0] Partition[DC=sesam,DC=lan] objects[6694/6594] linked_values[1500/0] Partition[DC=sesam,DC=lan] objects[6694/6594] linked_values[1500/0] Partition[DC=sesam,DC=lan] objects[6694/6594] linked_values[1500/0] Partition[DC=sesam,DC=lan] objects[6694/6594] linked_values[1500/0] Partition[DC=sesam,DC=lan] objects[6694/6594] linked_values[811/0] ERROR(runtime): uncaught exception - (-1073741807, 'NT_STATUS_END_OF_FILE') File /usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py, line 175, in _run return self.run(*args, **kwargs) File /usr/lib/python2.7/dist-packages/samba/netcmd/domain.py, line 552, in run machinepass=machinepass, use_ntvfs=use_ntvfs, dns_backend=dns_backend) File /usr/lib/python2.7/dist-packages/samba/join.py, line 1104, in join_DC ctx.do_join() File /usr/lib/python2.7/dist-packages/samba/join.py, line 1014, in do_join ctx.join_finalise() File /usr/lib/python2.7/dist-packages/samba/join.py, line 812, in join_finalise ctx.send_DsReplicaUpdateRefs(nc) File /usr/lib/python2.7/dist-packages/samba/join.py, line 797, in send_DsReplicaUpdateRefs ctx.drsuapi.DsReplicaUpdateRefs(ctx.drsuapi_handle, 1, r) //danileh -- With best regards, Daniel Hedblom Sysadmin Phone: +46 (0) 620-68 22 02 Mobile: + 46 (0) 70 383 72 44 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Problem joining Samba 4 to an older Samba 4 alpha 17
On Fri, 2013-01-18 at 10:11 +0100, Daniel Hedblom wrote: Hi there, Im trying to join a samba 4.0.1 server to an older samba 4 alpha 17 server. Whatever i do the join is interrupted but i dont know what goes wrong. Dns is double checked and correct as is most other stuff. How can i get a better view of what is happening than this? Can it be the source domain that contains erroneous objects? My goal is to move the old server to a new one, maybe there are a better way of doing this? Suggestions? Honestly, upgrading in place is the best way to do this. Backup the old DC, upgrade in place, and start the 4.0.1 release. The role transfer stuff isn't as reliable as we would like, whereas in-place is. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Problem joining Samba 4 to an older Samba 4 alpha 17
2013/1/18 Andrew Bartlett abart...@samba.org On Fri, 2013-01-18 at 10:11 +0100, Daniel Hedblom wrote: Hi there, Im trying to join a samba 4.0.1 server to an older samba 4 alpha 17 server. Whatever i do the join is interrupted but i dont know what goes wrong. Dns is double checked and correct as is most other stuff. How can i get a better view of what is happening than this? Can it be the source domain that contains erroneous objects? My goal is to move the old server to a new one, maybe there are a better way of doing this? Suggestions? Honestly, upgrading in place is the best way to do this. Backup the old DC, upgrade in place, and start the 4.0.1 release. The role transfer stuff isn't as reliable as we would like, whereas in-place is. Thanks for answering so fast. Im trying to move to a new hardware at the same time, and the server is not easily upgraded as its an Resara Server with their own packages of Samba4. Not so sure i would be successfull if i upgrade. I would very much prefer if i could move the machine and user accounts somehow without doing nasty stuff to the original server. If i upgrade in place will a subsequent join of another DC be easier then? Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org //danielh -- With best regards, Daniel Hedblom Sysadmin Phone: +46 (0) 620-68 22 02 Mobile: + 46 (0) 70 383 72 44 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
