Directory Default IP Camera Addresses

By Derek Ward, Published Feb 13, 2015, 12:00am EST (Info+)

Initializing IP cameras can be tedious and frustrating, made worse because manufacturers have no standardization, with some supporting DHCP, some using default IP addresses, and some using both.

In this post, we have compiled a list of 14 IP camera manufacturers (including ACTi, Arecont, Avigilon, Axis, Bosch, Canon, Dahua, Geovision, Hikvision, Panasonic, Pelco, Samsung, Sony, and Vivotek), what IP addressing they support by default, and the pros and cons to these methods. Additionally, we have included a directory of links to each manufacturer's discovery tool.

Default IP Addresses

This table lists the most common IP camera manufacturers as well as their support for DHCP, default IP address, or both.

****:

  1. ******* ****** ******* ** *** **** a ******* ** *******, *** ** they *** **** ************ ********* (***.*). *******, ********** **** use ***** ***** ******** ** ******** and ******* *** ******.
  2. ******** *** ******* ** *** **** default ** *********, *** **** *** a ******** ******* ** ** **** ****** is *******.

Default ** *******

** ***, *** **** ****** ****** manufacturers *** *** ******* ** ******* is ** ******* **** *****, *** default ** * ***** ******* ** no **** ****** ** *******. **** ***** installation ******, ***** ********** *** **** ** multiple ******* ** **** ***** ******* * DHCP *******, *** **** *** ******* tools (*** *****) ** ****** ** addresses ** ****. ******* **** *******, ******* must ***** ** ******* ** *** at * ****, ***** ********* ************ time.

*******, **** ********* * ******* ***** IP ******* ******** * ******** ****** in ***** ***** ** **** ****** is ******* ** ***** **** ** configure * ****** ******. **** ******* ******* Zeroconf, ***** ****** ***** * **** to ******* ** ** **** * laptop ******* **** ** * **** server. *******, ***** ** * ***** between ********** *** *** *** **** receiving **'* ** ******* (** *** 169 *******), ***** *** ** ********* as ** *****. ** ***** *****, it *** ****** **** ** **** at ***. ******* ** ****, * fixed ******* ** ******* ** ******** preferred.

** ******* **/** ****

*** ******* ******* ******* **** *** a ******* ** *******, **** ** Arecont. ** ***** *****, *** **** is ******** ** *** * *********** discovery **** ***** ****** **** ******* connected ** *** **** ******. *******, in ********, ** **** ********** **** this **** **** ** ******** ******* on *** ***, **** ********* ******** to *** ******** ***** *** ********* tool. ******* ** ****, **** ****** is ****** ****, ********* *** ***** more ******** *****.

Camera *********/********** *****

** ****** ***** ******* ** ****** is ****, ***** **** * *** to **** ******* *** ****** **** a ********* ** *******. **** ********, proprietary ************ ********* ***** *** ****. These ************ **** *** ***** ******* for ***** ******* (***** ***** ******* ***). **** **** ****, ***** *** typically ****** ** *******, ****** **** tools ******* ***** *************, ******** **********, or ****. 

