Re: Cannot find domain controller
- From: "Austin Osuide" <austin@xxxxxxxxxxx>
- Date: Tue, 20 Nov 2007 13:23:44 -0000
Bingo!
As I said earlier, It's a generic event that's thrown when negotiated auth fails.
You potentially could have a host of causally related factors at play here. Understanding what the error means allows you, in addition to other events generated at the time to work through a logical differential diagnosis process and removes guess work.
Regards,
Austin
"Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx> wrote in message news:e0ETAzzKIHA.3848@xxxxxxxxxxxxxxxxxxxxxxx
In news:OBp0j.18091$bK4.9262@xxxxxxxxxxxxxxxxxxxxx,
Austin Osuide <austin@xxxxxxxxxxx> typed:
To quote Yakob's posting of the of the 7th at 09:07:
<quote>
C:\Documents and Settings\gtg.PROGRESSIVE>
reverse DNS is created
AD DNS progressive.local
When try to open Outlook warnings in System log: source LsaSrv Event
ID 40960 and 40961 category: SPNEGO (Negotiator) ,repeatdly and
source Kerberos Event ID 10 category none appears once.
When user logs on in the Application log source Userenv, event id
1054.
Hope we can find the answer.
</quote>
So, you see? Not a reverse lookup registration issue apparently.
The reflex action of attributing all cases of 40960/40961 errors to
PTR registrations is wrong. Also, if you understand how DNS works and
why you use PTR records, you'll see you can live without them.
Sometimes. Yes, some diagnostic tools will barf but it hardly ever
results in loss of functionality if you don't have them set. As I
mentioned earlier, the initial DNS rfcs' don't even mention PTR
records and in the MS KB we reviewed earlier, a second option is to
turn off the registration to reduce unnecessary network traffic.
Just trying to share my view of the problem and solution.
Regards,
Austin
Ahh, not trying to pick the post, but he said he has a reverse zone, however didn't mention if a PTR existed. Of course we'll assume one exists and this brings us back to square one.
There is one other thing that I've seen this associated with. It's something in the security policy of the local DC that could be causing it. Interestingly enough, we saw on XP desktops getting 40960 and 1058 errors. A PTR exists for it too. A restart fixes it. There is a KB fix that addresses it. I'm not saying it is related or not, but an interesting issue. I have to dig up my notes on this one. I'll post back.
Ace
.
- Follow-Ups:
- Re: Cannot find domain controller
- From: Ace Fekay [MVP]
- Re: Cannot find domain controller
- References:
- Re: Cannot find domain controller
- From: Jorge Silva
- Re: Cannot find domain controller
- From: Ace Fekay [MVP]
- Re: Cannot find domain controller
- From: Jorge Silva
- Re: Cannot find domain controller
- From: Ace Fekay [MVP]
- Re: Cannot find domain controller
- From: Austin Osuide
- Re: Cannot find domain controller
- From: Jorge Silva
- Re: Cannot find domain controller
- From: Austin Osuide
- Re: Cannot find domain controller
- From: Jorge Silva
- Re: Cannot find domain controller
- From: Austin Osuide
- Re: Cannot find domain controller
- From: Jorge Silva
- Re: Cannot find domain controller
- From: Austin Osuide
- Re: Cannot find domain controller
- From: Ace Fekay [MVP]
- Re: Cannot find domain controller
- Prev by Date: Re: User privilege caching in Active Directory?
- Next by Date: Re: migration tool error
- Previous by thread: Re: Cannot find domain controller
- Next by thread: Re: Cannot find domain controller
- Index(es):
Relevant Pages
|
Loading