![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/b/39/b394d6b1-b1a2-48c6-b78d-b649e0bc02ec/b394d6b1-b1a2-48c6-b78d-b649e0bc02ec-bg44.png)
58 RF Throughput, Performance and Troubleshooting
MX2 Reference Guide E-EQ-MX2RG-L-ARC
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 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.
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
Slow or erratic performance
• Out of communication range
• Faulty antenna, antenna connector, or cable
Driver does not install, or driver hangs during installation
• Incompatible firmware and driver versions
• Memory range not reserved
• Memory range does not match setting in NET.CFG file
• Memory range is too small (use I/O mode if memory is restricted)
• Memory, I/O, or IRQ setup conflicts with other installed software or hardware