Gmail Setup .... "Test" Fails

[pbc]

Okay...changing the subnet worked. Changed it to 255.255.255.0, then selected SSL and port 587 and I got a "testing succeeded". Progress!

So next to figure out how to get the cameras themselves to send out emails on event triggers, as my NVR records continuously, and I don't want to go searching like crazy for footage. Cameras are set to record to SD card on trigger.

 

[pbc]

...odd as I didn't think Google supported SSL anymore??

 

[pbc]

So a couple things, seems I'm getting a "IP Conflict" issue in my NVR. But don't seem to see any conflicts in my router. Not sure if it's related to the changes I made above.

Second, there's been an increase in breakins in my area, so I want to start setting up the email motion alerts, but my cams are connected to my NVR (would like to keep it that way if at all possible vs buying another POE switch).

I see this thread, but curious if there is a "dummies guide" somewhere to this as it's a bit confusing for me!

How to get Hikvision camera connected to POE ports of Hikvision NVR to access WAN (WWW) ?

 

[58chev]

If your cameras are getting out to the internet, these two pages are all you need.

 

[alastairstevenson]

I see this thread, but curious if there is a "dummies guide" somewhere to this as it's a bit confusing for me!

This is what you need as the way to gain normal access to cameras connected to NVR POE ports, and for them to access the internet to send email etc ...

3 things needed -
Virtual Host enabled on the NVR.
Cameras must have the NVR PoE interface as the default gateway, usually 192.168.254.1 To do this you'll need to have the PoE channel in manual mode to stop the NVR changing the gateway back to an unsuitable value.
And in order to tell your network that packets for the cameras need to be directed through the NVR LAN interface, you will need to add a static route in your router/gateway, something like -
For network 192.168.254.0/24 (ie subnet mask 255.255.255.0) use <Your_NVR_LAN_interface_IP_address> as gateway.
Then the cameras can access the LAN (eg for a NAS) and also the internet.

 

[pbc]

So virtual host is enabled, not sure how to do the other two..

 

[pbc]

Looked at my NVR web interface, can't find any settings for the POE channel?

 

[alastairstevenson]

Looked at my NVR web interface, can't find any settings for the POE channel?

Example, under Camera Management, Select the channel in question, Modify, Adding Method :

 

[pbc]

Perfect, thank you. Also noticed the IP Conflict there as I had two cameras set to 198.168.254.3 for some reason.

Now to try and figure out the router setting thing.

While I'm at it, right now I have port 8000 for the NVR. Should I be selecting a different port?

 

[alastairstevenson]

No reason to change ports away from the defaults.

 

[pbc]

Hmm...just checked my ivms-4500, only shows my first camera after I changed to "manual". Curious why that would be?

 

[pbc]

Just following up, any idea why ivms-4500 only presents the first camera ever since I switched from plug and play to manual on the NVR? I have it setup via a DDNS service if that matters.

 

[alastairstevenson]

Sorry, I've no idea - I've never used iVMS-4500.

 

[pbc]

It's definitely the manual setting vs plug and play. Just reset one camera to plug and play and it shows up in ivms-4500.

What mobile app do you use?

 

[alastairstevenson]

What mobile app do you use?

I don't use any mobile app.

 

[pbc]

Aha...something is off. When I switch my cameras to manual, I just noticed in "Status" in the camera management page it shows up as "Offline (Network abnormal)" instead of online? So the first camera in the list shows up as "Active", but the rest show up as "Offline (Network abnormal)".

Is that because I still have to do this in my router? "And in order to tell your network that packets for the cameras need to be directed through the NVR LAN interface, you will need to add a static route in your router/gateway, something like -
For network 192.168.254.0/24 (ie subnet mask 255.255.255.0) use <Your_NVR_LAN_interface_IP_address> as gateway.
Then the cameras can access the LAN (eg for a NAS) and also the internet."

 

[pbc]

Tried that, not sure if I set it up in my netgear router properly as it still doesn't work. Here are my NVR network settings again:

IPv4: 192.168.1.21 (my NVR)
Subnet: 255.255.255.0
Default Gateway: 192.168.1.1 (my routers main address)

On my router for the route I have:

Private unchecked
Active Checked

Desination IP Address: 192.168.1.254.0
IP Subnet Mask: 255.255.255.0
Gateway IP: 192.168.1.21

Anything look off?

 

[pbc]

Hmmm...can we no longer upload images on this site? I only get a URL option now, no option to choose from PC.

 

[alastairstevenson]

Is that because I still have to do this in my router?

No, operating the NVR PoE channel in Manual mode has no dependency on the router settings.

Remember - the reason for switching the NVR PoE channel to Manual instead of Plug&Play is to stop the NVR from automatically putting the camera default gateway back to the default gateway used on the NVR LAN interface (ie 192.168.1.1) after you have set the camera default gateway to the IP address of the NVR PoE interface (ie 192.168.254.1).
If you haven't done that yet, it could be why you get a 'network abnormal' error.

Desination IP Address: 192.168.1.254.0
IP Subnet Mask: 255.255.255.0
Gateway IP: 192.168.1.21

That should be OK - if you mean 192.168.254.0 for the network.
I don't recall if the static route needs to be 'private'.
You can prove it works using at a Windows command prompt
tracert 192.168.254.1
and check it lists the NVR LAN interface IP address in the route.

 

[pbc]

Yes, that's what I meant. All the tracert 192.168.254.1 command did was return 192.168.254.1.