DVR5100 Series

Network Design Guide

C3640M (7/08)
Contents
Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Bandwidth Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Bandwidth Utilization and Local Area Network Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Determining Bandwidth Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Determining Bandwidth Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Considerations for Trunk Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Considerations for Wireless Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Considerations for Wide Area Networks and Internet Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installation Scenarios and Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Pre-Existing Wide Area Network Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Common Installation Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Intermittent or No Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
IP Camera Recording Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Appendix A: Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 C3640M (7/08)
List of Illustrations
1 Trunk Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 Physical Network Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Physical Network Topology with IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4 Physical Network Topology with Complete IP Addressing Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5 Physical Network Topology with Three IP Cameras. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6 Using Ping to Test DDNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7 Ping Echo Reply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8 Output from the Tracert Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9 Tracert Displaying Network Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

List of Tables
A Single-Stream Display Bit Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
B Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

C3640M (7/08) 3
Welcome
The DVR5100 Series hybrid video recorder is an embedded, high-performance hybrid digital video recorder (DVR), capable of recording up to
20 cameras at a combined 600/500 images per second (NTSC/PAL) at 4CIF resolution. The DVR comes with a choice of 4, 8, or 16 analog camera
inputs, and supports 16, 12, and 4 IP camera inputs, respectively. The DVR5100 can be networked in a server-to-server configuration, with up to
four additional servers, and support a virtual matrix implementation for up to 100 cameras across five servers. Additionally, it can be integrated
into a fully distributed Endura® system, allowing for centralized monitoring and management of an unlimited number of cameras and servers in a
scalable and expandable IP surveillance system. The DVR5100 provides all of these features, along with efficient configuration, intuitive
operation, and cutting-edge storage optimization technologies, in a mainstream DVR.

This document is a guide for video surveillance system integrators who have a basic understanding of TCP/IP networks and digital video. This
document covers network basics and considerations for installations of DVR5100s with IP cameras in stand-alone mode. For network
considerations and guidelines when installing a DVR5100 in an Endura network, refer to the Endura Network Design Guide (C1640M).

NOTE: Refer to Appendix A: Glossary of Terms on page 17 for terms used in this document

4 C3640M (7/08)
Network Requirements
BANDWIDTH UTILIZATION
To ensure reliable DVR5100 recording and playback, determine the amount of bandwidth to be used during live view, recording, and playback
modes:
• A basic installation of a DVR5100 connected to remote clients (up to five) can be supported with 100 Mbps of network bandwidth available
to the DVR. Each remote client connection leverages the built-in virtual private network (VPN) server for secure communication. Each VPN
connection is limited to 10 Mbps of network bandwidth. Performance of remote access viewing over a wide area network (WAN)
connection varies depending on the following items:
– The bandwidth limiter setting on the DVR5100 server. For reliable operation, ensure that the bandwidth limit is set to a value at or
below the physical limitation of the network being used.
– The bandwidth throttle configuration setting for each remote client.
– The frame rate/resolution settings of the video being recorded and streamed across the network.
• If the DVR5100 installation includes IP cameras, add up to 4 Mbps of network bandwidth for each IP camera connected to a DVR5100.

BANDWIDTH UTILIZATION AND LOCAL AREA NETWORK PLANNING

You must determine the amount of bandwidth that will be required based upon how you plan to use the DVR5100. Table A provides bandwidth
requirements for video frame rate/resolution combinations available on the DVR5100 for each stream of video on the network.

Table A. Single-Stream Display Bit Rates (1 of 2)

Recorded Frame Rate Bit Rate

Resolution (NTSC/PAL) (1 x 1 Display)
CIF 30/25 1.0 Mbps
CIF 15/12.5 800 Kbps
CIF 10/8.3 450 Kbps
CIF 6/5 300 Kbps
CIF 5 840 Kbps
CIF 3 660 Kbps
CIF 1 480 Kbps
CIF 1/2 second 430 Kbps
CIF 1/3 second 415 Kbps
CIF 1/5 second 400 Kbps
2CIF 30/25 1.5 Mbps
2CIF 15/12.5 1.0 Mbps
2CIF 10/8.3 800 Kbps
2CIF 6/5 500 Kbps
2CIF 5 1.6 Mbps
2CIF 3 1.26 Mbps
2CIF 1 980 Kbps
2CIF 1/2 second 910 Kbps
2CIF 1/3 second 890 Kbps
2CIF 1/5 second 870 Kbps
4CIF 30/25 2.0 Mbps
4CIF 15/12.5 1.5 Mbps
4CIF 10/8.3 1.0 Mbps
4CIF 6/5 800 Kbps
4CIF 5 2.0 Mbps
4CIF 3 1.7 Mbps
4CIF 1 1.4 Mbps
4CIF 1/2 second 1.31 Mbps

