dahua NVR not reaching WAN?

[salo225]

Hi all, newbie doing first build and have run into a roadblock. I've searched all over the site and went thru all 55 pages in this forum for an answer/clues as I didnt want to ask a question when I could find the answer myself, but here I am....

So I'm starting to suspect my dahua 4208-8p-4k is not getting out past my router/modem for 2 reason.

First, I'm unable to set up email alerts and keep getting "test failed" message. I've read ~50 threads on this and I'm confident I have set the smtp parameters properly and have tried every combo of ports and encryption types (SSL/TLS/none on ports 25, 2525, 465, 587) I have found thru searching. I have also tried creating unique accts with gmail (w/ "less secure apps" enabled), hotmail, and yahoo - same result. I have also tried the NVR's OSD, webUI, and smartpss. Nothing. Odd.

Next, I tried to see if I was getting NTP updates. I tried time.windows.com, time.apple.com, and time.nist.gov - all result in "update failed". The NTP update should be simple enough and has convinced me the NVR is not reaching the WAN.

I can access the NVR via webUI so the LAN config is good, but is there a way to assess if the NVR has WAN/internet connectivity? Could my router be blocking the NVR from communicating to the world? Would appreciate any thoughts/help!

 

[alastairstevenson]

Try using an IP address for one of those time servers, see what the test button shows.
If that works OK, it's a name resolution problem.
If it doesn't - it's a network connectivity / routing problem.
Is there any telnet or SSH access to the NVR?

 

[salo225]

Thanks. I entered the actual IP addresses for both time.apple.com and time.nist.gov but it failed each time.



The request timed out in the CMD prompt when I try to ping time.windows.com

I'm not very familiar with how to use telnet or SSH. During my research into this issue, I bookmarked this thread by @nayr (Dahua Enable Telnet) on how to access the NVR via telnet but I have no idea what I would do after that.

 

[Fastb]

The NVR:
- can't send emails.
- can't reach time server
- ping to time server doesn't work.

But you can surf into the NVR when you're connected to your local lan.

Sounds like your home subnet;
- can't reach WAN. Can you ping google, yahoo, etc from your locally connected PC? (which is on the same subnet as NVR)
Maybe you need to change subnet mask?

Does your main router (the one connected to the WAN) see the NVR? Does the NVR appear in a "connected devices" screen when you're viewing the screens in that router?

Fastb

 

[alastairstevenson]

If you do manage to use a telnet client to get to a command prompt, what you can usefully do depends on the set of commands that has been made available. Sorry - but I'm unfamiliar with Dahua internals.
Some useful ones, if available:
But don't be surprised if none are.

route
ping time.windows.com
ping 52.169.179.91
traceroute 52.169.179.91
nslookup google.com

 

[salo225]

Does your main router (the one connected to the WAN) see the NVR? Does the NVR appear in a "connected devices" screen when you're viewing the screens in that router?

I checked my router and in fact did NOT see my NVR in the connected devices screen, which really threw me for a loop given I was able to reach it via the webUI. As I'm over at the NVR and router, I realize I connected the router to one of the NVR's PoE ports vs the ethernet/network port. FML. I reconnect to the proper port, the NVR immediately pops up on my connected devices screen, and NTP/email now work with no problem.

Wow I feel like such a moron. Since I could access the webUI, I didnt even think about a connection issue with the router.

Sorry to waste folks time helping me troubleshoot such a dumb mistake but I really do appreciate your assistance in resolving this.

 

[Fastb]

salo225,

BTW, welcome to the forum!

No need to fall on your sword! (in your 4th post) Everyone was a newbie sometime. (except @nayr, he was born a pro)

So just pay it backward, and help other newbies in the future!

I'm glad you figured it out,
Fastb

 

[alastairstevenson]

Well that's an interesting result, and explains the symptoms.
And credit to @Fastb for the suggestion to check the router. Nice one.

Just to satisfy my curiosity I have a question if I may.
I presume that, like a Hikvision PoE NVR, the NVR PoE interface has an IP address on a separate address range than the LAN interface.
With the router plugged in to a PoE port and the NVR web GUI being accessed at its LAN address, that implies the NVR is routing traffic internally between its 2 interfaces.
Had you been accessing the PoE-connected cameras directly at their native addresses?

And thanks for sharing - it all adds to the knowledge base, and may help others.

 

[salo225]

Had you been accessing the PoE-connected cameras directly at their native addresses?

No, just thru the NVR. The only way I can access the cameras thru their IP address is if I hook my laptop directly to the NVR via Ethernet. Router plugged into a POE port doesn't allow me access to camera via IP.

 

