Netlogon service error

[whit]

I have a XP Pro machine that has been working on a
network for months. Last week the server was rebooted --
now this machine keeps returning a message when I try to
logon as anyone else of :
"Could not start the NetLogon Service on local computer
Error 10106: The requested service provider could not be
located and initialized. "

The only services this is dependent on is
the "workstation" service and it is started. however, I
still cannot start the Netlogon service.

Can anyone help?
Thanks so much in advance,
Whit

[Ísleifur Gíslason]

"whit" > wrote in message >...
> I have a XP Pro machine that has been working on a
> network for months. Last week the server was rebooted --
> now this machine keeps returning a message when I try to
> logon as anyone else of :
> "Could not start the NetLogon Service on local computer
> Error 10106: The requested service provider could not be
> located and initialized. "
>
> The only services this is dependent on is
> the "workstation" service and it is started. however, I
> still cannot start the Netlogon service.
>
> Can anyone help?
> Thanks so much in advance,
> Whit

I´m having exactly the same proplem!

Isleifur

[Ken Wickes [MSFT]]

"Ísleifur Gíslason" > wrote in message
om...
> "whit" > wrote in message
>...
> > I have a XP Pro machine that has been working on a
> > network for months. Last week the server was rebooted --
> > now this machine keeps returning a message when I try to
> > logon as anyone else of :
> > "Could not start the NetLogon Service on local computer
> > Error 10106: The requested service provider could not be
> > located and initialized. "
> >
> > The only services this is dependent on is
> > the "workstation" service and it is started. however, I
> > still cannot start the Netlogon service.
> >
> > Can anyone help?
> > Thanks so much in advance,
> > Whit
>
> I´m having exactly the same proplem!
>
> Isleifur

I have traced several of these problems to improperly configured winsock
LSPs. Run "winmsd" and go to Components/Network/Protocol. Look at the
names in the list, anything with "MSAFD" in it or the "RSVP xxx Service
Provider" should be fine. Anything else is suspect, and uninstalling the
owning program might help.

If that fails or your provider list is empty, you may need to rebuild the
catalog from scratch. The following instructions will rebuild your catalog
for TCP/IP. If you are using any other transports (If you don't know, then
you probably aren't) then you will have to reinstall them as well.


1. Backup and delete the following registry keys

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock2

2. Reboot

3. Go to the network connections folder, right click the icon for your
network connection, and select properties.

4. Click install, choose "protocol", and click "add..."

5. Click "Have Disk...", enter "\windows\inf", click OK

6. Select "Internet Protocol (TCP/IP), click OK

7. When the process in complete, reboot



--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.