Gmail Setup .... "Test" Fails

[pbc]

Trying to go back and setup emails within my cameras and/or NVR. I have a dummy account setup via gmail.

Have set SMTP Server to smtp.gmail.com
SMTP Port: Tried 587 and TLS, as well as 465 with SSL

Have not enabled SmartTLS

Authentication is checked. Have inserted my gmail and password.

But when I click "Test" it keeps failing. Could swear this worked once before, but am not getting any motion emails.

Thoughts on the above settings?

 

[TonyR]

Go here and follow the steps to change your G-mail security settings to 'allow less secure apps to access your account'==>> Allow or disallow less secure apps to access accounts

EDIT:

---OR---

If no joy, go here for more info from @crw030

 

[pbc]

Thanks...Have already checked the box on allowing less secure apps to access the account. Doesn't seem to be the issue here. I beleive crw030's suggestion relates more to fearing that the gmail acct password is compromised, in any event set up an "NVR" app with the suggested password, same result. Testing failed.

Could swear I had this issue with another camera at some point, but can't recall how I fixed it.

 

[pbc]

Also, I tried two different methods. The first by inserting "smtp.gmail.com" as the smtp server. Get a message "Testing Failed" with 465 (SSL) or 587 (TLS).

If I ping smtp.gmail.com through cmd, it gives me an IP address. If I use that IP address in the smtp server box, i get "failed to connect to the test server".

FWIW

 

[pbc]

Tried everything in this link...

[SOLVED] Hikvision Gmail Failure

Attempted ports 25, 465, 587. Tried TLS, SSL. Tried to use the app generated password vs main password, etc.

Nada.

 

[alastairstevenson]

What's the version of the NVR firmware?
When Google increased the security on Gmail, there was a Hikvision firmware update required to get the connection back working, but that was a while back.
Example : Email alerts not working when Hikvision cameras connected to DS-7608NI-E2/8P

 

[pbc]

Haven't updated it since I bought it. Will have a look when I get home after turkey...

 

[pbc]

Okay, maybe I have updated it. It is running:

 

[pbc]

Some other screen shots:






Should I change this port btw?

 

[pbc]

Noticed on my cameras I can select TLS in the firmware (still doesn't work though), while from the NVR it doesn't have a TLS option. Is there a newer firmware somewhere for this NVR that enables TLS?

 

[pbc]

Tried an individual camera as well since it has the TLS drop down. Same thing, test failed.

 

[pbc]

BTW, used the "app specific" two factor enabled password for the above as well.

 

[pbc]

A few other questions while I'm at it:

1. How do I set up my cameras (which are connected to the POE ports of my NVR) to get access to the internet?
2. The time on my NVR keeps getting out of sync, is there a recommended server? I just changed it to time.windows.com, NTP port 123, Interval 1440. But no idea if it's working as there is no "test" button in the NVR firmware.

Thanks!

 

[pbc]

Okay, found this thread...

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

But not sure how to do this on a Netgear r7000 router:

"- A static route added to your gateway/router to tell it how to direct the traffic.
For your network configuration this would be something like :
"For network 192.168.254/0 (subnet mask 255.255.255.0) use gateway 192.168.0.64 (the NVR LAN interface IP address)"
This method works OK - quite a few people are using it."

 

[alastairstevenson]

Okay, maybe I have updated it. It is running:

Are you sure that the Receiver address is set correctly?
With that V3.4.95 version of firmware, gmail will work OK when using port 587 and Enable SSL ticked.
Provided that DNS resolution is working OK and that, as you have indicated, 'allow less secure devices' is configured in the Gmail account.

 

[alastairstevenson]

2. The time on my NVR keeps getting out of sync, is there a recommended server? I just changed it to time.windows.com, NTP port 123, Interval 1440. But no idea if it's working as there is no "test" button in the NVR firmware

If that's still the case - it suggests the NVR is not able to communicate with the internet, or that DNS resolution is not working.
That would be a factor in the Gmail problem.

Suggestion :
Try changing the time server DNS name to an IP address, set the interval short for testing and see if time gets synced.

 

[pbc]

Can you dumb that down for me? I.e.,which IP address for testing time?

 

[alastairstevenson]

which IP address for testing time?

This should work OK :

alastair@PC-I5 ~ $ ping time.windows.com
PING time.microsoft.akadns.net (51.141.32.51) 56(84) bytes of data.
^C
--- time.microsoft.akadns.net ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4100ms

alastair@PC-I5 ~ $ nslookup time.windows.com
Server:       127.0.0.53
Address:   127.0.0.53#53

Non-authoritative answer:
time.windows.com   canonical name = time.microsoft.akadns.net.
Name:   time.microsoft.akadns.net
Address: 51.141.32.51

alastair@PC-I5 ~ $

 

[catcamstar]

I am betting on a "block internet access" firewall rule on the NVR? This will be proven (or not) by the NTP sync on ip address. If this test also fails, I suggest you grab a pc, put in the ip addresses, subnet, gateways like entered in the NVR, and reproduce there. Only advice from what I see is to change subnet to 255.255.255.0 as your gateway is inside your own subnet.

 

[TonyR]

Only advice from what I see is to change subnet to 255.255.255.0 as your gateway is inside your own subnet.

Yep