Call: 614 356 3319 

Managing a network IP camera system


Remotely accessing video recorders and cameras on the internet (WAN) is an important feature to most clients and it should be considered when installing and implementing a video surveillance system.  Discussed on this page are three critical aspects of networking a video recorder or camera system:

Page 1 - Port forwarding video recorder(s) and camera(s)
Page 2 - Multiple Router Port Forwarding
Page 3 - Managing an network IP camera system
Page 4 - Bandwidth and throughput limitations

                                                                                                                                                                      Download the Networking guide in .PDF form here.


Besides port forwarding, managing a network IP camera system requires changing device IP addresses to prevent conflicts, plotting out power over Ethernet (PoE) switches and cable distances.  This next section will give some basic information on how to organize and maintain an network camera setup.

DH Vision recommends using a Windows PC so that the installer can use the ConfigTool to configure a new network IP camera system.  If a Mac is used, a custom network must be created and each camera must be attached and configured one at a time.

Configuring using the ConfigTool (Windows)


Download the ConfigTool here.  Uncompress the file and run the ConfigTool.exe application file.  Allow the ConfigTool through any firewall alerts.

In the lower left hand corner of the software, in the IP Version dropdown, select IPv4. 

Click the Refresh button.  The ConfigTool should now list all attached devices IP addresses. 

With the latest firmware, the network IP cameras will be set to DHCP.  If all the devices listed on the ConfigTool have different IP addresses, then the installer can move on to adding the cameras into the network video recorder(s) or VMS software. 

If the cameras are all set to the default static, then they must be changed to different IP addresses that match the current network segment  Using the ConfigTool, double click a device listed in the program and log in.  If the device is on a different segment than, then the program will request an IP address and default gateway change, otherwise it will log in.  In either case, change the IP address to an available one on the LAN and also make sure that the gateway and subnet mask is correct (matches the LAN settings).

Repeat step 5 on all cameras, ensuring each one has a different IP address.  DH Vision suggests ordering the IP address to keep things organized.  For example,,, and so on.

Configuring using a Mac computer


First check to see if the cameras are set to DHCP by default.  To do so, connect all cameras to the network and log in to the router using the default gateway.  Most routers have a connected devices menu that will show all devices connected to the router and what IP addresses are being assigned.  Check if the cameras are listed in the connected devices and try to log in to a few of the IP addresses using Safari.  If the cameras are confirmed as set to DHCP, then no further camera configuration is needed.

If the cameras are not on DHCP, then a new network location must be created.  Choose Apple menu > System Preferences, and then click Network.  Choose Edit Locations from the Location pop-up menu, and then click Add (+).  Enter settings for that match the network segment the cameras are on by default which is gateway, subnet and the local IP of the Mac computer can be set to

After setting up the new network location, connect one camera to the Mac.  Usually this is done by connecting a PoE switch to the Mac's Ethernet port.

Using Safari, connect to the default static IP address of the camera –  Log in to the Web Service using the default credentials – admin : admin.  Click the Setup tab and navigate to the Network menu on the left.  Change the IP address, default gateway and subnet mask of the target network segment in the TCP/IP submenu.  Be aware that after changing the information, the installer will not be able to access the camera on the custom network location, so make sure the information is correct.

Repeat step 4 for each camera, making sure that each IP address is unique and available on the target network segment.
                                                                                                                                                                                                                                                  <<  1 - 2 - 3 - 4  >>