C3640M (7/08) 5
 Table A. Single-Stream Display Bit Rates (2 of 2)

Recorded Frame Rate Bit Rate

Resolution (NTSC/PAL) (1 x 1 Display)
4CIF 1/3 second 1.28 Mbps
4CIF 1/5 second 1.26 Mbps

DETERMINING BANDWIDTH REQUIREMENTS

To find the amount of bandwidth needed at a DVR5100 server, you must determine the number of video streams you plan to view and record over
the network. You must also determine the frame rate and resolution of the identified video streams, look up the bitrate for these video streams,
and then calculate the total amount of bandwidth required for reliable operation.

The following example illustrates how to calculate bandwidth requirements:

• Assume an installation requires remote client software on two computers (PC1 and PC2). Both computers will view live and playback
video regularly in a 2 x 2 display.
• The DVR5100 will record four IP cameras.
• The resolution/frame rate of all video streams will be CIF/30.

In such a system, the following bandwidth utilization can be calculated:

• PC1: 4 video streams at CIF/30 = 4 Mbps bandwidth utilization
• PC2: 4 video streams at CIF/30 = 4 Mbps bandwidth utilization
• Four IP Cameras: 4 video streams at CIF/30 = 4 Mbps bandwidth utilization

The calculation would be 4 + 4 + 4 = 12 Mbps.

To accommodate variance in network traffic as well as traffic generated by other software applications and systems on the network, you should
multiply the bandwidth utilization by 2 (for example, 12 Mbps x 2 = 24 Mbps). In this example, the network at the DVR5100 must have 24 Mbps
of bandwidth available at all times to ensure reliable recording and viewing.

In summary, the bandwidth calculation steps are as follows:

1. Determine the number of IP cameras to be recorded to the DVR5100.

2. Determine the number of video streams to be viewed on a consistent basis and the display type to be used for viewing.

3. Determine the resolution and frame rate of all video streams to be transported across the network.

4. Determine the bitrate of the video streams you have identified in Table A on page 5.

5. Multiply the number of streams by the appropriate bitrate. This calculation must be performed separately for each group of video streams
that have the same frame rate/resolution.

6. Double the bitrate result from step 5.

7. Add all bitrate results from step 6 to find the amount of bandwidth utilization required.

DETERMINING BANDWIDTH AVAILABILITY

After the required bandwidth is determined, you must determine the amount of bandwidth available on the network. If the DVR5100 and IP
cameras will be installed on a corporate network managed by an IT department, you must consult with the IT administrator to determine if the
network can support the bandwidth requirements for your installation or if the network must be upgraded to support the DVR5100 installation.

If the network is unmanaged or a new installation, many network devices provide bandwidth measurements through a Web-based administration
status page or on the administration command line. Refer to the documentation that was provided with the network devices for instructions on
determining current bandwidth utilization.

Bandwidth constraints on some network paths must also be considered. For example, if you intend to record video from an IP camera over a
network connection between two switches, the bandwidth utilization on this connection (referred to as a trunk line) must be measured to
determine if there is bandwidth available to support recording video from IP cameras.

6 C3640M (7/08)
 CONSIDERATIONS FOR TRUNK CONNECTIONS
Trunk connections (sometimes referred to as uplinks) are configured between network devices (typically between two switches, or between a
switch and a router). If the DVR5100 is configured to record IP cameras through a trunk connection, a 1000 Mbps (1 Gigabit) trunk connection
must be used between network devices. Testing shows that, though a lower-bandwidth trunk connection can accommodate a given number of
IP cameras, trunk connections using 100 Mbps links are not as reliable in long-term operations.

IMPORTANT NOTE. PLEASE READ.

The network implementations in this document are shown as general representations only and are not intended to show detailed network
topologies. Your actual network will differ, requiring changes or perhaps additional network equipment to accommodate the systems as
illustrated. Please contact your local Pelco Representative to discuss your specific requirements.

