Understanding why Banalytics VMS may stop working: corporate prohibitions and security concerns

In today's corporate environments, stringent security measures are essential for protecting sensitive data and ensuring that all software running on company devices aligns with organisational policies. However, these same security measures can sometimes interfere with the operation of legitimate applications, leading to issues like the inability to run the Banalytics Video Management Software (VMS). In this article, we'll explore some common reasons why corporate prohibitions may prevent Banalytics VMS from running and the underlying security concerns that drive these restrictions.

Why Banalytics VMS may stop working

One of the main reasons Banalytics VMS might fail to run is due to the configuration of the corporate PC on which it is installed. Corporate IT departments typically enforce strict security policies to control what software can run on company devices. These policies can include:

Anti-virus and anti-malware software

Modern anti-virus programs are highly vigilant about identifying and blocking software that might pose a risk, including applications that require extensive access to system resources. Banalytics VMS, like other video management software, may require (depending on surveillance needs) significant processing power and access to video data streams, which anti-virus programs can sometimes flag as suspicious activity. If an anti-virus program blocks Banalytics, the service may fail to run until the software is whitelisted or the IT department adjusts the settings.

Prohibitions on running specific services

Corporate environments often impose direct prohibitions on certain types of software. These prohibitions can be based on the software's perceived security risks, potential to disrupt other services, or the need to comply with industry regulations. In the case of Banalytics VMS, the software relies on certain services to function properly, such as a Java Virtual Machine (JVM). If a corporate policy prohibits running a JVM—perhaps due to concerns over security vulnerabilities or the need to limit the installation of third-party frameworks—this would directly prevent Banalytics from functioning.

System configuration restrictions

Sometimes, the issue isn't a direct prohibition but a broader restriction on how the PC's system resources can be used. Corporate IT departments often lock down system configurations to prevent unauthorised changes, including disabling or restricting certain services that Banalytics VMS relies on. For instance, the software might require specific network configurations, access to particular ports, or permissions not granted in a tightly controlled corporate environment. 

Corporate compliance and legal regulations

In some industries, compliance with legal regulations is a critical concern. Video management software like Banalytics VMS might be subject to specific compliance requirements, as the software handles sensitive data like video surveillance footage. IT might prohibit its use altogether to avoid potential legal ramifications if the software's operation or its underlying components are deemed non-compliant with corporate or legal standards.

How can I understand that software malfunction relates to corporate restrictions?

Banalytics uses WebRTC (Web Real-Time Communication) technology for data transmission. Therefore, the blocked access to the following ports may cause problems. You may be unable to access the login page https://console.banalytics.live/ or set up a connection with the server.

Dynamic UDP Ports (49152–65535): WebRTC primarily uses UDP to transmit real-time data. The exact port numbers used can vary as they are dynamically assigned. However, they generally fall within the dynamic range of 49152–65535. 

STUN/TURN/ICE Servers: WebRTC uses STUN (Session Traversal Utilities for NAT) and TURN (Traversal Using Relays around NAT) servers to handle NAT traversal. Banalytics uses pre-configured STUN and TURN servers on port 3478. 

TCP Port 443 (HTTPS): While UDP is preferred for real-time media due to its lower latency, WebRTC can also fall back to using TCP, particularly over port 443 (the standard port for HTTPS), when UDP connections are blocked or unreliable. 

You will experience the same issues if some antivirus or company restrictions block the Banalytics process.  This can be quickly investigated by opening the “Services” tab in Task Manager (Ctrl+Alt+Del). Opt to restart the process to ensure nothing prevents it from running. 

You may have successfully installed Banalytics software on a corporate PC, but it suddenly stopped working when you tried to restart the server. IT departments routinely apply security patches and updates to protect systems from vulnerabilities. If the service ran fine before but failed to restart after an update, a recent patch may have altered the environment to prevent the software from functioning as expected.

What can be done?

If you're facing an issue where Banalytics VMS fails to restart, here are a few steps you can take. Remember, the below steps make sense if you use Banalytics in your company surveillance setup:

• Consult IT support. The first step should always be to contact your IT department. They can check whether corporate policies, anti-virus programs, or security configurations block the software. 

• Request whitelisting or exception. If the issue concerns an anti-virus program or a specific service prohibition, you can request that the software be whitelisted or an exception be made. 

You most probably won't have such problems with a personal PC running Banalytics software. If so, check your network ports and anti-virus logs.