Firewall Increases LabVIEW Launch Time

Updated Jul 25, 2023

Reported In


  • LabVIEW

Issue Details

Several NI applications can act as a server or use TCP/IP to communicate with another NI application. This can cause personal firewalls, such as Norton firewall and ZoneLabs ZoneAlarm, to question whether these applications should be allowed access to the Internet or if they can act as a server. Which LabVIEW components can cause conflicts with personal firewalls?


The following items can trigger an alert in a personal firewall:
  • LabVIEW VI Server and Web Server - These are the most common ways in which LabVIEW acts as a server. Select Tools»Options to configure these servers.
  • NI Example Finder - Acts as a server so NI applications can communicate with it. The NI Example Finder accepts only local connections. It accesses the Internet to search and download examples from the NI Web site and communicates with other local applications such as the Service Locator and HelpServer by way of TCP/IP. This server listens on a dynamic port.
  • HelpServer - A server and a client used by the LabVIEW Help and the NI Example Finder. This server accepts only local connections and connects to only local applications. This server listens on a dynamic port.
  • Service Locator - A server used by different NI products, such as the LabVIEW Help, the NI Example Finder, and LabVIEW. This server accepts both local and remote connections. On Windows, this server runs as an operating system service but on all other operating systems, it runs as a VI inside LabVIEW. This server listens on port 3580.
If you experience a slow launch time and slow VI execution with LabVIEW (labview.exe), the NI Example Finder (NIExampleFinder.exe), or the Service Locator (nisvcloc.exe) and you have a personal firewall running, consider the following options:
  • Configure the firewalls so LabVIEW, the NI Example Finder, and the Service Locator (Windows only) have server and client permission. You can set these permissions using the firewall application.
  • Add localhost and your IP address to the list of trusted network addresses in your personal firewall.
  • Make sure you have the newest version of your personal firewall installed.