[Bryan]

Hi all, newbie doing first build and have run into a roadblock. I've searched all over the site and went thru all 55 pages in this forum for an answer/clues as I didnt want to ask a question when I could find the answer myself, but here I am....

So I'm starting to suspect my dahua 4208-8p-4k is not getting out past my router/modem for 2 reason.

First, I'm unable to set up email alerts and keep getting "test failed" message. I've read ~50 threads on this and I'm confident I have set the smtp parameters properly and have tried every combo of ports and encryption types (SSL/TLS/none on ports 25, 2525, 465, 587) I have found thru searching. I have also tried creating unique accts with gmail (w/ "less secure apps" enabled), hotmail, and yahoo - same result. I have also tried the NVR's OSD, webUI, and smartpss. Nothing. Odd.

Next, I tried to see if I was getting NTP updates. I tried time.windows.com, time.apple.com, and time.nist.gov - all result in "update failed". The NTP update should be simple enough and has convinced me the NVR is not reaching the WAN.

I can access the NVR via webUI so the LAN config is good, but is there a way to assess if the NVR has WAN/internet connectivity? Could my router be blocking the NVR from communicating to the world? Would appreciate any thoughts/help!

View attachment 14107

Just learning how to do it myself, I feel your pain, took me hours. You have to go into your email settings and write down the OUTgoing SMTP address and port (under advanced in Outlook) not the IP address as the manual makes it appear. Sender is same as receiver. Device config -> Network -> SMTP see my pic. Getting the health emails now and alarm emails..even though they don't state which alarm.. The Alarm Center menu - I set it up the same as my NVR IP address, don't know whether that is also making it work. See 2nd pic.

 

[c hris527]

Well that's an interesting result, and explains the symptoms.
And credit to @Fastb for the suggestion to check the router. Nice one.

Just to satisfy my curiosity I have a question if I may.
I presume that, like a Hikvision PoE NVR, the NVR PoE interface has an IP address on a separate address range than the LAN interface.
With the router plugged in to a PoE port and the NVR web GUI being accessed at its LAN address, that implies the NVR is routing traffic internally between its 2 interfaces.
Had you been accessing the PoE-connected cameras directly at their native addresses?
And thanks for sharing - it all adds to the knowledge base, and may help others.

I can tell you for sure on my Dahua's NVR's it does not. I have some with built in poe and you can not access the management side of the NVR from the POE side where your cameras are plugged in. It will not let you even assign the same IP pool as your management side to the cameras. If I need to get at those cameras for a serious look, I have to hit them with my laptop on the same IP range as my camera side plugged into the switch on the NVR. Not sure what was going on on his end but I have tried that trick with a no go. I guess I will now have to test this again.

 

[c hris527]

I checked my router and in fact did NOT see my NVR in the connected devices screen, which really threw me for a loop given I was able to reach it via the webUI. As I'm over at the NVR and router, I realize I connected the router to one of the NVR's PoE ports vs the ethernet/network port. FML. I reconnect to the proper port, the NVR immediately pops up on my connected devices screen, and NTP/email now work with no problem.

Wow I feel like such a moron. Since I could access the webUI, I didnt even think about a connection issue with the router.

Sorry to waste folks time helping me troubleshoot such a dumb mistake but I really do appreciate your assistance in resolving this.

Ok now that you have my full attention on this, I do have a few questions.
I was looking at your network settings on the pictures you provided. You have a static IP of 192.168.0.108 Correct?
How did you log into the NVR to set that, are you saying that you never used the management port on the the nvr to set that. If you had the LAN port plugged into one of the POE ports, you are saying you can access the NVR's web gui this way? This might be true or a back door in with no network cable plugged into the management port, who knows, your web gui almost looks like you were logged into a camera and not the nvr but they are pretty similar. Just a thought. This is going to drive me nuts now. UPDATE, I just went and tried it, could not ping the nvr and smart pss lost its connection when I plugged my lan connection into the poe side. Could be different firmware who knows but these things should act the same.

 

[dahuaptz1A]

1 in the tcp/ip menu if you go to the edit pencil icon on your nic card and toggle dhcp on apply , off apply and back on apply see if that changes the status in p2p menu
2 In the maintenance tab, under network detection on the second header labelled "test" if you type in google.com in the field see if your device can reach the world wide web
3 date and time settings go to system , date and time and check your in the London time zone dd/mm/yy format dst enabled and setup correctly
4 in your security tab please ensure that https is disabled
5 if after all these you still cannot connect please call your isp and see if ipv6 is enabled , this can sometimes stop p2p from working ask them to disable this and try again