WMI Access Denied when incorrect DNS search order
- From: "Bobby" <bobby.owens@xxxxxxxxxxxxx>
- Date: 21 Apr 2006 08:38:50 -0700
Hi,
I was wondering if anyone could help me with the following problem I
came across.
One of our clients uses our software (A .NET windows service) to
perform remote WMI enquiries on 2 machines on the W2K3 domain and 1
machine that is a standalone server. The calls use the IP Address, not
the remote host name. The application would run more-or-less fine for
about 1-2 hours. There would be occasional "Call was canceled by the
message filter" messages, but would then recover.
After the 1-2 hours, all calls would return access denied and not
recover. If the service running the calls was restarted, all is fine
for another few hours, then same issues again. Usually, there were some
event log entries with the following info:
Source: LSASRV
Category: SPNEGO (Negotiator)
Event ID: 40960
Desc: The security system detected an authentication error for the
server RPCSS/xxx.xxx.xxx.xxx. "There are currently no logon servers
available to service the logon request (0x000005e).
xxx = the IP Adress of any of the machines being queried
All DCOM settings are fine. The user account for the service is a
domain admin and also admin on the non-domain machine. All machines are
either W2K3 or W2K with latest service packs.
I noticed however that the DNS search order was going to the gateway
1st and then the Domain Controller 2nd. When I switched these round,
the whole thing works fine. I'm assuming that because our application
is making multiple repetative calls, sometimes the domain controller
responds with Access Denied due to the route the DNS resolution is
going for authenticating the user account of the service.
The problem is now solved, but I want to understand the underlying
reason for the eventual failure of the calls. Has anyone got any
information that could be helpful?
.
- Prev by Date: Re: Site replication
- Next by Date: Re: system state backup
- Previous by thread: system state backup
- Next by thread: Re: Server 2003 AD problems
- Index(es):
Relevant Pages
|
Loading
