My first attempts have failed..

J

jerome8283

n3wb
Sep 28, 2015
29
0
I recently purchased 2 DS-2CD2332-1 cameras and a DS-7608NI-E2/8P.

I've been trying to get a few things working...


  1. Access the camera from my iPhone while away from my home, not connected to my local network.
  2. Send myself an email when motion is detected within the area I defined, with a copy of the image attached
  3. Send myself an email based on line crossing/intrusion detection I defined, with a copy of the image attached
  4. Send emails from the camera. Sending from the NVR works.

My NVR is setup on my local network, 192.168.1.13 and my camera are on .254

If anyone can offer instructions or a post to follow that would be great.

ok, they're not really my first attempts :)
 
Last edited by a moderator:
You can't access the camera directly while it's on the NVR POE ports unless you have virtual host or 'mod' it. The camera's can't see the internet this way.

You can do the email motion detection on the NVR itself.

You need to port forward the correct ports for it to work outside the network. If you have a dynamic IP address you will need to use a DDNS service.

If you search these forums, all these have been answered with great detail.
 
Michelin Man said:
You can't access the camera directly while it's on the NVR POE ports unless you have virtual host or 'mod' it. The camera's can't see the internet this way.

You can do the email motion detection on the NVR itself.

You need to port forward the correct ports for it to work outside the network. If you have a dynamic IP address you will need to use a DDNS service.

If you search these forums, all these have been answered with great detail.
Click to expand...


I have Virtual Host and can access the camera. This is not an issue.

Email motion works from the NVR but I'd like to receive emails for line crossing/intrusion detection and these settings are only available via the camera's interface but I cannot get mail to work from the camera's interface.

So I need to do port forward and DDNS?

Thanks for your response.
 
Last edited by a moderator:
Emails don't work because as I stated the cameras can't 'see' the internet from where they are.

Fenderman/Del Boy/alastairstevenson may be able to answer the email from camera part.

You need to port forward, to see the NVR, in which with virtual host then you can see the cameras. If you have a static ip you don't need DDNS, if you have a dynamic ip address then you will as the ip address will change.
 
but I cannot get mail to work from the camera's interface.
Click to expand...
When the camera is on the separate network segment that the PoE ports use, by default it's traffic will not reach the internet. You need routing information and name resolution for that to work.
I would guess that if you set an internet time source (eg time.windows.com) in the camera config, the 'test' button will show failure.

As you already have 'Virtual Host' working OK, there are just a couple of things you need to do to make this work. These things will enable network routing to work properly to and from the camera, and add name resolution:

In the camera web GUI, set the IP address of the NVR PoE interface as its default gateway. The default value for this is '192.168.254.1'
In the camera web GUI, set a valid entry for DNS. This is necessary for mail server name resolution. Usually the DNS setting would be the IP address of your router, '192.168.1.1' but it does seem to be the case that Hikvision cameras work better with '8.8.8.8'
You should probably reboot the camera and confirm the settings hold OK.
And lastly - this is the trickiest as it depends on your specific router model - you must add a permanent, private static route so that your router/gateway knows how to route traffic to and from the camera.
Assuming the default values for the PoE interface, the values you need for the 'static route configuration' in your router are:
Destination network 192.168.254.0 (yes, it's a zero), subnet mask 255.255.255.0, gateway 192.168.1.13 (ie your NVR LAN address) and some metric such as 2.

And you can test with the time source button.

*edit* Oh, and by the way, for what is an 'outbound' connection from the camera to an internet mail server, there is no requirement for port forwarding or DDNS.
 
  • Like
Reactions: aster1x, Michelin Man, fenderman and 3 others
This probably works what alastairstevenson describes, but I did not want to deal with separate subnets. In my case I got it work all in the same subnet, might be fluke, but it works. I don't even bother with .254. Simply in the initial wizard set the nic ip to be in the same subnet. The downside while this works with NVR and cameras on the same subnet, I cannot access NVR remotely, only cams are accessible.
 
tate16t said:
No backing out now! You are now considered an expert and must answer all questions via this thread anyway! :)
Click to expand...
Expert at spending money on more cameras than I could possibly need, that's for sure!

I have experienced it too where if the NVR is say 192.168.1.14, then setting the cameras to 192.168.1.100, 101, 102, 103 etc has allowed me to access them. I prefer to have the cameras inaccessible though.
 
Del Boy said:
I have experienced it too where if the NVR is say 192.168.1.14, then setting the cameras to 192.168.1.100, 101, 102, 103 etc has allowed me to access them. I prefer to have the cameras inaccessible though.
Click to expand...

It's probably a bug though, because you cannot change to the same subnet in the configuration menu, it lets you do that only in the wizard and lan cable needs to be connected to one of the poe ports.
A
 
alastairstevenson said:
When the camera is on the separate network segment that the PoE ports use, by default it's traffic will not reach the internet. You need routing information and name resolution for that to work.
I would guess that if you set an internet time source (eg time.windows.com) in the camera config, the 'test' button will show failure.

