System: A new Windows 7 workstation serving in a manufacturing area that runs a manufacturing app . It has 2 NICs. (1) on the domain with normal IPv4 provisioning, and a 2nd NIC on the 172.16.0.0 range for direct connection to a test machine.
During initializing, the manufacturing app merely attempts to connect to the 2nd NIC via the TcpClient class provided in the .NET (C#) framework, using the IP address 172.16.0.20 and port 69 (the default TFTP port). If a connection is established, the test passes; otherwise it fails, and the MFG app displays that error message.
Previously, on Windows 7 PCs using for instance, an Infineon AN983B PCI Based Fast Ethernet, the the manufacturing app was able to connect to the nic without a cable connection. But the new Windows 7 system, incorporating a Realtek PCI GBE adapter will not respond to an internal ping with it's cable disconnected.
Is there a method of making a newer NIC respond internally even if the Ethernet cable is disconnected?