Verify Your Mobotix Camera's Network Configuration
Mobotix app disconnection often stems from network misconfigurations or firmware incompatibilities. Begin by confirming the camera is correctly assigned to a VLAN, its PoE power budget is sufficient, and the VMS is properly integrated. Addressing these root causes ensures reliable communication between the camera and the management platform.
Quick Fixes to Try First
Perform these 30-second checks before diving into advanced diagnostics:
- Check VMS dashboard status: Open MxManagementCenter and verify the camera is listed as online. If offline, check for recent firmware updates or configuration changes.
- Verify PoE link light: For Mobotix M73, c71, or MOVE SD-340-IR, inspect the PoE link light on the switch port. A steady light indicates proper power delivery; a blinking or absent light suggests power negotiation issues.
- Ping the camera IP: Use the command prompt or terminal to ping the camera’s IP address. If unreachable, check switch port configuration or network segmentation.
- Power cycle the camera: Disable the switch port, wait 30 seconds, then re-enable it. This resolves temporary power or network glitches.
Diagnose VLAN Misconfigurations
Check VLAN Assignment
Ensure the camera’s VLAN matches the switch port configuration. In MxManagementCenter, navigate to Network → Camera Settings and cross-reference the assigned VLAN with the switch port’s VLAN tag. Mismatched VLANs prevent the camera from communicating with the management platform.
Validate VLAN Tag Propagation
Use MxThinClient diagnostics to confirm VLAN tags are correctly propagated. If the camera is on a different subnet than the management server, enable QoS policies in the switch to prioritize Mobotix traffic. For UK networks with double NAT (e.g. Virgin Media Hub 5x), assign a static IP to the camera outside the ISP’s default range (e.g. 192.168.2.x instead of 192.168.1.x).
Resolve Firmware Update Failures
Confirm Firmware Channel Settings
Access MxManagementCenter → Firmware → Channels and ensure the camera is set to the correct firmware channel (stable or beta). If updates are pending, initiate a staged rollout via the management platform to avoid disrupting live feeds.
Address Firmware Rollback
For Mobotix MOVE SD-340-IR PTZ, ensure PoE++ compatibility with the switch. If firmware updates fail, use the event log in MxThinClient to identify errors. Roll back to a previous version and reattempt the update after resolving network or VMS conflicts.
Troubleshoot RTSP Stream Failures
Test RTSP Stream Directly
For Mobotix c71, test the RTSP stream using a media player with the URL rtsp://<camera_ip>:554/stream1. If the stream fails, reconfigure the camera’s RTSP port in MxManagementCenter and restart the camera. Verify the VMS is using the correct ONVIF profile (Profile S or Profile G) for compatibility.
Adjust RTSP Port Settings
If the stream fails intermittently, check for MTU mismatches. Adjust the camera’s MTU settings in MxManagementCenter to match the network’s standard (typically 1500). For UK networks with double NAT, configure the VMS to use a static IP outside the ISP’s default range.
Advanced Network Diagnostics
Capture Packets with MxThinClient
Use MxThinClient diagnostics to capture packets on the camera’s network interface. Analyze for TCP retransmissions, IP fragmentation, or MTU mismatches. For UK networks with double NAT (e.g. Virgin Media Hub 5x), configure the VMS to use a static IP outside the ISP’s default range.
Repair VMS Database Consistency
If the camera appears offline in the VMS dashboard but responds to ping, perform a database consistency check in MxManagementCenter. Re-register the camera if necessary and ensure the VMS license is valid. For large deployments, use SNMP monitoring to track camera health and network performance.
Factory Reset and Escalation
Perform Model-Specific Factory Reset
For MOBOTIX M73, remove the housing cover to access the reset button on the main board. Press and hold for 10 seconds while the camera is powered. For MOBOTIX c71, use the supplied tool to remove the dome cover and access the reset button. For MOVE SD-340-IR, access the reset button through the maintenance port and hold for 15 seconds.
Escalate to Enterprise Support
If basic fixes fail, escalate to Mobotix enterprise support via https://www.mobotix.com/en/support. Provide the MxThinClient diagnostics report, VMS event logs, and firmware channel settings for expedited resolution.
Root Causes of Mobotix App Disconnection
Enterprise-level issues often stem from PoE budget exhaustion, DHCP scope exhaustion, or VMS licensing conflicts. For UK deployments, ensure compliance with GDPR retention policies and Building Regulations Part Q for surveillance systems. Firmware incompatibilities after staged rollouts can also disrupt connectivity.
Prevention and Long-Term Care
Schedule Regular Firmware Updates
Use MxManagementCenter to schedule firmware updates during off-peak hours. Monitor VMS health metrics via SNMP and ensure dedicated camera VLANs are configured with QoS policies. For large deployments, allocate 10-15% PoE headroom on switches to accommodate future expansion.
Full disclosure: we built scOS to address exactly this
the complexity of managing enterprise camera fleets across VLANs. scOS uses permanently powered cameras connected via ethernet.
Replacement Decisions for Enterprise Deployments
For wired cameras (e.g. M73, c71), plan for a 5-8 year lifecycle. Replace surveillance-rated HDDs in NVRs every 3-5 years and use high-endurance microSD cards for edge storage. Under the Consumer Rights Act 2015, UK consumers have up to 6 years to claim faulty goods. If troubleshooting exceeds 30 minutes without success, hardware failure is likely.