Cursed event ID 677

Hi

According to MS, This problem occurs because the Kerberos client on Windows
2000-based computers and on Windows Server 2003-based computers examines the
Key Distribution Center (KDC) at set intervals to verify that the
Service-for-User (S4U) Kerberos extension is supported. By default, the
Kerberos client examines the KDC every 15 minutes. Because Windows 2000 does
not support the S4U Kerberos extension, event ID 677 messages are logged to
the security event log of a Windows 2000 domain controller. In Windows
Server 2003, event ID 673 messages are logged to the security event log if
the S4U Kerberos extension is not configured. To use the S4U Kerberos
extension, you must have a Windows Server 2003 native domain, and you must
configure the appropriate computer accounts for constrained delegation.

Workaround Solution here:
Event ID 677 and event ID 673 audit failure messages are repeatedly logged
to the Security log of domain controllers that are running Windows 2000 and
Windows Server 2003
http://support.microsoft.com/kb/824905/en-us

Exchange Connector related error:
Logon Failure Event ID 677 with Exchange Server 5.5 and Active Directory
Connector
http://support.microsoft.com/kb/281431/en-us


I hop that helps

Good Luck
Jorge Silva
MCSA
Systems Administrator





"dw" <donWilwol@(EMAIL)yahoo.com> wrote in message
news:

or here
http://www.windowsecurity.com/artic...vents.html

Hope It Helps!

dw

_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
http://spaces.msn.com/members/wilwol/
www.datbusieness.com
www.skyphere.com

"Gadi Feldman" wrote in message
news:

This error appears on 2k dc's.
Time symchronization is ok.
Full event info:

Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 677
Date: 4/30/2006
Time: 7:37:27 PM
User: NT AUTHORITY\SYSTEM
Computer: dcserver
Description:
Service Ticket Request Failed:
User Name:
User Domain:
Service Name:
Ticket Options: 0x40830000
Failure Code: 0x29
Client Address: 1.1.1.1




"dw" wrote:

First thing I would check is time synchronization. If not give us some
more
information.
2000 or 2003? Where do you see the error etc.

Hope It Helps!

dw

_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
http://spaces.msn.com/members/wilwol/
www.datbusieness.com
www.skyphere.com

"Gadi Feldman" wrote in message
news:
> Hi guys,
>
> Does any one have solution to evade this cursed event 677, Failure
> Code:0x29.
> I've tried anything, but nothing helped...
> Any idea?

Thnx guys,

But i've already tried this workaround for my all 2003 servers, but the
errors are still here.

"Jorge Silva" wrote:

Hi

According to MS, This problem occurs because the Kerberos client on Windows
2000-based computers and on Windows Server 2003-based computers examines the
Key Distribution Center (KDC) at set intervals to verify that the
Service-for-User (S4U) Kerberos extension is supported. By default, the
Kerberos client examines the KDC every 15 minutes. Because Windows 2000 does
not support the S4U Kerberos extension, event ID 677 messages are logged to
the security event log of a Windows 2000 domain controller. In Windows
Server 2003, event ID 673 messages are logged to the security event log if
the S4U Kerberos extension is not configured. To use the S4U Kerberos
extension, you must have a Windows Server 2003 native domain, and you must
configure the appropriate computer accounts for constrained delegation.

Workaround Solution here:
Event ID 677 and event ID 673 audit failure messages are repeatedly logged
to the Security log of domain controllers that are running Windows 2000 and
Windows Server 2003
http://support.microsoft.com/kb/824905/en-us

Exchange Connector related error:
Logon Failure Event ID 677 with Exchange Server 5.5 and Active Directory
Connector
http://support.microsoft.com/kb/281431/en-us


I hop that helps

Good Luck
Jorge Silva
MCSA
Systems Administrator





