Home > Dcom Was > Dcom Was Unable To Communicate With The Computer Sbs 2008

Dcom Was Unable To Communicate With The Computer Sbs 2008

Contents

I have 2 different errors in my event log, (Event ID 10009 &10016). Depending on your firewall solution this might be implemented or might require opening several ports. Every time when the network health check runs the DCOM event 10009 appeared for some machines (running XP Pro). Select the Windows SBS Client �?? http://netfiscal.com/dcom-was/event-10009-dcom-was-unable-to-communicate-sbs-2008.html

Help, my office wants infinite branch merges as policy; what other options do we have? Nothing worked. Resolve performance issues faster by quickly isolating problematic components. This is a semester long project. https://social.technet.microsoft.com/Forums/en-US/86438bb1-e0b1-4c08-a7dd-496f4aaabfe2/dcom-was-unable-to-communicate-with-the-computer-using-any-of-the-configured-protocols?forum=smallbusinessserver

Dcom Was Unable To Communicate With The Computer Computername Using Any Of The Configured Protocols

Whenever I start managed application, I see event 10009 for all the computers in domain which are not up or not reachable. Expand Computer Configuration, Policies, Administrative Templates, Network, Network Connections, Windows Firewall, Domain Profile 6. Please find those entries and remove those records. But please read for the options. 0 LVL 1 Overall: Level 1 Message Active today Author Comment by:bdhtechnology ID: 362104892011-07-18 I saw this information: TCP/135, TCP/139 But it also states:

Expand Forest: Domain.local, Domains, Domain.local and select Group Policy Objects. (Replace Domain.local with your domain) 4. Privacy statement  © 2016 Microsoft. Please try to follow articles below to fix your issue. An Array of Challenges #2: Separate a Nested Array Big O Notation "is element of" or "is equal" Depowering a high AC PC without killing the rest of the group Does

It seems that this error occurs because of IP address conflicts. Expand Computer Configuration, Policies, Administrative Templates, Network, Network Connections, Windows Firewall, Domain Profile. 6. Find out more Read the post LVL 1 Overall: Level 1 Message Active today Author Comment by:bdhtechnology ID: 362099462011-07-18 Is there any way to tell what port(s) it is using? https://blogs.msmvps.com/bradley/2009/11/28/dcom-was-unable-to-communicate-with-the-computer/ I ignore it at those times.

That is what I wasn't sure of. I can ping all the pc's via ip and name. You should edit the Client XP GPO and change the scope of the rules to allow subnet + the internal IP of the server. Browse other questions tagged windows-sbs-2008 or ask your own question.

Dcom 10009 Sbs 2011

We shall see after the firewall policy applies to them. 0 Message Expert Comment by:49ernut ID: 380422412012-06-03 The DCOM error I am researching referrs to the old 2003 SBS that Click Start, click Run, type GPMC.MSC, and click OK. 2. Dcom Was Unable To Communicate With The Computer Computername Using Any Of The Configured Protocols Not a member? Dcom Was Unable To Communicate With The Computer Using Any Of The Configured Protocols 10028 This just started 2 nights ago for no apparent reason. "DCOM was unable to communicate with the computer xxx using any of the configured protocols." The security status for all pc's

All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback Contact me 28Nov 2009 Dcom was unable to communicate with the computer admin EVENT # 15343 EVENT LOG System EVENT TYPE Error this contact form This computer had not actually been on the network in months, but the error was showing up every thirty minutes in ten-error bursts. I've seen this happen with ours when the DNS doesn't flush out the IP's that were released from the DHCP server. It's SBS2008

Mar 24, 2012 DCOM was unable to communicate with the computer 92.65.38.228 using any of the configured protocols.

How to use LINQ to find a sum? The service stops unexpectedly while a network scan is going on. Help Desk » Inventory » Monitor » Community » Login with LinkedIN Or Log In Locally Email Password Remember Me Forgot Password?Register ENGINEERING.com Eng-Tips Forums Tek-Tips Forums Search Posts Find http://netfiscal.com/dcom-was/event-id-10009-dcom-was-unable-to-communicate-server-2008.html Follow the extra steps below to properly monitor XP SP2 (or higher) machines running in the SBS domain on different subnets than the SBS server, and prevent the DCOM event ID

I've tried the articals but they didn't solve the problems for me. The HOST A record of the machine is registered in the DNS, may be Go to Solution +1 4 Participants Rob Williams LVL 77 SBS47 susguperf LVL 7 SBS1 acstechee LVL RE: DCOM event id 10009 ShackDaddy (MIS) 12 Jul 12 13:43 Honestly, I've worked on 100+ SBS servers, and more than 60% have this issue.

The majority of computers seem to be at another location that are connected to the primary site via VPN. 0 LVL 26 Overall: Level 26 SBS 14 Windows Server

By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Creating your account only takes a few minutes. http://technet.microsoft.com/en-us/library/cc774368(WS.10).aspx Tabasco Aug 26, 2009 AlanK Manufacturing, 51-100 Employees I see this happening during every Spiceworks scan. Main Sections Technology News Reviews Features Product Finder Downloads Drivers Community TechSpot Forums Today's Posts Ask a Question News & Comments Useful Resources Best of the Best Must Reads Trending Now

Get 1:1 Help Now Advertise Here Enjoyed your answer? You may still run into the same problem with BYOD. 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. Check This Out Can anyone give me any suggestion as to where to go with this?

I think the problem was the affected computers were in the wrong container in AD Users &Computers. All rights reserved. Get Your Free Trial! Join the community of 500,000 technology professionals and ask your questions.

© Copyright 2017 netfiscal.com. All rights reserved.