***** ** **** ******** *********/********** ***** for ****** *************:

***** *******

***** **** ************-******** *****, ***** *** two ***** ****** **** ** ******** cameras ** *** ***** *******:

  • *** *********:********* ******* ****** ********* ******* ***** ****** ** ***** *****. However, *** ************* ** ***** ******** varied ********* ** *** *** *** the ****** *****, *** **** *** generally *** ** ********* ** ************'* own *****.
  • ** ********:*******, ** ******** ******* ****, ********** *** use **** ********* **** *** **** ***** ** discover *** ****** *******. ***** ***** do *** ******* **-********** ** ************* as ************ ***** **, *** ******* a ****** ***** ** **** ** addresses.

********

***** ******* *, ** *********** *********, aims ** *********** *** ** ******* are **********. ** ***** ****, ***: *** ***** ******* * **** ** Change ********* *** ******* *********.

 

Comments (12)

Now THIS is very handy!

A couple points to add:

1. I've run into a few cameras that will try DHCP first, then "fail over" to a default IP if none is provided by DHCP. I think a Panasonic was one of those. Most seem to just be one or the other out-of-the-box, though.

2. An IP scanner is handy, BUT the computer you're running it on must already be configured on the same subnet as the camera(s). Not a problem with DHCP, but if cameras are using 192.168.1.xxx but your computer is configured with 192.168.0.xxx, it won't find anything on an IP scanner (not that you'd be able to connect to those cameras anyway). Of course, there's a bunch of other parenthetical stuff here, like, this assumes you're directly connected to the same LAN as the cameras and not going through any kind of NAT or routing, etc.

IP scanners are also handy for finding other things on the network, like managed switches :)

Agree: 4
Disagree
Informative
Unhelpful
Funny

Thanks for the info.

Where does the discovery methods that ONVIF Device Manager use fit into this scheme? It seems faster and better than most VMSes (for ONVIF devices), but I think it's pure IP, so Matt's caveats apply.

Agree
Disagree
Informative
Unhelpful
Funny

Samsung cameras can also be set up using the IP Installer tool, which does not require installation. Their VMS and NVRs can also discover their cameras and configure their IP addresses. NVRs can provide DHCP. Some NVRs will auto discover and configure cameras out of the box for easy small system setup.

IPInstaller utility

Cameras default to DHCP. If no DHCP is present then they will go to a static IP address of 192.168.1.100. (NVRs are typically 192.168.1.200).

The device manager is great for dealing with and assigning settings and IP addresses to many cameras at once...

Agree
Disagree
Informative
Unhelpful
Funny

Panasonic cameras actually default to 192.168.0.10 (The 192.168.0.253 is actually for some of their other "consumer" models, which look for DHCP first). You can use the EasyIP Setup utility to find cameras and change their IP addresses without installing any software.

EasyIP Setup Tool

Agree
Disagree
Informative
Unhelpful
Funny

Thanks for pointing both of these out. We've changed Panasonic and added the additional tools to the post.

Agree: 1
Disagree
Informative
Unhelpful
Funny

IndigoVision products default to 10.5.1.10. 2-channel devices (ie. encoders) default the second channel to 10.5.1.11.

Agree: 1
Disagree
Informative
Unhelpful
Funny

By the way, if a camera uses a default IP address that is outside of the range of your computer's current scheme, you can click on the "Advanced" tab of the TCP/IPv4 properties and enter additional IP addresses, subnet masks and gateways.

Agree
Disagree
Informative: 1
Unhelpful
Funny

Yep, a trick I use often. Would recommend NOT using multiple gateways, though (and Windows will warn against this if you try). The gateway (aka "default route") tells the system what address to route through for addresses outside its own subnet... if you put the machine on the same subnet as the cameras, you don't need a gateway for it.

Also, be careful you don't give your machine an IP that's already in use on the network!

This is where the IP Networking course comes in handy :)

Agree
Disagree
Informative
Unhelpful
Funny

Matt, Agreed in principle. However, I have set multiple gateways on dual-port cards without a problem. Indeed, Windows squawks about it but that was the way our old Honeywell system was set up: one port for encoders and the second port for clients. Each VLAN had its own gateway on the switch.

Agree
Disagree
Informative
Unhelpful
Funny

Yeah, but it's different with multiple NICs or multi-port cards, or if you're doing funky stuff like load balancing, VLANs, etc. where the separate gateways have a specific purpose.

Main point is, if you're adding IPs to find a camera on a different subnet, it's just not necessary, and especially for someone just learning this trick, there's no point in adding to the confusion, especially if it might break proper operation and leave the noob confused. Add the IP, set the netmask appropriately, and you're good to go.

Really, if all the communications on a network will be with addresses in the same subnet (eg. everything you're connecting has a 192.168.1.xxx address and you don't need internet), you don't need a gateway configured at all; it exists for sending traffic to outside subnets.

I know YOU know all this, of course... :o)

Agree
Disagree
Informative
Unhelpful
Funny

I worked with GeoVision & double check with our tech team and found the discovery tool information posted for GeoVision IP device is incorrect on this page. You will want to use IP utility tool instead of Central Monitoring Software instead.

By default, all GeoVision IP devices have the IP address of 192.168.0.10 with default ID: admin and password: admin.

If the ID and password have been changed, press on "Default" button on the camera to apply default settings on the IP camera to bring back default ID and password.

You can download the GV-IP Device Utility from website at http://www.geovision.com.tw/english/5_8.asp

Select IP Camera -> DVR/NVR -> GV-IP device Utility to download.

The interface would look something like this:

Agree
Disagree
Informative: 1
Unhelpful
Funny: 1

Thank you for the feedback Vickee Liang! The Geovision IP Utility is now linked.

Agree
Disagree
Informative
Unhelpful
Funny
Login to read this IPVM report.
Why do I need to log in?
IPVM conducts reporting, tutorials and software funded by subscriber's payments enabling us to offer the most independent, accurate and in-depth information.
Loading Related Reports