Displaying 5 results from an estimated 5 matches for "negresult".
2008 Aug 29
2
SPNEGO NTLMSSP failure
Hi,
The cifs client that I am working on is having some problem with SPNEGO/NTLMSSP. Session Setup AndX is failing in the last exchange of NTLMSSP. The error I am getting is 0xC00000D(STATUS_INVALID_PARAMETER). I am also seeing the following message in the log
"spnego_parse_auth(466) spnego_auth_parse failed at 7. "
I am using Heimdal library to generate SPNEGO/NTLMSSP messages.
I
2018 Jun 25
2
Samba 4.7.1 Generating Core Dumps
...000', mechToken = {
data = 0x7ffcba8c556f "", length = 140723438245232}, mechListMIC = {data = 0x7fc21e396881 <asn1_peek_full_tag+81> "\204\300t\aD:t$\017t\024H\203\304H\270Z", length = 140471821547978},
targetPrincipal = 0x0}, negTokenTarg = {negResult = SPNEGO_ACCEPT_COMPLETED, supportedMech = 0x0, responseToken = {data = 0x0, length = 0}, mechListMIC = {data = 0x1 <Address 0x1 out of bounds>,
length = 140471821525470}}}
send_mech_types = <optimized out>
ok = <optimized out>
i = 0
n...
2016 Nov 05
2
Win10 forcing NTLMSSP when KRB5 desired
...Security Blob: a1819f30819ca0030a0100a10b06092a864882f712010202...
Offset: 0x00000048
Length: 162
GSS-API Generic Security Service Application Program Interface
Simple Protected Negotiation
negTokenTarg
negResult: accept-completed (0)
supportedMech: 1.2.840.48018.1.2.2 (MS KRB5 -
Microsoft Kerberos 5)
responseToken:
60818106092a864886f71201020202006f723070a0030201...
krb5_blob:
60818106092a864886f71201020202006f723070a0030201......
2016 Nov 03
2
Win10 forcing NTLMSSP when KRB5 desired
Hi all,
I've 4.5.1 Samba on a machine with SSSD 1.13.4 setup and joined with a
Windows Server 2012 domain. Everything works great for Windows 8.1 - I can
connect to the Samba share and get authenticated as a domain user and files
are created with the correct Windows domain username and group.
With a Windows 10 client, I get an 'Access Denied'. After some debugging,
I'm putting
2007 Jun 03
0
Samba/Winbind slow with Active Directory
...or this packet I see that it is the answer to
the client packet and it toke the request 52.48116500 seconds to
respond! I've noticed no specific packets indicating the server talking
to the AD server during those 52 seconds.
The response packet includes a SPNEGO section which reports that the
negResult is accept-completed. The supportedMech is returned as 'MS KRB5
- Microsoft Kerberos 5' After this packet the rest of the communication
is handled quickly and the Windows XP reports success on the share. The
whole process of getting to the share required 1 minute which is not
acceptable for...