TRUNK LINK

ETHERNET
SWITCH
IP CAMERAS
BUILDING 2 ETHERNET
SWITCH

TRUNK LINK

DVR5100
BUILDING 3
ETHERNET
SWITCH

IP CAMERA
BUILDING 1

Figure 1. Trunk Connections

CONSIDERATIONS FOR WIRELESS NETWORK CONNECTIONS

Several factors may contribute to the stability and reliability of a wireless network, including the following environmental factors:
• Weather
• Line of site obstructions
• Radio interference (such as microwave ovens and wireless phones)

NOTE: If you must record video from an IP camera over a wireless connection, Pelco strongly recommends that a site survey and network design
be performed by a wireless network professional prior to installation, following the guidelines set forth in the Endura Wireless Design Guide
(C1640M). Ensure that a wireless network connection provides the bandwidth required, based on the calculations provided in Bandwidth
Utilization and Local Area Network Planning on page 5.

CONSIDERATIONS FOR WIDE AREA NETWORKS AND INTERNET CONNECTIONS

WAN connections typically provide lower available bandwidth than local area networks (LAN) connections. WANs should be considered as view
only and should not be used to record IP cameras.

You must consider the amount of bandwidth available on your WAN connection when you design your DVR5100 Series network and installation
plan. The following is a list of typical bandwidth measurements from various WAN types:
• T3: 44 Mbps
• T1: 1.544 Mbps
• Cable Modem: 1–6 Mbps download; 128–768 Kbps upload
• DSL: 768 Kbps download and 384 Kbps upload
• PSTN (Phone Line): 44 Kbps with a 56 Kbps modem

C3640M (7/08) 7
Installation Scenarios and Security Considerations
PRE-EXISTING WIDE AREA NETWORK INSTALLATION
For pre-existing corporate networks managed by corporate IT personnel, contact your IT administrator to proceed with the installation. The IT
administrator must provide you with the following information:
• IP addresses for the DVR5100.
• IP addresses for the IP cameras. If you must use Dynamic Host Configuration Protocol (DHCP), request IP Addresses with an infinite lease.
This will ensure that the IP cameras always have the same IP Addresses, and will provide high availability and ease of management.
• Network ports allocated to the DVR5100.
• Network ports allocated to the IP cameras (if any).
• Amount of WAN bandwidth available for remote viewing.

The IT administrator will require the following information to assist with the installation:
• Installation location of each device.
• Total amount of bandwidth required on the WAN, based on the number of planned, simultaneous, IP camera, and remote viewing video
streams (both live and playback).
• Total amount of bandwidth required on the LAN, based on the number of planned simultaneous remote viewing video streams (both live
and playback).
– Configure the DVR5100 bandwidth limiter and the bandwidth throttle on the remote client with a setting that is at or below the
bandwidth number provided by the IT administrator. For example, if the IT administrator says that you will receive a bandwidth of
300 Kbps on the WAN connection, configure the bandwidth limiter on the DVR5100 server to 256 Kbps and the bandwidth throttle of
the remote client for the 256 Kbps setting.
– If you have more than one remote client accessing the DVR5100 simultaneously, configure the remote clients to operate within the
bandwidth parameters provided by the IT administrator. For example, if you are going to provide a connection to the DVR from three
remote clients, and the IT administrator provides you with 512 Kbps, configure each remote client with a 128 Kbps bandwidth throttle.
This ensures that the three remote clients can access the DVR simultaneously.

COMMON INSTALLATION SCENARIO

This section provides examples of a DVR5100 network installation and covers the most common scenarios.
• Draw a network diagram prior to the installation of the equipment.
• Plan IP addresses for each device on your network. Use a private IP address range for networks that are separated from the Internet by a
router or firewall. For this example, use 192.168.0.100 through 192.168.0.110.

There are two ways to assign IP addresses to your network:

• DHCP: PCs using DHCP
• Static: Servers (such as the DVR5100 and IP cameras) using Static IP addressing.

If the router/firewall provides DHCP services, you can enter the range of IP addresses to be assigned to the PCs according to the router/firewall
installation manual. For this example, apply a range of IP addresses (192.168.0.101 through 192.168.0.103) to the DHCP scope or IP address
range of the router/firewall.

8 C3640M (7/08)
 Figure 2 shows a network diagram that provides a simple physical network topology. The network contains one DVR5100, three PCs, and a
