Closed Bug 489536 Opened 15 years ago Closed 15 years ago

SSPI InitializeSecurityContext failed

Categories

(MailNews Core :: Networking, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: l.tylski, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.0.9) Gecko/2009040821 Firefox/3.0.9
Build Identifier: 2.0.0.21 (20090302)

When try to use SSPI the error occurs InitializeSecurityContext failed [rc=-2146893053:]

Reproducible: Always

Steps to Reproduce:
1. Enable SSPI (default on Windows)
2. Set up account with secure logon
3. Try to login
Actual Results:  
Common login windows is shown

Expected Results:  
Autologon with SSPI

XP Pro with SP3
Ok this looks a lot like bug 276094 and bug 284538. I'm pretty sure that in the later case imap is not the only protocol not working.
Component: General → Networking
Product: Thunderbird → MailNews Core
QA Contact: general → networking
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.0.9)
> Gecko/2009040821 Firefox/3.0.9
> Build Identifier: 2.0.0.21 (20090302)
> 
> When try to use SSPI the error occurs InitializeSecurityContext failed
> [rc=-2146893053:]

  Hex         : 0x80090303
  Decimal     : -2146893053 (2148074243)
  Define(s)   : [winerror.h  ] SEC_E_TARGET_UNKNOWN
  Message     : The specified target is unknown or unreachable

This would seem to indicate an infrastructure issue, possibly in naming or in DNS resolution.

Are both domains part of the same forest, using the same DNS? If not, do you have correct DNS resolution between each domain? If they are in separate forests, do you have a forest level trust?
Please ignore text about forest and two domains.
Thunderbird isn't issue currently any messages if SSPI/Kerberos fail. So this error comes from somewhere else, anyway this is DNS/Kerberos problem you may not have appropriate DNS name or not matched Principial name.
Whiteboard: CLOSEME 2009-09-20
Whiteboard: CLOSEME 2009-09-20 → closeme 2009-09-20
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme 2009-09-20
You need to log in before you can comment on or make changes to this bug.