Error messages with "IPX" numbers (such
as IPX00010) are NetWare Connectivity errors. These messages are
listed here, along with tips for solving the problems causing each
error.
Messages with "NET" numbers are LAN Manager
errors. On workstations running LAN Manager Enhanced, you
can use the net helpmsg command to get help
about "NET" errors. For example, to see more information
about error NET2141, you would type:
NetWare Connectivity Errors |
 |
IPX00010: Cannot load the IPXNDIS.DOS driver or
cannot read PROTOCOL.INI.
Check that the CONFIG.SYS file has
a device entry loading the IPXNDIS.DOS driver; for example:
device=c:\lanman.dos\drivers\protocol\ipxndis\ipxndis.dos |
If the device entry is missing, add
it.
Check that the IPXNDIS.DOS driver is installed in
the directory specified by the device entry
loading it. If it is not there, copy it from another workstation
that runs NetWare Connectivity, and then reboot the computer. If
this is not possible, reinstall NetWare Connectivity on the computer.
Check that the IPX driver is bound to a network
adapter driver. To do so, use the LAN Manager Setup program.
(For more information, see Chapter 2, "Installing
and Configuring NetWare Connectivity.")
If you change the workstation's configuration, reboot
the workstation before loading NetWare Connectivity again.
Be sure the PROTOCOL.INI file is in the LANMAN.DOS
directory. If it is not, use the LAN Manager Setup program
to again specify the network drivers you are using. This will re-create
the PROTOCOL.INI file. Now reboot the workstation.
Check the CONFIG.SYS file to be sure Protocol Manager
(the PROTMAN.DOS file) is loaded. CONFIG.SYS should contain a device
entry loading PROTMAN.DOS, similar to this:
device=c:\lanman.dos\drivers\protman\protman.dos /i:c:\lan
man.dos |
This device entry must appear before
all device entries that load protocol drivers (such as IPXNDIS.DOS)
and network adapter drivers.
IPX00011: Cannot release environment space. Proceeding
to unload NetWare Connectivity.
No action is required. The workstation
will have about 256 bytes less environment space available, however.
If this loss of environment space is a problem and this continues
to occur, contact your technical support personnel.
The environment space is an amount of
memory set aside by MS-DOS to store the values of various variables,
including the search path. To allocate more environment space on
the workstation, add the /e option to the
shell entry in CONFIG.SYS, and then reboot
the workstation so the change can take effect. For more information,
see your MS-DOS manual(s).
IPX00012: Cannot locate PATH entry. After you unload
NetWare Connectivity, your search path may be incorrect.
If the workstation has a search path
specified by a path entry in the AUTOEXEC.BAT
file (or another batch file), NetWare Connectivity cannot read it.
Check the syntax of CONFIG.SYS to be sure the path
entry is correct.
IPX00014: NetWare Connectivity is already loaded.
IPX00015: NetWare Connectivity does not support
this version of MS-DOS.
Install a different version of MS-DOS.
NetWare Connectivity supports versions 3.1 and later.
IPX00020: You cannot load this program while the
Windows operating system is running.
Close the Microsoft Windows
operating system and try again.
You cannot use nwload, nwunload,
or ipx commands while the Windows operating
system is running.
IPX00021: NWUNLOAD cannot be completed. NetWare
Connectivity may still be using memory.
If the workstation can still run the
programs it needs to, no action is required. Otherwise, reboot the
workstation.
This message also appears if you start NetWare by
typing ipx and netx
directly (bypassing nwload), and then try
to use nwunload.
If this error occurs often when you use nwload
and nwunload, contact your technical support
personnel.
IPX00022: Other TSRs loaded after NetWare Connectivity
loaded. Unload these before unloading NetWare Connectivity.
Unload the other terminate-and-stay-resident
programs (TSRs), and then try unloading NetWare Connectivity again.
To prevent this problem, don't load other TSRs after
you load NetWare Connectivity.
IPX00023: Cannot unbind IPX from network adapter
driver. NetWare Connectivity cannot unload.
Reboot the workstation and try again.
If the problem persists, the network adapter driver may not be compatible
with NetWare Connectivity.
IPX00026: Cannot restore the saved PATH entry because
there is not enough environment space.
To restore the search path after you
run NetWare Connectivity, increase the amount of environment space
on the workstation. To do so, add the /e
option to the shell entry in the CONFIG.SYS
file, and then reboot the workstation so the changes can take effect.
For more information, see your MS-DOS manual(s).
IPX00027: NetWare Connectivity is not loaded.
To load NetWare Connectivity, type
nwload or the combination of ipx
and netx.
IPX00028: Cannot unload IPX because it is not an
NDIS version.
The IPX protocol that is currently
running is a monolithic version for Novell NetWare rather than the
NDIS-compliant version for NetWare Connectivity. You can't
unload it without rebooting the computer.
To prevent this problem, be sure to use only the NDIS-compliant
version of IPX.COM.
IPX0100: Unknown error.
Contact your technical support personnel.
IPX0101: Cannot open Protocol Manager.
Check CONFIG.SYS to be sure Protocol
Manager (the PROTMAN.DOS file) is loaded. CONFIG.SYS should contain
a device entry loading PROTMAN.DOS, similar
to the following:
device=c:\lanman.dos\drivers\protman\protman.dos /i:c:\lan
man.dos |
This entry must appear before all device
entries that load protocol drivers (such as IPXNDIS.DOS) and network
adapter drivers.
If CONFIG.SYS has such an entry, be sure it specifies the
correct path of the PROTMAN.DOS file.
IPX0102: Cannot bind IPX to the network adapter
driver.
Check the CONFIG.SYS and PROTOCOL.INI
files.
In CONFIG.SYS, check that the correct
network adapter driver is being load ed by a device
entry.
In PROTOCOL.INI, check that the correct network
adapter driver is specified in the bindings entry in the [IPX] section.
If the problem persists, use the LAN Manager
Setup program to remove and then to reinstall both the IPX protocol
and the network adapter driver that IPX is bound to. This procedure
recreates PROTOCOL.INI
IPX0103: Cannot load network adapter card driver.
Check PROTOCOL.INI to be sure the
[IPX] section has a bindings entry that specifies
a network adapter driver. Also check the CONFIG.SYS file to be sure
that there is a device entry loading that
network adapter driver.
IPX0104: The network adapter card driver cannot
load because it is incompatible with the computer's network adapter
card.
Use the correct driver for the computer's
adapter.
IPX0105: The network adapter card failed.
Have the network adapter checked and
serviced.
IPX0106: The PROTOCOL.INI file is not correct.
Check the [IPX] section of the PROTOCOL.INI
file for errors.
If you can find no error in PROTOCOL.INI, use the
LAN Manager Setup program to remove and then to reinstall
both the IPX protocol and the network adapter that IPX is bound
to. This procedure automatically re-creates PROTOCOL.INI.
IPX0107: NetWare Connectivity doesn't support this
network adapter card driver.
Check the interrupt settings on your
network adapter.
Be sure you are using a network adapter driver that
conforms to NDIS standards.
IPX0108: Cannot initialize IPX shell driver.
If the workstation has a search path
specified by a path entry in the AUTOEXEC.BAT file (or another batch
file), NetWare Connectivity cannot read it. Check the syntax of
CONFIG.SYS to be sure the path entry is correct.
Try again. If the problem persists, contact your
technical support personnel.
IPX0109: IPX cannot bind to network adapter card
driver.
Check the CONFIG.SYS and PROTOCOL.INI
files.
In CONFIG.SYS, check that the correct
network adapter driver is being load ed by a device
entry.
In PROTOCOL.INI, check that the correct network
adapter driver is specified in the bindings
entry in the [IPX] section.
If the problem persists, use the LAN Manager
Setup program to remove and then to reinstall both the IPX protocol
and the network adapter driver that IPX is bound to.
IPX0110: Network adapter card has a bad connection.
Check the connection, including the
adapter's connection and the network cable attached to
the adapter. If necessary, replace the network adapter or cable.
IPX0113: Novell's IPX can bind to only one network
adapter card driver.
Use the LAN Manager Setup
program to specify that IPX be used with only one network adapter.
This single-adapter requirement is a limitation of Novell's
IPX.
IPX0115: Protocol Manager isn't loaded correctly
in CONFIG.SYS or isn't installed.
Check the CONFIG.SYS file to be sure
Protocol Manager (the PROTMAN.DOS file) is loaded. CONFIG.SYS should
contain a device entry loading PROTMAN.DOS, similar to the following:
device=c:\lanman.dos\drivers\protman\protman.dos /i:c:\lan
man.dos |
This entry must appear before all device
entries that load protocol drivers (such as IPXNDIS.DOS) or network
adapter drivers.
If CONFIG.SYS has such an entry, be sure it specifies
the correct path of the PROTMAN.DOS file.
IPX0116: Not enough memory.
Free additional memory by stopping
other terminate-and-stay-resident (TSR) programs or other processes,
and then try again.
If you can, free more conventional memory by loading
MS-DOS and/or LAN Manager into other areas of memory. For
more information, see Chapter 2, "Installing and
Configuring NetWare Connectivity."
If you get this error, you may be able to load NetWare by
following the steps in Chapter 2, but you still may run
into more memory problems when you start applications. It may be
necessary to add more memory to the computer.
IPX0117: You must use the IPXNDIS.DOS device driver
or type LOAD IPX.
To run the IPX protocol, you must
use either the nwload or load
ipx command to start it, or load the IPXNDIS.DOS driver
in CONFIG.SYS.
If you normally don't use the nwload
or load ipx commands, but instead type ipx,
check your CONFIG.SYS file. It should contain a device
command loading IPXNDIS.DOS.
If CONFIG.SYS does contain such a
device line, be sure that the IPXNDIS.DOS
file is located in the path specified by the line in CONFIG.SYS.
IPX0119: IPXNDIS.DOS driver isn't loaded correctly
in CONFIG.SYS.
In CONFIG.SYS, check that there is
a device entry loading IPXNDIS.DOS, such
as the following:
device=c:\lanman.dos\drivers\protocol\ipxndis\ipxndis.dos |
Check that the IPXNDIS.DOS driver is installed on
the hard disk in the path specified by the device
entry loading it.
If the problem persists, use the LAN Manager Setup
program to remove and then to reinstall both the IPX protocol and
the network adapter driver that IPX is bound to.
Printable version
