I SEE

[CABRON]

So after troubleshooting the SIP/stream problem i found out that:

1. I had to remove my private DNS from my router.

2. I had to allow ARlo and who knows who access to my network thru 443/80. 

3.I have to lower my security to let ARLO do its job. What a joke. 

No wonder we get hacked left and right. 

[StephenB]

---

@CABRON wrote:

2. I had to allow ARlo and who knows who access to my network thru 443/80. 

---

Unfortunately Arlo support tends to ask people to unblock these ports when they reach the end of their troubleshooting script w/o finding a solution. 

Try undoing that change and test again.  The Arlo equipment only makes outbound connections to ports 80 (http), 123 (NTP), and 443 (HTTPS).  There are never any unsolicited inbound connections.

Proxies on these ports could fail, so it can be necessary to forward ports to bypass the proxies. 

---

@CABRON wrote:

1. I had to remove my private DNS from my router.

---

How many DNS servers are advertised to DHCP clients?  Someone reported a bug a while ago, saying that the equipment stopped working when the server list expanded from 3 to 4.  No idea if Arlo fixed that.