firewall with eight LAN ports. The network is connected to the Internet through DSL.

REMOTE
PC

PC1 INTERNET

DSL MODEM
PC2

ROUTER/FIREWALL

PC3

DVR5100

Figure 2. Physical Network Topology

C3640M (7/08) 9
 For devices to communicate on a TCP/IP network, they must have IP addresses within the same network address range (also referred to as a
subnet). If device IP addresses are not within the same subnet, a router is required to forward information between the two devices. This rule
also applies to network devices (including your firewall).

In Figure 3, IP address 192.168.0.100 is assigned to the internal firewall interface.

REMOTE
PC

PC1 INTERNET
192.168.0.101 (THROUGH DHCP)

DSL MODEM

PC2
192.168.0.102 (THROUGH DHCP)
ROUTER/FIREWALL
192.168.0.100 (STATIC)

PC3
192.168.0.103 (THROUGH DHCP)

DVR5100
192.168.0.104 (STATIC)

Figure 3. Physical Network Topology with IP Addresses

10 C3640M (7/08)
 Figure 3 displays the connections between PCs and the DVR5100, using the assigned IP addresses. However, these devices cannot communicate
with devices on the Internet without additional configuration. The devices on the private network must be configured with a subnet mask and
gateway address to communicate with devices outside of this network. Since the router/firewall can forward traffic from the local private
network to other networks (for example, to the Internet), the router/firewall's internal IP address is the gateway address.

In Figure 4, a 255.255.255.0 subnet mask is used. After adding these configuration parameters (subnet mask and gateway address), all devices
on the local private network should be able to access the Internet (assuming that the router/firewall is configured according to the
manufacturer’s instructions).

REMOTE
PC

PC1 INTERNET
192.168.0.101 (THROUGH DHCP)
255.255.255.0 SUBNET MASK
192.168.0.100 GATEWAY
DSL MODEM

PC2
192.168.0.102 (THROUGH DHCP) ROUTER/FIREWALL
255.255.255.0 SUBNET MASK 192.168.0.100 (STATIC)
192.168.0.100 GATEWAY 255.255.255.0 SUBNET MASK
NO GATEWAY NEEDED
PC3
192.168.0.103 (THROUGH DHCP)
255.255.255.0 SUBNET MASK
192.168.0.100 GATEWAY

DVR5100
192.168.0.104 (STATIC)
255.255.255.0 SUBNET MASK
192.168.0.100 GATEWAY

Figure 4. Physical Network Topology with Complete IP Addressing Scheme

C3640M (7/08) 11
 In Figure 5, the DVR5100 is now configured to record three IP cameras added to the network. Refer to the DVR5100 Series Installation manual
(C1695M) for IP camera installation. To ensure proper operation, viewing, and recording, the IP camera addresses must be within the same
private IP address range, subnet, and gateway as the devices that are already configured. This includes the DVR5100 and PCs on the local LAN.
IP CAMERA 1
192.168.0.104 (STATIC)
255.255.255.0 SUBNET MASK
192.168.0.100 GATEWAY
IP CAMERA 2
192.168.0.105 (STATIC)
255.255.255.0 SUBNET MASK
192.168.0.100 GATEWAY REMOTE
IP CAMERA 3 PC
192.168.0.106 (STATIC)
255.255.255.0 SUBNET MASK
192.168.0.100 GATEWAY
PC1 INTERNET
192.168.0.101 (THROUGH DHCP)
255.255.255.0 SUBNET MASK
192.168.0.100 GATEWAY
DSL MODEM

PC2
192.168.0.102 (THROUGH DHCP) ROUTER/FIREWALL
255.255.255.0 SUBNET MASK 192.168.0.100 (STATIC)
192.168.0.100 GATEWAY 255.255.255.0 SUBNET MASK
NO GATEWAY NEEDED
PC3
192.168.0.103 (THROUGH DHCP)
255.255.255.0 SUBNET MASK
192.168.0.100 GATEWAY

DVR5100
192.168.0.104 (STATIC)
255.255.255.0 SUBNET MASK
192.168.0.100 GATEWAY

Figure 5. Physical Network Topology with Three IP Cameras

