We help IT Professionals succeed at work.

DCOM unable to communicate with the computer xxx.xxx.xxx.xxx using any of the configured protocols

I have a server running Server 2003 that all of the sudden started throwing out this error this morning around 11:00AM EST - Source: DCOM  Event ID:  10009  "DCOM unable to communicate with the computer xxx.xxx.xxx.xxx using any of the configured ."  The main issue is that once this Server is plugged into the network...it max'es out my internet connection...and no one can get out.  When I am pinging gateway IP, everything is good...with a second or two after plugging the server in, I loose ping and no one can get through...unplug the server and everything is good again.  I have followed quite a few of the suggestions on this fourm and others...I have checked the DCOM services order, reg info, etc.  When looking through Event Logs...the IP just keeps going up and up...and randomly switching to a new public subnet...so you can see where the traffic is coming from...but I don't know how to stop it.  Please let me know if anyone has seen this before...I am going to keep searching...thanks.
Comment
Watch Question

Bradley FoxLAN/WAN Systems Administrator
BRONZE EXPERT

Commented:
There are a lot of reference to DNS issues around this error, read through this and see if any apply to you.

http://eventid.net/display.asp?eventid=10009&eventno=579&source=DCOM&phase=1
Thank you for the information.  We did check this prior to posting...there where no duplicate entries at the time.  The DCOM errors were attempting to contact public IP's...which appeared to be random...then it would cycle through the subnet...by jumping forward through the block...then switch to a new block and start all over...killing the internet circuit.  We ended up moving the files and services over to a replica of the server that we had on the shelf, that was originally created for a Double-Take failover solution...so we were back up and running that night (morning) at about 12:50am.  The odd thing is, that whatever happened, blew away all the share permissions on the file folders within windows.  We had to break the shares just to allow us to copy files period.  It was very odd...thanks again for the suggestion.

Author

Commented:
We didn't really fix the issue, but this was the quickest method to resolution of the issue.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.