Difference between revisions of "Microsoft KB Archive/170569"

From BetaArchive Wiki
m (Text replacement - "<" to "<")
m (Text replacement - ">" to ">")
 
Line 77: Line 77:
 
</p>
 
</p>
 
<pre class="fixed_text">      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
 
<pre class="fixed_text">      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
         \<Network Adapter Driver&gt;\Parameters
+
         \<Network Adapter Driver>\Parameters
 
                             </pre></li>
 
                             </pre></li>
 
<li>Modify the bus and slot numbers to the new settings.</li></ol>
 
<li>Modify the bus and slot numbers to the new settings.</li></ol>

Latest revision as of 20:41, 20 July 2020

Knowledge Base


WinNT Stops Recognizing PCI Network Adapter After It Is Moved to Another PCI Slot

Article ID: 170569

Article Last Modified on 10/31/2006



APPLIES TO

  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition



This article was previously published under Q170569

SYMPTOMS

If you move a PCI network adapter from one PCI slot to another without changing its configuration, Windows NT no longer recognizes the adapter.

CAUSE

This occurs due to a problem in PCI cards that cannot detect themselves.

RESOLUTION

Perform one of the following to work around this problem:

  • Reinstall the driver after the card has been moved.

    -or-

  • Perform the following steps:

    WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

    1. Start Registry Editor (Regedt32.exe) and go to the following key:

            HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
               \<Network Adapter Driver>\Parameters
                                  
    2. Modify the bus and slot numbers to the new settings.


STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51 and Windows NT version 4.0 Service Pack 2 and Service Pack 3. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords: kbbug kbenv kbhardware kbnetwork KB170569