Search squid archive

Re: squid proxy kerberos authentication failure. Help!!!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

If you get an NTLM token form the client it usually means that the client can not get the service principal for HTTP/<proxy> where <proxy> is the string (yes string if it is an IP it is used as a string) of the configured Browser proxy. If you take a wireshark capture on the client you should see on port 88 the TGS Requests and TGS Replies with the error code.

Markus


"flypast"  wrote in message news:1387662168302-4663967.post@xxxxxxxxxxxxx...

Hi,

BTW, below is the latest alert log
==> /var/log/squid/cache.log <==
2013/12/22 08:39:39| squid_kerb_auth: DEBUG: Got 'YR
TlRMTVNTUAABAAAAt4II4gAAAAAAAAAAAAAAAAAAAAAFASgKAAAADw==' from squid
(length: 59).
2013/12/22 08:39:39| squid_kerb_auth: DEBUG: Decode
'TlRMTVNTUAABAAAAt4II4gAAAAAAAAAAAAAAAAAAAAAFASgKAAAADw==' (decoded length:
40).
2013/12/22 08:39:39| squid_kerb_auth: WARNING: received type 1 NTLM token
2013/12/22 08:39:39| authenticateNegotiateHandleReply: Error validating user
via Negotiate. Error returned 'BH received type 1 NTLM token'



--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/squid-proxy-kerberos-authentication-failure-Help-tp4663964p4663967.html Sent from the Squid - Users mailing list archive at Nabble.com.





[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux