Windows 2003 Event Id 10009

Did you saw this?
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=10009&EvtSrc=DCOM&LCID=1033

Explanation
The network connections might not be configured properly.

Thanks for the info

I checked the registry entry    DCOM Protocols    ncacn_ip_tcp


Do not know why it is looking for that ip address.

Did you check the network Connections?

Yes

this server communicates with the network with no problems.

I have three applications that run on this server that need to access the entire network / domain they all work

I know it is just a setting some where just can t find it.

The ip address 10.2.8.18 no longer exists on the network and dcom is pointing to that address for some reason.

I checked my DNS and no reference to that ip address I checked WINS database no records for that ip address

I have two DC servers both Windows 2003 that do not have this issue.

Explanation

The network connections might not be configured properly.
 
What network connections they talking about?

Puzzled ???

Do you have a Firewall?
Is LabTech installed?
Can you ping the Server from any client?
Is the Server up-to-date?

Try How to troubleshoot 1- 4:
http://blogs.msdn.com/b/asiatech/archive/2010/03/16/how-to-troubleshoot-dcom-10009-error-logged-in-system-event.aspx

Do you use Windows Firewall? If yes try this:
https://technet.microsoft.com/en-us/library/cc774368(v=WS.10).aspx

Also run this test:
https://support.microsoft.com/en-us/kb/259011

Do you have a Firewall?      NO
 Is LabTech installed?           NO
 Can you ping the Server from any client? YES
 Is the Server up-to-date? YES

The server it is trying to communicate with Ip address has changed the ip address that shows in the error is not the correct address any longer

I will try the test but I need to find where this old ip address is located on this server getting this error

Thoughts

Ok try all and let me know.

http://blogs.msdn.com/b/asiatech/archive/2010/03/16/how-to-troubleshoot-dcom-10009-error-logged-in-system-event.aspx

This I already saw no help at all

Do you use Windows Firewall? If yes try this:
https://technet.microsoft.com/en-us/library/cc774368(v=WS.10).aspx


Run Firewall on the Server that is trying to be connected to this is a Windows 2008 Server
The server getting the error 10009 is a windows 2003 server

So I modified the firewall on the windows 2008 server
Check the firewall settings and enable the firewall exception rule

To check the firewall settings and enable the firewall exception rule:
1.Click Start, and then click Run.
2.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.
3.In the console tree, click Inbound rules.
4.In the list of firewall exception rules, look for COM+ Network Access (DCOM In).
5.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.



I set this up on the Windows 2003 as server and on the windows 2008 as client

Also run this test:
https://support.microsoft.com/en-us/kb/259011 


Ran successfully

Windows 2003 Server
C:\Test>regedit tstsrvr.reg

C:\Test>tstsrvr
Server: Waiting
Server: IClassFactory:CreateInstance\

Windows 2008 Server
C:\Test>tstclnt SERV013.FQDN.com
Client: Creating Instance...0.0922 seconds
Client: Reading data...0.0056 seconds
Client: Writing data...0.0004 seconds
Client: Done
C:\Test>

So it look s good but as I asked in the beginning where is my windows 2003 server getting the old ip address from?

We find that then we resolve the problem

Did you check the DHCP?

What should I check in DHCP?

Will look at that when I get on site

Thanks

Check if you have a reservation to the old Server.

Will do

Thanks

Ok give me an update after.

Just checked DHCP no entries

Note they where all configured manually on the servers.

No DNS entry
No Wins Entry.

Ran arp -a     that ip address not listed in arp cache

Where in the world is this ip address stored on this server

awawada

Update

I ran this command on the server  ipconfig /displaydns

18.8.2.10.in-addr.arpa
 ----------------------------------------
 Name does not exist.


This is the ip address 10.2.8.18   that is the problem on this server


should I do a ipconfig /flushdns

I checked all other servers non reference this address

Thoughts

awawada

 Update

 I ran ipconfig /flushdns

then ipconfig /displaydns      and this still appears

 18.8.2.10.in-addr.arpa
  ----------------------------------------
 Name does not exist.

Could this be the issue?

How do I get rid of this?

Steve

Found it

Running Opmanager on this server and it had the ip address of the second nic from the server that I removed still in the devices being managed.

Every time it poled this device caused the error.

Will thank you very much

That's terrific. I appreciate the feedback.