If the RT-TCP/IP Stack cannot attach to the interrupt vector requested by a network device, it is likely that an RTX64 driver or Windows driver is using the same IRQ in the system.
The RT-TCP/IP Stack can also fail when:
- The RTX64 dedicated NIC is not a supported network card.
- The IPV4 Address 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, IPAddr and Netmask using Windows.
To test the IP Address using the Windows driver:
- Use Device Manager to select a Windows-provided driver.
- Once the NIC is configured as a Windows network adapter, you should be able to ping its IP Address from another system on the LAN and get a response. If problems occur, assistance is available from the Network Troubleshooter under Windows Help.
- Once you have finished testing, be sure to convert the device back to RTX64.
To test the Netmask using the Windows driver:
- Use Device Manager to select a Windows-provided driver.
- On Windows, you can find the IRQ in Device Manager by right-clicking on the Network Card's icon and selecting Properties.
- An additional test is needed to ensure 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 a legacy device, such as a USB controller. 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. Move the PCI card to a slot that does not share its interrupt, or, if possible, disable the Windows device with which it is sharing its interrupt.
- Once you have finished testing, be sure convert the device back to RTX64.
