Wow, that's an overly-general question.
My first thought: Are you even really ready to handle an "Install Location"?
My second thought: Your general question shows you didn't put much detail (or thought?) into it before lobbing it out to us. Therefore, I think most knowledgeable people won't invest more time than you spent (in typing in that question)
Do some research on your own nickel, then ask specific questions on the forum.
I will cut him some slack, I always set up my cams to the NVR beforehand and burn them in. When i go to the site at least i know everything works before I get there. BTW, before I go to the site, I would have already have visited that site most likely a few times and prepared a plan on networking, tcpip scheme and the goals of the end user, cam locations ..it goes on and on. I usually use NVR's with built in POE to keep the routing off existing equipment. In house IT people do NOT like the camera guy encroaching on their networks so I usually try to keep it as private as possible(as far as the networking goes). Their is NO way you can predict a outcome if you are adding IP cameras to a existing network BUT if you do your homework ahead of time about what already in place, you can get a general feel of the outcome ...in other words..it looked good on paper.
Curious, is there any particular reason not to use the DHCP option for the NVR Ethernet port?
Thanks guys for that additional information.
So I got around to looking through the NVR settings today and noticed there are 3 accounts. One being the account I setup during the first boot, the others if I remember correctly being "default" and "888888". Neither of which allow you to directly change the passwords. I remember reading this somewhere so it wasn't much of a surprise but is there a way around this as it does not seem very secure. If not, are these accounts limited to local use only or could someone use these accounts remotely once a dns was setup and ports forwarded?
Then when you get to the install location, all you should need to do is set the IP address of the NVR (not the cams) to the same range as the local network at the install site.
AFAIK NO I love the Dahua stuff but you have to take the good with the bad and the 888888 is bad. if you have a environment where you are worried about people illegally probing your nvr then you need to plan to keep it locked up, My Racks are under lock and key.Ok good to know. How do you prevent someone with access to google and a keyboard that has the following keys "dahua NVR default user 888888" from figuring out the password? lol Is there anyway to change it to prevent a local unauthorized user from getting in?
Can you explain this a bit as I may be interested in doing this so I can have full access to the cameras features through team viewer via a connection from a windows pc at the installed location if something gets fuxed.Adding to this, a common go-to is to set up a route to bounce in between subnets as well. This will allow a surveillance network of 192.x.x.x/24 to speak to a main network of 172.x.x.x/24.