Microsoft KB Archive/107995

= NDIS2 Drivers Load but NDIS3 Drivers Don't--Errors 6200 & 58 =

Article ID: 107995

Article Last Modified on 9/24/1999

-

APPLIES TO


 * Microsoft Windows for Workgroups 3.11

-



This article was previously published under Q107995



SYMPTOMS
When you start Windows for Workgroups, you may receive one of the following error messages:

Error 6200: Adapter  not found

-or-

Error 58: The network has responded incorrectly

NOTE: These errors usually occur in protected mode; real-mode networking usually loads correctly.



CAUSE
The above error messages may be caused by an incorrect I/O base address, an incorrect RAM address, or an improper IRQ setting in the PROTOCOL.INI file.

These errors may be generated if the Transport= line in the [386Enh] section of the SYSTEM.INI contains protocols that are not in use. For example, if the Transport= line contains the following Transport=netbeui.386,nwlink.386,nwnblink.386 but the only protocol in use is NetBeui, the errors may occur.



RESOLUTION
Correct the invalid setting.

If the Transport= line contains invalid references, remove them (that is, remove the references to nwlink.386, nwnblink.386, and IPX/SPX compatible transport).



MORE INFORMATION
The NDIS2 network interface card (NIC) driver may not rely on the PROTOCOL.INI settings; however, the NDIS3 NIC driver relies almost exclusively on these settings.

Additional query words: 3.11 error message err msg enhanced mode protect NDIS tshoot

Keywords: KB107995

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.