Gmail Setup .... "Test" Fails

[alastairstevenson]

All the tracert 192.168.254.1 command did was return 192.168.254.1.

That's OK, if there was no timeout it reached it.
You should be able to ping it as well.
And will be able to ping the cameras if their default gateway is now 192.168.254.1

 

[pbc]

When I try to ping the individual cameras (e.g., 192.168.254.11), it times out..

 

[pbc]

Wait...after putting them on "manual", do I need to go into the web interface of each individual camera and change settings of some sort there?

As in set the default gateway of each camera to 192.168.254.1?

 

[alastairstevenson]

Do they have their gateway set to the NVR PoE interface IP address, ie 192.168.254.1 ?
Maybe the static route needs to be 'private'.

 

[pbc]

Perfect...that was the missing step. Back online.

 

[pbc]

Now back to the original subject of getting the cameras to send out email notifications. Hopefully it works now.

 

[pbc]

Okay, tested the NVR email and I get a successful test.

Then went into an individual camera, set it up identically (email addresses, passwords, 587, enable SSL)...and test failed.

...and I hate that we can't upload pics anymore!

My settings on my camera are:

ipv4: 192.168.254.11
subnet: 255.255.255.0
Gateway: 192.168.254.1

Am I missing something again that needs to be done differently on the individual camera?

 

[alastairstevenson]

Am I missing something again that needs to be done differently on the individual camera?

Your settings should be OK.

Does the version of camera firmware have a 'Test' button on the Time settings such that you can confirm that 'time.windows.com' resolves and connects OK?

 

[pbc]

Yes it does. NTP port 123, 1440 intervals, the test fails meaning cameras are not getting out to the internet still?

 

[SouthernYankee]

IT depends on where your NTP server is located. What is the address of the NTP server ?
Some of us have an NTP server on the network to keep the cameras from accessing the internet.

 

[pbc]

time.windows.com

Weird, wasn't able to get back on to this site until this morning, was the site down?

 

[pbc]

 

[pbc]

Screen shots of my route setup in my netgear router, and then the camera network and gmail setup.

 

[alastairstevenson]

Screen shots of my route setup in my netgear router, and then the camera network and gmail setup.

If you can't ping 192.168.254.11 then the static route is not working.
Your configuration looks OK.
But try ticking the 'Private' box on the router configuration.

was the site down?

Unusually, yes, the HTTP and HTTPS services were closed, the rest were normal looking.

 

[pbc]

If you can't ping 192.168.254.11 then the static route is not working.
Your configuration looks OK.
But try ticking the 'Private' box on the router configuration.


Unusually, yes, the HTTP and HTTPS services were closed, the rest were normal looking.

I am able to ping 192.168.254.11.

Just can't get the time.windows.com test to succeed, nor can I get a gmail out from the cameras.

Have tried clicking private as well, same result, Failed gmail test and failed time server test.

Anything else you can think of that I should try?

 

[alastairstevenson]

Ok, try changing the DNS setting in one of the cameras.
If it's currently 192.168.1.1 try changing it to 8.8.8.8

*edit*
Another suggestion to try with the 'Test' button, to check connectivity that doesn't depend on name resolution -
Temporarily replace time.windows.com with an associated IP address, and see if it connectes.
Sample IP address :

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 ~ $

 

[pbc]

The DNS setting in my cameras is 8.8.8.8, should it be 192.168.1.1?

Sorry, when you post that code, I'm not sure what you're asking me to do. I.e., what is
alastair@PC-I5 ~ $ nslookup time.windows.com?

A CMD command of some sort?

 

[pbc]

Just to check, I change the DNS server from 8.8.8.8 to 192.168.1.1. Ran the time test, this time I get a "Failed to connect to test server".

With it set to 8.8.8.8, I get "Testing Failed".

Different messages.

I get "Failed to connect to test server" error with 8.8.8.8 if I use 51.141.32.51 as my time server. Having said that, if I simply go to that IP address I get a 403-forbidden access page.

 

[pbc]

Did a tracert on time.windows.com, it gave me this IP address 52.168.138.145. Received a "Failed to connect to test server" error with that one vs "Testing Failed" with time.windows.com.

Too bad there is no "test" button in the NVR for the time page.

 

[alastairstevenson]

Sorry, when you post that code, I'm not sure what you're asking me to do. I.e., what is
alastair@PC-I5 ~ $ nslookup time.windows.com?

It's an example of how to find a time server IP address to experiment with testing the ability to access it, not using a name that must be resolved.
There will be multiple possible addresses, depending on location, load etc.

if I simply go to that IP address I get a 403-forbidden access page.

Yes, it's not a website.