Ask a question and give support. x 2 EventID.Net As per Microsoft: "Component Services Administrative tool or DCOMCNFG incorrectly allows you to add Datagram User Datagram Protocol/Internet Protocol (UDP/IP) and Datagram Internet packet exchange (IPX) protocols to I had tried all the above solutions but to no avail pl help anybody!!!! I got this error on the workstation running Spiceworks (XP Pro). Source
Click Start, click Run, type GPMC.MSC, and click OK. 2. Reply Scott5297 says: January 9, 2014 at 9:25 am I had this on a SBS 2011 domain. Remove any of the Datagram protocols from DCOM protocols tab. I'm also seeing the same dcom errors when N-Able is trying to connect to machines that are no longer on the network.
You may also... It does give the reason of the DCOM attempts, but explains you what is triggering the DCOM call and gives tips on getting rid of it. Close Windows Firewall with Advanced Security Right mouse click and enable the rule Then to get the server to be able to query thename/model of theremote server enable the WMI
Check the affected station if the firewall is configured right on these machines, maybe the GPO is not applting correct? 2. As far as DCOM is configured it's only setup to use TCP-IP. Please, try this solution - Run ESET Remote Administrator Maintenance Tool - Next - Next - Stop ERA Server Service. Dcom Was Unable To Communicate With The Computer 188.8.131.52 Using Any Of The Configured Protocols Stats Reported 7 years ago 34 Comments 143,793 Views Other sources for 10009 VSS Microsoft-Windows-DistributedCOM MKS SNMPTrapd Service neskfax IISCrashHangAgent Microsoft-Windows-RestartManager Others from DCOM 10016 10006 10010 10005 10004 10028 10020
But we continue to get the events. Dcom Was Unable To Communicate With The Computer Event Id 10009 Now when I open up component services and go to default protocols tab, the only protocol listed there is "Connection-oriented TCP/IP". After removing the printer port, some events disappeared. https://community.spiceworks.com/windows_event/show/4-dcom-10009 x 3 A.Buttigieg This error can occur when an IISRESET command is issued without the "/" character in front of an option.
Ask a Question See Latest Posts TechSpot Forums are dedicated to computer enthusiasts and power users. Dcom Was Unable To Communicate With The Computer Dns Forwarder Several functions may not work. Both claim every test passed. To resolve this issue, identify the user account that is used to run the AFS Packages, and then assign the "Impersonate a client after authentication" user right to that user account.
Click the Default Protocols tab. 5. http://serverfault.com/questions/531043/event-id-10009-dcom Expand Forest: Domain.local, Domains, Domain.local and select Group Policy Objects. (Replace Domain.local with your domain) 4. Dcom Was Unable To Communicate With The Computer Using Any Of The Configured Protocols 10028 In my case the only fix was to change the RpcSs key : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\RpcSs] "ObjectName"="LocalSystem" Note: Please backup the registry before making any changes to it. Dcom Was Unable To Communicate With The Computer Domain.local Using Any Of The Configured Protocols Not the answer you're looking for?
x 3 Tim Noble From a newsgroup post: "When I use the Message Tracking Center in Exchange I see all handled messages. this contact form Windows 2000 does not support any datagram protocols. " See the links below for more details. Reply Winston He says: July 16, 2014 at 12:51 am @MJ Almassud There must be an process or service which is sending DCOM call to the non-existing machine, so you need If you are not getting these errors are you AD integrated? Dcom Was Unable To Communicate With The Computer Dcdiag
Pimiento Jul 3, 2012 Zombian Manufacturing I again began receiving this error but only from the server running SW. x 1 Anonymous A Windows XP PC had been renamed. a. have a peek here x 657 EventID.Net ME245197 indicates that to connect to a DCOM server on Windows 2000 and Windows XP, there must be at least one common connection-oriented protocol between the client and
On every XenApp Host I see DCOM Errors in the Windows Event-Log. (See attached Example Screenshot) The Error reads "DCOM was unable to communicate with the Computer %computername% using any Dcom 10009 Sbs 2011 I hope this helps someone out there Cubert Share this:FacebookLinkedInPrintEmailLike this:Like Loading... Removing the forwarders from DNS seems to have cleared the errors when running the command from above, and the test runs much faster.
Microsoft Customer Support Microsoft Community Forums Resources for IT Professionals Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย also Check the network connections. x 202 SWICORP As per Microsoft, make sure that connection-oriented protocols are in the DCOM protocols tab. Dcom Was Unable To Communicate With The Computer No Longer Exists How do I stop this event from logging?
Should I disable dcdiag script in labtech because it doesn't give me right information? Jalapeno Oct 19, 2010 Clark Keller Engineering, 51-100 Employees this is a rough one I cant seem to fix it either. Ask a question and give support. http://netfiscal.com/unable-to/dcom-10009-unable-to-communicate.html Posted in: Migrationextras 3 Thoughts on “Dcom was unable to communicate with the computer” Dennis on November 29, 2009 at 3:41 pm said: Should the actions be performed on the SERVER,
Finally I got it: Running the command "netsh firewall set service REMOTEADMIN ENABLE SUBNET" on the reported computer (not the SW-workstation) did the trick. Pimiento May 10, 2011 balu Other, 51-100 Employees Hi everyone, i checked the links above unfortunately no real help. One finished quickly and didn't log any errors, the other took 2-3 mins and logged 3 errors... 184.108.40.206 being one of them. Most likely it is going to be the PC from DCOM error.
Take a look at this kb article search for 10009, there is a possible solution for configuring the firewall on the affected client.