AllenM
Mon May 05 13:37:38 PDT 2008
You'd be amazed if you were to google the first part of your error message
"DCOM was unable to communicate with the computer" all the hits it comes up
with.
"newguy" <newguy@discussions.microsoft.com> wrote in message
news:D47934C9-A407-4354-8C56-7C7F21DB3666@microsoft.com...
> Here is the complete error from the event viewer. the IP resolves to
> cncnoh-dns-cac-02.cinci.rr.com. I know this ip belongs to our ISP but i
> don't what it is doing.
>
>
> Log Name: System
> Source: Microsoft-Windows-DistributedCOM
> Date: 5/5/2008 12:05:01 PM
> Event ID: 10009
> Task Category: None
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: server.mydomain.com
> Description:
> DCOM was unable to communicate with the computer 24.29.1.219 using any of
> the configured protocols.
> Event Xml:
> <Event xmlns="
http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Microsoft-Windows-DistributedCOM"
> Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
> <EventID Qualifiers="49152">10009</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x80000000000000</Keywords>
> <TimeCreated SystemTime="2008-05-05T16:05:01.000Z" />
> <EventRecordID>6418</EventRecordID>
> <Correlation />
> <Execution ProcessID="0" ThreadID="0" />
> <Channel>System</Channel>
> <Computer>server.mydomain.com</Computer>
> <Security />
> </System>
> <EventData>
> <Data Name="param1">24.29.1.219</Data>
>
> <Binary>3C5265636F726423313A20436F6D70757465723D286E756C6C293B5069643D3934383B352F352F323030382031363A353A313A3537363B5374617475733D313732323B47656E636F6D703D323B4465746C6F633D313731303B466C6167733D303B506172616D733D313B7B506172616D23303A307D3E3C5265636F726423323A20436F6D70757465723D286E756C6C293B5069643D3934383B352F352F323030382031363A353A313A3537363B5374617475733D313732323B47656E636F6D703D383B4465746C6F633D3331333B466C6167733D303B506172616D733D303B3E3C5265636F726423333A20436F6D70757465723D286E756C6C293B5069643D3934383B352F352F323030382031363A353A313A3537363B5374617475733D31303036313B47656E636F6D703D383B4465746C6F633D3331313B466C6167733D303B506172616D733D333B7B506172616D23303A3133357D7B506172616D23313A307D7B506172616D23323A3078646230313164313830303030303030307D3E3C5265636F726423343A20436F6D70757465723D286E756C6C293B5069643D3934383B352F352F323030382031363A353A313A3537363B5374617475733D31303036313B47656E636F6D703D383B4465746C6F633D3331383B466C6167733D303B506172616D733D303B3E</Binary>
> </EventData>
> </Event>
>
> "Meinolf Weber" wrote:
>
>> Hello newguy,
>>
>> What is the ip that you are posting? Is the error from event viewer? Then
>> please post it complete.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
>>
>> > I am getting this error on my 2008 server. Its running as a DC and
>> > DNS. Our other server is a 2003 server running as DC and DNS.
>> >
>> > DCOM was unable to communicate with the computer 24.29.1.219 using any
>> > of the configured protocols.
>> >
>> > the ip resolves to my ISP. I don't know why the server is doing this.
>> > I don't think it should be trying to communicate with the ips server
>> > any way. Does anyone have any suggestions on how to fix this error.
>> >
>>
>>
>>