Skip to main content
Print

Fix: Building Access Control or Security Cameras Offline (Network Troubleshooting for Property Managers)

A tenant calls because their badge will not open the suite door. The lobby camera feed shows No Signal or Camera Offline. The access control portal (Brivo, Verkada, Avigilon Alta, Genetec, LenelS2, or a local panel) shows the controller as Offline or Last seen 3 hours ago, and the door has fallen back to its fail-safe or fail-secure state.

This guide is for property managers, building engineers, and on-site staff who hear about it first. Access control and cameras almost always ride on the building’s IT network, so most outages are network problems that follow a pattern: power, link, addressing, path to the cloud. Working through those in order resolves most cases without waiting for the security vendor.

Why This Happens

Power over Ethernet (PoE) budget or a failed switch port

Door controllers, readers, intercoms, and IP cameras draw PoE from a switch with a fixed budget in watts. Adding a heated outdoor camera or another controller can push the switch past its budget, and it drops power to the lowest-priority ports, often at night when heaters kick on. Individual ports fail too, and small unmanaged PoE switches behind a panel fail more often than anything else in the building.

IP address changes

Many installers leave devices on DHCP. When the firewall is replaced, a scope changes, or a lease expires while the device is offline, the camera or panel takes a new address and the NVR or access control server keeps polling the old one.

VLAN, firewall, or ISP path changes

Cloud-managed systems (Verkada, Brivo, Avigilon Alta, Meraki MV) need outbound HTTPS to reach their cloud. A firewall change, a new TLS inspection policy, or an ISP outage takes every cloud device offline at once while the local network still works. Devices landed on the wrong VLAN after a switch replacement show a link light but cannot reach their controller.

Time and firmware

Controllers with a drifted clock reject cloud certificates and drop offline, and devices years behind on firmware can lose compatibility after a vendor platform change.

How to Fix It

Method 1: Determine the scope

  1. Determine whether one device, one area, or everything is offline. One camera means a device or cable; one floor means a switch or VLAN; everything means the firewall, internet circuit, or vendor cloud.
  2. Check the vendor status page (Verkada, Brivo, Avigilon Alta, and Genetec all publish one). A cloud incident cannot be fixed on site.
  3. Confirm the internet circuit is up from a computer on the building network. On a Cisco Meraki firewall, uplink status is under Security & SD-WAN > Monitor > Appliance status.

Method 2: Check power and link

  1. Find the switch feeding the offline device and look at the port for a link light and PoE indicator. No light means a cable, port, or device failure.
  2. In the Meraki dashboard, open Switching > Monitor > Switches > select switch; the Ports view shows PoE draw per port and total budget used. If the total is near the budget, disable PoE on non-essential ports or move devices to a second switch. UniFi shows the same under Devices > select switch > Ports.
  3. Cycle the port from the dashboard (Cycle port in Meraki, Power Cycle in UniFi) and wait two minutes.
  4. If a local injector or small unmanaged PoE switch behind the panel powers the device, replug it and check for a dead power brick.

Method 3: Verify the IP address

  1. In Meraki, go to Network-wide > Monitor > Clients, search by name or the MAC address on the device label, and compare its IP and VLAN to what the NVR or access server expects.
  2. If the address changed, give the device a fixed address rather than editing the server: in Meraki, open the client and choose Assign a fixed IP (a DHCP reservation); in UniFi, open the client’s Settings and set Fixed IP Address. Reboot the device so it takes the reservation.
  3. Document every reservation: device, location, MAC, IP, switch, and port.

Method 4: Check VLAN and firewall rules

  1. Confirm the switch port is on the security VLAN. In Meraki, open the port and check VLAN (access) or Allowed VLANs (trunk). A replaced switch often ships with every port on VLAN 1.
  2. Allow the vendor’s published ports and domains under Security & SD-WAN > Configure > Firewall and exclude them from content filtering and TLS inspection.

Method 5: Time and firmware

Check the controller clock in its web interface or the vendor portal, set NTP to a reliable source with UDP 123 allowed outbound, and update firmware during a low-traffic window.

How to Verify the Fix Worked

  • The vendor portal or NVR shows the device Online with a current heartbeat and live video or door status.
  • A test badge opens the door and the event appears in the access log with the correct timestamp.
  • Recorded video resumes with no gaps after the fix time.
  • The device holds its reserved IP after a reboot.

If It Still Isn’t Working

Check the controller board. Power with no network LED on a known-good cable and port means a failed board. Doors on that panel stay in their fail mode until it is replaced; know whether yours fail secure (locked) or fail safe (unlocked) and post staff accordingly.

Check the cable run and the logs. Runs over 100 meters, runs through electrical rooms, and runs damaged during a tenant build-out are common; Meraki’s Cable test on the port identifies opens and shorts. Meraki’s Event log shows DHCP and port flap events, and vendor portals show exactly when heartbeats stopped, which you can compare to power events, firewall changes, or construction.

Escalate to the security integrator when power, link, IP, VLAN, firewall, and time are verified and the device still fails. Give them the switch, port, IP, and event timeline; it turns a half-day visit into an hour.

How Capital Techies Handles This for Managed Clients

Capital Techies manages building networks for property management firms across the DC metro area with Cisco Meraki switching and firewalls, a dedicated security VLAN with documented rules for each vendor cloud, DHCP reservations for every controller and camera, and PoE budgets sized with headroom. Monitoring alerts us when a camera or controller stops responding, a port flaps, or PoE nears its limit, so we often reach the integrator before the tenant calls. Our low-voltage team maintains port maps and labeled cabling for every managed property.

That keeps doors working, video continuous for incident review, and tenant confidence intact. If your building’s security systems ride on a network nobody owns, contact Capital Techies about managed IT for commercial properties.

Frequently Asked Questions

Should cameras and access control be on a separate network from tenants?

Yes. Put them on a dedicated VLAN with firewall rules that allow only the vendor cloud, the NVR, and management access. This keeps a compromised tenant device away from door controllers and keeps camera traffic off tenant bandwidth. Cyber insurers increasingly ask for this segmentation.

Why did every camera go offline at the same time?

A simultaneous outage points to a shared dependency: the internet circuit, the firewall, a content filter or TLS inspection change, the vendor cloud, or a switch that lost power. Check the vendor status page and firewall uplink first, then the switch.

How do I keep a camera from changing its IP address?

Create a DHCP reservation (Meraki calls it a fixed IP assignment) tied to the device’s MAC address, or set a static IP outside the DHCP range and record it. Reservations are preferred because the address is documented in the dashboard and survives device replacement.

Related Articles

Table of Contents