similar to: samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)

Displaying 20 results from an estimated 3000 matches similar to: "samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)"

2017 Feb 07
2
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On 07/02/17 17:01, Andrew Bartlett via samba wrote: > On Tue, 2017-02-07 at 15:58 +1100, Tom Robinson via samba wrote: >> Hi, >> \ >> Next rid = 13001 >> krb5_init_context failed (Invalid argument) >> smb_krb5_context_init_basic failed (Invalid argument) >> # >> >> Is this a CentOS 6/7 difference issue or is the classicupgrade broken >> for
2017 Feb 09
3
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On Thu, 2017-02-09 at 10:53 +1100, Tom Robinson via samba wrote: > On 07/02/17 21:45, Tom Robinson via samba wrote: > > On 07/02/17 17:01, Andrew Bartlett via samba wrote: > > > On Tue, 2017-02-07 at 15:58 +1100, Tom Robinson via samba wrote: > > > > Hi, > > > > \ > > > > Next rid = 13001 > > > > krb5_init_context failed (Invalid
2017 Feb 08
0
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On 07/02/17 21:45, Tom Robinson via samba wrote: > On 07/02/17 17:01, Andrew Bartlett via samba wrote: >> On Tue, 2017-02-07 at 15:58 +1100, Tom Robinson via samba wrote: >>> Hi, >>> \ >>> Next rid = 13001 >>> krb5_init_context failed (Invalid argument) >>> smb_krb5_context_init_basic failed (Invalid argument) >>> # >>>
2017 Feb 15
2
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On 15/02/17 14:40, Tom Robinson via samba wrote: > On 13/02/17 10:18, Andrew Bartlett via samba wrote: >> On Mon, 2017-02-13 at 10:00 +1100, Tom Robinson via samba wrote: >>> On 12/02/17 03:13, Rowland Penny via samba wrote: >>>> On Fri, 10 Feb 2017 12:34:23 +1100 >>>> Tom Robinson via samba <samba at lists.samba.org> wrote: >>>>
2017 Feb 10
0
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On 09/02/17 11:14, Andrew Bartlett via samba wrote: > On Thu, 2017-02-09 at 10:53 +1100, Tom Robinson via samba wrote: >> On 07/02/17 21:45, Tom Robinson via samba wrote: >>> On 07/02/17 17:01, Andrew Bartlett via samba wrote: >>>> On Tue, 2017-02-07 at 15:58 +1100, Tom Robinson via samba wrote: >>>>> Hi, >>>>> \ >>>>> Next
2017 Feb 26
0
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On 17/02/17 07:58, Andrew Bartlett via samba wrote: > On Fri, 2017-02-17 at 07:48 +1100, Tom Robinson via samba wrote: >> Anyone? > Can you please post a gdb backtrace --full? > > Hi, I replied last week with a full backtrace but I didn't see my post come through. The email was only 266KB. Is the list server or SPAM filter blocking my previous message? In attempt to
2017 Jun 29
1
samba-tool SIGSEGV
Hi, Not sure if I should post in samba-technical or just samba list. Please advise. Back in February I was trying to do a samba-tool classicupgrade but kept getting SIGSEGV: https://lists.samba.org/archive/samba/2017-February/206409.html I didn't progress much after that. This week I've compiled samba-4.6.5 and installed that. Following the HOW-TO for classic upgrade
2017 Feb 16
0
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
Anyone? My next concern is codepages. The latest source (I've moved to 4.5.5 now) doesn't have any >> codepages. The RPM spec file I'm customising lists and wants to install them here: >> >> /usr/share/samba/codepages >> /usr/share/samba/codepages/lowcase.dat >> /usr/share/samba/codepages/upcase.dat >> /usr/share/samba/codepages/valid.dat >>
2017 Feb 12
2
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On Mon, 2017-02-13 at 10:00 +1100, Tom Robinson via samba wrote: > On 12/02/17 03:13, Rowland Penny via samba wrote: > > On Fri, 10 Feb 2017 12:34:23 +1100 > > Tom Robinson via samba <samba at lists.samba.org> wrote: > > > > > I've grabbed samba 4.5.4 and customised an existing rpm spec > > > file. > > > Still some issues there. > >
2017 Feb 26
2
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On 27/02/17 08:05, Tom Robinson via samba wrote: > On 17/02/17 07:58, Andrew Bartlett via samba wrote: >> On Fri, 2017-02-17 at 07:48 +1100, Tom Robinson via samba wrote: >>> Anyone? >> Can you please post a gdb backtrace --full? >> >> > Hi, > > I replied last week with a full backtrace but I didn't see my post come through. The email was only >
2017 Feb 16
2
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On Fri, 2017-02-17 at 07:48 +1100, Tom Robinson via samba wrote: > Anyone? Can you please post a gdb backtrace --full? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 862 bytes Desc: This is a digitally signed message part URL:
2017 Mar 06
2
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On Mon, 2017-03-06 at 08:37 +1100, Tom Robinson via samba wrote: > Full back trace provided in previous message. Still don't know why > samba-tool is crashing. Any help > is appreciated. Can you run testparm over the smb.conf file? I think it may be refusing to load it. Andrew Bartlett
2017 Feb 07
0
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On Tue, 2017-02-07 at 15:58 +1100, Tom Robinson via samba wrote: > Hi, > \ > Next rid = 13001 > krb5_init_context failed (Invalid argument) > smb_krb5_context_init_basic failed (Invalid argument) > # > > Is this a CentOS 6/7 difference issue or is the classicupgrade broken > for Samba Version > 4.2.14-SerNet? Any help is appreciated. Remove the include lines from
2018 Apr 23
1
NT_STATUS_TOO_MANY_OPENED_FILES on AD DCs
Hello guys Yesterday afternoon kerberos stopped working on both of our domain controllers. Unfortunately, I did not have time to examine it thoroughly, I needed to have it up asap. I know that RDP authentication took a few minutes, but it ended up being logged. LDAP was normally working. There were a lot of these messages in the logs: [2018/04/22 14:46:43.315705, 1]
2017 Feb 12
0
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On 12/02/17 03:13, Rowland Penny via samba wrote: > On Fri, 10 Feb 2017 12:34:23 +1100 > Tom Robinson via samba <samba at lists.samba.org> wrote: > >> I've grabbed samba 4.5.4 and customised an existing rpm spec file. >> Still some issues there. >> >> What replaces '--with-aio-support' in the configuration step now? >> > As far as I can
2017 Feb 15
0
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On 13/02/17 10:18, Andrew Bartlett via samba wrote: > On Mon, 2017-02-13 at 10:00 +1100, Tom Robinson via samba wrote: >> On 12/02/17 03:13, Rowland Penny via samba wrote: >>> On Fri, 10 Feb 2017 12:34:23 +1100 >>> Tom Robinson via samba <samba at lists.samba.org> wrote: >>> >>>> I've grabbed samba 4.5.4 and customised an existing rpm spec
2017 Feb 11
2
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On Fri, 10 Feb 2017 12:34:23 +1100 Tom Robinson via samba <samba at lists.samba.org> wrote: > > I've grabbed samba 4.5.4 and customised an existing rpm spec file. > Still some issues there. > > What replaces '--with-aio-support' in the configuration step now? > As far as I can see, nothing, see the 4.4.0 release notes here:
2017 Apr 17
2
doubt
On Mon, 17 Apr 2017 14:57:45 -0300 Luiz Guilherme Nunes Fernandes <narutospinal at gmail.com> wrote: > Well, i dont have sssd installed. OK, now we know that ;-) > > With winbind i install this packages: > yum install realmd oddjob oddjob-mkhomedir adcli samba-common > samba-common-tools krb5-workstation openldap-clients > policycoreutils-python samba-winbind-clients I
2019 Apr 25
2
Win7 client error after classicupgrade from S3 to S4
Hi. We're trying to upgrade an old NT domain to AD. It's our second upgrade, and while the first was successfull this one has raised some issues for existing Windows 7 clients. If we disconnect the computer from the domain and join it back to the new S4 AD it works. Existing clients throws this error in Samba: Kerberos: AS-REQ b1rd42nbtmp648$@NT4DOMAIN from ipv4:10.0.0.42:49472 for krbt
2018 Sep 05
2
Migration samba 3 to 4
Hello, Indeed when I copied the result for the mailing I made a mistake. MY.DOMAIN is a dummy name. The result of the migration command is Reading smb.conf WARNING: The "idmap backend" option is deprecated WARNING: The "idmap uid" option is deprecated WARNING: The "idmap gid" option is deprecated Provisioning Exporting account policy Exporting groups Severe DB