For DVR5100 LAN-based remote client connections, follow the instructions provided in the DVR5100 Series Remote Client Operation manual
(C1697M) for proper configuration. Use the manual to configure PC1, PC2, and PC3 (refer to Figure 5), and then verify connectivity and operation
through the remote client. Refer to Troubleshooting on page 14 if you experience DVR5100 connection issues.

For the DVR5100 to be accessible from the Internet (for example, by the remote PC), the router/firewall must be configured to forward remote
client communication requests from the Internet to the DVR5100. One option is to configure port forwarding on the router/firewall using the
DVR5100 service port number (27235), and the DVR5100 IP address on the private network as the destination. Refer to the user manual provided
by your router/firewall to configure port forwarding for your device. If you are installing the DVR5100 on a pre-existing network, contact the
network administrator to request a port forwarding configuration.

Another way to forward Internet traffic to the DVR5100 is to configure the DVR5100 to reside in the DMZ on the router/firewall. This is a less
desirable configuration because the firewall typically will not filter DVR5100 traffic. This option is strongly discouraged. However, if you are
installing the DVR5100 on a pre-existing corporate network, the network administrator may configure the DVR5100 to reside in the DMZ. In this
example, Internet traffic filtering by a firewall is included to protect the DVR5100.

Once port forwarding is configured, install and configure the remote client software on computers that will access the DVR5100 from the
Internet. In this example, you would configure the remote PC (refer to Figure 5). Again, follow the instructions in the DVR5100 Remote Client
Operation manual (C1697M) for the remote client configuration.

Refer to Troubleshooting on page 14 for any connectivity issues experienced during or after configuration.

12 C3640M (7/08)
SECURITY CONSIDERATIONS
The DVR5100 ensures that only authorized remote client connections are allowed by employing a remote access preconfiguration process. Refer
to the DVR5100 Remote Client Operation manual (C1697M) for additional information. In addition, the number of open and active ports is
minimized on the DVR5100 to block all unauthorized remote client connections.

Adhere to the following security best practices when installing the DVR5100. This will ensure that the unit is properly protected from malware
and remote attacks that are common to the Internet.
• Configure the firewall to forward requests from the Internet to the DVR5100 using port number 27235. This is the DVR5100 VPN base port.
• Because the DVR5100 is a security surveillance device, limit remote access to authorized personnel only.
• Assign user IDs based on a particular permissions set. Each permissions set should provide users with access only to those features
necessary to perform their duties.

C3640M (7/08) 13
Troubleshooting
INTERMITTENT OR NO CONNECTION
You might experience intermittent or no connection to the DVR5100 when attempting remote access through the Internet. The following
examples provide possible causes for intermittent or no connection. Each example is followed by a possible solution.
1. The DVR5100 does not allow a VPN in a VPN connection: This configuration is not supported. Thus, if your remote access connection to the
DVR5100 requires you to establish a VPN session with the remote network prior to connecting to the DVR5100, the connection typically will
fail. An alternative solution is to configure the remote network firewall port forwarding to provide access to the DVR5100.

2. Port forwarding is not configured properly on your firewall:

a. Confirm that you programmed your firewall to forward port 27235 to the DVR5100 private IP address.
b. Confirm that your firewall configuration does not block access to this port from the remote PC location.
c. Test the port forwarding configuration as follows:
(1) Open a Web browser on a PC that has Internet access
(2) Type http://Firewall_Public_IP_address_here:27235.
(3) Click Enter.

If port forwarding is working, the browser establishes a connection and does not time out with an error message (for example, page or site
not found).

3. Dynamic Domain Name System (DDNS) failure: You may have a problem connecting to the DVR5100 if the correct public IP address of the
DVR5100 is not up to date with the current public IP address in DDNS. You can confirm that DDNS has the correct public IP address of the
firewall (or the DVR5100, if it is not behind a firewall) by performing the following steps:
a. From a Windows® PC that has access to the DVR5100 only through the Internet (using Windows XP):
(1) Click Start.
(2) Click Run.
(3) Type cmd.
b. At the command prompt:
(1) Type ping.
(2) Press the space bar once.
(3) Type the fully qualified domain name (FQDN) of the DVR5100.
(4) Press Enter.

The reply should return the current public IP address of the firewall. The Public IP address can usually be confirmed by accessing the
firewall's status Web pages, or the IP address of the DVR5100 (if not protected by a firewall).

Figure 6. Using Ping to Test DDNS

