Network issue in runtime

[rolfk]

Windows Firewall (and most others) have rules that are based on the executable and the actual location in the filesystem. When you run in the development system, your executable is LabVIEW.exe (The LabVIEW Development System in whatever path it was installed, and yes there are different rules for each LabVIEW version since they are installed in different locations).

When you run in a build executable your executable is whatever the name is that you gave it and its installation location. You need to allow it specifically in the firewall rules too. The Windows Firewall knows nothing about that is was created in the the LabVIEW Development System and doesn't use its settings. If you then move the executable you will need to create a new rule (and delete the old).

Without a rule that allows (specifc) network access, the firewall will blackhole the executable. Basically any network traffic the application tries to do is directed into a big black hole where nothing ever comes out again, also often called /dev/null which is the unix name of a stream device that simply swallows any data it gets send to.

[hasse · Accepted solution]

Thank you for your tips about setting up the firewall rules for each app. However I found the real root cause now, it was in the Network configuration for the IP addresses.

I didn't have the IP address for the Iboot set high enough. When I changed the IP address to include the Iboot device it was working fine. It is strange how it was working when I was running this from the LabVIEW source code. But it is maybe as someone says the network is running differently in EXE configurations.

Anyway, thanks for your help and suggestions.