Hikvision 4g Router
Destini Armstrong
I need some advice on how to proceed. My Hikvision security camera has been working very well for the past year. It was connected to my computer via a Linksys router with an ip address of 192.168.1.67.
Unfortunately I had to replace my router. The new router can not "see" the Hikvision camera. I think this is because the new router uses a different internal ip address system. IP addresses are in the form of "192.168.10.xxx" instead of the old "192.168.1.xxx" form. I have been unable to figure out how to change the camera's ip address to be viewable on the new router. The SADP app in Windows does not recognize the camera. The IVMS 4200 app on my Mac does not see the camera.
I was able to reconnect my old router (the one with the 192.168.1.xx addresses) and I have no trouble viewing the camera and opening the web configuration pages. I see that there is a way to change the ip address inside the configuration tab. I'm wondering if this is safe to do. I'm afraid that if I change the ip address to something in the new router's range (192.168.10.xxx) that I might lose all connection with the camera altogether. If that happens how do I recover the ability to connect to the camera?
You can go into your routers settings and change the IP address of the router back to 192.168.1.1 and set the starting IP address to 192.168.1.100. But once you set the IP of the router to 192.168.1.1, it will automatically start the IPs at .100+ . If you have the newest GUI of the Linksys, you should be able to go to Connectivity--> Local Internet and change the Routers IP to 192.168.1.1.
Connect the NVR/DVR back to the old router, log into the NVR/DVR and set the IP to DHCP so it can pick up an IP that the Router gives. Or just Connect it the old router and change the IP to a static one that is 192.168.10.x and then unplug it and plug it back in the new router and try to log into it with the new IP you just gave it.
Now, as an aside, I will tell you why I was so anxious in doing this. The whole reason I needed the new router in the first place is that I had just bricked my perfectly fine Asus RT-N16 router trying to update the Tomato firmware. I struggled with it for two days unsuccessfully trying to recover it to a usable state. The idea of doing the same thing to my Hikvision camera haunted me.
My ISP sent me an updated router. I have installed the router, and I can view my Hikvision cameras through the IVMS-4200 PC software. But I cannot view them via the IVMS-4500 app on my iphone or ipad.
I suppose you access your DVR from PC using local IP address (192.168.xxx.yyy) so it's accessible in local network, but for internet access you probably need to forward some ports on your router or use P2P Cloud connection. For more extensive answer I need more information about your system.
And typically, for the first time, I now have a real need to view my CCTV. Overnight my nvr emailed pictures of someone hanging around my front door and driveway at 1:40am, so I am now very keen to get this working and see the footage!!
I just purchased a TP Link Archer VR2100v to replace my failing Netcomm NF18ACV. The TP Link is failing to assign reserved DHCP addresses to 4 of my 5 HIKVISION cameras. Has anyone else had problems with this model of router and DHCP address reservation?
The TP Link system log shows that the cameras are sending DISCOVER broadcasts and the TP Link seems to be sending an OFFER response with the correct IP address but the cameras never acquire the address.
Most cellular network operators provide connectivity over carrier grade NAT. This means that the IP address that gets allocated to the cellular WAN of the BR1 is actually a private address that is not directly accessible over the internet.
Outbound traffic from devices on the LAN of the BR1 works fine because the traffic goes over the private address space and breaks out to the internet via the operators NAT gateway/router. However when you try and access the BR1 using any identified public IP address, that inbound traffic will get blocked by the operator.
The most common way to get remote access is to host a VPN server in the cloud on a public IP and connect your BR1 Minis to that. You can then connect your phone via VPN to the same VPN server and access the LAN devices on the remote BR1s.
Alternatively you can look for a cellular service that offers public IP addressing (normally more expensive than the usual dynamic private addressing). When each BR1 mini has a statuc public IP you will be able to port forward inbound traffic from that IP to LAN side devices,
I always host a cloud based VPN server for this kind of requirement (I use a combination of Peplinks FusionHub and other 3rd party VPN servers), because I hate the extra cost of fixed public IPs and the inherant risks of having cellular devices directly accessible over the internet.
Hi Martin,
Thank you for your help but Rogers gave me a static ip after explaining them what i wanted to do. Now what do i need to do to be able to see my camera remotely?
The router already changed the ip and apn by itself.
Sorry for this long message, but my knowledge on this is pretty limited. I was wondering if anything has changed regarding the recommended methods described here to remotely access a Hikvision NVR via a Max BR1 Mini? Our group was about to go spend $500 for the static IP from Verizon with port forwarding, but then saw this thread. This is just for a single remote installation but it would be accessed from multiple remote sites. We do not currently have a cloud VPN, so if we went with the VPN method I think we would have to purchase it using AWS or another provider. I also saw something in another thread that firmware 8.0 (beta) has an OpenVPN option, so not sure if that changes things. I am not very familiar with using L2TP and we only have the one Max BR1 Mini, but can any router be configured to the access via L2TP and would it require a router at each user access location? Thanks
So I think the static IP with port forwarding is probably the simplest solution even though there may be some security risks. Note Verizon is running low on IPv4 addresses and asked if the device could use an IPv6 address, but I understand we need an IPv4.
I would like to give the FusionHub (solo) and PepVPN configuration a try since it is more secure. Since the BR1-Mini is remotely accessed via Verizon 4G LTE, do I need the static-ip or do I need a DDNS solution or neither?
I see Fusionhub is supported on Amazon Web Services, Google Cloud Engine, Microsoft Azure and Vultr. So if I went with AWS, I think it requires AWS EC2. This appears to have a free 12-month trial. So would that be the way to go?
Hikvision DS-3WR12GC is a dual-band Wi-Fi router designed by Hikvision. You can easily deploy, monitor and expand your home Wi-Fi network anytime and anywhere. DS3WR12GC comes equipped with dual-band coverage, which can offer a smooth online game and 4K video experience. Powered with beamforming technology, DS3WR12GC ensures excellent high-speed Wi-Fi coverage in every corner at home.
This article is aimed at providing configuration examples for using RUT routers and Hikvision cameras in tandem. All examples provided in this article are intended to be used with any RUT routers (with the exception of RUT850) and Hikvision's DS-2CD2332-I cameras. Although this guide was created with these specific products in mind, the examples from this chapter can still be applied to other Hikvision cameras as well as other cameras in general, although there may be differences in the user interfaces of these other products, the principles should remain the same.
You can configure the camera by connecting to it's Web User Interface (WebUI) via a web browser. To reach the camera's WebUI, you'll need to be aware of and able to reach the camera's IP address. The Hikvision DS-2CD2332-I camera has a Static IP address (a fact that is also true for most IP cameras), which means that it will not "ask" for a DHCP lease when connected to a device that has an operational DHCP Server. Therefore, whether you connect it to your PC or RUT router, the PC or the router will have to be in the same Subnetwork (subnet) as the camera for you to be able to reach it from your local network.
Otherwise, if you have made changes to the router's LAN IP address or if you are simply trying to reach the camera by connecting it directly to your PCs Ethernet board, you will need to make some changes to the router's or PC's network settings.
As mentioned earlier, since the camera's IP address is in the first subnet, you will need to modify the router's IP address (only if you've made changes to router's default IP address before!) so that it is also in the same subnet (at least temporarily; later you can change the camera's IP address to correspond with your router's).
Even though this guide focuses on setup that involves the camera being connected to one of the router's LAN ports, we recognize that some users may be configuring their camera separately by connecting it to a PC. Therefore, this section will provide a short guide on how to do this.
If you are connecting the camera straight to your PC's Ethernet board, you will need to configure a Static IP address on your computer. Since the camera's IP address (192.168.1.64), the computer's IP address must be in the first subnet as well. Presented below are links to two short guides on how to configure a Static IP address on a PC - one for Windows, the other for Linux.
Abide to the provided description and choose a valid password for the camera. If you've logged in to the camera before, you probably already have a password. In that case, just type in the user name (default: admin), the password (the one you chose during first log in) and click "Login".
FINAL NOTE: as you can see, once you add the new rule, it is already enabled and ready for use. From this point no more additional configurations are required, as your remote camera monitoring configuration is fully set up. Unless you want to set up Dynamic DNS for your router, you can skip to the Testing the set up part of this guide.
4a15465005