Cepera wrote:
> I built a simple LabVIEW executable (e.g. doing a+b=c, or even just
> empty), using all default options in the Application Builder (VI
> Server disabled - both TCP/IP and ActiveX; Web Server disabled).
> Target platform - Windows 2000. LabVIEW version 7.1 (the same behavior
> on 7.0, but not on 6.1).
>
> When I launch my executable, the firewall (ZoneAlarm Pro) reports the
> application trying to access the internet (in my case,
> 63.240.76.19:DNS - probably the DNS server of my ISP). I tell the
> firewall to deny service; after that the application launches and
> works fine.
I just tried to watch the network traffic with Ethereal while starting
up LabVIEW 7.0 PDS and I can not detect any LabVIEW related
communication whatsoever. DNS lookups are
not filtered by Ethereal, but
if that is the only thing happening, there are no risicos with it.
It could be that LabVIEW initializes the Winsock library on startup and
causes a reverse DNS for its own IP address and depending on your
network setup this could result in a remote DNS request. Maybe something
to detect multi network PCs or whatsoever, or the library for Infrared
tries to do something on initialization of the Winsock. But unless
someone can tell me what address it tries to resolve and show that it
then tries to actually communicate with a higher level protocol with
anything else, I do not consider it an attempt to call home, at least on
my computer. However it would be nice if someone from NI could shed some
light on the reasons for this just to make sure.
Rolf Kalbermatter