So I have wrote this 5 or 6 times now lol.. So to keep it short.. I will just say before long I will have my POE NVR from my House in WA and I sent my son the 4018h I had here and a 24port 12ch Switch so I can have my 4108e in front of me lol..
Now more on that in other topics later..
So here is a Picture of my current Computers IP setup... Please note that the Main IP and The Gateway are only 2 in the same range of IP's
SO when I take a Camera that I might have setup in another area outside of my home network, I can take that camera connect to my Switch either POE Port or standard port and with no other magic I can just type 192.168.1.108 is a common IP static for IP cameras I have had over the years.. SO if I get one and Reset it I don't have to go looking around for what IP it is set at I can just go to some Common IPs or Bring up IP config tool lol.. Most times I just use IP address in IE.. If the first few fail I will ARP in a CMD prompt window.. last resort I will bring up IP config..
revo2max - thank you for your response and additional clarifying info about placing the camera on a switch other than connected to the nvr. prior to that i was just adding the ip using advanced tp/ip4 option and the trying to connect directly to the camera. by turning off automatically get my ip, adding a static ip for my pc, adding an additional ip using the advanced option and then putting the camera on a switch i was able to access the camera directly.
There are some issues with this approach that need to be recognized. It was easier for me to initially use a laptop. this is problematic because if you take the laptop to the outside world, say a starbucks, you need to remember to turn dhcp on. and this will erase all your additional ip's and later you need to renter them. also, while on my home internet, i needed to manually add dns entries to access the internet with this approach.
so i switched to using a desktop because it was non mobile. this desktop was on a subnet that cascades off my front end main router. in this case, adding dns entries did not allow me access to the internet, don't know why. so still have the problem of switching dhcp on and erasing the additional ips. but much easier to recognize the corrective actions needed then where i at starbucks.
the desktop also had 2 lan ports, so i thought i would do the additional ips in the second one and leave my normal lan port unchanged and just toggle the cable between the two when i need direct access to the camera. didn't work, appears the configuration of the 2nd lan port got confused when adding additional ips. don't know why, might investigate further in the future.
my reason for spending the time now was to understand how to fix a problem when the nvr access to the camera didn't provide what i needed. in the process i found an instance where this is true. i have a ptz camera the i mounted upside down near a high ceiling. it needed to be 180 and mirrored to provide the correct view. i found the mirror toggle in the nvr to be non-functional. and i certainly don't expect this to be the last.
i'll also list some of my failures so others don't go down the same rabbit hole. I connected a pc to the poe ports out of the nvr. some times a ptz camera would be found with amcrest ipconfig, never a bullet camera.
i set up a standalone router with a base ip of 10.1.1.1. connected the camera and a pc with dhcp on to this. didn't work, and don't know why. this was an older router linksys wrt310n that doesn't provide a connected client list, only dhcp clients so i dodn't know if it ever recognized the camera. and ipconfig didn't show anything.
there are a few more things i would like to check out. my bullet cameras have a pigtail for a power hookup but to access the camera i need to get on a ladder. i have a single poe port injector on order to help with this. no more ladder work.
plan on posting further results but likely wouldn't get to until a week or more.
An Idea for your setup... Please note I have done things you mention you can't so I know it can be done.. I have some other Routers I will go pull and try some other things
But rather then setting up your Router to be on the same IP as your NVR's Backend.. Setup your router on the same Range just different IP.. I think your issue was that the NVR and Router were in a Fight for who own the IP...
SO setup your Router to be at 10.1.1.200 and if it is setup to hand out xyz IP setup to give out above 200.. Then when you put your Router on the back side of the NVR cameras in Range of 10.1.1.202 say that could be Pulled into the NVR backside...
So I have my computer setup with Multi IP addresses.. 10.1.1.109 is one of the IP's This IP when I plug my POE+ Switch on a NON poe port into my POE NVR I can access all cameras on the back side of the NVR... I can also take a Camera that I have setup normally on the Backside of the NVR and plug into my POE switch POE Port while connected to my NVR VIA as I just said and that camera will go over the cable and go back to the port it was already in..
I would need to do more testing to see what it does when I don't connect that IP camera to my Switch before setting up another camera to go into another channel because I have always taken say a Channel say like Ch3 Removed cable from NVR and Plugged into Switch, Connect that camera to POE port in Switch and it comes on that channel however making another camera with 10.1.1.205 and the other removed was 10.1.1.67 that 205 will load into the NVR if it setup for it in an empty Slot.. In this case I was working with a camera I had setup at 10.0.0.205 in my NVR from the front side, I then made the change on the camera IP to see if it would go to the back side from being on the front while it was connected so only needed to make change to my IP and Gateway and sure enough it came up on CH1 though ch3 while ch3 was connected through my Switch if that made since...
HP POE+ Switch
4108E 10.0.0.224 Front Side IP for NVR
Switch Side of NVR is 10.1.1.1 and cameras started at 10.1.1.65, 66, 67 and so on.. First camera on my NVR was on CH1 but camera came in on front side.. When you plug cable in there (Ch1 Port) it will Pop up say there is a camera there do you want to Replace it I said no plug in different channel port.. Anyway connected in 2, 3, 4, 5, 6 and as I said I had 1 already from the Front.. I removed camera from 3 because it was easy to get to, then plugged cable into Switch, Had camera from 3 now plugged into my Switch and no it wouldn't go in over Front side because wrong range of IP.. So I can access it over my Computer because my computer has multi range of IP and 10.1.1.109 is one of them, So then I took cable from Non POE port of my Switch and plugged into Ch3 of the NVR and Camera that was on my Switch now loaded in.. I logged into the camera that I had on CH1, view its Web UI at 10.0.0.205 and changed it to match backend ip info 10.1.1.205, I then using NVR main menu, camera, and changed the camera that is now Red because the IP in camera for Ch1 I changed so I changed it to 10.1.1.205 and save and it came online... Now I have 2 cameras coming over 1 Cable... So I then wanted to see if there was any delay or lag if I went to log into any of the cameras on the back end and was able to log in the cameras over the Webui of the camera without having any issue of ch3 or ch1 dropping and everything was working fine... Now while doing some Camera work via Camera WebUI from my computer that shares that Range of IP I feel would be ok for a short time to be connected this way.. I wouldn't keep it connected this way and only had it on there maybe 30 min at the most...
There are other ways of setting up my networking and I know this... I have it setup the way I do because If I setup the other way then the IP's off the back side of the NVR when connected could be granted Access to the Internet and the whole reason for me to even have a POE NVR is to have my Camera Secure from a Backdoor that could be in the cameras that couldn't just peek out without me having some type of idea that they are even connected in a way that they could get to the Outside world if there was an issue with the cameras of having backdoors and or hacked and so on and so on.. Keeping my setup keeps me able to keep on eye on my Network and have an idea what comes and goes outside my Network...
PS for all the ones that are going to say wait your 10.1.1.109 isn't listed in your computer IPCONFIG listed above your right and that is because I use a different Computer on my network for that task just keep the 109 in list of my IPs I use so I know it was mine and that is why for the ones that might have seen it not in the picture above... That IP is on my Computer that I have as 10.0.0.139 in my normal Network range...
thanks when i set up my standalone router as 10.1.1.1, i had moved the camera off the nvr and the router wasn't connected to anything else so there wasn't anything it was battling with. so don't know why it didn't work but since i had better alternatives, didn't pursue it further.
however, i have found a far simpler solution doesn't require adding additional ip's. when you first get your camera, make sure it is configured to dhcp. I know the manual says make it static but that doesn't apply for poe nvr's.
when you attach it to the nvr, it sets it's ip to something like 10.1.1.xxx and leave dhcp alone. when if you need to get to the camera interface, connect it to your router or switch that you pc is on, say 192.168.1.xxx. if your switch lacks poe, add in a single port injector. now the camera will get it's ip from the 192.168.1.1 and can easily access it, no additional ip's needed. you can get the camera ip from ipconfig or your routers list of connected devices.
if you want the camera to come up with the same ip when connected directly to the 192.168.1.xxx, you can use your routers reserve ip list. for my router, i could only reserve connected devices. so when the camera connected with dhcp, i changed this to static put in the ip i wanted it to have. then i could add it to the reserved ip list. after i confirmed that i could get to the camera interface with my reserved list ip, i set the camera back to dhcp.
i needed to reboot router and power down/up camera when making changes. i seemed to be getting stale ip's that weren't resolved by refreshing the routers connected device list when i set the camera to have a new ip.
now when connected to the nvr, i don't really care what the ip is as i'm accessing it through the nvr channel. if i need to get directly to the camera interface, connect it to the 192.168.1.xxx network and i access it through the a constant ip set by the routers reserved list.