It is normal for the first line of output to display the correct IP address, with no reply from the firewall. This occurs because most firewalls
disable ping echo replies as a security measure (refer to your firewall manual to confirm that the output is correct).

14 C3640M (7/08)
 If the ping echo reply does not provide the correct public IP address, or does not provide any IP address (host not found), check your DDNS
configuration on the firewall or DVR5100. If the configuration is correct, reboot the device, and then rerun the ping test.

Figure 7. Ping Echo Reply

4. Network failure: Follow the instructions in step 3 to for running a ping test, with one exception: replace the word “ping” with “tracert.”
Tracert (pronounced “trace route”) provides a response from every device along the path to the DVR5100. Some network devices are
configured to not respond, such as firewalls and certain routers. If the device does not respond, but the next device in the path does, the
output shows a set of stars and states that the request to that device timed out (refer to Figure 8).

Figure 8. Output from the Tracert Tool

5. Intermittent Network Failures: Confirm that there is enough bandwidth on the WAN connection. Other traffic may be consuming bandwidth
on your WAN link, or the WAN link may be faulty. You can quickly test your available bandwidth using speed report Web sites (for example,
www.dslreports.com). Bandwidth availability on your WAN connection may fluctuate throughout the day depending on the amount of WAN
network traffic.

C3640M (7/08) 15
IP CAMERA RECORDING FAILURE
The following are three possible causes for the recording failure of the IP camera. Each example is followed by a solution.
1. There is an IP address mismatch between the DVR5100 and the IP camera.

Solution: Verify the configuration settings for both devices to ensure that they match.

2. A connection appears to fail between the DVR5100 and the IP camera.

Solution: Perform a tracert test using the IP address of the IP camera. Run the test from the DVR5100 side of the network.
• The path is working if the tracert finishes, and ends with the IP camera.
• One of the devices along the network path failed if the tracert stopped before receiving a response from the IP camera. The first series
of stars displayed in the tracert output identifies the point at which the network failed (refer to Figure 9).

Figure 9. Tracert Displaying Network Failure

3. There is an IP camera Power over Ethernet (PoE) issue with the PoE injector, switch, or panel.

Solution: Confirm that the IP camera is working and providing video by accessing it directly through a Web browser. If you can connect to
the IP camera and receive video, the camera is working and should provide recording streams. If you cannot connect to the camera, verify
that the camera is receiving proper power from the PoE injector or device (refer to the IP camera user manual).

16 C3640M (7/08)
Appendix A: Glossary of Terms

Table B. Glossary of Terms (1 of 2)

