2-42 RF Throughput, Performance and Troubleshooting
MX2 Reference Guide Revision A MX2A137REFGD
Problems with DOS Drivers
Some problems may occur in the DOS environment. Many problems can
be caused by inappropriate memory, I/O, or IRQ settings for the MX2. If
changing those settings in the NET.CFG or PROTOCOL.INI file doesn’t
solve the problem, consult the following list of symptoms to identify
other possible causes. Contact your systems administrator if you need
additional help.
NDIS driver does not install or does not work
• Domain, memory address, I/O address hex values in
PROTOCOL.INI
file not specified with leading 0x.
• Memory range not reserved
• Incompatible protocol manager and stack
• Improper linking in PROTOCOL.INI
file
• Memory, I/O, or IRQ setup conflicts with other installed
software or hardware
ODI driver does not install or does not work
• Memory range not reserved
• Incompatible protocol manager and stack
• Improper linking in NET.CFG
file
• Memory, I/O, or IRQ setup conflicts with other installed
software and hardware
TCP/IP fails
• Incorrect IP/subnet address
• Incorrect domain; check for MU association
Nothing happens after installation of the network software (no
login, cannot find server, no TCP connection)
• Incompatible firmware and driver versions
• Memory, I/O, or IRQ setup conflicts with other installed
software or hardware
• MU is out of range
• All cards must have matching security IDs to communicate
