Share via

NetBios over TCP/IP is not in Device Manager

Anonymous
2011-11-14T23:15:29+00:00

I am unable to connect to the network - DHCP won't start because it is dependent on NetBios over TCP/IP.

NetBios over TCP/IP is not in Device Manager - I've looked at it with "Show hidden devices" on. I know it is supposed to be located under "Non-Plug and Play Drivers".

I located it under the registry, it runs under NetBt.sys:

Key Name:          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT

Class Name:        <NO CLASS>

Last Write Time:   11/14/2011 - 5:54 PM

Value 0

  Name:            Type

  Type:            REG_DWORD

  Data:            0x1

Value 1

  Name:            Start

  Type:            REG_DWORD

  Data:            0x1

Value 2

  Name:            ErrorControl

  Type:            REG_DWORD

  Data:            0x1

Value 3

  Name:            Tag

  Type:            REG_DWORD

  Data:            0x6

Value 4

  Name:            ImagePath

  Type:            REG_EXPAND_SZ

  Data:            system32\DRIVERS\netbt.sys

Value 5

  Name:            DisplayName

  Type:            REG_SZ

  Data:            NetBios over Tcpip

Value 6

  Name:            Group

  Type:            REG_SZ

  Data:            PNP_TDI

Value 7

  Name:            DependOnService

  Type:            REG_MULTI_SZ

  Data:            Tcpip

Value 8

  Name:            DependOnGroup

  Type:            REG_MULTI_SZ

  Data:           

Value 9

  Name:            Description

  Type:            REG_SZ

  Data:            NetBios over Tcpip

Don't know if it helps, but I've tried changing the "Start" key to 2, as I saw it on another site, with no change. I've also uninstalled and reinstalled SP3, no change.

Thank you in advance.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

10 answers

Sort by: Most helpful
  1. Anonymous
    2011-11-15T20:45:43+00:00

    Yeah, I've tried System Restore - I tried 2 or 3 different ones, they all failed.

    And, of course, I don't have an install CD.

    Finally, my attempt at changing the DHCP registry key to use the NWLink didn't do any good.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-11-15T20:24:24+00:00

    I'm not sure it will work in this case, but have you tried a "System Restore" to a point in time before you deleted your DHCP?

    "How to restore Windows XP to a previous state"

      < http://support.microsoft.com/kb/306084 >

    Probably worth a try...

    HTH,

      JW

    Was this answer helpful?

    0 comments No comments
  3. LemP 74,940 Reputation points Volunteer Moderator
    2011-11-15T17:59:14+00:00

    Apparently the malware did some rather extensive damage.  Exactly what it did or how to fix it is, unfortunately for you, over my head. 

    If someone else doesn't jump in soon, your options as I see it are (a) repost in the Technet forum (http://social.technet.microsoft.com/Forums/en-us/itproxpsp/threads) or (b) do a repair install (which, of course, requires that you have an XP install CD, which many people do not have).

    Sorry I don't have better news for you.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-11-15T13:42:28+00:00

    First off, thanks for getting back to me so soon.

    Alright, let's see.

    I had something malicious (not really sure what, but I should still have some logs if necessary), so I ran Malwarebytes, SpyBot and a rootkit (tdsskiller I think).

    I'm running Windows XP Pro SP3.

    After removal, I was unable to connect to any router, either wired or wireless. I uninstalled SpyBot, because I thought it was the TeaTimer that was screwing me up, with no luck. So I reinstalled it, without TeaTimer this time.

    After some searching, I found that DHCP wasn't starting (Error 1068: The dependency service or group failed to start) - it is still set to automatic. I found that it relies on NetBIOS over TCP/IP (among other things) to start. Under Device Manager, I found that it had a yellow exclamation point. At this point I was stupid and uninstalled it instead of disabling, thinking that it would come up on restarting and potentially load correctly. It didn't. So I extracted the NetBT and NetBIOS drivers from C:\I386 and copied them to C:\Windows\system32\drivers, overwriting the old ones. NetBIOS over TCP/IP still didn't load when I restarted.

    I've also reloaded the Winsock registry keys twice, with no luck.

    Finally, I installed the NWLink IPX/SPX/NetBios Compatible Transport Protocol to my connection - is it possible that I can assign DHCP to use that instead of NetBIOS over TCP/IP? That's my only new thought that I haven't tried at the moment.

    As for your suggestions:

    I've tried both before, but no harm in trying again - I tried both at once and then rebooted. No luck. Here's the log:

    reset   SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{EB690DCB-1A5E-46D7-9F03-B9EE282F2F89}\NetbiosOptions

                old REG_DWORD = 1

    deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts

    reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces{8086D980-D5BD-48F6-8131-7A60044276CD}\EnableDhcp

                old REG_DWORD = 0

    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGatewayDefault

    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect

    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters

    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList

    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution

    reset   Linkage\UpperBind for ROOT\MS_NDISWANIPX\0000.  bad value was:

                REG_MULTI_SZ =

                    TVTPktFilter

    reset   Linkage\UpperBind for PCI\VEN_8086&DEV_4227&SUBSYS_10108086&REV_02\4&20975680&0&00E1.  bad value was:

                REG_MULTI_SZ =

                    DNE

    reset   Linkage\UpperBind for PCI\VEN_8086&DEV_109A&SUBSYS_200117AA&REV_00\4&192AC53F&0&00E0.  bad value was:

                REG_MULTI_SZ =

                    DNE

    reset   Linkage\UpperBind for {95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BTWDNDIS\1&30EE4AD&0&1000000020000.  bad value was:

                REG_MULTI_SZ =

                    DNE

    reset   Linkage\UpperBind for ROOT\NET\0000.  bad value was:

                REG_MULTI_SZ =

                    DNE

    reset   Linkage\UpperBind for ROOT\MS_NDISWANIP\0000.  bad value was:

                REG_MULTI_SZ =

                    DNE

    <completed>

    Was this answer helpful?

    0 comments No comments
  5. LemP 74,940 Reputation points Volunteer Moderator
    2011-11-15T00:22:02+00:00

    Why not start at the beginning, explain what happened, what you've done, and what version of Windows, including service pack is installed?  As part of your explanation, please provide complete error messages without paraphrasing.

    Although the following may not fix your DHCP issue, one thing that you might start with is:

    Open Network Connections (Start > Run > ncpa.cpl > OK)

    • Right-click on the icon for your Local Area Connection (assuming that you are connecting by Ethernet to a router)
    • On the General tab, under the heading "This connection uses the following items," select "Internet Protocol (TCP/IP)" and click the "Properties" button
    • On this second General tab, confirm that the radio button to "Obtain an IP address automatically" is selected and click the "Advanced" button at the bottom
    • Click the "WINS" tab
    • Select the radio button to "Enable NetBIOS over TCP/IP"
    • OK your way out

    If the above doesn't help after a reboot, I'd reinstall the TCP/IP stack, just on general principles:

    Open a Command Prompt window (Start > Run > cmd > OK)

    Type the following line in the black Command Prompt window and press Enter

             netsh int ip reset c:\resetlog.txt

    Reboot.

    Was this answer helpful?

    0 comments No comments