Term Description
The amount of space or resources available through which data can be sent on a network. This is equivalent to a hose
used to transport water; the larger the hose diameter, the more bandwidth available to transport water. Thus,
Bandwidth
bandwidth is the width of a communication channel. In digital communication, bandwidth is typically measured in bits
per second (bps).
The cable used for 10/100/1000 Ethernet networks. These types of cable are commonly referred to as unshielded
Cat5 or Cat6 twisted pair (UTP) because they contain eight wires twisted together in pairs. The higher category ratings have more
twists per inch, which increases their resistance to electromagnetic interference.
Domain Naming System (DNS) is the commonly accepted way of naming computers on the network. For example,
DNS when you type www.pelco.com (host name) into your Internet browser, the DNS server converts www.pelco.com into
an IP address (numbers only).
Dynamic Domain Name System (DDNS). Most Internet service providers assign IP addresses dynamically using DHCP
and often change or renew the IP addresses. To ensure that a device is always accessible on the Internet at the same
DDNS
address (without using a static IP), the DDNS automatically updates DNS servers whenever a device IP address has
changed, while keeping the same FQDN.
Dynamic Host Configuration Protocol (DHCP) is a TCP/IP protocol that enables PCs and workstations to get temporary
or permanent IP addresses from centrally administered servers. The host computer runs the DHCP server, and the
DHCP
workstation runs the DHCP client. When DHCP is enabled, you are not required to manually assign static IP addresses
to each device on the network.
A demilitarized zone refers to a firewall configuration in which a server or device resides on the private side of the
DMZ firewall. The filtering and protection of the firewall is substantially reduced or disabled for that server to provide full
access to the Internet server.
A network device designed to protect a LAN from malware and malicious intrusion from other networks, specifically
Firewall
the Internet.
Fully Qualified Domain Name (FQDN) is the unique, full length, DNS name used to locate and send information to a
FQDN
device on the Internet. For example, www.pelco.com is the FQDN for the Pelco Web site.
For purposes of this guide, gateway refers to the IP address of the router/firewall that forwards communication to
Gateway
devices that are not within the local private network.
Internet Protocol (IP) is a data-oriented, lower layer protocol used to communicate data across a packet-switched
IP
internetwork. IP addresses and sends messages.
A unique address used by electronic devices to identify and communicate with each other on a computer network,
IP Address
utilizing the IP standard.
A video surveillance camera that uses a TCP/IP network to transport video streams to the user for live viewing or the
IP Camera
DVR for recording.
IT Administrator The person in charge of the design, installation, and maintenance of a corporate network.
Kbps A measurement of bandwidth, Kilobits per second equals 1,000 bits per second.
A local area network (LAN) is contained within a relatively small area, usually within a building. A LAN typically uses
LAN Ethernet as the underlying protocol and TCP/IP to address, transport, and deliver data. A LAN typically has a higher
bandwidth availability than a WAN and is usually 10, 100, or 1000 Mbps.
Software designed to infiltrate or damage a computer system without the owner’s informed consent (commonly
Malware
referred to as a virus, worm, or trojan).
A measurement of bandwidth. Megabits per second (Mbps) equals one million bits per second; the higher the number,
Mbps
the more available bandwidth.
PoE Power over Ethernet (PoE) delivers both power and network data transport through the same Cat5 or Cat6 cable.
A reserved range of IP addresses that can only be used on private networks and cannot be routed on the Internet. The
Private IP address ranges include:
Private IP Addresses • 10.0.0.0 through 10.255.255.255
• 172.16.0.0 through 172.31.255.255
• 192.168.0.0 through 192.168.255.255.

C3640M (7/08) 17
 Table B. Glossary of Terms (2 of 2)