"dw" <donWilwol@(EMAIL)yahoo.com> wrote in message
news:
> or here
> http://www.windowsecurity.com/artic...vents.html
>
> Hope It Helps!
>
> dw
>
> _______________________________
> Don Wilwol
> Distributed Application Technologies.
> dwilwol(DELETE)@datbusiness.com
> http://spaces.msn.com/members/wilwol/
> www.datbusieness.com
> www.skyphere.com
>
> "Gadi Feldman" wrote in message
> news:
>> This error appears on 2k dc's.
>> Time symchronization is ok.
>> Full event info:
>>
>> Event Type: Failure Audit
>> Event Source: Security
>> Event Category: Account Logon
>> Event ID: 677
>> Date: 4/30/2006
>> Time: 7:37:27 PM
>> User: NT AUTHORITY\SYSTEM
>> Computer: dcserver
>> Description:
>> Service Ticket Request Failed:
>> User Name:
>> User Domain:
>> Service Name:
>> Ticket Options: 0x40830000
>> Failure Code: 0x29
>> Client Address: 1.1.1.1
>>
>>
>>
>>
>> "dw" wrote:
>>
>>> First thing I would check is time synchronization. If not give us some
>>> more
>>> information.
>>> 2000 or 2003? Where do you see the error etc.
>>>
>>> Hope It Helps!
>>>
>>> dw
>>>
>>> _______________________________
>>> Don Wilwol
>>> Distributed Application Technologies.
>>> dwilwol(DELETE)@datbusiness.com
>>> http://spaces.msn.com/members/wilwol/
>>> www.datbusieness.com
>>> www.skyphere.com
>>>
>>> "Gadi Feldman" wrote in message
>>> news:
>>> > Hi guys,
>>> >
>>> > Does any one have solution to evade this cursed event 677, Failure
>>> > Code:0x29.
>>> > I've tried anything, but nothing helped...
>>> > Any idea?
>>>
>>>
>>>
>
>

http://eventid.net/display.asp?even...mp;phase=1

Regards,
Hank Arnold

Gadi Feldman wrote:

This error appears on 2k dc's.
Time symchronization is ok.
Full event info:

Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 677
Date: 4/30/2006
Time: 7:37:27 PM
User: NT AUTHORITY\SYSTEM
Computer: dcserver
Description:
Service Ticket Request Failed:
User Name:
User Domain:
Service Name:
Ticket Options: 0x40830000
Failure Code: 0x29
Client Address: 1.1.1.1




"dw" wrote:

First thing I would check is time synchronization. If not give us some more
information.
2000 or 2003? Where do you see the error etc.

Hope It Helps!

dw

_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
http://spaces.msn.com/members/wilwol/
www.datbusieness.com
www.skyphere.com

"Gadi Feldman" wrote in message
news:

Hi guys,

Does any one have solution to evade this cursed event 677, Failure
Code:0x29.
I've tried anything, but nothing helped...
Any idea?

I think i've already tried every solution that there in the internet, but
without any success :(

"Hank Arnold" wrote:

http://eventid.net/display.asp?even...mp;phase=1

Regards,
Hank Arnold

Gadi Feldman wrote:
> This error appears on 2k dc's.
> Time symchronization is ok.
> Full event info:
>
> Event Type: Failure Audit
> Event Source: Security
> Event Category: Account Logon
> Event ID: 677
> Date: 4/30/2006
> Time: 7:37:27 PM
> User: NT AUTHORITY\SYSTEM
> Computer: dcserver
> Description:
> Service Ticket Request Failed:
> User Name:
> User Domain:
> Service Name:
> Ticket Options: 0x40830000
> Failure Code: 0x29
> Client Address: 1.1.1.1
>
>
>
>
> "dw" wrote:
>
>> First thing I would check is time synchronization. If not give us some more
>> information.
>> 2000 or 2003? Where do you see the error etc.
>>
>> Hope It Helps!
>>
>> dw
>>
>> _______________________________
>> Don Wilwol
>> Distributed Application Technologies.
>> dwilwol(DELETE)@datbusiness.com
>> http://spaces.msn.com/members/wilwol/
>> www.datbusieness.com
>> www.skyphere.com
>>
>> "Gadi Feldman" wrote in message
>> news:
>>> Hi guys,
>>>
>>> Does any one have solution to evade this cursed event 677, Failure
>>> Code:0x29.
>>> I've tried anything, but nothing helped...
>>> Any idea?
>>
>>