Netlogon service fails event ID: 5373 and 7024 Win 2000 domain controller

  • Thread starter Thread starter John
  • Start date Start date
J

John

Hi All

I have an issue with a Win 2000 DC that will not start Netlogon, IPSec agent
etc with event IOD: 5373 and 7024. No changes to hardware of software
prior to this. Any ideas please?

ta John
 
John said:
Hi All

I have an issue with a Win 2000 DC that will not start Netlogon,
IPSec agent etc with event IOD: 5373 and 7024. No changes to
hardware of software prior to this. Any ideas please?
Click to expand...

Copy and paste the full details of these events.
Are these events the only events you have?
Does Netlogon give you an error when you try to manually start it?
 
Hi Kevin

I am offsite at present so I cannot get the entire log - but the service
fails and will not start even in safe mode. I have removed the ethernet
controller and readded it now and am having problems with MS Cleint re
installaling - I will advise my position when I have overcome this - Thanks
for the reply

John
 
You know, posting to every Win2000 ng you can find just pisses people
off. What, on earth, does this have to do with group policy, Windows
update or DNS???????????

BTW, there are about 20 "microsoft.public.win2000" groups you missed...
:-)

Regards,
Hank Arnold
 
Hank said:
You know, posting to every Win2000 ng you can find just pisses people
off. What, on earth, does this have to do with group policy, Windows
update or DNS???????????
Click to expand...

Hank, with all due respect, I can excuse John's cross posting far better
than if he had multi-posted in different groups, and the language you used.

As for what this could have to do with Group Policy, two years ago I had a
DC eating my proverbial lunch because the Netlogon server would not start
and the server would not manually start. It turned out to be group policy on
the Domain Controller policy, the netlogon service was disabled in the
policy, and the security was set to deny access to everyone.
I fixed the security and set the policy to Automatic, problem solved. At
this point I cannot say that this is John's problem because I don't have the
data to support a resolution.
You never know who has the answer, if you don't exactly know where to post
it, get it out to as many groups he might think is relevant.
 
If the use of the single word upsets anyone, sorry about that......

Other than that, I stand by my point. posting to multiple ng's in a
shotgun manner is bad netiquette. I follow dozens of ng's. It's hard
enough to keep up and this just makes it harder...

All the OP had to do is post it to relevant groups and others only if
there were no resolution....

Regards,
Hank Arnold

I second those thoughts !

-- Dave Britt Dave's Weblog http://davebritt.blogspot.com "Kevin D.
 
Hank Arnold said:
If the use of the single word upsets anyone, sorry about that......

Other than that, I stand by my point. posting to multiple ng's in a
shotgun manner is bad netiquette.
Right!

I follow dozens of ng's. It's hard
enough to keep up and this just makes it harder...
Click to expand...

Why don't you set a FollowUp-To: to the appropriate group then?
All the OP had to do is post it to relevant groups and others only if
there were no resolution....

Regards,
Hank Arnold
Click to expand...

BTW: Top posting and full quotes, especially when broken by "format=flawed"
in addition do their best to keep postings hard to read!
Just take a look! The signature separator has gone too.

Stefan

[full quote left with reason]

fup2 microsoft.test
 
Back
Top