Announcement

Collapse
No announcement yet.

NBT DEVICE ERROR

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NBT DEVICE ERROR

    I run Win2k and I have this error in the Event Viewer Unable to read IO control information from NBT device. I have no network or NIC cards installed just the dialup. Any help on this .....thanks
    I have a Abit BX6 R2 with G200 video card

  • #2
    A lot of people seem to be getting this event log entry. I could not track down the source by now but it doesn't seem to cause any trouble yet. Most of the folks ignore that message anyway. Seems to be related to some driver. but since I can't disable anything that would not cause my system to become unusable I ignored that too.
    I will have a look on W2K's long list of event messages and re-post after that.

    Alegria

    ------------------
    The pump don't work, 'cause the vandals took the handle...
    Bob Dylan

    The pump don't work, 'cause the vandals took the handle...
    Bob Dylan

    Comment


    • #3
      Maybe that is just the point. No NIC and no network connection at boot time. Since it has to do something with the NetBIOS over IP part of the Network configuration you can't stop happening just live with it.

      Regards, Alegria

      ------------------
      The pump don't work, 'cause the vandals took the handle...
      Bob Dylan

      The pump don't work, 'cause the vandals took the handle...
      Bob Dylan

      Comment


      • #4
        The pump don't work, 'cause the vandals took the handle...
        Bob Dylan
        LOL, I love that song. I think that has to be one of the first rap songs ever


        Comment


        • #5
          Event Type: Error
          Event Source: perfctrs
          Event Category: None
          Event ID: 3101
          Description:
          Unable to read IO control information from NBT device

          Maybe this will help..

          Comment


          • #6
            I know that already and it is a message that is in conjunction with NetBios over IP routing. The knowledge base didn't have an entry that really explained that error message. Must be one of the 64k bugs in 2000. Is anything not working in your OS environment right now or is it just the annoying message you want to get rid of?

            Alegria

            ------------------
            The pump don't work, 'cause the vandals took the handle...
            Bob Dylan

            The pump don't work, 'cause the vandals took the handle...
            Bob Dylan

            Comment


            • #7
              Everything seems to be working, I can do a
              reinstall and the error is gone. But as soon as I run Msbackup or run any program that scans my other drives the error comes right back

              Comment


              • #8
                I got the fix for this.......

                Error 3101: If you do not have a network card installed, you'll get that error message.

                Fix: Bring up the 'Add/Remove Hardware Wizard', select
                'Add/Troubleshoot a Device', select 'Add a New Device', 'I want to select hardware from a list', 'Microsoft', 'Microsoft Loopback Adapter'.


                After doing that procedure, 'Local Area Connection' will appear in the 'Network & Dialup Connections' folder. Right-click on that folder and set the properties for TCP/IP. Use 10.0.0.1 for the IP Address and 255.0.0.1 for the Subnet Mask.

                After you reboot your computer, subsequent 3101 error messages will not appear.

                Error 1000: You may have deleted a program from your machine you didn't want, but it's registry key is still looking for it. The error message will show you which registry key you need to delete in your registry. Run 'Regedit' to find and delete this key. Be absolutely sure you only delete the key that was referenced in your error log!

                Afterward, reboot your 'puter and then run 'ScanDisk'. Reboot again and this error message will no longer appear.

                I also had both of these error messages, and I'm now "error-free" after applying the above fixes

                Comment


                • #9
                  The subnet mask is wrong. It has to be changed to 255.0.0.0. The error was gone then and it never came back. No other error message appeared in the event log. I still believe this to be a bug. I didn't have to remove any registry entry.

                  Regards, Alegria

                  ------------------
                  The pump don't work, 'cause the vandals took the handle...
                  Bob Dylan

                  The pump don't work, 'cause the vandals took the handle...
                  Bob Dylan

                  Comment

                  Working...
                  X