76.0 Shared Messages for LAN Drivers
The following includes Shared Messages for LAN Drivers.
001: The LSL is not loaded.
Source:
TRXNET-DOS.LAN
Explanation:
Before loading the driver, the Link Support Layer (LSL) must be loaded.
Action:
Load the LSL. Then load the driver, using the syntax in the following example:
C:\NWCLIENT\LSL <Enter>
C:\NWCLIENT\TRXNET <Enter>
002: The LSL has no room for a board using frame type.
Source:
TRXNET-DOS.LAN
Explanation:
The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.
Action:
Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example:
LINK SUPPORT
MAX BOARDS 6
Unload the driver; then reload it as in the following example:
C:\NWCLIENT\TRXNET /u <Enter>
C:\NWCLIENT\TRXNET <Enter>
003: Could not find TRXNET MLID to unload.
Source:
TRXNET-DOS.LAN
Explanation:
This is an informational message indicating that the TRXNET driver is not loaded.
004: A TSR is loaded above the TRXNET MLID.
Source:
TRXNET-DOS.LAN
Explanation:
Another TSR (terminate-and-stay-resident) program was loaded after the TRXNET driver.
Action:
The drivers must be unloaded in reverse order, as follows:
C:\NWCLIENT\NETX /u <Enter>
C:\NWCLIENT\IPXODI /u <Enter>
C:\NWCLIENT\TRXNET /u <Enter>
Unload the TSRs; then try to unload the TRXNET driver. If you wish, you can force the TRXNET driver to unload from the command line by using the /F switch after the driver name, as follows:
C:\NWCLIENT\TRXNET /f <Enter>
Use caution when using the /F switch because it could cause the system to hang.
005: TRXNET MLID could not be unloaded; the operation was aborted.
Source:
TRXNET-DOS.LAN
Explanation:
The TRXNET driver could not be shut down and unregistered. Consequently, it cannot be unloaded.
Action:
To unload the driver, reboot the system.
006: The adapter did not initialize. TRXNET did not load.
Source:
TRXNET-DOS.LAN
Explanation:
The TRXNET driver encountered an error while loading.
Action:
Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.
007: You need another MLID section heading in the NET.CFG file in order to load the MLID again.
Source:
TRXNET-DOS.LAN
Explanation:
The driver cannot be loaded consecutively unless you edit the configuration parameters and add a section heading for each instance in the NET.CFG file.
Action:
Unload the TRXNET driver. Edit/create the NET.CFG file and add a Link Driver section heading for each time the driver is to be loaded; then reload the driver.
008: A NET.CFG is required to load the MLID again.
Source:
TRXNET-DOS.LAN
Explanation:
The driver cannot be loaded unless you create a NET.CFG file. A Link Driver section heading must be edited into the NET.CFG file for each time the driver is to be loaded.
Action:
Unload the TRXNET driver. Edit and create the NET.CFG file and add a Link Driver section heading for each time the driver is to be loaded.
009: The NET.CFG entry has been ignored.
Source:
TRXNET-DOS.LAN
Explanation:
The driver cannot be loaded consecutively unless you create a NET.CFG file each time.
Action:
Unload the TRXNET driver. Edit/create the NET.CFG file and add a Link Driver section heading for each time the driver is to be loaded.
011: The MLID does not support frame type. The protocol keyword has been ignored.
Source:
TRXNET-DOS.LAN
Explanation:
An unsupported or incorrectly typed frame type has been specified with the protocol keyword.
Action:
Check the contents of the NET.CFG file, and verify the frame type assigned under the PROTOCOL keyword is valid.
012: The protocol keyword must have a frame type. Entry ignored.
Source:
TRXNET-DOS.LAN
Explanation:
The PROTOCOL keyword entry is incomplete.
Action:
Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:
PROTOCOL TRXNE hex_protocol_ID frame_type
013: The MLID could not register Protocol ID number for protocol stack name for frame type type.
Source:
TRXNET-DOS.LAN
Explanation:
The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.
Action:
Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:
LINK SUPPORT
MAX STACKS 6
Unload the driver; then reload it as in the following example:
C:\NWCLIENT\TRXNET /u <Enter>
C:\NWCLIENT\LSL /u <Enter>
C:\NWCLIENT\LSL <Enter>
C:\NWCLIENT\TRXNET <Enter>
014: This version of the LSL is not supported.
Source:
TRXNET-DOS.LAN
Explanation:
The driver you are using supports only Link Support Layer (LSL) versions later than 1.0.
Action:
Unload the LSL and replace it with a newer version.
015: The frame type is already active for frame type.
Source:
TRXNET-DOS.LAN
Explanation:
The frame type is already loaded, and it cannot be loaded repeatedly.
Action:
Edit the NET.CFG file to load the frame type only once for a given network board.
016: The node address was incorrectly specified in the NET.CFG file.
Source:
TRXNET-DOS.LAN
Explanation:
The node address override in the NET.CFG file is too long.
Action:
Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits.
017: An invalid keyword was specified in NET.CFG on line number.
Source:
TRXNET-DOS.LAN
Explanation:
The key word on the line indicated was not recognized.
Action:
Edit the NET.CFG file and correct the spelling of the keyword.
018: The frame type specified in the NET.CFG is not supported.
Source:
TRXNET-DOS.LAN
Explanation:
The frame type specified with the FRAME keyword is not supported by the driver.
Action:
Edit the NET.CFG file and fix frame type.
019: An invalid TRXNET node address is specified in NET.CFG. The MLID modified the incorrect address bits.
Source:
TRXNET-DOS.LAN
Explanation:
The node address specified in the NET.CFG file has set reserved bits.
Action:
Edit the NET.CFG file and correct the node address.
025: You cannot load MSM31X on a NetWare 3.10 server.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Explanation:
The computer attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.
Action:
Load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare 3.11 or later server.
026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM after the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)
Action:
Unload MSM31X.NLM; then load LSLENH.NLM. After the LSLENH.NLM has been loaded, load MSM31X.NLM again.
050: The board cannot be found.
Source:
NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The network board is not present in the computer, or the network board’s configuration cannot be obtained.
Action:
Do one of the following:
-
Make sure the network board is properly seated into the slot.
-
Insert the network board into a slot, and run the Reference diskette to install it.
Possible Cause:
The network board settings are not the defaults, and they are not defined in the AUTOEXEC.NCF file.
Action:
If jumper settings are not the defaults, make sure they match the settings in the AUTOEXEC.NCF file. If the computer is not using the AUTOEXEC.NCF file, make sure the jumper settings are set to the defaults.
Possible Cause:
Another network board is using the same hardware settings as this network board.
Action:
If other network boards are using the same hardware settings, change the settings and try to reload the driver.
Possible Cause:
The network board is faulty.
Action:
Replace the bad network board.
050: [Microchannel] The board cannot be found.
Source:
TRXNET-DOS.LAN
Explanation:
If you are using a microchannel network board, the network board is not in the machine, or the network board’s configuration could not be obtained.
Action:
Do one of the following:
-
Make sure the network board is properly seated into a slot.
-
Insert the network board into a slot, and run the Reference diskette to install it.
051: Board RAM failed the memory test.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The memory test on the network board’s internal static RAM failed.
Action:
Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. If the settings match, replace the network board.
054: The board did not respond to the initialization command.
Source:
NE1000-NW.LAN, TRXNET-DOS.LAN
Possible Cause:
The network board didn’t respond to a reset command.
Action:
Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. If the settings match, replace the network board.
065: Board cannot be found at slot/IO port. (Please check SLOT and PORT values in the NET.CFG.)
Source:
TRXNET-DOS.LAN
Action:
If you are using an ISA Bus network board, check the slot number and the I/O address in the NET.CFG file.
If you are using a microchannel network board, do one or more of the following:
-
Correct the slot number in the NET.CFG file to match the slot where the network board is physically located.
-
Move the network board to the slot specified in the NET.CFG file; then run the Reference diskette to install the network board.
066-Adapter 1: The cable might be disconnected on the board.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN
Possible Cause:
The cable is disconnected, or heavy traffic on the wire is delaying a packet from being sent.
Action:
If the problem persists, check the cable, or consider adding more networks to decrease LAN traffic.
067: The group bit in the node address override was cleared.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Explanation:
This informational message informs you that you entered a node address with the Group address bit set. The Topology Specific Module (TSM) cleared it.
068: The local bit in the node address override was set.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
This informational message inform you that you entered a node address without the local bit being set and that the Topology Specific Module (TSM) set it.
071: The matching virtual adapter could not be found.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.
Action:
Obtain the latest version of MSM.NLM.
072: A resource tag is unavailable.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The server does not have enough available memory. NetWare cannot allocate memory for a resource tag.
073: Unable to allocate memory.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The server does not have enough available memory. NetWare cannot allocate memory for the LAN driver.
074: The hardware interrupt cannot be set.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.
Action:
Make sure the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file.
075: The MLID cannot be registered with the LSL.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The LAN driver’s Link Support Layer (LSL) ran out of logical boards,
Action:
Unload nonessential LAN drivers that are consuming large numbers of logical boards.
Possible Cause:
The LAN driver’s Link Support Layer could not allocate memory for its internal structures.
076: The polling procedure cannot be added.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
Too many polling processes are registered with the operating system.
Action:
Unload nonessential NLM programs that are using a polling procedure.
077: The event notification routine cannot be registered.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The server does not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification.
079: The MLID did not initialize MSMTxFreeCount.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The .LAN file is outdated or corrupted.
Action:
Obtain a new .LAN file.
086: The driver parameter block is too small.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The .LAN file is designed to run with an older version of the MSM.NLM.
Action:
Obtain a newer version of the .LAN file or an older version of the MSM.NLM.
087: The media parameter block is too small.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The topology NLM is designed to run with an older version of the MSM.NLM.
Action:
Obtain a newer version of the topology NLM program or an older version of the MSM.NLM.
091: The hardware configuration conflicts.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
Another hardware resource is being used, which the LAN driver is trying to register.
Action:
Change the hardware configuration of the network board or of the conflicting device.
092: Cannot schedule AES without an HSM routine.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The LAN driver is outdated or corrupted.
Action:
Obtain a new .LAN file.
093: Cannot schedule interrupt time call back without an HSM routine.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The LAN driver is outdated or corrupted.
Action:
Obtain a new .LAN file.
094: Cannot set hardware interrupt without an HSM routine.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The LAN driver is outdated or corrupted.
Action:
Obtain a new .LAN file.
095: Cannot add polling without an HSM routine.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN, NE3200-NW.LAN
Possible Cause:
The LAN driver is outdated or corrupted.
Action:
Obtain a new .LAN file.
200-Adapter 1: The board’s DMA did not complete the write.
Source:
NE1000-NW.LAN, NE2-NW.LAN, NE2000-NW.LAN
Possible Cause:
The network board did not complete a Direct Memory Access (DMA) transaction within the specified time. The driver will attempt to correct the problem by resetting the network board and resending the packet.
Action:
If the problem occurs often (more than once or twice a day), replace the network board.
201: DIR.OPEN.ADAPTER error code = error_bit_number.
Source:
CNTR2000.LAN
Explanation:
The network board cannot be opened for operation.
223: The board must be placed in a 16-bit slot.
Source:
NE2000-NW.LAN
Explanation:
The network board was placed in an 8-bit slot.
Action:
Move the network board to a 16-bit slot.
224: This board is configured as an NE1000.
Source:
NE2000-NW.LAN
Explanation:
The board is responding with an NE1000 ROM signature.
Action:
Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. If the settings match, replace the network board.
233: The adapter detected a duplicate station during the insertion process.
Source:
CNTR2000.LAN
Explanation:
Another network board is using the same node address.
Action:
Use a different node address.
235: The adapter cable was disconnected during the insertion process.
Source:
CNTR2000.LAN
Explanation:
The network board could not access the network because the cable was disconnected.
Action:
Securely fasten the cable links, reboot the workstation, and reload the driver.
236: The ring was beaconing during the insertion process.
Source:
CNTR2000.LAN
Explanation:
The network board could not access the network because it is set at an incorrect data rate.
Action:
Set the network board to the correct data rate.
237: The adapter is beaconing.
Source:
CNTR2000.LAN
Explanation:
The ring has detected a network board that is trying to access the network with an incorrect data rate.
Action:
Find out which network board in the ring is set at an incorrect data rate, and correct it.
239: The cable is disconnected at the board.
Source:
CNTR2000.LAN
Explanation:
The cable is disconnected from the network board.
Action:
Securely fasten the cable to the network board.
240: Cable is disconnected at the MAU.
Source:
CNTR2000.LAN
Explanation:
The cable is disconnected from the Multistation Access Unit (MAU).
Action:
Securely fasten the cable into the MAU.
241: The Auto Removal process reset the adapter.
Source:
CNTR2000.LAN
Explanation:
The network board removed itself from the ring due to internal errors. The driver will reset the network board and continue.
Action:
No action is required. If this condition occurs frequently, install another board to see if it continues.
241: The board’s ROM has checksum errors.
Source:
NE3200-NW, CNTR2000.LAN
Possible Cause:
The network board failed the self-test. A ROM checksum error occurred.
Action:
Check the network board and other hardware. If necessary, replace the network board.
242: The Remove MAC Frame process shut down the adapter.
Source:
CNTR2000.LAN
Explanation:
The network board removed itself from the ring as requested by another network board.
Action:
Replace the network board with one that works.
A transmit timed out. The cable might be disconnected from the board.
Source:
CNE2.LAN, CNE2000.LAN, CNE2_32..LAN
Explanation:
The transmission process timed out. This could be due to one of two reasons: the network cable is disconnected, or heavy traffic on the wire is delaying packets from being sent.
Action:
Check the cable to ensure the connection is good. If the cable connection is good and the problem persists, network traffic might be heavy. Consider redesigning the cabling to decrease LAN traffic.
An interrupt failed to occur during initialization.
Source:
CNTR2000.LAN
Explanation:
The network board never interrupted the host after it was reset.
Action:
Replace the network board with one that works.
No interrupt was selected. The board must be reconfigured.
Source:
CNE3200.LAN
Explanation:
No interrupt was specified when the network board was installed.
Action:
Run the EISA Configuration diskette that came with the computer, and select an interrupt.
The board cannot be found.
Source:
CNE2.LAN, CNE2000.LAN, CNE2_32..LAN, CNE3200.LAN
Explanation:
The driver cannot find or recognize the adaptor board. Either the network board is not present in the computer, or the network board’s configuration cannot be obtained.
Action:
Make sure the network board is properly seated in the slot and properly configured.
Also, refer to the manufacturer’s instructions for configuring the network board.
If the board still does not respond, replace it with one that works.
The board did not respond to the initialization command.
Source:
CNEAMD.LAN, CNE2.LAN, CNE2000.LAN
Explanation:
The LAN driver cannot get the network board to initialize. This could be due to improper configuration or faulty hardware.
Action:
Make sure the port and interrupt settings on the network board match the settings in the configuration file.
Also, refer to the manufacturer’s instructions for configuring the network board.
If the board still does not respond, replace it with one that works.
Source:
CNE3200.LAN
Explanation:
Firmware was downloaded to the network board, but the network board did not accept commands. The board is not operating correctly, and it has failed.
Action:
Check the network board and other hardware. If necessary, replace the network board.
The board must be placed in a 16-bit slot.
Source:
CNE2000.LAN
Explanation:
The network board was placed in an 8-bit slot, but it was designed to operate in a 16-bit slot.
Action:
Move the network board to a 16-bit slot.
The board’s DMA did not complete.
Source:
CNE2.LAN, CNE2000.LAN
Explanation:
The network board’s remote Direct Memory Access (DMA) transaction did not complete within the specified time. The driver will attempt to correct the problem by resetting the network board and resending the packet.
Action:
If the problem occurs often (more than once or twice a day), replace the network board.
The board’s IRQ cannot be found.
Source:
CNEAMD.LAN
Explanation:
The interrupt setting is incorrect or is not available.
Action:
Make sure the interrupt setting on the network board matches the setting in the configuration file.
Also, refer to the manufacturer’s instructions for configuring the network board.
If the board still does not respond, replace it with one that works.
The board’s memory failed the memory test.
Source:
CNE2.LAN, CNE2000.LAN, CNE3200.LAN
Explanation:
The network board’s memory failed.
Action:
Make sure the port and interrupt settings on the network board match the settings in the configuration file.
Also, refer to the manufacturer’s instructions for configuring the network board.
If the board still does not respond, replace it with one that works.
The board’s PORT cannot be found.
Source:
CNEAMD.LAN
Explanation:
The port address setting is incorrect or not available.
Action:
Make sure the port setting on the network board matches the setting in the configuration file.
Also, refer to the manufacturer’s instructions for configuring the network board.
If the board still does not respond, replace it with one that works.
The cable might be disconnected on the board.
Source:
CNEAMD.LAN,
Explanation:
The network cable is disconnected, or heavy traffic on the wire is delaying packets from being sent.
Action:
Check the cable to ensure the connection is good. If the cable connection is good and the problem persists, network traffic might be heavy.
The driver was unable to schedule periodic AES callbacks.
Source:
CNE2.LAN, CNE2000.LAN
Explanation:
The LAN driver was unable to schedule an asynchronous event on a periodic basis.
Action:
Contact a Novell support provider.
Unable to allocate memory.
Source:
CNEAMD.LAN
Explanation:
The client workstation or NetWare server might not have enough available memory. NetWare cannot allocate memory for the LAN driver.