Skip to main content

PTZOptics Camera Not Receiving a DHCP Address

April 28, 2025​

This guide walks through a  set of troubleshooting steps—For a camera that does not receive an address using DHCP.

Check for a DHCP Server

Ensure the camera is connected to a network that includes a DHCP server. In most small setups—such as houses of worship, homes, or small offices—this is typically the router provided by your internet service provider.

**Use DHCP Reservations

**

  • It's highly recommended that the camera be assigned a DHCP reservation .

  • A consistent IP address makes it easier for control devices (e.g., joysticks or software controllers) to reliably connect.

Understand the Difference Between a Router and a SwitchThere is a significant difference between a Layer 2 switch and a router:

  • Layer 2 Switches do not provide DHCP addresses.

  • Routers do provide DHCP, but do not provide PoE (Power over Ethernet).

  • If your camera is receiving power from the device it’s connected to, that device is likely a switch , not a router. Make sure the switch is connected to a router or another device that functions as a DHCP server.

  • If you're unsure whether the device is a switch or router, look up its model number online to check its capabilities.

  • If the device was provided by your ISP it is likely a router .

**Consider the Type of Switch

**

  • Some older or basic switches (such as 10/100 "Fast Ethernet" switches) can sometimes cause issues with the DHCP handshake. While uncommon, using a 10/100/1000 (Gigabit) switch is recommended for better compatibility.

  • While rare, Hubs and bridges do still exist in the world, so make sure that you are using a network switch and not legacy hardware .

DHCP Request Timing

  • Sometimes, the camera's DHCP request doesn't reach the server—especially if the camera powers on before the router or DHCP server is ready. In this case:

    • Use the handheld remote to switch the camera to DHCP mode.

    • Press (#) + (*) + (4) on the remote. This will:

      • Set the camera to DHCP mode.

      • Reboot the camera

      • Force it to resend the DHCP request.

Static IP ConfigurationIf the camera is set to a static IP address , it will not request a DHCP address. To switch it back to DHCP:

  • Use the remote and press (#) + (*) + 4

    • This will change the mode to DHCP .

    • Reboot the camera

    • Attempt to obtain a new address via **DHCP
      **

Check for Cabling IssuesIf the camera isn’t reaching the DHCP server, inspect the network cables:

  • Ensure all cables are properly connected.

  • Try replacing the existing cable with a known good one.

  • If the camera works with a shorter or different cable, the original may be faulty.

    Advanced Networks :

    This section is for enterprise or more advanced networks.

**VLANs and Firewalls

**

If your camera is connected to a VLAN, there are several important considerations to ensure proper network communication:

  • **DHCP Server Access

    **

    • Ensure your DHCP server is configured to provide addresses on the VLAN the camera is connected to, and that it is assigning the camera to the desired subnet.

  • Verify that the traffic from the VLAN is routed to the DHCP server correctly in both directions.

  • Ensure that if there is a firewall or an ACL setup on a router between the VLAN the camera is on and the DHCP server to allow the DHCP traffic in both directions .

  • If the DHCP server is on a different subnet/ Vlan, a DHCP relay must be set up.

    • DHCP relay is configured on the Layer 3 interface that is directly connected to the subnet/Vlan containing the DHCP clients. This is typically the interface that serves as the default gateway for the Camera(s) .

**Port Access

**

  • Make sure that ports 67 and 68 (used for DHCP communication) are not blocked by your firewall or access control rules.

    • **Allow UDP 67–68 both ways.

      **

**DHCP Snooping

**

  • Confirm that DHCP snooping does not interfere with DHCP requests. Misconfigured DHCP snooping can prevent the camera from receiving an address.

    • If the port connecting to the DHCP server is not configured as trusted , the switch will drop all DHCP offers and acknowledgments from the server, preventing clients from receiving IP addresses.

    • If DHCP snooping is not enabled on the VLAN where the camera resides, or inconsistently enabled across switches in the path, DHCP packets may be dropped, blocking address assignment.

    • If the DHCP snooping binding table is full, corrupted, or not updated correctly, new DHCP requests may be denied because the switch cannot create new entries or validate the camera.

**VLAN Configuration
**

Setting up DHCP for a new VLAN involves configuring both the VLAN itself and ensuring DHCP requests from camera(s) in that VLAN are properly handled.

  • If the DHCP server is on the same device (Layer 3 switch/router)
    .

    • The DHCP server has a scope or pool configured for the new VLAN so that it can assign appropriate addresses.

    • If the switch the camera is connected to has multiple VLANs, configure trunk ports to carry VLAN traffic to the **Layer 3 switch/router.

      **

  • If the DHCP server is on a different (Layer 3 switch/router)

    • You need a DHCP relay agent configured on the router interface that is the default gateway for the camera’s VLAN . This relay agent listens for DHCP broadcast requests from the camera, then forwards them as unicast packets directly to the DHCP server’s IP address.

    • The layer 3 devices between the relay agent and the DHCP server must have proper routing so that the forwarded DHCP packets can reach the server, and the server’s replies can return to the relay agent and ultimately to the client.

    • The DHCP server has a scope or pool configured for the new VLAN so that it can assign appropriate addresses.

    • If the switch the camera is connected to has multiple VLANs, configure trunk ports to carry VLAN traffic to the **Layer 3 switch/router.

      **

The PTZOptics Upgrade Tools and mDNS

  • If you’re using the PTZOptics upgrade tool, be aware that this tool relies on mDNS to discover the camera.

    • mDNS (Multicast DNS) is designed primarily for local area networking —specifically, to resolve hostnames and discover services within a single local subnet or broadcast domain, without requiring a central DNS server. By default, mDNS uses multicast packets sent to the reserved address 224.0.0.251.

    • By design, standard mDNS does not work across routers or over wide-area networks (WAN); multicast packets are typically not forwarded beyond the local subnet .

    • Vendors like Cisco have developed solutions (e.g., Wide Area Bonjour) that enable mDNS-like service discovery across larger, routed enterprise networks by translating multicast mDNS into unicast queries and distributing them according to defined policies.

  • It is suggested that the computer running the PTZOptics Upgrade tool is on the same VLAN or subnet as the camera.

  • The Upgrade Tool may not work reliably on macOS due to mac often having issues with **Multicast traffic.

    **

Please contact support if you are having any issues and if there is anything we can help with

  • Support can be reached M-TH 8AM-6PM EST, and 8AM - 4PM FRI EST.

  • Call 484-593-2584

  • Email support@ptzoptics.com