Diagnosing RT-TCP/IP Configuration Problems

If the RtxTcpIp Stack cannot attach to the interrupt vector requested by a network device, then chances are that an RTX or Windows driver is using the same IRQ in the system.

The RtxTcpIp Stack can also fail for any of the following reasons:

The RTX dedicated NIC is not configured to use the IRQ or IOAddr specified in the configuration file or these resources conflict with another device.
The RTX dedicated NIC is not a supported network card.
The IPAddr conflicts with another network adapter on the LAN.
The Netmask is incorrectly set.

Before calling customer support, please eliminate the above by testing your intended configuration of IRQ, IOAddr, IPAddr and Netmask using Windows.

NOTE: When using Windows, physically install the card and it will be automatically configured on boot.

Once the NIC is configured as a Windows network adapter, you should be able to ping its IPAddr from another system on the LAN and get a response. If problems occur, assistance is available from the Network Troubleshooter under Windows Help.

On Windows, you can find the IRQ and IOAddr in Device Manager by right-clicking on the Network Card's icon and selecting Properties.

An additional test is needed to insure that the NIC is not sharing interrupts with other devices. Even if the NIC is on a PCI bus, it could be inadvertently installed in a PCI slot that shares its interrupt with an ISA slot. To rule out interrupt sharing on Windows, you need to check the device status through Device Manager.

A NIC that shares its interrupt may work correctly with Windows, but will not work when dedicated for real-time use. If the NIC is an ISA card, reassign its IRQ so that the interrupt is unshared. If the NIC is a PCI card, move the PCI card to a slot that does not share its interrupt.

Once this testing is complete, be sure to either uninstall or disable the Windows driver for the NIC so that it is again dedicated to RT-TCP/IP use.