Directory Default IP Camera Addresses

By: Derek Ward, Published on Feb 13, 2015

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.

************ ** ******* *** be ******* *** ***********, made ***** ******* ************* have ** ***************, **** some ********** ****, **** using ******* ** *********, and **** ***** ****.

** **** ****, ** have ******** * **** ** 14 ** ****** ************* (including ****, *******, ********, Axis, *****, *****, *****, Geovision, *********, *********, *****, Samsung, ****, *** *******), what ** ********** **** support ** *******, *** the **** *** **** to ***** *******. ************, we **** ******** * directory ** ***** ** each ************'* ********* ****.

Default ** *********

**** ***** ***** *** most ****** ** ****** manufacturers ** **** ** their ******* *** ****, default ** *******, ** both.

[***************]

****:

  1. ******* ****** ******* ** not **** * ******* IP *******, *** ** they *** **** ************ ********* (***.*). *******, installers **** *** ***** AV200 ******** ** ******** and ******* *** ******.
  2. ******** *** ******* ** not **** ******* ** addresses, *** **** *** a ******** ******* ** ** DHCP ****** ** *******.

Default ** *******

** ***, *** **** common ****** ************* *** for ******* ** ******* is ** ******* **** first, *** ******* ** a ***** ******* ** no **** ****** ** present. **** ***** ************ ******, since installers *** **** ** multiple ******* ** **** ***** receive * **** *******, and **** *** ******* tools (*** *****) ** change ** ********* ** bulk. Without **** *******, ******* must ***** ** ******* in *** ** * time, ***** ********* ************ time.

*******, **** ********* * default ***** ** ******* provides * ******** ****** in ***** ***** ** DHCP ****** ** ******* or ***** **** ** configure * ****** ******. **** cameras ******* ********, ***** should ***** * **** to ******* ** ** from * ****** ******* need ** * **** server. *******, ***** ** a ***** ******* ********** the *** *** **** receiving **'* ** ******* (in *** *** *******), which *** ** ********* as ** *****. ** other *****, ** *** simply **** ** **** at ***. ******* ** this, * ***** ******* IP ******* ** ******** preferred.

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

*** ******* ******* ******* DHCP *** * ******* IP *******, **** ** Arecont. ** ***** *****, the **** ** ******** to *** * *********** discovery **** ***** ****** find ******* ********* ** the **** ******. *******, in ********, ** **** personally **** **** **** fail ** ******** ******* on *** ***, **** connected ******** ** *** computer ***** *** ********* tool. ******* ** ****, this ****** ** ****** used, ********* *** ***** more ******** *****.

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

** ****** ***** ******* IP ****** ** ****, users **** * *** to **** ******* *** assign **** * ********* IP *******. **** ********, proprietary ************ ********* ***** are ****. ***** ************ scan *** ***** ******* for ***** ******* (***** on*** ******* ***). **** **** ****, users *** ********* ****** IP *******, ****** **** tools ******* ***** *************, firmware **********, ** ****. 

***** ** **** ******** discovery/addressing ***** *** ****** manufacturers:

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

***** **** ************-******** *****, there *** *** ***** common **** ** ******** cameras ** *** ***** network:

  • *** *********:********* ******* ****** ********* tools** ***** ****** ** admin *****. *******, *** effectiveness ** ***** ******** varied ********* ** *** VMS *** *** ****** model, *** **** *** generally *** ** ********* as ************'* *** *****.
  • ** ********:*******, ** ******** ******* ****, installers *** *** **** ********* **** *** **** range ** ******** *** access *******. ***** ***** do *** ******* **-********** or ************* ** ************ tools **, *** ******* a ****** ***** ** find ** *********.

********

***** ******* *, ** development *********, **** ** standardize *** ** ******* are **********. ** ***** more, ***: *** ***** ******* * Aims ** ****** ********* and ******* *********.

 

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 :)

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.

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...

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

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

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

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.

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 :)

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.

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)

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:

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

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports

