Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 787 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

Authentication - SBS 2003

pelumu
Some days ago I switched our AD-Server from SBS 2000 to SBS 2003.
Since that time I have problems with authentication against the AD. (ASG 7.401)

Sometimes the authentication works well sometimes not. The most time I have that problem is the evening. When authentication fails I get the following line in the log:

2009:04:13-17:54:51 ASG httpproxy[13626]: [0xb2f02d60] adir_auth_process_negotiate (auth_adir.c:311) gss_accept_sec_context: Key table entry not found

Any ideas?

Regards
Peter


This thread was automatically locked due to age.
Parents
  • 0
    Unless you get lucky with someone here who's had that problem, I think you'll have more luck in a Microsoft forum.  That looks to me like the Astaro is reporting failure of your AD to authorize.

    In any case, I have clients with SBS2003 and haven't seen this.  I must admit, that we never installed SBS2000 anywhere, so we never had to deal with an upgrade.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    I googled on '"Key table entry not found" Windows Server 2003' and found some things that might help you fix the problem on your Windows server.

    Kerberos/Troubleshooting - Joomla! Authentication Tools (JAuthTools)

    In another spot, I read that, prior to Win Server 2003R2, there were additional steps needed to allow Active Directory to work with Linux devices.  If you did an upgrade in place, then you might need to get the new ktpass.exe that corresponds to 2003R2.

    CHeers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    I've found the solution (simple but hard to find):

    In the AD-Useraccount the German 'Umlaut' in the last name was the problem!

    Regards
    Peter
  • 0 in reply to pelumu
    Please submit this to support.  That problem was not supposed to exist any more.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    That's a known problem. See knowledgebase Article # 172044

    Regards
    Peter
  • 0 in reply to pelumu
    Peter, that article appeared around V6.  I think the Astaro devlopment team thought it had resolved all of the issues with special characters, besonders Umlaute!
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0 in reply to pelumu
    Peter, that article appeared around V6.  I think the Astaro devlopment team thought it had resolved all of the issues with special characters, besonders Umlaute!
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data