03-27-2012 03:56 PM
Hi, Our company no longer lets most users configure the windows firewall. To use various Labview communications resources you need to have various ports open. Our wiz-bang security keeps them closed, and there is no feed back to let you know if they are closed, or if a program is trying to use them (unlike normal windows operations). I have found good documentation that shows what needs to be opened for various resources. http://zone.ni.com/devzone/cda/tut/p/id/12402 I was thinking of building a program to test these out, so that the administrators of the systems could test to see if they indeed opened the correct ports. I was thinking of a program that just tries to use all the needed ports to communicate with a second computer on the network. Then you could get a report back saying if any ports did not communicate succesfully. What better to use to test for Labview's ability to communicate than Labview itself. Has someone seen this already done? Thanks for your input!
03-28-2012 04:43 PM
I have never tried this myself, but from what you have described I believe that would be a sound way to test the ports your firewall would be blocking. Let me know how it works.