On Tue, February 7, 2017 14:29, Alnis Morics wrote:> May I ask an off-topic question? > > James, does saying "samba43" mean you installed this FreeBSD port or > package? Which is known to crash during provisioning as DC. Did you > find the solution to that issue? >Samba43 was installed on FreeBSD-10.3 as a binary package using the pkg utility. Other than ignorance I had no problems with provisioning a Domain with it. On the other hand Samba44 could not be successfully provisioned at the time I was setting Samba up which is why we went with Samba43. The ports entry for Samba44 no longer shows the reservation respecting provisioning so I infer that the problem is solved. I will find out shortly as I am about to install a second DC and I plan on using Samba44 on FreeBSD-11.0. If it succeeds i will drop you a note. Regards, -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3
On Wed, 8 Feb 2017 10:40:34 -0500 "James B. Byrne via samba" <samba at lists.samba.org> wrote:> > On Tue, February 7, 2017 14:29, Alnis Morics wrote: > > May I ask an off-topic question? > > > > James, does saying "samba43" mean you installed this FreeBSD port or > > package? Which is known to crash during provisioning as DC. Did you > > find the solution to that issue? > > > > Samba43 was installed on FreeBSD-10.3 as a binary package using the > pkg utility. Other than ignorance I had no problems with provisioning > a Domain with it. On the other hand Samba44 could not be successfully > provisioned at the time I was setting Samba up which is why we went > with Samba43. > > The ports entry for Samba44 no longer shows the reservation respecting > provisioning so I infer that the problem is solved. I will find out > shortly as I am about to install a second DC and I plan on using > Samba44 on FreeBSD-11.0. If it succeeds i will drop you a note. > > Regards, >I tried provisioning Samba44 on Freebsd 11 a couple of days ago and it segfaulted, so if you do get it to work, please let us know. Rowland
On Wed, February 8, 2017 10:40, James B. Byrne wrote:> > Samba43 was installed on FreeBSD-10.3 as a binary package using the > pkg utility. Other than ignorance I had no problems with provisioning > a Domain with it. On the other hand Samba44 could not be successfully > provisioned at the time I was setting Samba up which is why we went > with Samba43. > > The ports entry for Samba44 no longer shows the reservation respecting > provisioning so I infer that the problem is solved. I will find out > shortly as I am about to install a second DC and I plan on using > Samba44 on FreeBSD-11.0. If it succeeds i will drop you a note. > > Regards, >I just completed the initial setup of Samba44 on Freebsd-11 using pkg. I have a simple bash script that I use to do this and it mostly went well. However, mostly means that some questions remain. At one point my script does this: host -t _msdcs which returns this: host: invalid type: _msdcs.BROCKLEY-2016.HARTE-LYNE.CA As I see the above described behaviour on the current DC (samba43) it does not appear to be fatal but I would like to know what this means. I also see this: samba-tool dns query localhost $HLL_REALM @ ALL Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for ncacn_ip_tcp:127.0.0.1[1024,sign,abstract_syntax=50abc2a4-574d-40b3-9d66-ee4fd5fba076/0x00000005,localaddress=127.0.0.1] NT_STATUS_INVALID_PARAMETER ERROR: Connecting to DNS RPC server 127.0.0.1 failed with (-1073741811, 'Unexpected information received') and samba-tool dns zoneinfo localhost $HLL_REALM -U administrator Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for ncacn_ip_tcp:127.0.0.1[1024,sign,abstract_syntax=50abc2a4-574d-40b3-9d66-ee4fd5fba076/0x00000005,localaddress=127.0.0.1] NT_STATUS_INVALID_PARAMETER ERROR: Connecting to DNS RPC server 127.0.0.1 failed with (-1073741811, 'Unexpected information received') Why does this occur and how is it fixed? Is this a configuration omission in our smb4.conf? Thanks -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3
On Wed, 8 Feb 2017 16:09:48 -0500 "James B. Byrne via samba" <samba at lists.samba.org> wrote:> > On Wed, February 8, 2017 10:40, James B. Byrne wrote: > > > > > Samba43 was installed on FreeBSD-10.3 as a binary package using the > > pkg utility. Other than ignorance I had no problems with > > provisioning a Domain with it. On the other hand Samba44 could not > > be successfully provisioned at the time I was setting Samba up > > which is why we went with Samba43. > > > > The ports entry for Samba44 no longer shows the reservation > > respecting provisioning so I infer that the problem is solved. I > > will find out shortly as I am about to install a second DC and I > > plan on using Samba44 on FreeBSD-11.0. If it succeeds i will drop > > you a note. > > > > Regards, > > > > I just completed the initial setup of Samba44 on Freebsd-11 using pkg. > I have a simple bash script that I use to do this and it mostly went > well. However, mostly means that some questions remain.Can I have a copy of your script ? Just so I can see what it is doing, you will probably have to send it to me directly, this list removes attachments.> > At one point my script does this: > > host -t _msdcs > > which returns this: > > host: invalid type: _msdcs.BROCKLEY-2016.HARTE-LYNE.CAI think you may be running into this: https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record> > As I see the above described behaviour on the current DC (samba43) it > does not appear to be fatal but I would like to know what this means. > > I also see this: > > samba-tool dns query localhost $HLL_REALM @ ALL > > Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for > ncacn_ip_tcp:127.0.0.1[1024,sign,abstract_syntax=50abc2a4-574d-40b3-9d66-ee4fd5fba076/0x00000005,localaddress=127.0.0.1] > NT_STATUS_INVALID_PARAMETER > ERROR: Connecting to DNS RPC server 127.0.0.1 failed with > (-1073741811, 'Unexpected information received') > > and > > samba-tool dns zoneinfo localhost $HLL_REALM -U administrator > Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for > ncacn_ip_tcp:127.0.0.1[1024,sign,abstract_syntax=50abc2a4-574d-40b3-9d66-ee4fd5fba076/0x00000005,localaddress=127.0.0.1] > NT_STATUS_INVALID_PARAMETER > ERROR: Connecting to DNS RPC server 127.0.0.1 failed with > (-1073741811, 'Unexpected information received') > > Why does this occur and how is it fixed? Is this a configuration > omission in our smb4.conf?More convinced it is the dns error, but what is interesting me is the 'omission in our smb4.conf'. the conf file should be created for you by the join. Rowland