Intel® PRO/1000 and EtherExpress™ 16, Flash 32, PRO/10, PRO/10+, PRO/100, PRO/100B, PRO/100+ adapters
NetWare* server error message: "Router configuration error detected. Router at node <nodeaddress> claims network <address1> should be <address2>."
Inconsistency in network numbering will cause this error message. Each segment of an IPX network must have a unique IPX external network number assigned for each frame type. This network number must be constant for all devices (servers, routers, etc.) attached to that segment and using that frame type.
In general, a segment can be defined as any shared network communication medium, such as;
- In 10base5 or 10base2, a contiguous coaxial cable .
- In twisted-pair cabling networks, a hub, or multiple hubs joined into a common collision domain.
- Any of the above joined by a repeater or layer 2 switch. A layer 2 switch (A.K.A. switching hub) is a device that routes packets based solely on the embedded MAC address and is indifferent to protocols.
This error message is most commonly caused by IPX being bound to 2 different network adapters with the same frame type on the same segment, but with different IPX external network numbers assigned to each. IPX external network numbers are assigned when you bind IPX to a logical board and must be unique for each segment, as opposed to an IPX internal network number, which is assigned on server startup and must be unique for each server.
For example, suppose you are using two EtherExpress™ PRO/10+ PCI adapters on a twisted pair network in your NetWare server and the following is your AUTOEXEC.NCF;
LOAD E100B SLOT=13 FRAME=ETHERNET_802.2 NAME=CARD1
LOAD E100B SLOT=14 FRAME=ETHERNET_802.2 NAME=CARD2
BIND IPX TO CARD1 NET=1
BIND IPX TO CARD2 NET=2
As long as each of the two cards is connected to a separate hub, this would work without error. However, if you connected the two hubs together with a twisted pair cable (joining them into a single segment), the computer will respond with the error message listed above.
In general, if your NetWare server displays this message, follow these steps;
- Look for loops in your network connections that might join segments together.
- Check the configuration of all devices (servers, routers, network printers, etc.) connected to the segment in question, making sure that the net number is consistent for that frame type.
- If no discrepancies are found in step 1 or 2, check for a malfunctioning or mis-configured router.
- For more information, see technical document 1202712 "Summary of Router Configuration Errors", available in Novell's* Knowledgebase.
NetWare server error message: "Insufficient Receive Buffers. Set maximum packet receive buffer size to 1536 in startup.ncf"
If you receive this message when loading an Intel® EtherExpress LAN driver, add the following line to your STARTUP.NCF file;
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE=2048
This parameter determines how much memory your server allocates to each packet buffer. It has no effect on the size of the actual packets.
NetWare server error message: "Loader cannot find public symbol: <symbol name>"
If this error is displayed when loading the LAN driver for your network adapter, it usually indicates an out of date network support NLM is in use (especially the files MSM.NLM, NBI.NLM and ETHERTSM.NLM for Ethernet adapters or TOKENTSM.NLM for Token ring adapters). Please update your NetWare server to the latest network support NLM's. Also, it is important to properly apply the latest patches / service packs to your server, carefully following the included instructions. These files are all available on Novell's* electronic services under the category, "Minimum Patch List".
Note: For NetWare 3.11 or 4.0x, you must use 3.2 specification LAN drivers. For newer versions of NetWare, use the latest LAN driver available from Intel.
NetWare server error message: "Warning: This version of NetWare does not support protected mode BIOS accesses. Without a loader patch some PCI drivers may fail."
This message may be displayed when loading a 3.3x ODI spec LAN driver. It is caused by the latest patches not being applied properly, or by out of date NLM's.
Make sure your NetWare server has the latest 3.3x spec NLM's and the latest patches. These are available from Novell's* electronic services under the category, "Minimum Patch List".
If the latest patches have been applied, make sure the loader patch was properly applied using the LSWAP utility per Novell's instructions.
This applies to: