Month: January 2022

Categories
Software Categories exacqVision Client MacOS Knowledge Support Support exacqVision Client Categories Products

Mac Clients having issues connecting to LDAP

Encountered on : Ventura 13.5 and above

We need to make sure that the client machine is Joined to the Domain via the GUI method using the instruction in the following link from Apple.

https://support.apple.com/guide/directory-utility/configure-domain-access-diru11f4f748/mac

Encountered on : BIG SUR 11.4
Behavior: MAC Clients are not able to connect to the Domain Using LDAP only.

We need to make sure that the client machine has the krb5.conf file locally along with the krb5.key.

Below is an example of the server default file of the krb5.conf file.
Please note that this is an example and that your information would need to be entered in for the default realm instead of EXACQ.COM.
This file can be placed in the /etc/krb5.conf.
NOTE:
This file would need to be on both linux and Mac units.

Below are a few links to assist with configuration of the krb5.conf file for Mac OS.

http://web.mit.edu/macdev/KfM/Common/Documentation/preferences-osx.html

http://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html

https://stackoverflow.com/questions/52409808/macos-sierra-kerberos

Categories
Knowledge Support Support exacqVision Enterprise exacqVision Client exacqVision Server Categories Products

Remote exacqVision Client Connections Constantly Disconnecting / Reconnecting

Customers using Cisco Meraki switches have reported that while the client on the NVR is stable, client connections from remote machines are constantly disconnecting/reconnecting.    We have found that for some reason the Cisco Meraki is identifying traffic between the NVR and the remote exacqVision Client software over port 22609 as Peer-to-Peer (P2P) traffic.

If a Peer-to-Peer (P2P)  firewall rule is enabled to deny P2P in the Meraki, exacqVision Client traffic will be blocked/terminated. 

It is our understanding that the Cisco Meraki establishes a flow, then the Deep Packet Inspection (DPI) is performed and once the traffic is identified as P2P the flow is killed.  Which explains why the client software will connect and then shortly afterward disconnect.  Once ExacqVision detects the connection has been dropped it will reconnect and the process repeats.

Please check your Firewall rules blocking P2P traffic.  If they are enabled the only solution known at this time is to disable the rule.   

Here is a screenshot showing a typical configuration and the firewall rule from a Cisco Meraki.

Network Configuration Example
Meraki P2P Firewall Rule Example

Categories
Knowledge Support Support exacqVision Server Categories Products Uncategorized

No motion detection on the bottom when changing to the corridor mode for the HikVision cameras

When changing the windows for the HikVision cameras to the corridor mode, it will not trigger the motion on the bottom because it’s not supported by Exacq yet.

This feature will be supported on the ExacqVision Server version 22.03.

Categories
Knowledge Support Support exacqVision Enterprise Categories

Solr Apache API on port 8983

There is currently a fix for customers who are able to access the Solr Apache API admin page from a workstation. Download EM version 21.12.2 and install it.

If you are still able to access the Solr Apache API admin page on a workstation that is not the local NVR hitting port 8983, it is because they have turned off the Windows Firewall.

They will need to block access to port 8983 in whatever firewall software they are using.

Categories
Knowledge Support Support exacqVision Client exacqVision Server Categories Products Uncategorized

Setting a primary group to an LDAP user

Issue

If you have an LDAP group listed on the ExacqVision server, and you set this group as a primary group for a specific user. The Active Directory will not authorize this user to log in on ExacqVision software.

Solution

Remove this group from being the primary group of the user, or add this user to the ExacqVision server users directly.

<br>

Categories
Knowledge Support exacqVision EDGE Support exacqVision Server Categories Products

Vivotek Edge not recording locally or displaying volume in the Exacq Client

Seen on Server 21.12
If you have a customer having issues with not being able to record locally to the camera’s SD and not seeing the drive status in our client make sure to check the following in the cameras gui.

Check the Configuration menu under Applications and Package Management to see if the “Save to SD Card” option has a check mark. Make sure this is checked. After checking the Save to SD Card you might need to reinstall the ExacqVision Edge Server software.

Categories
Knowledge Support Support exacqVision Webservice Products

Thin Client Maps do not produce an image when cycling through the different maps

Starting at 21.06 version of Web Service we found that using maps that have children with links to cameras from more than one server can trigger this behavior.

Example:
If cycling through your list of maps the screens would not load and produce a black image. Sometimes the screens would load but would only show a few cameras.

Workaround is optional:
A possible workaround for the customer could be to decouple their maps based on server, so only have cameras / devices from one server per map, and possibly even make sure they are top level maps with no children.

To Correct this we can use the following builds. We will need to transfer these for the time to the customer server and then run the installer.

https://artifactory.exacq.org/artifactory/webservice-local/21.09.x/31982xx/3198203/

exacqVisionWebService_21.09.3198203.0_x64.deb
exacqVisionWebService_21.09.3198203.0_x64.exe
exacqVisionWebService_21.09.3198203.0_x86.deb
exacqVisionWebService_21.09.3198203.0_x86.exe

NOTE*
These versions have not been merged yet so it’s not in Release as of yet.
This fix scheduled for the March 2022 release.

Categories
Knowledge Support Support exacqVision Server Categories Products

Limitations of M-Series Servers

Overview:

Known limitations of exacqVision M-Series servers.

Issue:

  1. Cloud Drive is not supported.
  2. Starting in version 21.12, EdgeStor for Illustra Cameras connected to an M-Series server will no longer be supported. If the customer still wants to upgrade, please refer to:
    • KB #1580 “How to update the M-Series recorder”
    • KB #6655 “M-Series – Updating Exacq Software”

Solution:

There are NO available workarounds for these limitations.

Categories
Knowledge Support Support exacqVision Server Products

Axis D2110-VE Radar Motion does not work

​

Please provide these builds to customers for this issue and make sure the customer knows that motion is available as an analytic now, and needs configuration from the webpage. We will tweak the record as well once we close the ticket and in the next official release.

Once this is version is out we can remove this KB.

https://crm.exacq.com/release/Vision%20Server/21.12.x/21.12.x/exacqVisionServer_21.12.2780501.0_x64.deb​https://crm.exacq.com/release/Vision%20Server/21.12.x/21.12.x/exacqVisionServer_21.12.2780501.0_x64.exe​https://crm.exacq.com/release/Vision%20Server/21.12.x/21.12.x/exacqVisionServer_21.12.2780501.0_x86.deb​https://crm.exacq.com/release/Vision%20Server/21.12.x/21.12.x/exacqVisionServer_21.12.2780501.0_x86.exe

Categories
Knowledge Support Support exacqVision Server Categories Products

Unexpected Throttling, Low Memory and Server Reboot

Description

In exacqVision Server versions 21.09 and 21.12 if audio outputs or push to talk are used it can cause a slow memory leak every minute. This will eventually cause the server to throttle and eventually hang or reboot.

Product

  • exacqVision Server 21.09
  • exacqVision Server 21.12

Solution

Upgrade exacqVision Server to RC 21.12.3 or higher, which contains enhancements which should resolve the issue. 


12/08/2021
v21.12.1

  • Enhancement – psfpi – Throttle audio as well as video when the system is throttling.

01/14/2022
v21.12.3

  • Bug Fix – psfpi – Changed to time based cache rather than packets to address an issue related to push to talk

<br>