7 replies
by vanster169
Well you havent' really given enough info yet. What protocols are you running (besides IPX of course...)? What error messages are you getting? now is your port on the switch configured? (10 mbit or 100?) Does it autosense, if so then you MUST lockdown either the NIC or the switch port to the highest speed the hardware permits, don't allow them both to autosense.
Check the server stats and see if you are getting "No ECB available" hits - this could mean not enough RAM on the server, not enouch buffers allocated for communications, a bad cable or just simply that your NIC is saturated and can't handle any more data. (in Monitor: LAN/WAN Info, then choose the protocol binding, and study it.)
cheers
by liontech
by liontech
In addition to the other two gentleman's answers, I did in fact have a similar situation while using NetWare 4.11, on a Compaq Server.
It ended up being the Compaq NIC driver. The one that comes with NetWare did not work correctly, even though NetWare did sense and use it on upon Install. What made it really tough, is that the file name is the same as the one available at Compaq. Still, it was intermittent, and we chased it around for a week or so, till we downloaded the EXACT matching NIC driver from Compaq. You may also need new firmware for the Compaq box. If you are not using the Compaq NIC, we have had similar problems with hardware version vs. driver versions on Intel and 3Com NICS. In addition, after we ran a NetWare 4.11 patch, itput the wrong NIC drivers back in, so we had to go back in and replace them once again. Since upgrading to NetWare 5, we have had little if any problems with NIC driver incompatabilities. You might try going to IRQ 5, instead of 12 (if possible)after reviewing the Compaq setup routine. It could be that a Compaq Server MotherBoard item, and an added 3rd party NIC are not handling IRQ 12 well. Compaq is so proprietary. Good luck!
by liontech
by liontech
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending