Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 28 replies
  • Subscribers 1 subscriber
  • Views 16676 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Web Proxy: Key table entry not found

pneumatic
For whatever reason, certain hosts can no longer access the web through the Astaro web proxy in SSO under Active Directory due to the following error:

[FONT="Courier New"]httpproxy[9752]: [ 0x88cd510] adir_auth_process_negotiate (auth_adir.c:311) gss_accept_sec_context: Key table entry not found [/FONT]

Anyone?  I have put an authentication bypass in place for the affected hosts.  I have reset the computer accounts in AD and re-joined them to the domain.


This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to pneumatic
    I've deleted the Astaro box from the AD servers list, renamed it and re-joined it to no avail.


    Soemthing isn't right in the communication between the two then.  in the advanced section of authentication hit the prefect now button and see if that succeeds.  also check the enable backend sync on login option./

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

Children
  • 0 in reply to William Warren
    Prefetching doesn't help.  At this point, I'm at a loss...  Rebuild?
  • 0 in reply to pneumatic
    I have an open case with Astaro concerning a similar issue at one of my customer sites; there are a few hosts, out of about 40 or 50, that fail to authenticate using AD SSO; there appears to be something wierd happening with the proxy's hostname; it apparently is case sensitive when using Kerberos. The wierd thing in my case is that all clients use the same case for the entry, as it's being pushed out by Windows GPO.

    Try using the IP for the proxy setting in IE; this forces the SSO authentication to use NTLM instead of Kerberos; in our case, while Astaro figures out the Kerberos issue, this made it work.  If your problem sounds like ours, I highly recommend that you start a case with Astaro support so they can chase this problem down.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Try using the IP for the proxy setting in IE; this forces the SSO authentication to use NTLM instead of Kerberos; in our case, while Astaro figures out the Kerberos issue, this made it work.  If your problem sounds like ours, I highly recommend that you start a case with Astaro support so they can chase this problem down.


    Ding, Ding!

    WE HAVE A WINNER!

    Thanks, man.
Cookie Information Banner