Dcom Error 10009 Sbs 2008
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: SBS 2008 DCOM errors 10009 - Still happening to a few computers? Windows Small Business Server > Small Business dcom 10009 sbs 2011 Server Question 0 Sign in to vote I understand this is a known issue dcom error 10009 server 2008 r2 that can arise after installing SBS 2008, but I have been so far, unable to quiet these errors and am in need
Dcom Error 10009 Unable To Communicate With Computer
of assistance if possible. Thank you in advance for the help. I have an SBS 2008 standard server with roughly 55 Windows 7 Enterprise client computers on the domain running well after migrating from SBS
Dcom 10009 Unable To Communicate With The Computer
2003 R2. The only issue I have now is the persisting DCOM 10009 errors along with some Kerberos event 4 errors. I receivea couple hundredof the DCOM event 10009 each day along with about ten or so Kerberos event 4 errors. (errors posted below) The odd thing is that these errors are coming from only 4 of my 50+ laptops. The server logs about 8 to 10 DCOM event 10009 dcom was unable to communicate with the computer using any of the configured protocols. errors every hour or so for the same few computers and none of the others. Along with the 8 to 10 DCOM errors for each computer are a single Kerberos event 4 error that comes at the same time. The affected computers are all on the same subnet as the server, I have checked their firewall configurations which appear good, and these laptops are not used with VPN connections. I am no DNS expert, but it would appear as if all is working well. All records match on DNS servers and in the reverse lookup zones. THe firewall logs appear to be allowing all communications for the server. I do see a UDP port 5355 being blocked sometimes over IPv6, but it seems random. I have followed the technet post regarding known installation issues with SBS 2008 and have matched the recommeded firewall configuration. Only the same four computers are logging the errors in the server's event log, and I never see these errors from the other Windows 7 computers that are configured the same. The affected laptops have the same standard image as all ofthers and aren't running different software. Kerberos - Event ID 4 The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server computername$. The target nam
Ask Premier Field Engineering (PFE) Platforms Ask the Core Team Cloud Platform Blogs Hybrid Cloud Microsoft Azure Building Clouds Datacenter Management Hybrid Cloud Operations Management Suite (OMS) System Center Virtual Machine Manager System Center Service Manager System Center Operations Manager System Center Orchestrator System Center Data Protection Manager Client Management System Center Configuration Manager Configuration Manager Team System Center Service Manager Malware Protection Center Microsoft Intune Server Update Services Enterprise Mobility Virtualization, VDI & Remote Desktop Virtualization Team Ben https://social.technet.microsoft.com/Forums/en-US/7733809e-16ff-4084-953c-a2711fba324b/sbs-2008-dcom-errors-10009-still-happening-to-a-few-computers?forum=smallbusinessserver Armstrong's Virtualization Remote Desktop Services Ask the Core Team on Hyper-V Enterprise Mobility File & Storage & High Availability File & Storage Ask the Core Team on Failover Cluster Clustering & High Availability Windows Server Management PowerShell Hey Scripting Guy (PowerShell) Networking Identity, Access & Security Datacenter and Private Cloud Security Active Directory Enterprise Mobility Ask Directory Services The Windows https://blogs.technet.microsoft.com/sbs/2008/08/26/known-post-installation-event-errors-in-sbs-2008-and-how-to-resolve-them/ Server Essentials and Small Business Server Blog The official blog for Windows Server Essentials and Small Business Server support and product group communications. Known post installation event errors in SBS 2008 (and how to resolve them) ★★★★★★★★★★★★★★★ August 26, 2008 by SBS Bloggers // 1 Comments 0 0 0 [Today's post comes to us courtesy of Lora McCambridge and Damian Leibaschoff] SBS 2008 has been released to manufacturing (RTM), and if you haven't installed yet, you most likely will soon. As with previous versions of SBS, the complex interactions with partner products and configurations in use can lead to some noise in the event logs. We know of a few issues that you will see and we want to share information on how to resolve them or take action to prevent them. We are focusing on errors that will appear in a frequent enough ratio that they will be noticed right away, we are not going to be discussing one time events that can happen on shutdown, startup or right after the setup has been co
PM MESSAGE DCOM was unable to communicate with the computer ANOTHERSERVER.DOMAIN.lan using any of the configured protocol So when you put another server on the network and just http://blogs.msmvps.com/bradley/2009/11/28/dcom-was-unable-to-communicate-with-the-computer/ set it up for a specific purpose it may not open up all of the needed protocols in the firewall that it needs to correspond to the SBS 2008 box. So here's http://www.eventid.net/display-eventid-10009-source-DCOM-eventno-579-phase-1.htm how to adjust the firewall to get the Dcom messages out of your event logs: Event ID 10009 Source DCOM: http://www.eventid.net/display.asp?eventid=10009&eventno=579&source=DCOM&phase=1 Check the firewall settings and enable the firewall exception dcom error rule To check the firewall settings and enable the firewall exception rule: Click Start, and then click Run. Type wf.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. In the console tree, click Inbound rules. In the list of firewall exception rules, look for COM+ dcom error 10009 Network Access (DCOM In). If the firewall exception rule is not enabled, in the details pane click Enable rule, and then scroll horizontally to confirm that the protocol is TCP and the LocalPort is 135. 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 in theinbound firewall rules as well. Once you do that your server will report into the console and provide the hardware information on the Network/Computers tab. 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, or on the machine in question that cannot be reached? admin on November 29, 2009 at 4:40 pm said: I was lazy and just did this on the machine in question. You could do a group policy at the server to push out this policy to the machine in question. RVR on December 28, 2009 at 3:29 pm said: As per http://support.microsoft.com/kb/957713 article
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 10009 Source: DCOM Source: DCOM Maintenance: Recommended maintenance tasks for Windows servers Type: Error Description:DCOM was unable to communicate with the computer