Displaying 5 results from an estimated 5 matches for "inrelev".
Did you mean:
aprelev
2020 Jul 22
1
Failed to modify SPNs
Adam, you already tried my suggestions?
What do you see here:
> Failed to modify SPNs on CN=SEC-CON03,CN=Computers,DC=domain,DC=com:
> acl: spn validation failed for ...
^^^^^^
So read the links below and post your results
The event id you showed, for now can be ignored. Inrelevant (for now).
And mostlikly wil disapear when you added/fixed the "correct" spn's
On topic for that event id you showed.
https://support.microsoft.com/en-us/help/935834/how-to-enable-ldap-signing-i
n-windows-server
The fix.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
&...
2006 Jan 20
1
RFE: centos-announce subject line rearrange
...horten somehow
the subject line? solutions:
- drop the name of the list (ie: [CentOS-announce] )
- drop the CESA reference number (ie: CESA-2006:0160 )
- or simple rearrange the subject eg into:
[CentOS-announce] CentOS 3 ia64 kernel - CESA-2006:0140 Important
security update
for me it's totaly inrelevant the solution just move the package name
somehow left.
yours.
just my 2c.
--
Levente "Si vis pacem para bellum!"
2015 Jul 11
5
Re: Migrate Win2k3 to KVM
Hi,
Do you need the exact error message (the codes)?
I don't want Virtio. I want to boot my image first.
As I mentioned I can't use the mergeide.req on the physical machine but I
can do anything with the image (if I don't het error messages from the
virt-win-reg).
I don't know if my restore to iSCSI volume was perfect. There wasn't any
error messages and the imag is able to
2020 Jul 22
4
Failed to modify SPNs
Hi all
my samba version is 4.12.5 and when a sql server windows machine join
the domain, It shows error in samba :
Failed to modify SPNs on CN=SEC-CON03,CN=Computers,DC=domain,DC=com:
acl: spn validation failed for
spn[E3514235-4B06-11D1-AB04-00C04FC2DCD2-ADAM/SEC-CON03:389] uac[0x1000]
account[SEC-CON03$] hostname[SEC-Con03.domain.com] nbname[DOMAIN]
ntds[(null)] forest[domain.com]
2015 Jul 11
8
Re: Migrate Win2k3 to KVM
Hi,
The error line is:
*** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000)
Nothing more! (Of course there are some inrelevant text line about chkdsk,
etc.)
> Basically, what's required is the "STOP:" line + the image where it
> fails (so, the line below). Image being likely to be NTOSKRNL.EXE
>
Nothing about NTOSKRNL.EXE on the blue screen!
> > I don't want Virtio. I want to boot my...