They are both online and responding, but I'm not sure why DCOM would be attempting to contact external DNS servers. Download proper MPS Report tool from the website below. I couldn't find the server name anywhere in the registry or otherwise - that is until i stumbled upon it in "Active Directory Certificate Services" > "Issued Certificates". Wednesday, August 22, 2012 7:59 PM 3 Sign in to vote All LabTech users try this: Find the dctest.bat file in the \windows\ltsvc folder on the server and edit it so Source
here is the result of nslookup with it disabled: Server: DC1 Address: xxx.xxx.xxx.xxx (IP address masked) Name: resolver1.opendns.com Address: 188.8.131.52 Just as a note on the secondary DC I am Does it pass test? 0 Message Author Comment by:jyoung127 ID: 408642332015-07-02 Yes it passes the test. 0 LVL 29 Overall: Level 29 MS Legacy OS 6 Active Directory 5 Under this kind of situation, DCOM 10027 will be logged on the server side at the same time. Depending on your firewall solution this might be implemented or might require opening several ports.
ADSI Edit and delete them. Removing the forwarders from DNS seems to have cleared the errors when running the command from above, and the test runs much faster. b.
Writing a recommendation letter for a student I reported for academic dishonesty In 4/4 time can I insert a half sized bar in the middle of the piece? Make note of the IPv4 address listed. 7. Wednesday, November 23, 2011 12:51 PM 0 Sign in to vote I'm getting a whole bunch of these filling up my event log, historically we have had scavenging turned off (for Dcom Was Unable To Communicate With The Computer Dcdiag We also use LabTech like the last couple of people have mentioned.
You may want to disable LSO if you're sniffing traffic as you wont be seeing the packets as they are transmitted on the wire Maybe this will help. Dcom Was Unable To Communicate With The Computer Domain.local Using Any Of The Configured Protocols Why would our DC being trying to contact network equipment via DCOM? It is a crazy issue. 0 LVL 29 Overall: Level 29 MS Legacy OS 6 Active Directory 5 Windows Server 2012 4 Message Active 3 days ago Expert Comment by:Randy You'll need to restart your computer after you save the changes, but it should be good to go afterwards!
Find the IP Address of the server: Open a command prompt window (cmd.exe) from the Start menu. Dcom Was Unable To Communicate With The Computer Dns Forwarder For example, if the IP of the server is 192.168.1.2, the text box should read: localsubnet,192.168.1.2. However, if the RPCSS service of remote target server is not available, DCOM 10009 will be logged locally to notify administrator. In this scenario, the DCOM event ID 10009 will happen repeatedly, potentially hundreds per day.
Saturday, October 29, 2011 6:42 AM 0 Sign in to vote same, system is gone, and not in AD/DNS, where else could a reference exist? http://www.lansweeper.com/kb/139/dcom-was-unable-to-communicate-with-the-computer.html Any help appriciated. Dcom Was Unable To Communicate With The Computer Event Id 10009 You are not alone. Dcom Was Unable To Communicate With The Computer 10009 Server 2008 I tried all of the suggested settings in LMHost and Host Files with no success.
If nothing else try hitting the 184.108.40.206 Open DNS servers instead of 220.127.116.11 0 Message Author Comment by:jyoung127 ID: 408391562015-06-19 Randy sorry for the delayed response. this contact form which it is not. 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. This error indicates that Lansweeper was unable to scan the client machine, but does not point to an underlying issue with your server or Lansweeper installation. Dcom Was Unable To Communicate With The Computer 18.104.22.168 Using Any Of The Configured Protocols
But we continue to get the events. Other reasons for the problem might be found in the Extended Remote Procedure Call (RPC) Error information that is available in Event Viewer. Windows Srvr 2012 Std 2. Installed Spiceworks from latest download. Copied data files over. have a peek here I have at least one client server that is receiving DCOM 10009 errors, and the IP addresses are of the server's external DNS forwarders.
About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up Dcom Was Unable To Communicate With The Computer 10028 Cluster Check with your firewall manufacturer for the proper ways of allowing dynamic RPC traffic. Could someone post a fix pls.
more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Same here. But we will not implement this solution, rather keep the DNS forwarders and just ignore these error messages in the eventlog. Dcom Was Unable To Communicate With The Computer Exchange So, the IP addresses of some of the workstations were correlated to the incorrect (old) host names.
You can upload the information files to the following link. (Please choose "Send Files to Microsoft") Workspace URL: (https://sftasia.one.microsoft.com/choosetransfer.aspx?key=a7031c4a-e8ca-48cd-bb5d-7727e2967780) Password: #PAxwF2A+1xvy[zj Note: Due to differences in text formatting with I was getting the DCOM 10009 error for a SBS 2003 server I had removed from the domain during a migration to SBS 2011. In this scenario, the DCOM event ID 10009 will happen repeatedly, potentially hundreds per day. For your convenience, I have created a workspace for you.
I know the forwarders seem to work but it may go better if it's setup under Windows 2012 R2. 0 Message Author Comment by:jyoung127 ID: 408577832015-06-29 I tired removing them Make the following changes on your physical NIC Go to the NIC properties, click on advanced button, disable features that has the "Offload" or "RSS" wording in feature name. Servers on multiple customer sites are connecting via port 135 to the Google DNS servers (configures as our forwarders) - would be great to get this nailed? For example, if the IP of the server is 192.168.1.2, the text box should read: localsubnet,192.168.1.2.
Something similar to this thread although it's another error code.