As you already have 'Virtual Host' working OK, there are just a couple of things you need to do to make this work. These things will enable network routing to work properly to and from the camera, and add name resolution:

In the camera web GUI, set the IP address of the NVR PoE interface as its default gateway. The default value for this is '192.168.254.1'
In the camera web GUI, set a valid entry for DNS. This is necessary for mail server name resolution. Usually the DNS setting would be the IP address of your router, '192.168.1.1' but it does seem to be the case that Hikvision cameras work better with '8.8.8.8'
You should probably reboot the camera and confirm the settings hold OK.
And lastly - this is the trickiest as it depends on your specific router model - you must add a permanent, private static route so that your router/gateway knows how to route traffic to and from the camera.
Assuming the default values for the PoE interface, the values you need for the 'static route configuration' in your router are:
Destination network 192.168.254.0 (yes, it's a zero), subnet mask 255.255.255.0, gateway 192.168.1.13 (ie your NVR LAN address) and some metric such as 2.

And you can test with the time source button.

*edit* Oh, and by the way, for what is an 'outbound' connection from the camera to an internet mail server, there is no requirement for port forwarding or DDNS.
Click to expand...

I will try your suggestions thanks for this!
 
alastairstevenson said:
I would guess that if you set an internet time source (eg time.windows.com) in the camera config, the 'test' button will show failure. -- get a failure when testing mail now without the time source. I believe the error was 'Failed to connect to server'.

In the camera web GUI, set the IP address of the NVR PoE interface as its default gateway. The default value for this is '192.168.254.1' -- I'm sure I tried this as well. Will take another look at it.

In the camera web GUI, set a valid entry for DNS. This is necessary for mail server name resolution. Usually the DNS setting would be the IP address of your router, '192.168.1.1' but it does seem to be the case that Hikvision cameras work better with '8.8.8.8' -- I tried both DNS entries, '192.168.1.1' and '8.8.8.8' with no success.

You should probably reboot the camera and confirm the settings hold OK.

And lastly - this is the trickiest as it depends on your specific router model - you must add a permanent, private static route so that your router/gateway knows how to route traffic to and from the camera.
Assuming the default values for the PoE interface, the values you need for the 'static route configuration' in your router are:
Destination network 192.168.254.0 (yes, it's a zero), subnet mask 255.255.255.0, gateway 192.168.1.13 (ie your NVR LAN address) and some metric such as 2. -- i will try this. What does the metric 2 represent?

And you can test with the time source button.

*edit* Oh, and by the way, for what is an 'outbound' connection from the camera to an internet mail server, there is no requirement for port forwarding or DDNS.
Click to expand...
-- I may also want to access the camera from the internet so I guess port forwarded would be required? I will think on this requirement. If I get the email with attachment there may not be a need to access the camera in the manner.



 
Last edited by a moderator:
Just to confirm, are you saying via the camera GUI to set the default gateway to 192.168.1.13 which is my NVR?

It's still not working. The only setting I did not have or try previuosly was the router setting. I set it as you suggested, Destination network 192.168.254.0 (yes, it's a zero), subnet mask 255.255.255.0, gateway 192.168.1.13 (ie your NVR LAN address) and some metric such as 2.

 
Just to confirm, are you saying via the camera GUI to set the default gateway to 192.168.1.13 which is my NVR?
Click to expand...
No - the camera default gateway must be 192.168.254.1
In the camera web GUI, set the IP address of the NVR PoE interface as its default gateway. The default value for this is '192.168.254.1'
Click to expand...

It's still not working. The only setting I did not have or try previuosly was the router setting. I set it as you suggested, Destination network 192.168.254.0 (yes, it's a zero), subnet mask 255.255.255.0, gateway 192.168.1.13 (ie your NVR LAN address) and some metric such as 2
Click to expand...
As a test to see if you have it all set up and working, at the PC command line
ping 192.168.1.13 That's your NVR LAN interface.
ping 192.168.254.1 That's your NVR PoE interface.
ping 192.168.254.x where x is the IP address of the PoE-connected camera
And check out the output from this:
tracert 192.168.254.1
It should look like this:
I:\Users\Alastair>tracert 192.168.254.1
Tracing route to 192.168.254.1 over a maximum of 30 hops
1 1 ms 1 ms <1 ms 192.168.1.1
2 <1 ms 1 ms <1 ms 192.168.254.1
Trace complete.
Click to expand...
 
All pings are successful. The trace looks good.


C:\>tracert 192.168.254.1

Tracing route to 192.168.254.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 192.168.254.1
Trace complete.
 
I can confirm that Alastair's instructions all work OK (my camera 2332 with fw 5.1.6 on the PoE of a 7604NI/SEP with fw 3.0.9).
One recommendation is avoid time.windows.com. I does not wok properly evn in my windows computers. Try alternative NTPs like time.nist.gov
 
You must log in or register to reply here.
Top Bottom