I just got this NVR(Running latest Firmware) and I have one existing IP4M-1051W Camera Seems to work fine with a lan connection.
I added a TPLink AP onto the NVR so I could bridge in Wireless Capabilities. The AP works fine but for what ever reason doesn't seem to give out an IP via DHCP to non video camera hosts. The AP just works as a simple hand off. I assigned static addresses and everything works just fine, no DHCP.
If I need to change something on the camera I need to constantly switch the wireless and move the AP. (The camera works on lan and wifi)
Oddly the Camera does connect via the same wifi and connect to the NVR but then I cannot configure anything on the camera as it goes offline. Virtual host is enabled and when I try to click on the web config through the NVR no website comes up. Seems the network configuration is really wonky and lacks some typical features. Firewall is disabled on the NVR.
No DHCP control
No DHCP listing
No basic troubleshooting of ARP or Ping tools or NS Lookup.
I am surprised the Camera manufacturer is not listed for ArmCrest.
The Web Liveview constantly locks up.
Lack of depth of documentation.
As this is a more expensive NVR I would suspect there would be more capabilities on the software. Is there any newer firmware that would have these basic tools available?
NVR5208E
Re: NVR5208E
Hello and Welcome to the forum.
So I am sorry I am having a hard time understanding what your trying to do!
This is an NVR that has 8POE ports and 1 normal Ethernet port. If you connect your camera to your normal network range for the rest of your home devices like computers, TV's, printers, cell phones and other things outside your normal CCTV needs that is normally where a person would connect a Wifi Camera to the normal network. This will give you the ability with Laptop or desktop to make a connection to this camera outside the NVR life as well.
So it would be for others with standard network something like 192.168.1.xxx for the home IP address then with a POE nvr the NVR has an area called Network in it, IN the Network area will be a Tab called Switch. At that point someone could change if they wanted to, however the standard IP of 10.1.1.1 range where the NVR normally hands out IPs starting at 10.1.1.65 and might start out at 10.1.1.128 if once connected before..
Then normally the NVR might have a Virtual Host switch in the Network tab area. This will turn on the ability to connect though the NVR's IP to other cameras that are connected to the POE port of the NVR. However your NVR might be like one of mine in the since that it don't have a Toggle and Virtual Host is just online already like my 4216E-AI NVR... Issue here is that you have to then connect to the NVR's normal network IP and go to the Camera area on the NVR's WebUI click on the E next to the camera you want to make changes to, this will pop up a new tab with in my case something that looks like this. 10.0.0.223:10080 that isn't always the same IP address depending on how many cameras you are trying to config however that is normally the starting port and other machines might have different port range but same idea...
So the NVR will or can hand out Ip addresses to cameras be it Wifi or non POE IP cameras if you were to make a connection from say a switch to the back of the NVR POE port. This issue can be Complex and if not done right your NVR could pass out IP to any device that connects to them. However most times it is looking for IP camera type devices..
Keep in mind that if you were to connect a router to a NVR's POE port you will need 2 cables for a 8ch NVR to work on all 8 channels you will need 1 for ch 1-4 and 1 for 5-8.
However in Truth the best thing is to connect your normal network cable to the NVR's port and do a search for your camera on your normal IP range the NVR will work on 2 ranges POE port range stated above normally 10.1.1.xx and then your normal home range where mine is 10.0.0.xxx so what ever your normal network range is normally where Wifi camera would connect.
About the Amcrest not being listed there is no need because it is an Amcrest NVR and has Special listing of Private and port of 37777 for making a connection. Doing a normal device search will bring up the Device in general as Either Private and or Onvif. Connecting to your 1051 would fall in the Private for device
So I am sorry I am having a hard time understanding what your trying to do!
This is an NVR that has 8POE ports and 1 normal Ethernet port. If you connect your camera to your normal network range for the rest of your home devices like computers, TV's, printers, cell phones and other things outside your normal CCTV needs that is normally where a person would connect a Wifi Camera to the normal network. This will give you the ability with Laptop or desktop to make a connection to this camera outside the NVR life as well.
So it would be for others with standard network something like 192.168.1.xxx for the home IP address then with a POE nvr the NVR has an area called Network in it, IN the Network area will be a Tab called Switch. At that point someone could change if they wanted to, however the standard IP of 10.1.1.1 range where the NVR normally hands out IPs starting at 10.1.1.65 and might start out at 10.1.1.128 if once connected before..
Then normally the NVR might have a Virtual Host switch in the Network tab area. This will turn on the ability to connect though the NVR's IP to other cameras that are connected to the POE port of the NVR. However your NVR might be like one of mine in the since that it don't have a Toggle and Virtual Host is just online already like my 4216E-AI NVR... Issue here is that you have to then connect to the NVR's normal network IP and go to the Camera area on the NVR's WebUI click on the E next to the camera you want to make changes to, this will pop up a new tab with in my case something that looks like this. 10.0.0.223:10080 that isn't always the same IP address depending on how many cameras you are trying to config however that is normally the starting port and other machines might have different port range but same idea...
So the NVR will or can hand out Ip addresses to cameras be it Wifi or non POE IP cameras if you were to make a connection from say a switch to the back of the NVR POE port. This issue can be Complex and if not done right your NVR could pass out IP to any device that connects to them. However most times it is looking for IP camera type devices..
Keep in mind that if you were to connect a router to a NVR's POE port you will need 2 cables for a 8ch NVR to work on all 8 channels you will need 1 for ch 1-4 and 1 for 5-8.
However in Truth the best thing is to connect your normal network cable to the NVR's port and do a search for your camera on your normal IP range the NVR will work on 2 ranges POE port range stated above normally 10.1.1.xx and then your normal home range where mine is 10.0.0.xxx so what ever your normal network range is normally where Wifi camera would connect.
About the Amcrest not being listed there is no need because it is an Amcrest NVR and has Special listing of Private and port of 37777 for making a connection. Doing a normal device search will bring up the Device in general as Either Private and or Onvif. Connecting to your 1051 would fall in the Private for device
Be Safe.
-
SomeCanuck
- Posts: 3
- Joined: Wed Feb 23, 2022 4:01 pm
Re: NVR5208E
Thanks for the response.
For what ever reason even plugging in a computer into the switch in the back of the nvr it doesn't get a dhcp I configure a static ip and scan the network and it doesn't find the camera yet the NVR picks it up. So unfortunately just pluging in my pc into the network on the NVR back pane doesn't result in access to the camera. I need to keep the Wifi on a different network and the wired network is for the NVR.
Oddly the Cameras get dhcp but no computer gets a dhcp (Windows or Linux/Android). Network is default 10.1.1.1
Additionally when I connected the computer to the backpane of the NVR using a static 10.1.1.25 and did basic tests I cannot ping camera 10.1.1.65
Scanning shows nothing but my AP appears just fine my phone connected to the AP with a static shows up.
I tried doing NSLookup/traceroute and nothing. It would appear that the NVR is not passing any traffic what so ever out. Not sure if this is by design but it would explain why I cannot get the web page for the came through web page (extranet or intranet) (port 10080)
Virtual Host doesn't seem to do anything.
There is something really funky going on here with out a smart switch in promiscuous mode I cannot look at the packets.
For what ever reason even plugging in a computer into the switch in the back of the nvr it doesn't get a dhcp I configure a static ip and scan the network and it doesn't find the camera yet the NVR picks it up. So unfortunately just pluging in my pc into the network on the NVR back pane doesn't result in access to the camera. I need to keep the Wifi on a different network and the wired network is for the NVR.
Oddly the Cameras get dhcp but no computer gets a dhcp (Windows or Linux/Android). Network is default 10.1.1.1
Additionally when I connected the computer to the backpane of the NVR using a static 10.1.1.25 and did basic tests I cannot ping camera 10.1.1.65
Scanning shows nothing but my AP appears just fine my phone connected to the AP with a static shows up.
I tried doing NSLookup/traceroute and nothing. It would appear that the NVR is not passing any traffic what so ever out. Not sure if this is by design but it would explain why I cannot get the web page for the came through web page (extranet or intranet) (port 10080)
Virtual Host doesn't seem to do anything.
There is something really funky going on here with out a smart switch in promiscuous mode I cannot look at the packets.
Re: NVR5208E
Here is some things I would do..
First setup IP on Laptop or Desktop with static ip of 10.1.1.129
Then if your camera is connected to port 1-4 then you need to connect your crossover cable from your desktop in one of the other 3 ports same for if you are connected from 5-8 connect the computer on one of the other 3. The 4 ports are connected so connecting to port 8 and camera on port 1 you won't find it
First setup IP on Laptop or Desktop with static ip of 10.1.1.129
Then if your camera is connected to port 1-4 then you need to connect your crossover cable from your desktop in one of the other 3 ports same for if you are connected from 5-8 connect the computer on one of the other 3. The 4 ports are connected so connecting to port 8 and camera on port 1 you won't find it
Be Safe.
-
SomeCanuck
- Posts: 3
- Joined: Wed Feb 23, 2022 4:01 pm
Re: NVR5208E
I did what you had recommended and nothing. Got frustrated and put a dumb switch on port one and plugged all the equipment into it and everything started working. I can ping and access all the equipment including the cameras.
The bottom line the switch in this device is BROKEN (networking) as no communication can happen per port.. Its performing a per port blocking.
Virtual Host doesn't work either.
Can you please release a firmware to address this problem? or do I have a broken unit and need RMA?
The bottom line the switch in this device is BROKEN (networking) as no communication can happen per port.. Its performing a per port blocking.
Virtual Host doesn't work either.
Can you please release a firmware to address this problem? or do I have a broken unit and need RMA?
Re: NVR5208E
Sorry to hear your troubles.. Just so I understand better because one your saying that your connected to port one and then your saying your NVR POE has no networking?
So I will try and point this as painless as I can. Networking port I will refer to Front Side and Ports 1-8 I call Port1-Port8
First, POE ports will only work with Amcrest or Dahua type POE devices Port1-Port8 Normally
Second I don't own the 5208E so I am going off the Devices that I do Own. 2108E-HS, 3108E-P4, 4108E-HS, 4116E-HS, 4108E, 4216E-AI and everyone of them work the same. Now only one I have with Built in Power Supply is my 4216E-AI all others besides the 3108E-4P all have 48v power supply the 3108E has 2 power supplies one 12v and 1 48v, If I want to use that one with only non POE cameras I can by using the 12v power even connecting 1051W to my Port1, and 941B to port 2 and so on. If I want POE cameras I have to use the 48v power along with the 12v to run the system..
Now there might be an issue if your NVR is with only 48v power where the NVR is getting less then the 48v then no other POE will work because the power supply isn't working to specs.
Then if your NVR is like my 4216E-AI and has built in power supply it might be that the POE power is either disconnected inside or the power supply isn't good and not powering the POE ports..
Then Front side port is for your normal network It might be that it is close to your POE ports or like my 4216E and is off to the right next to the USB port, That port is for normal network traffic and Wifi type or Non POE IP cameras and would have a different IP address... In my case 10.0.0.xxx then the NVR switch from Reset or new install is setup with 10.1.1.xxx and normally starts at port1 with 10.1.1.65 but can start also at 10.1.1.128 if it likes to be difficult,
Looking at the NVR's GUI, When you connect a Camera that is Dahua or Amcrest to teh POE ports they will come online your NVR's GUI under Camera, Remote Device. Top is listing for search and bottom box is ones that are loaded and or on Port 1-8..
So if you take a Camera, lets say your 1051 from your first post here, Take a wire from camera and plug into port1, the NVR should give that camera a IP address of something like 10.1.1.xx if you have not changed it. What happens next is that connection will not be an AUTO connection unless your camera is Fresh install (No new Password) the NVR starts out with admin admin, If there is a different password, you will need to from NVR's GUI, Right click, Main menu, (Log in if you have to) then Camera, Remote Device, Bottom box list of cameras should have red dot, click pencil and change the password to the one you have in camera, click save and after a little few seconds that red dot should go green...
Now normally for my system to work. if I was looking to use non POE, I can put 1 cable to port1 and load 4 cameras using IP address in the 10.1.1.xx range. If I try to connect a 5th it won't let me so I connect another cable in Port5 and now I can again add 4 more cameras if I choose to. However if I want to use all 16ch of lets say me 4216E that has 16ch POE I can do so without attaching any cables to port1-16 and only connect 1 cable to my normal network port. This will have all cameras with ip addresses in the 10.0.0.xxx range only if I try to connet to that port with 10.1.1.xxx range it won't work on any of my other NVRS' (it does on my 4216E-AI) think that was a flaw However they don't last longer then 24 hours using front side with PORT IP range..
I personally have not been able to connect any Hikvision IP camera that I own to my Amcrest POE ports and have the cameras work. I have to add them to my switch and either use my Front side IP range or if I want I can use my Managed Switch to forward that port of the camera to a port that I connect to my NVR and it would see it as a normal camera connected that way it just won't connect with Camera connected to a PORT1-16 on it's own even if I setup the camera with a 10.1.1.xx range IP it won't be found like the Amcrest or Dahua cameras will..
Can you upload some pictures of your NVR's Camera/Remote device window.. It would look like this below. Mine is from a Direct Screen Capture you can be a picture either way I am clearing some of my SN.. You can see the one that shows PORT16 is connected to POE port 16 direct the rest are connected over my normal network IP range..
So I will try and point this as painless as I can. Networking port I will refer to Front Side and Ports 1-8 I call Port1-Port8
First, POE ports will only work with Amcrest or Dahua type POE devices Port1-Port8 Normally
Second I don't own the 5208E so I am going off the Devices that I do Own. 2108E-HS, 3108E-P4, 4108E-HS, 4116E-HS, 4108E, 4216E-AI and everyone of them work the same. Now only one I have with Built in Power Supply is my 4216E-AI all others besides the 3108E-4P all have 48v power supply the 3108E has 2 power supplies one 12v and 1 48v, If I want to use that one with only non POE cameras I can by using the 12v power even connecting 1051W to my Port1, and 941B to port 2 and so on. If I want POE cameras I have to use the 48v power along with the 12v to run the system..
Now there might be an issue if your NVR is with only 48v power where the NVR is getting less then the 48v then no other POE will work because the power supply isn't working to specs.
Then if your NVR is like my 4216E-AI and has built in power supply it might be that the POE power is either disconnected inside or the power supply isn't good and not powering the POE ports..
Then Front side port is for your normal network It might be that it is close to your POE ports or like my 4216E and is off to the right next to the USB port, That port is for normal network traffic and Wifi type or Non POE IP cameras and would have a different IP address... In my case 10.0.0.xxx then the NVR switch from Reset or new install is setup with 10.1.1.xxx and normally starts at port1 with 10.1.1.65 but can start also at 10.1.1.128 if it likes to be difficult,
Looking at the NVR's GUI, When you connect a Camera that is Dahua or Amcrest to teh POE ports they will come online your NVR's GUI under Camera, Remote Device. Top is listing for search and bottom box is ones that are loaded and or on Port 1-8..
So if you take a Camera, lets say your 1051 from your first post here, Take a wire from camera and plug into port1, the NVR should give that camera a IP address of something like 10.1.1.xx if you have not changed it. What happens next is that connection will not be an AUTO connection unless your camera is Fresh install (No new Password) the NVR starts out with admin admin, If there is a different password, you will need to from NVR's GUI, Right click, Main menu, (Log in if you have to) then Camera, Remote Device, Bottom box list of cameras should have red dot, click pencil and change the password to the one you have in camera, click save and after a little few seconds that red dot should go green...
Now normally for my system to work. if I was looking to use non POE, I can put 1 cable to port1 and load 4 cameras using IP address in the 10.1.1.xx range. If I try to connect a 5th it won't let me so I connect another cable in Port5 and now I can again add 4 more cameras if I choose to. However if I want to use all 16ch of lets say me 4216E that has 16ch POE I can do so without attaching any cables to port1-16 and only connect 1 cable to my normal network port. This will have all cameras with ip addresses in the 10.0.0.xxx range only if I try to connet to that port with 10.1.1.xxx range it won't work on any of my other NVRS' (it does on my 4216E-AI) think that was a flaw However they don't last longer then 24 hours using front side with PORT IP range..
I personally have not been able to connect any Hikvision IP camera that I own to my Amcrest POE ports and have the cameras work. I have to add them to my switch and either use my Front side IP range or if I want I can use my Managed Switch to forward that port of the camera to a port that I connect to my NVR and it would see it as a normal camera connected that way it just won't connect with Camera connected to a PORT1-16 on it's own even if I setup the camera with a 10.1.1.xx range IP it won't be found like the Amcrest or Dahua cameras will..
Can you upload some pictures of your NVR's Camera/Remote device window.. It would look like this below. Mine is from a Direct Screen Capture you can be a picture either way I am clearing some of my SN.. You can see the one that shows PORT16 is connected to POE port 16 direct the rest are connected over my normal network IP range..
- Screenshot (2185).png (319.13 KiB) Viewed 1658 times
Be Safe.
Re: NVR5208E
So that is the 4216E-AI above, here is a picture of another 8ch POE with older FW incase your system looks like this on the WebUI. I am showing the WebUI as an area that you would click the e to access the cameras WebUI... Please note that only 1 of the 2 cameras connected to POE is really a POE camera the other is a 841W IP/Wifi camera that has a cable from the camera to the Listed Port on the NVR.. Please notice in the second picture that is what I was talking about when you do a Connection with your NVR's WebUI, Then click that e and it will be the IP of the NVR with a Port number that you can see in the second picture...
- Screenshot (2186).png (166.22 KiB) Viewed 1656 times
- Screenshot (2187).png (398.14 KiB) Viewed 1656 times
Be Safe.
Re: NVR5208E
Ok So I have done some testing of my Devices
2108E-HS is Remote and my Son was there, On a Zoom call with him I conducted the test though him, Connection Port 8 was able to ping all cameras 1-8 on the device (This using older FW like last picture posted above, not 4.0)
3108E is only 4 port and plugged in I can scan the cameras connected.
4108E-hs forgot to run test before Installing 4.0 and with 4.0 plugged in 8 can see only 5-8 plugged in 4 can only see 1-4 (Also shows IP for NVR)
4116E-HS 4.0fw same results as above can see NVR IP in normal range 10.0.0.xxx and cameras on ports of 4 blocks. nothing else...
Here is where I think your 5208E is at the same spot my 4216E-AI is..
Connecting my computer to the NVR and doing a port scan in any of the 16ch ports has a Result of 0 ip of devices that are connected in any of the blocks. it also don't show my NVR IP either..
However as stated above with Pictures, Once you connect and setup cameras on your NVR with good Passwords and are connected to NVR for Preview and what not. Once you make a WebUI connection to the NVR (NOT Able to access using NVR GUI) WebUI access as pictures above show click on the e next to the camera that is connected to your NVR's POE port will open a Port to access that camera for accessing camera data it will be like the NVR's IP with /10080
The picture below I don't think is something that is needed with your 5208E however if it is something that was present in the FW your using seeing I don't know what VER is current in your NVR it might be that you need to turn on Virtual Host. That isn't something I have to do in my 4216E-AI however have it in my 4116E-HS and 4108E-HS so I wanted to cover as much as I could incase it is needed in yours as well..
2108E-HS is Remote and my Son was there, On a Zoom call with him I conducted the test though him, Connection Port 8 was able to ping all cameras 1-8 on the device (This using older FW like last picture posted above, not 4.0)
3108E is only 4 port and plugged in I can scan the cameras connected.
4108E-hs forgot to run test before Installing 4.0 and with 4.0 plugged in 8 can see only 5-8 plugged in 4 can only see 1-4 (Also shows IP for NVR)
4116E-HS 4.0fw same results as above can see NVR IP in normal range 10.0.0.xxx and cameras on ports of 4 blocks. nothing else...
Here is where I think your 5208E is at the same spot my 4216E-AI is..
Connecting my computer to the NVR and doing a port scan in any of the 16ch ports has a Result of 0 ip of devices that are connected in any of the blocks. it also don't show my NVR IP either..
However as stated above with Pictures, Once you connect and setup cameras on your NVR with good Passwords and are connected to NVR for Preview and what not. Once you make a WebUI connection to the NVR (NOT Able to access using NVR GUI) WebUI access as pictures above show click on the e next to the camera that is connected to your NVR's POE port will open a Port to access that camera for accessing camera data it will be like the NVR's IP with /10080
The picture below I don't think is something that is needed with your 5208E however if it is something that was present in the FW your using seeing I don't know what VER is current in your NVR it might be that you need to turn on Virtual Host. That isn't something I have to do in my 4216E-AI however have it in my 4116E-HS and 4108E-HS so I wanted to cover as much as I could incase it is needed in yours as well..
- Screenshot (2188).png (79.39 KiB) Viewed 1651 times
Be Safe.