• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1265
  • Last Modified:

Cannot add computer to Windows 2000 domain - IpSec and NetLogon services do not start

I have a Windows XP Pro computer that was on a Windows 2000 domain yesterday (one of about 50 in my domain) that refuses to access the internet or the domain. Trying to troubleshoot, I've managed to drop it from the domain down to a local workgroup and sever any ties at all to the network. The IpSec and NetLogon services refuse to start with event log errors like this:

Event Source:      Service Control Manager
Event Category:      None
Event ID:      7023
User:            N/A
Description:
The IPSEC Services service terminated with the following error:
The requested service provider could not be loaded or initialized.

Event Source:      NETLOGON
Event Category:      None
Event ID:      5737
User:            N/A
Description:
The system returned the following unexpected error code:
The requested service provider could not be loaded or initialized.

Before I stupidly dropped it off the domain, I could still access network files if I provided a logon and password. Now when I try to add it back to the domain, I get messages that the machine cannot connect to a dc, and that tcp/ip is not installed. I figure that is due to the services not running, but here is the error message if you want it:

An error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain <DOMAIN>.

The error was: "TCP/IP network protocol not installed."
(error code 0x0000267B DNS_ERROR_NO_TCPIP)

The query was for the SRV record for _ldap._tcp.dc._msdcs.<DOMAIN>

I get error code 10106 when I try to manually start the either service. I'm at a loss. I'm tired, I have 50 other machines that do just fine on this network, and I would just chuck it all and wipe the machine, but it's the only box in my domain that has certain software on it, and I'd like to save it if I can. Sorry about the length, but I'm a too much information rather than too little kind of guy.
0
timbercoyote
Asked:
timbercoyote
1 Solution
 
oBdACommented:
Seems like your TCP/IP stack has gone overboard, and without that, you obviously can't start any service that relies on it.
How to remove and reinstall TCP/IP for Windows 2000
http://support.microsoft.com/?kbid=285034
0
 
timbercoyoteAuthor Commented:
Thanks oBdA, I had wanted to try to re-install TCP/IP, but apparently you can't do that in Windows XP. I did find the Microsoft article on resetting TCP/IP for Windows XP, but no solution there. I have run standard diagnostics and everything checks out, other than the services failing to start... including pinging the gateway, dns, a different workstation on the domain, the computer names for all of the above, and even pinging from the network to the affected workstation works fine. I tried DHCP, static addressing (default), a new static address, deleting and readding the computer from Active Directory, verifying and changing the dns pointers on the server, and asking it to please just be nice to me. Nothing. I'm working through troubleshooting trying to find anything else wrong, but nothing yet. Again, I can't wipe the box unless I want a serious hassle re-installing software I'm not even sure I know where the discs are. Thanks for any and all help.
0
 
lancecopelandCommented:
Having the same problem.  Mine occurred after SP2.  I know I know, learn from your mistakes right?  Anyway.....
oBdA was right.  But remove and reinstall did noting for me plus anyway you can't uninstall TCP for XP you can only "reset" it.  Still doesn't fix it.  He led me in the right direction by making me check my TCP stack to see if anything was out of the ordinary.  Load up your msinfo32 console and check your stack.  Components...Network... Protocol.  Check first the name.  Should say MSAFD Tcpip [TCP/IP].  Mine in fact did not say this.  I "HAD" Panda Antivirus 2004 installed (others may cause problems too) and my TCP stack started with "PAV over MSAFD"  AHA!!  uninstalled Panda and back on the domain now.  I will try and reinstall Panda 2004 and hopefully it won't screw it up again.  Don't feel bad Timbercoyote, this was my personal computer at work and this beat me up for 2 days too.  Going WAY too technical and getting lost.  Don't ever forget, someone, somewhere has had your problem.  Keep checking the forums.  :-)
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
dkattanCommented:
I'm having this same problem. I can't get a IP address on the network and I noticed that IPSEC wasn't started. When I try to start it I get
"Could not start the IPSEC Services service on Local Computer.
Error 10106: The requested service provider could not be loaded or initialized."

I wish I could reinstall TCP/IP or something.
0
 
gayagaya2Commented:
how do i check my tcp stack? please help! i am having the same problem
0
 
lancecopelandCommented:
Load up your msinfo32 console and check your stack.  Components...Network... Protocol.  Check first the name.  Should say MSAFD Tcpip [TCP/IP].  (This was from my previous post)
0
 
moduloCommented:
PAQed with no points refunded (of 500)

modulo
Community Support Moderator
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now