Failure Audits in 2003 Server

2003 Server displaying this message in Event Viewer.

Type: Failure Audit
Source: Security
Category: Account logon
Event ID: 673
User: System

I am also having the trouble with a 2000 Server but with a different Event
ID #. I found the solution I thought in the knowledge base and called
Microsoft for the hotfix, but it hasn't helped the problem. This is
effecting my logon scripts and Group Policy from processing. Thanks in
advance for any help.

You mention that it seems to be stopping group policy and
login scripts (sysvol) from replicating.

What are the results when you run netdiag and dcdiag from
the windows 2003 resource kit?

Are both servers on the same domain? has sysvol
replicated?


>-----Original Message-----
>2003 Server displaying this message in Event Viewer.
>
>Type: Failure Audit
>Source: Security
>Category: Account logon
>Event ID: 673
>User: System
>
>I am also having the trouble with a 2000 Server but with
a different Event
>ID #. I found the solution I thought in the knowledge
base and called
>Microsoft for the hotfix, but it hasn't helped the
problem. This is
>effecting my logon scripts and Group Policy from
processing. Thanks in
>advance for any help.
>
>
>
>
>.
>

Tony thanks for the help. I ran the diagnostics, it seems that the Sysvol
replicates sometimes ok and other times with errors. How can you fix this? I
have a 2000 Server and 2003 Server, I have moved the operations masters and
some other services to the newer server because the 2000 is only 366 mhz with
about 350mb of ram. I am new here and the 2000 has been neglected for a long
time. For instance when you run disk defrag the entire disk is almost red,
however when you run defragmenter it says it completes but still displays all
red(fragmented files).
One other thing: Wwhen running netdiag and dcdiag the first lines usaully
indicate the server name address and os. My 2003 server is saying os
2000(build 7903 or some number?) is that normal?

"Tony Roberts" wrote:

> You mention that it seems to be stopping group policy and
> login scripts (sysvol) from replicating.
>
> What are the results when you run netdiag and dcdiag from
> the windows 2003 resource kit?
>
> Are both servers on the same domain? has sysvol
> replicated?
>
>
> >-----Original Message-----
> >2003 Server displaying this message in Event Viewer.
> >
> >Type: Failure Audit
> >Source: Security
> >Category: Account logon
> >Event ID: 673
> >User: System
> >
> >I am also having the trouble with a 2000 Server but with
> a different Event
> >ID #. I found the solution I thought in the knowledge
> base and called
> >Microsoft for the hotfix, but it hasn't helped the
> problem. This is
> >effecting my logon scripts and Group Policy from
> processing. Thanks in
> >advance for any help.
> >
> >
> >
> >
> >.
> >
>

It is worth checking the _msdcs entries in DNS - if there
are issues there, ad replication can start failing. Also,
try manual directory replication, and carefully check the
event log messages for errors after doing that.

Those reports should have identified that though.

Also, i'm assuming you have installed the patches
required on the 2k box to get ready for 2003?

>-----Original Message-----
>Tony thanks for the help. I ran the diagnostics, it
seems that the Sysvol
>replicates sometimes ok and other times with errors. How
can you fix this? I
>have a 2000 Server and 2003 Server, I have moved the
operations masters and
>some other services to the newer server because the 2000
is only 366 mhz with
>about 350mb of ram. I am new here and the 2000 has been
neglected for a long
>time. For instance when you run disk defrag the entire
disk is almost red,
>however when you run defragmenter it says it completes
but still displays all
>red(fragmented files).
>One other thing: Wwhen running netdiag and dcdiag the
first lines usaully
>indicate the server name address and os. My 2003 server
is saying os
>2000(build 7903 or some number?) is that normal?
>
>"Tony Roberts" wrote:
>
>> You mention that it seems to be stopping group policy
and
>> login scripts (sysvol) from replicating.
>>
>> What are the results when you run netdiag and dcdiag
from
>> the windows 2003 resource kit?
>>
>> Are both servers on the same domain? has sysvol
>> replicated?
>>
>>
>> >-----Original Message-----
>> >2003 Server displaying this message in Event Viewer.
>> >
>> >Type: Failure Audit
>> >Source: Security
>> >Category: Account logon
>> >Event ID: 673
>> >User: System
>> >
>> >I am also having the trouble with a 2000 Server but
with
>> a different Event
>> >ID #. I found the solution I thought in the knowledge
>> base and called
>> >Microsoft for the hotfix, but it hasn't helped the
>> problem. This is
>> >effecting my logon scripts and Group Policy from
>> processing. Thanks in
>> >advance for any help.
>> >
>> >
>> >
>> >
>> >.
>> >
>>
>.
>

Tony I am new to the company have only been here for about 6 weeks. The 2000
Server has been neglected for so long, it has several issues. However I am
not sure what patches you are referring to? But these errors have really
gotten bad. The 2003 Showing constant failure audits.
Event 673, event 675.

The 2000 Mostly event 677. I went to the knowledge base and called and got
the hotfixes but it hasnt seemed to help.

"Tony Roberts" wrote:

> It is worth checking the _msdcs entries in DNS - if there
> are issues there, ad replication can start failing. Also,
> try manual directory replication, and carefully check the
> event log messages for errors after doing that.
>
> Those reports should have identified that though.
>
> Also, i'm assuming you have installed the patches
> required on the 2k box to get ready for 2003?
>
> >-----Original Message-----
> >Tony thanks for the help. I ran the diagnostics, it
> seems that the Sysvol
> >replicates sometimes ok and other times with errors. How
> can you fix this? I
> >have a 2000 Server and 2003 Server, I have moved the
> operations masters and
> >some other services to the newer server because the 2000
> is only 366 mhz with
> >about 350mb of ram. I am new here and the 2000 has been
> neglected for a long
> >time. For instance when you run disk defrag the entire
> disk is almost red,
> >however when you run defragmenter it says it completes
> but still displays all
> >red(fragmented files).
> >One other thing: Wwhen running netdiag and dcdiag the
> first lines usaully
> >indicate the server name address and os. My 2003 server
> is saying os
> >2000(build 7903 or some number?) is that normal?
> >
> >"Tony Roberts" wrote:
> >
> >> You mention that it seems to be stopping group policy
> and
> >> login scripts (sysvol) from replicating.
> >>
> >> What are the results when you run netdiag and dcdiag
> from
> >> the windows 2003 resource kit?
> >>
> >> Are both servers on the same domain? has sysvol
> >> replicated?
> >>
> >>
> >> >-----Original Message-----
> >> >2003 Server displaying this message in Event Viewer.
> >> >
> >> >Type: Failure Audit
> >> >Source: Security
> >> >Category: Account logon
> >> >Event ID: 673
> >> >User: System
> >> >
> >> >I am also having the trouble with a 2000 Server but
> with
> >> a different Event
> >> >ID #. I found the solution I thought in the knowledge
> >> base and called
> >> >Microsoft for the hotfix, but it hasn't helped the
> >> problem. This is
> >> >effecting my logon scripts and Group Policy from
> >> processing. Thanks in
> >> >advance for any help.
> >> >
> >> >
> >> >
> >> >
> >> >.
> >> >
> >>
> >.
> >
>