Err Msg: Failure: PROTOCOL.INI Does Not Have a DRIVERNAME=Last reviewed: November 21, 1994Article ID: Q114653  | 
	
	
 
The information in this article applies to:
 
 SYMPTOMSWhen the NET START command is executed, you receive one or more of the following error messages 
 Failure: PROTOCOL.INI does not have a DRIVERNAME=xxx. Failure: Protocol Manager did not accept xxx. Failure: NDIS environment invalid. Driver not loaded. Error loading device driver xxx. Error 7306: The driver failed to initialize. xxx was not loaded. Error 7321: Network card drivers failed to load.where "xxx" is your network card driver name (for example, EXP16 or EXP16.DOS). 
 CAUSEIf you install a second network interface card (NIC) of the same brand and model as the original and then load an NDIS 2 (real-mode) driver and protocol for this card, you encounter problems if the initial adapter is using an NDIS 3 (protected-mode) driver and protocol. Because an NDIS 2 driver must run in real mode, it is initialized before Windows for Workgroups 3.11 is loaded. The adapter binding with the NDIS 2 driver becomes the first physical adapter. To complete the binding process, the NDIS 2 driver looks in the PROTOCOL.INI file for a DriverName=FirstDriverInstance$ setting. Because an NDIS 3 driver was installed first, no such setting exists since NDIS 3 drivers do not require this setting. 
 RESOLUTIONTo avoid the above error messages, perform the following steps: 
  | 
	
	KBCategory: kbnetwork kberrmsg kbhw 
 © 1998 Microsoft Corporation. All rights reserved. Terms of Use.  |