MonitorWare Knowledge Base

by **wcollins_894** on Sun Nov 23, 2003 3:04 am

Does anyone know anything about this error?

by **alorbach** on Mon Nov 24, 2003 9:34 am

Are you sure this is the correct eventid?
Google doesn't find anything :shock:

!

Maybe you could quote the whole event including ID and source here.

by **snyderga1** on Mon Dec 01, 2003 6:52 pm

That is the correct error. I am having the same problem.

This error reports it can not start the net logon service. When I try to start it manually it reports the same error.

by **GeRM** on Thu Jan 08, 2004 9:50 am

I had this a while ago, i was able to solve it by deleting the static mappings from the wins server.

by **peporro** on Fri Jan 16, 2004 10:14 am

tengo el mismo problema que vosotros, no puedo iniciar sesion porque no me arranca el netlogon y me ha pasado en los equipos clonados con ghost, el original si funciona bien.

by **therget** on Wed Jan 21, 2004 2:50 pm

I found something about this on a Newsgroup Posting(Google Link)

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\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\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

maybe it will help someone :wink:

by **Guest** on Mon Apr 12, 2004 9:15 am

therget wrote:I found something about this on a Newsgroup Posting(Google Link)
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\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\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

maybe it will help someone

Can the above steps be followed for Windows XP OS as well?

thanks
RA

by **guest** on Mon Apr 12, 2004 9:15 am

therget wrote:I found something about this on a Newsgroup Posting(Google Link)
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\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\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

maybe it will help someone

Can the above steps be followed for Windows XP OS as well?

thanks
RA

by **Guest** on Mon Apr 12, 2004 7:56 pm

guest wrote:
therget wrote:I found something about this on a Newsgroup Posting(Google Link)
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\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\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

maybe it will help someone

Can the above steps be followed for Windows XP OS as well?

thanks
RA

I think it helped me! I am back online now...

by **Ryn** on Fri Jun 04, 2004 1:02 pm

Genius! This worked perfectly for me :-)

by **Jamirae** on Thu Jun 10, 2004 3:07 am

oh yes!!! Thank you!! google brought me here first and that worked like a champ.. had the 10106 error with "simple tcp/ip" services not starting.

awesome!

by **Bladzz30** on Thu Aug 26, 2004 9:41 pm

When I first read the solution I was optimistic, but worked like a charm.

by **nick portlock** on Thu Sep 02, 2004 2:22 pm

therget, you're a star! thanks much!

Nick

by **Rudeman** on Mon Sep 06, 2004 4:02 pm

I had the same problem and removing the registry keys and reinstall TCP/ IP worked for me

1. Backup and delete the following registry keys

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\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

by **CairoBoy** on Wed Sep 08, 2004 7:37 am

Ryn wrote:Genius! This worked perfectly for me

Thank you

MonitorWare Knowledge Base

Error 10106 Netlogon fails to start

Error 10106 Netlogon fails to start

yo tambien

error 10106

Re: error 10106

thanks!

Worked great

10106 error

Google Ads

Who is online