Email Notification on ZD Failed!

  • 1
  • Question
  • Updated 1 year ago
Need help! I am setting up an email notification on ZD3000 (ver 9.5) but always "Failed!". I've tried all my email accounts gmail, yahoo mail and followed some steps but got no luck.
I associated the IP Address of the ZD to the private IP network that can go to the internet but failures always there.

I also add the DNS of 4.2.2.2 and also 8.8.8.8 to make sure that the DNS were not affecting the failures.

Please see my settings below:
Photo of Noel Saldaña

Noel Saldaña

  • 17 Posts
  • 1 Reply Like

Posted 1 year ago

  • 1
Photo of Big Dog

Big Dog

  • 60 Posts
  • 10 Reply Likes
Hi try SSL on port 465
Photo of Noel Saldaña

Noel Saldaña

  • 17 Posts
  • 1 Reply Like
465 is not working.. :(
Photo of Alan Rothenstreich

Alan Rothenstreich

  • 63 Posts
  • 11 Reply Likes
If I recall correctly, you have to enable and confirm mail being sent from a non-gmail application.  I am using the same settings as you have without an issue.

There were issues with GMail in some of the past versions.  I am running 9.12.
(Edited)
Photo of Noel Saldaña

Noel Saldaña

  • 17 Posts
  • 1 Reply Like
Well thanks for your help. I managed to try first on my yahoo mail and I received a notification that I need to lower the security settings to give way for the application to send emails. It now works fine and I also tried it using gmail now and it was successful.

I just want to ask now, do I need to add the IP address of my ZD subnets to the NAT router? Because in our network, we separate the subnet of ZD management from the IP address it provides to the clients for them to go to the internet..
(Edited)
Photo of Alan Rothenstreich

Alan Rothenstreich

  • 63 Posts
  • 11 Reply Likes
As long as the APs can see the ZD.  How are your clients getting their IP addresses?  Are they each being assigned a VLAN?
Photo of Alan Rothenstreich

Alan Rothenstreich

  • 63 Posts
  • 11 Reply Likes
The APs should be added to the NAT.  Besides the ZD, you should have a gateway for authentication and accounting that can manage the end users..
Photo of Noel Saldaña

Noel Saldaña

  • 17 Posts
  • 1 Reply Like
If I put the subnets for NAT would my devices be now vulnerable to security risks on the internet? and if so, what would I do to prevent them?
Photo of Alan Rothenstreich

Alan Rothenstreich

  • 63 Posts
  • 11 Reply Likes
The APs are NATed so should not be accessible through a public IP.  They should be on the same subnet as the ZD.  Clients should be given IP addresses from a different IP group such as 10.x.x.x with isolation and dynamic VLAN managed by a gateway/RADIUS server.  There are different providers of hardware and cloud managed software to work with the ZD.
Photo of Noel Saldaña

Noel Saldaña

  • 17 Posts
  • 1 Reply Like
Clients are given an IP address from a different DHCP server, the DHCP server of the ZD only gives IP to the AP members. If I put the ZD and APs for NAT would there be any security risks on them? What could I do to prevent any risks of incoming attacks from the internet going to my internal private IP like here on my ZD and APs?
Photo of Alan Rothenstreich

Alan Rothenstreich

  • 63 Posts
  • 11 Reply Likes
Install a firewall that restricts incoming traffic to only be allowed from specific ip addresses or through a VPN.
Photo of Noel Saldaña

Noel Saldaña

  • 17 Posts
  • 1 Reply Like
Hi, sorry for opening this topic again..
I just want to know, to make the email notification to work.. is there a way that the ZoneDirector could bypass the IP Based provider (HSIA provider was for hospitality)..

The network system was like this.. all clients was provided an IP address from the HSIA provider via DHCP that goes to the internet, but the ZD and APs have separate VLANs (ZD provides DHCP to the APs) that is not routable to the HSIA or through the internet.

I don't have any control on the HSIA provider who has the router and internet and I only configure the ZD and the L3 switches that lwas linked to them in order for the clients to reach the internet.