Netlogon service won't start

[stjulian]

(My sincerest apologies for a cross-post)

I can't get a Windows XP Pro machine to access any domain resources. It is
running in a Windows Small Business Server 2000 domain. None of the other
WinXP machines have such a problem.

It doesn't even get a DHCP address. I had to manually set it.

Most importantly, the NetLogon service is not running. Can't start it up
either. I get the "Error 10106: The requested service provider could not be
loaded or initialized."

Some symptoms include errors 7023 on Service Control Manager and NetLogon
service as well as 5737 on the NetLogon service.

At the suggestion of a series of other I have removed references to this
pc's name in the domain controllers DNS, DHCP and AD before rebooting and
logging in. However, at this time, this is redundant. Tried to remove TCP/IP
but the option is grayed out. I have put the machine back into a workgroup.
But because of the problems, I can't get it back into the domain.

Don't really know where to look, any ideas?

 

[Amnon Feiner]

If you tries everything and no avail, try applying a new SID to the machine,
from sysinternals.com. apply the new sid including name change if possible.

 

[SuperGumby [SBS MVP]]

OK, a search on 5737 at www.eventid.net prompts me to ask if new.net
software was ever installed on this PC? If so, fdisk it and re-install
(YEAH, I know this is a bit radical, the software can be removed)

You have fundamental networking problems, the rest is just flow on from
that.

I plugged 'XP remove TCP/IP' into the search engine at support.microsoft.com
and the third article in the list was:
http://support.microsoft.com/default.aspx?scid=kb;en-us;299357
How to reset Internet Protocol (TCP/IP) in Windows XP

worth trying

Part of the reason for suspecting new.net is that I think the errors may
point to a problem with the Winsock LSP's. I'm also aware of an AntiVirus
program that does this (mucks up the LSP's, it's actually the mail scanning
function of a non-network designed package which does this) but rather than
me blindly blaming something, what AV package are you using?

fix the networking to the point where this PC gets an IP via DHCP and, I
believe, the rest of your troubles will disappear.

Cross posting is OK, you sent your message to a small number of appropriate
groups. Handling it this way is much better than posting individual threads.

 

[stjulian]

We use Symantec AntiVirus Corporate Edition 10.0. YES! it has email
scanning. But no other machines running XP were affected.