WMI query from remote computer fails with Impersonation failed - access denied and WDM call returned error: 4200

Hi all,

We have a remote querying a server using WMI to check on the status of various services, however for some reason it has now started to fail.

The wmiprov.log shows:

Impersonation failed - access denied
WDM call returned error: 4200

I believe the account has the correct rights, but for some reason it still keeps on failing.

Does anyone have any ideas on how to troubleshhot and resolve this ?

Thanks

Matt
LVL 1
themoogyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

grayeCommented:
Tell us more about the "remote" end of this scenario....    Domain vs Workgroup?, Windows Server 2003?,  With Service Pack 2?   Any recent firewall adjustments, etc.
0
themoogyAuthor Commented:
Both windows 2003 sp2, with all the latest hotfixes. Both a memeber of the same domain and in the same OU, no firewall between the hosts or enabled on the hosts.

I have confimred that the host affected is rejecting all WMI queries over the network, WMI only works when queried on the host itself.
Thanks

Matt
0
grayeCommented:
OK... I recommend the next step be to download and run the WMIDiag script on the remote PC.
http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
There might be some that pops out at us.
Just curious... does the "reverse direction" work?   Can you sucessfully run a script with Impersonation from the "failed" server to the "good" server?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
themoogyAuthor Commented:
Great tool, thanks for pointing me in the right direction, it proved to be a dcom error, the tool suggested registry changes and after a reboot all the problems were solved.
Thanks for your help

Matt
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.