As far as i know, security business and ip cameras are not meant to be installed by your average end user with no knowledge about cameras, ip addresses or networks.
I work with static IPs rather than cameras with DHCP enabled. Most of the times when you take a camera out of the package, you're already installing it on a customer, on a isolated network with no dhcp servers around.
If an end-user that doesn't know anything about IP cameras plugs one in, DHCP and config/search tool is the easy way to go, but without search tool the end-user has no clue which ip did the router/modem DHCP assign to the camera, thus making it very hard to access it.
Some manufacturers (i've come up with one) do it correctly by having static IP and DHCP enabled at the same time as factory default setting. If the camera does not get IP from DHCP, static ip works, if it does, DHCP one works.
I work with static IPs rather than cameras with DHCP enabled. Most of the times when you take a camera out of the package, you're already installing it on a customer, on a isolated network with no dhcp servers around.
If an end-user that doesn't know anything about IP cameras plugs one in, DHCP and config/search tool is the easy way to go, but without search tool the end-user has no clue which ip did the router/modem DHCP assign to the camera, thus making it very hard to access it.
Some manufacturers (i've come up with one) do it correctly by having static IP and DHCP enabled at the same time as factory default setting. If the camera does not get IP from DHCP, static ip works, if it does, DHCP one works.