Quick answer: Identify the actual device, account and lockout message, then use the recovery process approved for that model and firmware. A configured self-service option may help; otherwise contact Anabon through the responsible installer or business account for the authorized support route. Protect existing recordings and configuration before any reset. Plan named accounts, secure credential storage and recovery ownership at handover.
On this page
Which lockout do you actually have?
Different account, channel-credential and device-recovery problems can look alike. Note the exact message and model/firmware before attempting another login. Stop automated retries where they continue a lockout, and confirm the approved recovery process; a reset may require recommissioning and affect recording or access.
| Situation | First approved route | Check before changing |
|---|---|---|
| Operator account lost; authorized admin available | Supported user/account management | Rights, lockout, dependent sessions and audit record |
| Admin lost; configured recovery option | Exact model/firmware self-service process | Requester authority, scope and dependent credentials |
| No available recovery option | Responsible installer/business account and Anabon support | Required verification, official process and potential configuration/recording impact |
| Channel authentication failure | Confirm device/channel account mapping | Actual camera credential, account method, rights and lockout; avoid unnecessary reset |
| Repeated failed login | Stop guesses/automated retries and record message/time | Actual lockout policy and supported escalation; no universal timer |
A recorder can hold separate credentials for a channel, depending on its integration and firmware. If that account changed, check the actual error and stored channel settings, lockout and permissions before choosing recovery. A reset can create more mismatches. ONVIF camera not connecting to the NVR covers the integration checks.
What is the official reset path for a CASE camera or NVR?
Recovery options, required authorization and reset effects vary by exact model/revision and firmware. Obtain the approved instructions from Anabon technical support and the responsible installer/business account. This guide does not publish a universal code, bypass or hardware reset sequence. Confirm what will be retained, what must be restored and how required recording will be protected before proceeding.
Step 0: identify the device exactly
Record the complete SKU, serial and firmware where accessible, and confirm actual device identity rather than relying on a channel name. For example, CS-N220 P16H-AI identifies a specific recorder family, not every 16-port recorder. Use only the supported discovery tool and authorized network path; whether it can report a locked device’s details depends on the device and configuration.
Path A: self-service recovery, if it was configured
Use a self-service option only if the exact firmware supports it and the required recovery enrollment/authority is available. Do not assume every system offers security questions or a recovery contact, or that an unconfigured method can be added while locked out. At commissioning, record the supported method and responsible contact without exposing recovery secrets. Check the IP camera user manual and confirm the exact revision’s supported recovery process.
Path B: support-assisted reset
Contact the installer, dealer or approved business account responsible for the system and ask Anabon technical support for the current authorized route and verification requirements. Do not promise that every locked unit can be reset remotely or by the same method. End users should contact the company that supplied or services their system.
Path C: factory reset, the last resort
A supported reset may clear some settings, accounts, integrations or other data; scope and access requirements depend on the exact device/firmware. Do not assume it always clears the password or always preserves/deletes recordings. Confirm the approved procedure and recovery plan first, preserve required configuration/footage where authorized and possible, and plan the resulting downtime and recommissioning.
What will technical support ask you for?
Recovery can change control of a system containing private footage. The responsible support team must establish authority using its current process. Provide only the information it requests through an approved private channel; a serial number or possession of a recorder alone is not proof of entitlement. See the security camera partner program for Anabon’s business-account channel.
- Your company/business-account reference, role and authorized site contact.
- The exact full SKU, serial and firmware if available, sent only through the support route that needs them.
- The exact error, time and redacted device/account context; a requested label/login photo must exclude passwords, secret QR codes, recovery answers and unrelated footage.
- The permitted connection method and relevant topology, including actual recorder/camera interface mapping.
- Required recording continuity, available authorized backups and who can approve any interruption or reset.
Retain an appropriate record of requester, authority, approver, changes and validation, following the site’s privacy/retention policy and applicable law. Limit unnecessary personal or site data in tickets. Obtain qualified advice for jurisdiction-specific obligations rather than assuming one privacy rule applies to every project.
How do you prevent the next lockout at handover?
Reduce dependence on one person or phone by agreeing credential custody, named accounts and a supported recovery owner at commissioning. Allow realistic time to test the handover; no fixed ten-minute task prevents every future lockout.
- Credential custody: store passwords and recovery secrets in an approved protected vault with controlled access and a usable recovery process. Keep the device/account inventory separate from shared tickets and drawings.
- Authority: agree designated administrators, customer responsibilities and any installer service access under the actual contract and policy; revoke access when no longer authorized.
- Least privilege: use supported named user and dedicated integration/service accounts with only the required permissions; document any device limits or unavoidable shared account control.
- Recovery: configure and test the supported enrollment and contact process without disclosing its secrets in the general handover pack.
- Changes: revoke departing people’s accounts/access and rotate affected shared or exposed secrets as needed. Never reuse credentials across customers; verify dependent integrations after a change.
After recovery, verify the current accounts, approved credentials/recovery custody, channel integrations and required recording/playback. Revoke temporary access and log the authorized work. User roles and permissions on CASE NVRs, Hardening a CASE NVR and the customer handover cybersecurity checklist cover the wider checks. CASE Connect, CASE Station and CASE Cloud have separate roles and supported versions; test the actual account and access workflow rather than assuming feature parity or blanket ONVIF support.
Password policy template for customers
Use the table as a discussion checklist, then adapt it to the exact device capabilities, customer policy and support process. It is not a claim that each camera implements a particular authentication standard or supports every account/recovery control.
| Policy item | Agree and verify |
|---|---|
| Password length | Use a unique long secret within supported limits. Current NIST SP800-63B-4 sets a15-character minimum for single-factor passwords in its scope; that is guidance to assess, not proof that a CASE device implements it. Document constraints and approved mitigations. |
| Storage and custody | Approved protected vault, designated authorized custodians and recovery access |
| Admin and daily operation | Separate least-privilege named accounts where supported; no routine admin sharing |
| Integration/service accounts | Dedicated required permissions; current dependencies and authorized lifetime documented |
| Recovery | Exact supported enrollment/process and responsible contacts; secrets kept protected |
| Revocation and rotation | Remove departing/stale access; change affected shared or compromised secrets and test dependencies. NIST does not call for routine calendar changes alone. |
| Lockout protection | Keep approved protections in place; record actual device behavior and support route |
| Review | Review at agreed handover/service/change points and correct the actual inventory |
What to tell your customer
We will agree who is authorized to administer the system, where credentials and recovery information are protected, and what service access we may retain. If recovery is needed, we will verify authority and follow the device’s approved process, then test the required recordings and access again. End users should contact their supplying or servicing company.
FAQ
Can I reset a CASE camera password without calling support?
Use an authorized self-service method only where the exact device/firmware supports it and its prerequisites are met. Otherwise ask the responsible installer/business account and Anabon support for the approved route. A hardware/factory reset is not a universal password-recovery shortcut and may affect configuration, access or footage.
Does Anabon reset passwords for end users who call directly?
Anabon’s warranty and technical service operate through its installer, dealer and business-account channel. Contact the company that supplied or services the system so authority and the current support requirements can be verified. Do not send passwords or recovery secrets in an initial request.
Will a factory reset delete the recordings on an NVR?
Confirm the exact device/firmware reset scope with the approved instructions before proceeding. Preservation of files, encryption/access keys, indexing and usable playback are separate questions. Preserve required footage/configuration where authorized and possible, verify the copy and agree a recovery plan; do not assume that a drive still containing data means the recording remains accessible. Use the NVR evidence export guide when the required footage is still readable.
The camera says wrong password after I changed it, but it is on an NVR PoE port. Why?
A confirmed stored-channel credential mismatch is one possibility, alongside account lockout, permissions or integration settings. Check the actual account and error, then update the approved mapping. Removing/re-adding a channel or resetting a camera can affect recording and settings; do it only as a supported, authorized change with final verification.
The device locked after several failed attempts. What now?
Stop guesses and identify any approved client or integration still retrying. Record the actual message/time and follow that model/firmware’s lockout and recovery instructions. There is no universal duration or guarantee that waiting makes every account usable. Escalate through the authorized recovery path if needed, preserving existing recording and access.
References
- Anabon: model and revision documents
- Anabon Technical Support
- NIST SP800-63B-4: current authentication and password guidance
