Right now my cameras are are 10.1.1.xxx i guess because i have my nvr configured with dhcp on. maybe that's what's causing me my problems. i would like to make changes directly to the camera.
password - my passwords are admin/admin. if i change them in the nvr, the status goes red.
ip address to static doesn't look like that option is available in the new ui for nvr nv4108e - hs
so if i connect the cameras to my router, they will get an 192.168.1.xxx ip. if this is changed to 10.1.1.xxx, will i be able to access them directly again.
I read that using a 10.1.1.xxx ip for the cameras makes them more secure. but maybe it just creates too many other problems.
camera ip of 10.1.1.xxx, need direct access to the camera
Re: camera ip of 10.1.1.xxx, need direct access to the camera
One IP over another don't do anything for more or less secure... Internal IP is just that.. What the issue is your camera is setup for DHCP... What you need to do if you want to access your camera after connected to your network that is in the Range of 192.168.1.xxx is add another range in your Computer... This way when you want to access your camera that is connected to your normal Network your computer having both ranges set in it as being Static IP's then you can connect..
So like for my system. My main computer is setup with 5 different IP addresses as Static IP.. I only have my Main Network as my Gateway and that is only option that is needed...
FOr me I have
10.0.0.xxx
10.0.1.xxx
192.168.1.xxx
192.168.0.xxx
192.168.234.xxx
All setup as Static IP's for my main computer.. This computer can connect to any of them IP address that is connected in my Switch on my Network as long as they are all behind my Switch..
Some of my IP cameras when Reset to Factory are setup Static in a different range then I have my system setup so I wanted to make sure I could reach all things connected into my network without much trouble.. The only down side to this is if you want to use a computer for PC-NVR you need to make sure that computer only has 1 IP or PC-NVR don't work...
So like for my system. My main computer is setup with 5 different IP addresses as Static IP.. I only have my Main Network as my Gateway and that is only option that is needed...
FOr me I have
10.0.0.xxx
10.0.1.xxx
192.168.1.xxx
192.168.0.xxx
192.168.234.xxx
All setup as Static IP's for my main computer.. This computer can connect to any of them IP address that is connected in my Switch on my Network as long as they are all behind my Switch..
Some of my IP cameras when Reset to Factory are setup Static in a different range then I have my system setup so I wanted to make sure I could reach all things connected into my network without much trouble.. The only down side to this is if you want to use a computer for PC-NVR you need to make sure that computer only has 1 IP or PC-NVR don't work...
Be Safe.
Re: camera ip of 10.1.1.xxx, need direct access to the camera
thanks, that makes sense. i didn't think the 10.1.1.xxx was any different than any other subnets but wanted to confirm if there was some magic that i wasn't aware of. maybe the 10.1.1.xxx is not as often used and that might make it easier to hide. i've already got all my smart devices on a different subnet hung off a front end router that i use to allow in bound wan access. another router handles all my home computers making them a bit more secure - I hope???
Re: camera ip of 10.1.1.xxx, need direct access to the camera
I must be missing the piece of magic to get this to work. They only way i've been able to access the cameras directly is to plug them into the router 192.168.1.1 along with an auxiliary power supply since they are poe cameras that have a pigtail where i can plug in a power supply. for now, i've changed the ip, made it static and also changed the password.
then i plug the camera into the poe of the nvr. i can see that the password stuck, i now get a new ip, can't see if it is static but if i'm getting a new ip it must not be. can't figure out how to access the camera directly and connected to the nvr it doesn't allow me to change static or ip.
i'm using a laptop, with wireless connection back to 192.168.1.1. my switch is set up to be 10.1.1.1 and gateway is 10.1.1.1. my nvr ip is 192.168.1.108.
om my laptop i tried a number of different options bu this one is easiest to explain
got to tcp/ip 4 setings. unselect ip automatically, use an ip of 10.1.1.121, mask 255.255.255.0, gateway 192.168.1.1, same as nvr. can't access cameras, can't ping them.
tried to move the poe switch to 192.168.1.xxx and nvr wouldn't allow it.
i also read another post where you suggested adding another switch. initially i just had the switch - unmanaged and my laptop wired into it. got 169 address. so i went back to the tcp/ip 4 procedure in mentioned above. then plugged the nvr ethernet into the switch. still no joy.
where am i going wrong?
then i plug the camera into the poe of the nvr. i can see that the password stuck, i now get a new ip, can't see if it is static but if i'm getting a new ip it must not be. can't figure out how to access the camera directly and connected to the nvr it doesn't allow me to change static or ip.
i'm using a laptop, with wireless connection back to 192.168.1.1. my switch is set up to be 10.1.1.1 and gateway is 10.1.1.1. my nvr ip is 192.168.1.108.
om my laptop i tried a number of different options bu this one is easiest to explain
got to tcp/ip 4 setings. unselect ip automatically, use an ip of 10.1.1.121, mask 255.255.255.0, gateway 192.168.1.1, same as nvr. can't access cameras, can't ping them.
tried to move the poe switch to 192.168.1.xxx and nvr wouldn't allow it.
i also read another post where you suggested adding another switch. initially i just had the switch - unmanaged and my laptop wired into it. got 169 address. so i went back to the tcp/ip 4 procedure in mentioned above. then plugged the nvr ethernet into the switch. still no joy.
where am i going wrong?
Re: camera ip of 10.1.1.xxx, need direct access to the camera
worked a little more on this and made some progress but also have some road blocks. first i reset an indoor IP2M-841 and connected it directly to the 192.168.1.1 router. was able to view in the web ui and changed the password as part of the startup to have a new password. i then did a scan and the nvr nv4108e-hs found it in the camera registration area. i did an add and it now shows up in channel d2. all appears good. still connected to 192.168.1.1
then i tried the same operation on an ip3m-954e outdoor bullet camera but didn't reset it. resetting it requires removing the lens and shorting 2 connectors. difficult with a camera on a work bench, much harder when the camera is under a roof eve and your 5 feet of the ground on a step ladder. I had just done this once because i forgot the password. my mistake. but i had to squeeze the shell so hard to twist the lens off, it cracked the lens.
i connected it directly to the router 192.168.1.1 but it came up with 10.1.1.65 because it had not been reset. so i can't connect to it to directly use the web ui. I was ok with having to reset the camera because i had forgotten the password. but doing changes that the nvr interface doesn't support is not okay.
my prior nvr - NV30M8-4B-B? also had 8 poe ports but i believe it did not set up the cameras in a separate subnet, so it was easy to access directly. if i can't find a way to directly access the cameras for changes, as amcrest recommends, i"ll return this nvr.
then i tried the same operation on an ip3m-954e outdoor bullet camera but didn't reset it. resetting it requires removing the lens and shorting 2 connectors. difficult with a camera on a work bench, much harder when the camera is under a roof eve and your 5 feet of the ground on a step ladder. I had just done this once because i forgot the password. my mistake. but i had to squeeze the shell so hard to twist the lens off, it cracked the lens.
i connected it directly to the router 192.168.1.1 but it came up with 10.1.1.65 because it had not been reset. so i can't connect to it to directly use the web ui. I was ok with having to reset the camera because i had forgotten the password. but doing changes that the nvr interface doesn't support is not okay.
my prior nvr - NV30M8-4B-B? also had 8 poe ports but i believe it did not set up the cameras in a separate subnet, so it was easy to access directly. if i can't find a way to directly access the cameras for changes, as amcrest recommends, i"ll return this nvr.
Re: camera ip of 10.1.1.xxx, need direct access to the camera
OK Good to hear your making some head way...
So here is what I have done to make this task easy for me... My main computer and I hate to admit I have a good few however my main computer has Static Ip with Multi IP ranges..
10.0.0.1, 10.0.1.1, 192.168.0.1, 192.168.1.1 and so on for all the ranges I work with on my network.. Then if I move a camera or just want or need to access a camera that is in a different range I can still make the connection another and maybe little easier solution would be to use Amcrest IP Config TOOL.. This tool can be found on the Website and while I don't remember because it has been long tine since I have looked at one of the Camera CD's it could be found there as well..
With IP config you load the program and do a Search by clicking a button and it will find any camera that is connected to the same network as you no matter the range with in reason.. Some times I do a Search and it will only pull up 8 to 10 items do it again and it will pull up 12 or 15 and only 1 or 2 of my Recorders then do again and mayne if I am lucking it will pull up any of my Dahua and Amcrest devices and some others from Dahua Line of Recorders it don't pull in any of my Hikvision products or any of my Crazy branded IP cameras that have Strange China Menus.. Anyway within that Ip config you can make changes to the device as long as you know the Log in for it. Can even do FW updates in Batch form..
So here is what I have done to make this task easy for me... My main computer and I hate to admit I have a good few however my main computer has Static Ip with Multi IP ranges..
10.0.0.1, 10.0.1.1, 192.168.0.1, 192.168.1.1 and so on for all the ranges I work with on my network.. Then if I move a camera or just want or need to access a camera that is in a different range I can still make the connection another and maybe little easier solution would be to use Amcrest IP Config TOOL.. This tool can be found on the Website and while I don't remember because it has been long tine since I have looked at one of the Camera CD's it could be found there as well..
With IP config you load the program and do a Search by clicking a button and it will find any camera that is connected to the same network as you no matter the range with in reason.. Some times I do a Search and it will only pull up 8 to 10 items do it again and it will pull up 12 or 15 and only 1 or 2 of my Recorders then do again and mayne if I am lucking it will pull up any of my Dahua and Amcrest devices and some others from Dahua Line of Recorders it don't pull in any of my Hikvision products or any of my Crazy branded IP cameras that have Strange China Menus.. Anyway within that Ip config you can make changes to the device as long as you know the Log in for it. Can even do FW updates in Batch form..
Be Safe.
Re: camera ip of 10.1.1.xxx, need direct access to the camera
One way to use camera Web UI to access your cameras connected to NVR is to connect your laptop to one of your NVR camera ports with ethernet cable.
Re: camera ip of 10.1.1.xxx, need direct access to the camera
Revo2Maxx - when i got into the tcp/ip 4 properties, i missed the advanced features that allows multiple ip ranges. however i did set use this ip and ip ranges of 10.1.1.1 as my single range for a temporary basis. connected to wirelessly to my router 192.168.1.1 but couldn't get anywhere. Would I need at least 2 ranges for this to work? will try this.
I have used the ip config tool to obtain the ip address of the camera but found i could just use the client list from router admin to get this. I'll look at it again to see what additional features it might provide.
Jack7 - thanks. I had thought of this but wanted to make sure connecting my laptop to a poe port wouldn't cause any problems. poe should negotiate to see if power is required first. but for some reason there is a reference in the manual to not connect a switch to the poe port.
I have used the ip config tool to obtain the ip address of the camera but found i could just use the client list from router admin to get this. I'll look at it again to see what additional features it might provide.
Jack7 - thanks. I had thought of this but wanted to make sure connecting my laptop to a poe port wouldn't cause any problems. poe should negotiate to see if power is required first. but for some reason there is a reference in the manual to not connect a switch to the poe port.
Re: camera ip of 10.1.1.xxx, need direct access to the camera
Yes and no.. Normally your main ip should match your Gateway and come not all computers can get confused if you try and setup a gate way on 192.168.1.1 and set your IP range to something like 10.1.1.xxx unless you have a multi route setup..
However if your computer was setup with 10.1.1.xxx and was static with it's gateway setup being added to a Range without an idea your using such range would let you work within your range on that network without being able to talk between the 2.. If you don't have it setup right your PVT IP in different segment might get tossed by your router and being junk and not return to you and your package with DIE as your TTL will be reduced to null or 1 and could be what is going on when you are using the 10.x.x.x IP on a 192.x.x.x Gateway
Then for best results without having to setup a network framework like mine it is best to have your computer with your Gateway and just add to that one the IP's missing as extra IP's
However if your computer was setup with 10.1.1.xxx and was static with it's gateway setup being added to a Range without an idea your using such range would let you work within your range on that network without being able to talk between the 2.. If you don't have it setup right your PVT IP in different segment might get tossed by your router and being junk and not return to you and your package with DIE as your TTL will be reduced to null or 1 and could be what is going on when you are using the 10.x.x.x IP on a 192.x.x.x Gateway
Then for best results without having to setup a network framework like mine it is best to have your computer with your Gateway and just add to that one the IP's missing as extra IP's
Be Safe.
Re: camera ip of 10.1.1.xxx, need direct access to the camera
more progress and getting close??
revo2maxx - didn't get any place by by adding a static 2nd ip address 10.1.1.121. i'ts not clear to me how that will be used. my 10.1.1.xxx only exists on the switch. i don't know how to get to that network except through the switch.
jack7 - i plugged a laptop into 1 of the poe ports. i don't have dhcp running on the nvr. so in tcp/ip 4 i set a static ip of 10.1.1.1.129, mask as 255.255.255.0 and gateway back to the router supporting the nvr 192.168.1.1. windows didn't like me using this as a gateway as it was outside my subnet but i ignored it. then in exiting ethernet status, windows wanted to fix by setting ip automatically. again i ignored.
i currently have 2 cameras plugged in. one is an indoor ip2m-841b externally powered which i now can access through it's web ui outside the nvr as well as ping it. . so that's really good news. the other, ipm3m-954 external bullet poe camera i can not access through the web ui standalone. nor can i ping it.
both cameras have a good status in the nvr and are viewable, so i'll need to look further into the poe camera. first i need to work on the physical aspects of my debugging setup. my poe camera has a 12v pigtail and i can put a power supply on a step ladder which allowed me to connect it to a non poe router for testing. my nvr and the ethernet cable to the poe camera are in the lower level of my house, so i needed to disconnect the poe from the nvr, connect a 100 foot cable to it and plug it into the router upstairs. that worked but was messy. I'll probably get a single port injector so i can easily test without the nvr and add a switch in so i don't need the extension cable.
then need to look at configuring alarming and remote viewing to make sure there aren't any other issues. my earlier nvr was an amcrest nv30m8. it had 8 poe ports but set things up in the same subnet as the router so there was no problem accessing through the camera standalone ui.
if i had known this, i would have gotten a none poe nvr and a separate 8 port injector. just a much simpler setup.
revo2maxx - didn't get any place by by adding a static 2nd ip address 10.1.1.121. i'ts not clear to me how that will be used. my 10.1.1.xxx only exists on the switch. i don't know how to get to that network except through the switch.
jack7 - i plugged a laptop into 1 of the poe ports. i don't have dhcp running on the nvr. so in tcp/ip 4 i set a static ip of 10.1.1.1.129, mask as 255.255.255.0 and gateway back to the router supporting the nvr 192.168.1.1. windows didn't like me using this as a gateway as it was outside my subnet but i ignored it. then in exiting ethernet status, windows wanted to fix by setting ip automatically. again i ignored.
i currently have 2 cameras plugged in. one is an indoor ip2m-841b externally powered which i now can access through it's web ui outside the nvr as well as ping it. . so that's really good news. the other, ipm3m-954 external bullet poe camera i can not access through the web ui standalone. nor can i ping it.
both cameras have a good status in the nvr and are viewable, so i'll need to look further into the poe camera. first i need to work on the physical aspects of my debugging setup. my poe camera has a 12v pigtail and i can put a power supply on a step ladder which allowed me to connect it to a non poe router for testing. my nvr and the ethernet cable to the poe camera are in the lower level of my house, so i needed to disconnect the poe from the nvr, connect a 100 foot cable to it and plug it into the router upstairs. that worked but was messy. I'll probably get a single port injector so i can easily test without the nvr and add a switch in so i don't need the extension cable.
then need to look at configuring alarming and remote viewing to make sure there aren't any other issues. my earlier nvr was an amcrest nv30m8. it had 8 poe ports but set things up in the same subnet as the router so there was no problem accessing through the camera standalone ui.
if i had known this, i would have gotten a none poe nvr and a separate 8 port injector. just a much simpler setup.