On 30/10/2013 3:49 a.m., Matteo De Lazzari wrote:
Now I have squid Version 3.3.9, but the problem still persist. This if
from cache.log
2013/10/29 15:07:49| negotiate_wrapper: Got 'YR
TlRMTVNTUAABAAAAB4IIogAAAAAAAAAAAAAAAAAAAAAFASgKAAAADw==' from squid
(length: 59).
2013/10/29 15:07:49| negotiate_wrapper: Decode
'TlRMTVNTUAABAAAAB4IIogAAAAAAAAAAAAAAAAAAAAAFASgKAAAADw==' (decoded
length: 40).
2013/10/29 15:07:49| negotiate_wrapper: received type 1 NTLM token
2013/10/29 15:07:49| negotiate_wrapper: Return 'TT
TlRMTVNTUAACAAAAEAAQADgAAAAFgomiMudf8qKFH9cAAAAAAAAAAKoAqgBIAAAABgEAAAAAAA9QAFIARQBWAEkARABPAE0AAgAQAFAAUgBFAFYASQBEAE8ATQABABoAUwBSAFYAUwBRAFUASQBEAFAAUgBPAFgAWQAEACgAcAByAGUAdgBpAGQAbwBtAC4AcAByAGUAdgBpAG4AZQB0AC4AaQB0AAMARABzAHIAdgBzAHEAdQBpAGQAcAByAG8AeAB5AC4AcAByAGUAdgBpAGQAbwBtAC4AcAByAGUAdgBpAG4AZQB0AC4AaQB0AAAAAAA=
'
2013/10/29 15:07:49| negotiate_wrapper: Got 'KK
TlRMTVNTUAADAAAAGAAYAIYAAAAYABgAngAAABIAEgBIAAAAGgAaAFoAAAASABIAdAAAAAAAAAC2AAAABYKIogUBKAoAAAAPRABFAEYAQQBWAEUAUgBJAEwAQQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBEAEUARgBBAFYARQBSAEkATACBrzocRC8vigAAAAAAAAAAAAAAAAAAAABvHsRiK+DEPUVqWMDAk2PS8BDbT/X3mBg='
from squid (length: 247).
2013/10/29 15:07:49| negotiate_wrapper: Decode
'TlRMTVNTUAADAAAAGAAYAIYAAAAYABgAngAAABIAEgBIAAAAGgAaAFoAAAASABIAdAAAAAAAAAC2AAAABYKIogUBKAoAAAAPRABFAEYAQQBWAEUAUgBJAEwAQQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBEAEUARgBBAFYARQBSAEkATACBrzocRC8vigAAAAAAAAAAAAAAAAAAAABvHsRiK+DEPUVqWMDAk2PS8BDbT/X3mBg='
(decoded length: 182).
2013/10/29 15:07:49| negotiate_wrapper: received type 216 NTLM token
NTLM Type: 3
Target Name: DEFAVERIL
User Name: Administrator
Workstation Name: DEFAVERIL
2013/10/29 15:07:49| negotiate_wrapper: Return 'NA =
NT_STATUS_NO_SUCH_USER
This is not a parser problem This is actually a user credentials not
existing problem. *NO SUCH USER*.
and again from command prompt all is good:
/usr/bin/ntlm_auth --username=provaproxy --password=Pass1word
--domain=PREVIDOM
NT_STATUS_OK: Success (0x0)
You are testing with different credentials to the ones which are failing.
Amos
