‎06-17-2014 02:30 PM
That makes sense, however, the windows firewall is turned off. And unless NI installed other firewall software, there should be no port or IP blocking what so ever. I'm open to any suggestions.
‎06-17-2014 03:15 PM
NI is not blocking ports, but as soon as you try to connect from one machine to another then there are multiple points of failure: The server OS can be blocking ports, or the router may have its own firewall, or the router may not even be configured properly for you to talk to the other machine. In diagnosing this kind of issue I usually start from the server side and work my way out:
‎06-17-2014 03:29 PM
On your points:
1) Verified.
2) Ping works between any two of the three NI 8135 controllers, yet only one has web services accessible.
3) Using IP's only.
4) Same application executing on three controllers with two different behaviors. They can all talk to themselves (#1), but only one is accessible from the other two.
And most importantly, none provide web services accessible from the linux host, even though all of the systems are accessed via remote desktop from the linux host.
Also, all the systems are connected via a switch (no router).
‎06-17-2014 03:40 PM
This still sounds like some kind of Windows security setting that is blocking that incoming port. I don't know enough about Windows security settings except to say that I have run into similar issues before and struggled to get it to allow my programs to open ports before, even with the firewall "off". Maybe this will help: http://technet.microsoft.com/en-us/library/cc766312%28WS.10%29.aspx
I'm sorry I can't help much more, but this really does sound like an OS or network configuration issue to me, and I just don't know enough about your system to help you there.