Ethernet setup question

[A1Penguin]

All of our test stands have two NIC cards.  One for the local test instrument network using the 192.168.1.xxx addresses.  The test stand computer and all of the instruments have fixed IP addresses on this local network.  The other NIC connects the test stand to the building network.   Somewhere out on the building network, there is a spectrum analyzer plugged directly into it without a local network of its own.  For some reason on all of the test stands, MAX not only sees the 192.168.1 instruments which are local to themselves, but also this rogue spectrum analyzer, which we would never want to communicate with.  Is there anything we might be doing incorrectly based on this information?  Can we tell LabVIEW or MAX not to be concerned with anything happening out on the building network?

This question came up because our test stands will run their test programs flawlessly for hundreds of iterations and then randomly, we will get a VISA error saying "Insufficient location information or resource not present in the system" for some instrument that was perfectly happy seconds ago.  We are wondering if something out on the building network (maybe this rogue analyzer) could be responsible for this.  Any other ideas would also be greatly appreciated. Thank you. 

[crossrulz]

---

@A1Penguin wrote:

This question came up because our test stands will run their test programs flawlessly for hundreds of iterations and then randomly, we will get a VISA error saying "Insufficient location information or resource not present in the system" for some instrument that was perfectly happy seconds ago.  We are wondering if something out on the building network (maybe this rogue analyzer) could be responsible for this.  Any other ideas would also be greatly appreciated. Thank you. 

---

That sounds more like you somehow lost your VISA reference.  A zero iteration FOR loop would be the first thing I would look for (been burnt there way too many times).  I would not expect something happening on the building network to affect your connections to the local network.  There is also the possibility that IT did something to cause the local connections to blip (I purposefully avoid putting my test stations on the building network because of this).