dannieboiz
Getting the hang of it
- Joined
- May 13, 2015
- Messages
- 491
- Reaction score
- 71
I have a DS7108 that doesn't have the "Virtual Host" feature. Has anyone figured out how to get email alerts working on the camera w/o the virtual host?
Email alerts not working when Hikvision cameras connected to DS-7608NI-E2/8P
- Thread starter butwhy
- Start date
So after it working flawlessly for the last year +, all of a sudden my cameras can no longer send emails. On testing it says "cannot connect to server". Nothing has changed, no firmware updates / network changes etc. I've checked all network settings / email addresses / passwords etc. I'm using Gmail for sending / receiving with a separate email address for every camera. Some were full, so I've emptied them out.
Has anyone else noticed this and any suggestions on how to solve it? Cameras are still working / Hikvision DDNS still working etc.
1x DS-2CD2332-I2 v5.2.5 Build 141201
6x DS-2CD2232-I5 v5.2.5 Build 141201
DS-7608NI-E2/8P v3.3.1 with virtual host enabled.
I'm able to access each camera from my LAN.
Thanks
Has anyone else noticed this and any suggestions on how to solve it? Cameras are still working / Hikvision DDNS still working etc.
1x DS-2CD2332-I2 v5.2.5 Build 141201
6x DS-2CD2232-I5 v5.2.5 Build 141201
DS-7608NI-E2/8P v3.3.1 with virtual host enabled.
I'm able to access each camera from my LAN.
Thanks
Sadly this has been an issue on and off. Most recently it stopped working mid June and then restarted again a week later. It just again stopped working for me so I got fed up and went back to yandex which seems to be working. Basically it's an issue caused by gmail where they turned off or are doing something with ssl and the camera software doesn't handle it.
https://www.ipcamtalk.com/showthread.php/10940-GMAIL-Failure-Anyone-Else
Have a read through of this (lengthy) thread. Google are phasing out SSL encryption which is in use by Hikvision NVRs. Lots of people with the issue at the moment
With a DS-7608NI-E2-8P, you should be able to get things up and running again with the Google app-specific password fix, or one of the many other SMTP service providers linked in the thread.
Jack B Nimble
Pulling my weight
This is a fix for camera and nvr but, I am all Chinese so don't know where I can find the 5.4.0 upgrade for CH region. If anyone has it ?
http://www.forum.use-ip.co.uk/threads/solved-hikvision-gmail-failure.775/
http://www.forum.use-ip.co.uk/threads/solved-hikvision-gmail-failure.775/
Bugger - saw that other huge thread. I've been getting my cameras to do the alert mailling in the past as when you get the NVR to do it, it only sends out very low res pictures.
I'm using an app specific password on all my cameras, but they aren't working. Unfortunately, they are chinese versions :-(
I've tried Yandex, but it keeps saying that the username / password is wrong. I've also tried app specific passwords for that with no success. I've also tried my internet provider's SMTP service with the same results.
I'm using an app specific password on all my cameras, but they aren't working. Unfortunately, they are chinese versions :-(
I've tried Yandex, but it keeps saying that the username / password is wrong. I've also tried app specific passwords for that with no success. I've also tried my internet provider's SMTP service with the same results.
Hi everyone,
I am having the same issue as others here, NVR sends emails but cameras seem blocked to the web; they can not send emails or access time servers. I believe I have the correct settings but I my knowleage of networking is limited (I am a competent linux user however) and something must be incorrect so I have included screenshots from my NVR, camera and routerhere: http://imgur.com/a/oLOxp
NVR: DS-7604NI-E1 / 4P, firmware V3.4.80 build 160718
Cameras: 3x DS-2CD3345-I, firmware V5.3.9 build 160612
Router with Gargoyle version 1.9.1 at 192.168.1.1
Steps I have taken which summarizes my screenshots at :
NVR: 192.168.1.101 / 192.168.254.1
Enabled Virtual host
NVR network settings:
NIC Type Auto
DHCP Yes
IPv4 Address 192.168.1.101
IPv4 Subnet Mask 255.255.255.0
IPv4 Default Gateway 192.168.1.1
....
DNS Server
Auto DNS Yes
Preferred DNS Server 192.168.1.1
Alternate DNS Server
Gargoyle Router 192.168.1.1DHCP Yes
IPv4 Address 192.168.1.101
IPv4 Subnet Mask 255.255.255.0
IPv4 Default Gateway 192.168.1.1
....
DNS Server
Auto DNS Yes
Preferred DNS Server 192.168.1.1
Alternate DNS Server
Added Static route
Destination 192.168.254.0/255.255.255.0
Interface lan (maybe I need to add a WAN setting? But I don't want to expose some security risk to the NVR)
Gateway 192.168.1.101
Camera 192.168.1.101:65003 / 192.168.254.4Destination 192.168.254.0/255.255.255.0
Interface lan (maybe I need to add a WAN setting? But I don't want to expose some security risk to the NVR)
Gateway 192.168.1.101
Camera network settings
NIC Type Auto
DHCP No
IPv4 Address 192.168.254.4
IPv4 Subnet Mask 255.255.255.0
IPv4 Default Gateway 192.168.1.1
....
DNS Server
Preferred DNS Server 192.168.1.1
Alternate DNS Server
DHCP No
IPv4 Address 192.168.254.4
IPv4 Subnet Mask 255.255.255.0
IPv4 Default Gateway 192.168.1.1
....
DNS Server
Preferred DNS Server 192.168.1.1
Alternate DNS Server
One extra annoyance, I have SSH enabled on my camera at 192.168.254.4 but cannot ssh or telnet to it in Windows with Putty.
Any assistance will be greatly appreciated.
Last edited:
Your camera gateway is wrong. It should be 192.168.254.1. The camera is routed First through the NVR Internal PoE switch which has an IP of 192.168.254.1.
Then the NVR routes all traffic to the Garcoyle LAN router at 192.168.1.1.
Also put as secondary DNS everywhere the google DNS 8.8.8.8. It helps sometimes.
Read again my instructions that you quoted and you will see your mistake. I hope I am correct and helpfull.
alastairstevenson
Staff member
Spot on.
When you think about it - with no additional explicit routes configured within the cameras themselves, which are on the 192.168.254.0 network, the camera networking has no way to determine the route to the LAN gateway of 192.168.1.1 - it's on an unreachable remote network.
But 192.168.254.1 is on the local network, so it's accessible, and as it's the dual-NIC NVR it has the required forwarding enabled.
Just one point though - if the PoE-connected camera channel on the NVR is set to Plug & Play the NVR will at some point revert the default gateway back to the LAN default gateway.
To inhibit this, the channel should be set to manual.
Hello Alastair. Now you confused me as well with the above. Are you referring to the configuration of the channel at the NVR camera menu? This menu is not accessible from the NVR browser GUI interface, it is only accesible from the native NVR interface through the HDMI display.
At which point and under which conditions would the NVR change the default camera gateway (NOT THE NVR GATEWAY to be clearer) to the LAN gateway 192.168.1.1 ?
Hi aster1x,
My mistake - I forgot to mention I did try setting the default gateway of the cameras to the NVR POE NIC (192.168.254.1) as in your post but had no success. It does make sense that it should be 192.168.254.1 as the camera has no idea how to get to 192.168.1.1 as alastairstevenson said.
I have taken another screenshot of my current camera network settings which can be seen at the end of this post (Changed Default Gateway 192.168.254.1 and DNS 8.8.8.8). I tried sending a test email on the camera with the same email settings as my NVR which failed with message "Failed to connect the test server." The camera also cannot access time servers.
Hi alastairstevenson,
As you mentioned, I have now set all the camera channels to manual. I have put a screenshot below of this.
Last edited:
alastairstevenson
Staff member
No - not the network settings, the NVR camera channel settings.
Camera Management | Select channel | Modify button | Adding method.
I think, if the camera rebooted and the NVR refreshed the subset of the camera configuration settings that the NVR holds.
And perhaps the same if the NVR was rebooted.
And also I believe, periodic automatic refresh also.
On the inability of the cameras to communicate over the internet, a couple of things to try:
From a PC on the LAN, ping the camera native address (eg 192.168.254.x)
From a PC on the LAN, tracert/traceroute the camera native address (eg 192.168.254.x)
On the camera, swap the DNS name of the NTP server for a valid IP address and see if the test works, which would point to name resolution.
Anecdotally, Google's 8.8.8.8 DNS works better for Hikvision than the LAN router, maybe swap the order, or remove the LAN router.
My following proposal may not sound reasonable but in my case in the past it has worked.
1. Reboot both camera and NVR in sequence.
2. Revisit all menus and ensure that the network settings are as they were before the reboot and as they should be per mine and alastair's instructions. If they are not changed them again and repeat steps 1-2.
3. Leave both NVR and camera alone .... for a few days and then retest if the camera can send email. (It sounds strange, I know)
In my case after a few days the email dispatching started working OK. Then after months of propoer funcioning, the camera email dispatch stopped sending emails again. After a couple of weeks it started sending again!!!!!
This is HIK Vision functionality, it's not a bug!!!! (And we have paid for it!)
Pinging from computer (192.168.1.100) on LAN to camera behind NVR (192.168.254.4):
Code:
ping -t 192.168.254.4
Pinging 192.168.254.4 with 32 bytes of data:
Reply from 192.168.254.4: bytes=32 time=3ms TTL=63
Reply from 192.168.254.4: bytes=32 time=4ms TTL=63
Reply from 192.168.254.4: bytes=32 time=5ms TTL=63
Reply from 192.168.254.4: bytes=32 time=3ms TTL=63
Reply from 192.168.254.4: bytes=32 time=7ms TTL=63
Reply from 192.168.254.4: bytes=32 time=4ms TTL=63
Reply from 192.168.254.4: bytes=32 time=3ms TTL=63
Reply from 192.168.254.4: bytes=32 time=4ms TTL=63
Reply from 192.168.254.4: bytes=32 time=4ms TTL=63
Ping statistics for 192.168.254.4:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 7ms, Average = 4msTraceroute from computer (192.168.1.100) on LAN to camera behind NVR (192.168.254.4):
Code:
tracert 192.168.254.4
Tracing route to 192.168.254.4 over a maximum of 30 hops
1 4 ms 3 ms 4 ms 192.168.1.1
2 4 ms 3 ms 3 ms 192.168.1.101
3 3 ms 3 ms 3 ms 192.168.254.4
Trace complete.Used online service to convert time.windows.com to 13.85.70.43. Camera successfully updates time!!! Then I used time.windows.com in camera and camera successfully updates time again!!! Also on the cameras "Platform Access" settings page, it has a "Register Status" as Online. So it looks like the camera can now access the web. However the camera does not send emails yet so I'll need to play around with the email settings (I am using GMX as Gmail doesn't work), I remember the first time I tried to send emails from the camera without the NVR (connected directly to the router) it took some fiddling about. Some screenshots can be seen below:
For future reference I am going to list my working NVR, router and camera settings below (also shown in the screenshots above):
NVR: DS-7604NI-E1 / 4P, firmware V3.4.80 build 160718
Cameras: 3x DS-2CD3345-I, firmware V5.3.9 build 160612
Router with Gargoyle version 1.9.1 at 192.168.1.1
NVR: 192.168.1.101 / 192.168.254.1
- Enabled Virtual host
- Cameras set in NVR (System > Camera Management > Select Camera > Modify) with "Adding Method" "Manual"
- NVR network settings:
NIC Type Auto
DHCP Yes
IPv4 Address 192.168.1.101
IPv4 Subnet Mask 255.255.255.0
IPv4 Default Gateway 192.168.1.1
....
DNS Server
Auto DNS Yes
Preferred DNS Server 192.168.1.1
Alternate DNS Server
Gargoyle Router 192.168.1.1
- Added Static route
Destination 192.168.254.0/255.255.255.0
Interface lan
Gateway 192.168.1.101
Camera 192.168.1.101:65003 / 192.168.254.4
Camera network settings
NIC Type Auto
DHCP No
IPv4 Address 192.168.254.4
IPv4 Subnet Mask 255.255.255.0
IPv4 Default Gateway 192.168.254.1
....
DNS Server
Preferred DNS Server 8.8.8.8
Alternate DNS Server
Edit Jan 2022:
edit to myself: MAKE SURE COMPUTERS DNS SERVER IS SET TO GARGOYLE ROUTER 192.168.1.1!!! (had my computer set to a different dns server but could directly access cameras on 192.168.254.x on my laptop)
It does sound strange but I think some element of this got my camera accessing the web, as I last changed the settings on the camera 10 hours ago and tested back then if the camera can access a time server and it fails, try again 10 hours later and it magically works.
Out of curiosity, which email service are you using?
Last edited:
Managed to get camera (at 192.168.254.4 behind NVR) to send a test email!!! I really appreciate your help aster1x and alastairstevenson!!!
Camera settings for GMX:
Sender xxxxxxx
Sender's Address xxxxxxxxxxxx@gmx.com
SMTP Server mail.gmx.com
SMTP Port 587
E-mail Encryption None (for some reason SSL doesn't work which is annoying)
Attached Image Yes
Interval 2 s
Authentication Yes
User Name xxxxxxxxxxxx@gmx.com (If you put an incorrect username, you get an error message stating incorrect username or password, this is a good way to test if the camera can access the mail server)
Password xxxxxxxxxxxxx
Confirm xxxxxxxxxxxxx
Camera settings for GMX:
Sender xxxxxxx
Sender's Address xxxxxxxxxxxx@gmx.com
SMTP Server mail.gmx.com
SMTP Port 587
E-mail Encryption None (for some reason SSL doesn't work which is annoying)
Attached Image Yes
Interval 2 s
Authentication Yes
User Name xxxxxxxxxxxx@gmx.com (If you put an incorrect username, you get an error message stating incorrect username or password, this is a good way to test if the camera can access the mail server)
Password xxxxxxxxxxxxx
Confirm xxxxxxxxxxxxx
alastairstevenson
Staff member
Great that you got there! Let's hope it sticks.
Just for future info:
ping DNS_name
or
nslookup DNS_name
to see what the IP addresses are.
Just for future info:
from a PC with working name resolution you can also
ping DNS_name
or
nslookup DNS_name
to see what the IP addresses are.
Yeah, still working haha, I've had numerous emails from the cameras already, need to turn down the sensitivities.
And the DNS lookups work nicely, cheers.
I am using my ISP email servers WHO allow SSL and also yandex email service.
just a quick update/question so my alerts are working from the cameras 2332 with gmail on port 465 and TLS enabled. the NVR 7608 however does not have the TLS option but only SSL on/off. So with 465, 587 and 25 does not work with gmail. Had to revert back to using yandex. anyone else have this issue? again gmail works so i know the setup works from cameras but NVR does not with gmail.
alastairstevenson
Staff member
Hikvision had to issue updated firmware to fix the gmail issue, 3.4.80
What version did you update your NVR to in order to fix the gmail problem?