Table 3. NetWare driver messages for the Ethernet controller (continued)Message DescriptionFailed to create AFT group.Make sure that the driversfor supported adapters areloaded, primary adapter isbound to protocols, andsecondary adapter is notbound to any protocols.Explanation: Binding of protocol failed. Protocol is eithernot bound to any adapter or is bound to more than oneadapter in the group. Action: Ensure that the protocol isbound to only adapter in an AFT team.Error identifying slotnumbers for the specifiedboard names.Explanation: The mapping between the board name enteredand the slot number for an adapter could not beestablished. Action: Check the board name for the adapterbefore issuing the bind command.Can’t unbind specified slotfrom AFT group. Make surethat the slot you specified isfor the primary adapter in anAFT group.Explanation: The number entered in the unbind commandwas not the primary adapter in an AFT group. Action:Reissue the unbind command and specify the slot numberfor the primary adapter.LAN adapter at slot nnnn(Port 0xaa) failed to reset.Check the state of theadapter.Explanation: The adapter that you specified could not beinitialized. Action:1. Load the driver for the supported adapter.2. Check that the adapter is seated properly in the slot andtry loading the AFT module again.AFT is not supported on thisversion of NetWare™.Explanation: The NetWare on your server is not a versionsupported by AFT. Action: Load and bind AFT only onsupported versions of NetWare (currently version 4.11 andabove).Failed to allocate resourcestags.Explanation: An unknown error has occurred when tryingto allocate needed resources for the AFT module. Action:Check server configuration.Please unload all LANdrivers before unloadingAFT.NLM.Explanation: An attempt was made to unload the AFT.NLMmodule before unloading the adapter driver. Action:Unload the adapter driver before unloading the AFTmodule.NDIS 4.0 (Windows NT) driver messagesThis section contains the error messages for the NDIS 4.0 drivers. The explanationand recommended action are included with each message.Table 4. NDIS (Windows NT or Windows 2000) driver messages for the Ethernet controllerError code(hex)Description0x00 Explanation: The driver could not register the specified interrupt. Action:Using the Configuration/Setup Utility program, make sure that a PCIinterrupt is assigned to your Ethernet card, and that Ethernet is enabled.0x01 Explanation: One of the PCI cards did not get the required resources.Action: Using the Configuration/Setup Utility program, make sure that aPCI interrupt is assigned to your Ethernet card, and that Ethernet isenabled.0x02 Explanation: Bad node address (multicast address). Action: Make sure thelocally administered address is valid, if one is specified. The address cannot be a multicast address.Chapter 3. Diagnostics 25