Re: DCOM Errors in Event log

we do have a hp 1300 laser printer on that workstation, and it is a dell
Pentium 4 2.8 everything on the system is original. Any ideas on what it
could be, the printer has been on there for a couple of weeks, but we did
just have to do a reinstall of SBS2003 due to lack of hard disk space, we
added new drives and repartitioned the old drives and when we connected the
workstations we had this problem. But the problem is only with one
workstation the others are working fine.


"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
wrote in message news:eeSBIc6UGHA.5092@xxxxxxxxxxxxxxxxxxxxxxx
You don't have

HP printing monitoring software

A time difference between the workstation and the server do you?

or a NIC helper software on that box do you?

Jerry P wrote:

Here is the 537 error.

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 3/29/2006
Time: 9:06:43 PM
User: NT AUTHORITY\SYSTEM
Computer: xxxxxx
Description:
Logon Failure:
Reason: An error occurred during logon
User Name: Assistant
Domain: Dxxxxxxx
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Status code: 0xC00002EE
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: -
Source Port: -


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

"Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
wrote in message news:OW$moY5UGHA.5592@xxxxxxxxxxxxxxxxxxxxxxx

Could you post one of the 537 errors?

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Jerry P" <annoymous@xxxxxxxxxxxxx> wrote in message
news:EJSdnRZMrf_8jLbZnZ2dnUVZ_uudnZ2d@xxxxxxxxxxx

dell1600 is the server, asst01 is the workstation with the error 10009
in the event log, on the server in the security log we are getting error
537 in the event log.

"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:412603A8-A976-495E-A35D-DD73ACD3DF0B@xxxxxxxxxxxxxxxx

So for what purpose is the user Assistant, or computer ASST01, trying
to connect to dell1600? What is dell 1600, a workstation? Server?

--
Les Connor [SBS MVP]


"Jerry P" <annoymous@xxxxxxxxxxxxx> wrote in message
news:e_6dnTZYEcv7QLfZnZ2dneKdnZydnZ2d@xxxxxxxxxxx

this is from the workstation
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10009
Date: 3/29/2006
Time: 2:16:49 PM
User: DISCOVERY\Assistant
Computer: ASST01
Description:
DCOM was unable to communicate with the computer dell1600 using any of
the configured protocols.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:58DC6A62-6201-4AC1-BE7A-642CBE3B347E@xxxxxxxxxxxxxxxx

Hi Jerry,

Can you copy/paste one of the errors into a reply.

When in event viewer, double click the event and click on the copy
button to copy to the clipboard, and then paste into a reply.

--
Les Connor [SBS MVP]


"Jerry P" <JerryP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:69836E5F-2A5B-4712-B5DD-001E0214A8D2@xxxxxxxxxxxxxxxx

Please Help,

I am getting overloaded in the event log with DCOM error event ID
10009,
does anyone know of a fix for this, Microsoft has articles about it
but no
fix for it.









.