Camera Configuration Manager Shootout - Avigilon, Axis, Bosch, Dahua, Hanwha, Hikvision on May 01, 2019
Which camera manufacturer has the best management tool? We tested 6 manufacturers - Avigilon, Axis, Bosch, Dahua, Hanwha, Hikvision to find...
LifeSafety Power NetLink Vulnerabilities And Problematic Response on May 20, 2019
'Power supplies' are not devices that many think about when considering vulnerabilities but as more and more devices go 'online', the risks for...
Vivotek Trend Micro Cyber Security Camera App Tested on Jul 22, 2019
Vivotek and Trend Micro are claiming five million blocked attacks on IP cameras, with their jointly developed app for Vivotek cameras. This new...
Dahua Wiretapping Vulnerability on Aug 02, 2019
IPVM has validated, with testing, and from Dahua, that many Dahua cameras have a wiretapping vulnerability. Even if the camera's audio has been...
Dahua OEM Directory on Aug 16, 2019
US Government banned Dahua OEMs for dozens of companies. The following directory includes 40+ of those companies with a graphic and links to...
Uniview OEM Directory on Sep 11, 2019
This directory lists 20+ companies that OEM products from Uniview, with a graphic and links to company websites below. It does not cover all...
Critical Vulnerability Across 18+ Network Switch Vendors: Cisco, Netgear, More on Aug 26, 2019
Cisco, Netgear and more than a dozen other brands, including small Asian ones, have been found to share the same critical vulnerability, discovered...
Mobotix First CNPP CCTV Cybersecurity Certification Examined on Sep 05, 2019
Mobotix recently became the first video surveillance manufacturer to receive the CNPP cybsersecurity certification for its cameras, in which they...
ONVIF Exposure To "Devastating DDoS Attacks" Examined on Sep 06, 2019
ZDnet reported "Protocol used by 630,000 devices can be abused for devastating DDoS attacks", citing exposure of ONVIF devices. And after an...
Dahua New Critical Vulnerability 2019 on Sep 23, 2019
Dahua has quietly admitted 5 new vulnerabilities including 1 critical vulnerability with a 9.8 / 10.0 CVSS score and 2 high vulnerabilities (scored...

Most Recent Industry Reports

Axis and Genetec Drop IFSEC 2020 on Jan 23, 2020
Two of the best-known video surveillance manufacturers are dropping IFSEC International 2020, joining Milestone who dropped IFSEC in 2019. The...
Multipoint Door Lock Tutorial on Jan 23, 2020
Despite widespread use, locked doors are notoriously weak at stopping entry, and thousands can be misspent on locks that leave doors quite...
Avigilon Shifts Cloud Strategy - Merges Blue and ACC on Jan 23, 2020
Avigilon is shifting its cloud strategy, phasing out its Blue web-managed surveillance platform as a stand-alone brand and merging it with its ACC...
Verkada Paying $100 For Referrals Just To Demo on Jan 22, 2020
Some companies pay for referrals when the referral becomes a customer. Verkada is taking it to the next level - paying $100 referrals fees simply...
Camera Analytics Shootout 2020 - Avigilon, Axis, Bosch, Dahua, Hanwha, Hikvision, Uniview, Vivotek on Jan 22, 2020
Analytics are hot again, thanks to a slew of AI-powered cameras, but whose analytics really work? And how do these new smart cameras compare to top...
Intersec 2020 Final Show Report on Jan 21, 2020
IPVM spent all 3 days at the Intersec 2020 show interviewing various companies and finding key trends. We cover: Middle East Enterprise...
Vehicle & Long Range Access Reader Tutorial on Jan 21, 2020
One of the classic challenges for access control are parking lots and garages, where the user's credential is far from the reader. With modern...
Clearview AI Alarm - NY Times Report Says "Might End Privacy" on Jan 20, 2020
Over the weekend, the NY Times released a report titled "The Secretive Company That Might End Privacy as We Know It" about a company named...
Favorite Camera Manufacturers 2020 on Jan 20, 2020
The past 2 years of US bans and sanctions have shaken the video surveillance industry but what impact would this have on integrators' favorite...
"Severely Impacted" Mercury Security 2020 Leap Year Firmware Issue on Jan 17, 2020
One of the largest access controller manufacturers has a big problem: February 29th. Mercury Security, owned by HID, is alerting partners of the...