Term Description
Port forwarding allows remote computers (for example, public machines on the Internet) to connect to a specific
Port Forwarding computer within a private LAN. Port forwarding uses the port number of a service on a private network host, and then
forwards traffic destined for that port number to a designated IP address (only to the specific port).
A general term used to describe a computer or device that provides a service to other hosts on a network (for
Server
example, a PC that provides access to information through a Web browser (Web server).
A number, typically written in dotted decimal notation, that identifies the network portion of an IP address. For
Subnet Mask example, if you are using IP address 10.0.0.1 and subnet mask 255.255.255.0, then the network address would be
10.0.0.0, and all devices within that network would communicate without the assistance of a router.
The Transmission Control Protocol/Internet Protocol (TCP/IP) is the prevalent protocol used in computer networks.
TCP/IP
TCP/IP is comprised of a suite of protocols that include IP, TCP, User Datagram Protocol (UDP), and so forth.
Wide Area Network (WAN) refers to networks that span large areas, such as the areas between cities. WAN
technology typically uses different underlying protocols than a LAN for transporting data, while still using TCP/IP to
establish sessions, and address and forward information. The WAN connection types are as follows:
• Dedicated Leased Line: A connection that is leased from the telephone company is typically used as a dedicated
line that is not shared by other companies.
WAN
• Virtual Private Network (VPN): A session established between two devices over the Internet. VPNs use
encryption to keep data secure while using the public Internet to transport private data.
• Internet Service Provider (ISP): An ISP provides a WAN connection through the public Internet, typically using
a digital subscriber line (DSL), cable modem (same line as cable TV), or a public switched telephone network
(PSTN). This is the least expensive WAN option.

18 C3640M (7/08)
 PRODUCT WARRANTY AND RETURN INFORMATION
WARRANTY
Pelco will repair or replace, without charge, any merchandise proved defective in
material or workmanship for a period of one year after the date of shipment.
Exceptions to this warranty are as noted below:
• Five years on fiber optic products and TW3000 Series unshielded twisted pair
(UTP) transmission products.
• Three years on Spectra® IV products.
• Three years on Genex® Series products (multiplexers, server, and keyboard).
• Three years on DX Series digital video recorders, DVR5100 Series digital video
recorders, Digital Sentry® Series hardware products, DVX Series digital video
recorders, NVR300 Series network video recorders, and Endura ® Series
distributed network-based video products.
• Three years on Camclosure® and Pelco-branded fixed camera models, except
the CC3701H-2, CC3701H-2X, CC3751H-2, CC3651H-2X, MC3651H-2, and
MC3651H-2X camera models, which have a five-year warranty.
• Three years on PMCL200/300/400 Series LCD monitors.
• Two years on standard motorized or fixed focal length lenses.
• Two years on Legacy®, CM6700/CM6800/CM9700 Series matrix, and DF5/DF8
Series fixed dome products.
• Two years on Spectra III™, Spectra Mini, Esprit®, ExSite®, and PS20 scanners,
including when used in continuous motion applications.
• Two years on Esprit and WW5700 Series window wiper (excluding wiper
blades).
• Two years (except lamp and color wheel) on Digital Light Processing (DLP®)
displays. The lamp and color wheel will be covered for a period of 90 days. The
air filter is not covered under warranty.
• Two years on Intelli-M® eIDC controllers.
• One year (except video heads) on video cassette recorders (VCRs). Video heads
will be covered for a period of six months.
• Six months on all pan and tilts, scanners, or preset lenses used in continuous
motion applications (preset scan, tour, and auto scan modes).
Pelco will warrant all replacement parts and repairs for 90 days from the date of
Pelco shipment. All goods requiring warranty repair shall be sent freight prepaid
to a Pelco designated location. Repairs made necessary by reason of misuse,
alteration, normal wear, or accident are not covered under this warranty.
Pelco assumes no risk and shall be subject to no liability for damages or loss
resulting from the specific use or application made of the Products. Pelco’s liability
for any claim, whether based on breach of contract, negligence, infringement of
any rights of any party or product liability, relating to the Products shall not exceed
the price paid by the Dealer to Pelco for such Products. In no event will Pelco be
liable for any special, incidental, or consequential damages (including loss of use,
loss of profit, and claims of third parties) however caused, whether by the
negligence of Pelco or otherwise.
The above warranty provides the Dealer with specific legal rights. The Dealer may
also have additional rights, which are subject to variation from state to state.
If a warranty repair is required, the Dealer must contact Pelco at (800) 289-9100 or
(559) 292-1981 to obtain a Repair Authorization number (RA), and provide the
following information:
1. Model and serial number
2. Date of shipment, P.O. number, sales order number, or Pelco invoice number
3. Details of the defect or problem
If there is a dispute regarding the warranty of a product that does not fall under
the warranty conditions stated above, please include a written explanation with
the product when returned.
Method of return shipment shall be the same or equal to the method by which the
item was received by Pelco.
RETURNS
To expedite parts returned for repair or credit, please call Pelco at (800) 289-9100
or (559) 292-1981 to obtain an authorization number (CA number if returned for
credit, and RA number if returned for repair) and designated return location.
All merchandise returned for credit may be subject to a 20 percent restocking and
refurbishing charge.
Goods returned for repair or credit should be clearly identified with the assigned
CA or RA number and freight should be prepaid.
6-20-08

The materials used in the manufacture of this document and its components are compliant to the requirements of Directive 2002/95/EC.

This equipment contains electrical or electronic components that must be recycled properly to comply with Directive 2002/96/EC of the European Union
regarding the disposal of waste electrical and electronic equipment (WEEE). Contact your local dealer for procedures for recycling this equipment.

REVISION HISTORY
Manual # Date Comments
C3640M 7/08 Original version.

Pelco, the Pelco logo, Camclosure, Digital Sentry, Endura, Esprit, ExSite, Genex, Intelli-M, Legacy, and Spectra are registered trademarks of Pelco, Inc. © Copyright 2008, Pelco, Inc. All rights reserved.
Spectra III is a trademark of Pelco, Inc.
DLP is a registered trademark of Texas Instruments Incorporated.
Windows is a registered trademark of Microsoft Corporation.
 Worldwide Headquarters
3500 Pelco Way
Clovis, California 93612 USA

USA & Canada

Tel: (800) 289-9100
Fax: (800) 289-9150

International
Tel: +1 (559) 292-1981
Fax: +1 (559) 348-1120

www.pelco.com

ISO9001

Australia | Finland | France | Germany | Italy | Macau | The Netherlands | Russia | Singapore
South Africa | Spain | Sweden | United Arab Emirates | United Kingdom | United States