You can enable P2P at any time by going into the NVR GUI.
But you can use DMSS app without P2P enabled, just when not home you won't be able to connect unless you VPN back into your network.
Is it normal to heave two IP entries for the NVR?
- Thread starter JPmedia
- Start date
You can enable P2P at any time by going into the NVR GUI.
But you can use DMSS app without P2P enabled, just when not home you won't be able to connect unless you VPN back into your network.
Well sure, that's being smart and if you weren't sure then you did the right thing, IMO....kudos!
I came from Lorex NVR to a Dahua as well. Take the Lorex out and go to the Dahua today. Setting things up with that Lorex can make a mess of things with the Dahua.
bigredfish
Known around here
Go to networking P2P on the NVR and enable
Then in DMSS when you go to add the NVR, use “manual” (not IP/Domain), and use the NVR serial number shown on the P2P screen to add it to DMSS
bigredfish
Known around here
Ok, so here is what I have. Moving cameras from the Lorex NVR to the 2 Dahua NVR5216-16P-4KS2E NVRs. I will have 18 cameras to assign and organize into a logical flow and order. My thought is to organize the order by camera location in a counterclockwise direction.
I'd like to split the camera count equally between the NVRs, but will it be of any benefit to performance? I don't have any other locations in mind currently, but I would like to keep order of location if possible.
Here is the list of cameras arranged by the port number from the old NVR. If I'm to keep a clockwise flow, the order of some of these will need to be changed:
The cameras marked in red will be new cameras mounted near existing cameras for different FOVs
I'd like to split the camera count equally between the NVRs, but will it be of any benefit to performance? I don't have any other locations in mind currently, but I would like to keep order of location if possible.
Here is the list of cameras arranged by the port number from the old NVR. If I'm to keep a clockwise flow, the order of some of these will need to be changed:
NUMBER | LOCATION | CAMERA | NEW NVR/CHANNEL |
1 | NORTH SIDE YARD PTZ | LOREX LN44P4B | |
2 | DRIVEWAY SW | DAHUA N45EFN2 | |
3 | DRIVEWAY NW | DAHUA N45EFN2 | |
4 | FRONT DOOR | DAHUA HDW5231R-Z | |
5 | CUL-DE-SAC | T54IR-AS-S3 3.6mm | |
6 | BACKYARD NE | DAHUA HDW5231R-Z | |
7A | SOUTH SIDE ZOOM | DAHUA HFW5442E-Z4E | |
7B | SOUTH SIDE WIDE | T54IR-AS-S3 2.8mm | |
8 | LYNBROOK SPTZ | PTZ5A4M-25X | |
9 | CAMDEN SPTZ | LOREX LN44P12B | |
10A | LOCUST/LYNBROOK ZOOM | DAHUA HFW5442E-Z4E | |
10B | LOCUST/LYNBROOK WIDE | B54IR-ZE-S3 | |
11 | LYNBROOK OVERVIEW | B54IR-ZE-S3 | |
12 | LPR EAST | B52IR-Z12E-S3 | |
13 | LPR WEST | B52IR-Z12E-S3 | |
14 | END OF DRIVEWAY | T5442T-ZE | |
15 | DRIVEWAY PTZ | LOREX LN44P12B | |
16 | END OF DRIVE (CAMDEN) LPR | B52IR-Z12E |
The cameras marked in red will be new cameras mounted near existing cameras for different FOVs
On to cameras. If the cameras are reset, do they need to be initialized through the camera GUI stand alone, or can you connect them to the NVR and they get the relevant data from the NVR (password, location, IP address, etc.)
The cameras will not "reset" on their own.
But if you have to factory reset them because you did something funky with them like manually assigned them passwords and what not, when you factory reset them, the NVR will initialize the cameras for you.
bigredfish
Known around here
bigredfish
Known around here
Factory reset (manual button) each camera, then plug them in one at a time, wait, wait, REFRESH, and when it appears in the bottom pane of the Camera Registration page with a 10.1.1.x address and a green indicator, go to the next one. DO NOT fuck around with each one, wait until you have them all connected so you dont get sidetracked, ..again
Since you are using 2 NVRs, I would probably split the cameras equally, but also don't put all of one side of a house on one NVR so when one fails, you don't completely lose all of one side.
If you have more than one LPR, put on on each NVR, etc.
If you have more than one LPR, put on on each NVR, etc.
192.169.x.x is an internet-routable subnet that should not be used on a private LAN. Unless you like having random websites not work just because your LAN IP range happens to overlap with their WAN IP. private ipv4 ranges
bigredfish
Known around here
The plan is to reset and start new to eliminate anything I possibly made a mess of. For some reason, I thought each camera had to be initialized individually by itself, but it looks like that is not the case
I never knew that. I never had an issue with websites not working. Changing the entire network device IP addresses is going to be fun. Uhhgh
bigredfish
Known around here
They will.
But they will connect and be recognized by the NVR, given a 10.1.1.x IP, accept/copy the NVR admin password, and show green in the bottom panel.
Only then will you login to each camera via the blue IE icon on the NVR and initialize them. (Which is just saying no to two questions)
bigredfish
Known around here
If your router is handing out 192.169.x.x to your internal LAN DHCP pool that’s not cool.
Go into your router and change the dhcp range to 192.168.1.1- 192.168.1.255
The router IP itself should be excluded from the range. Likely .1