


I'm using the latest version (3000.96.1). I'm no longer seeing any direct communication so I'm guessing it's using the proxy now but I'm still getting the above message. So then I changed the On-Premise Service to use a domain service account vs the default and gave that login admin privleges on the server and set the user to use the proxy via IE - Lan Settings. Apparently the Registration wants to communicate directly with an Azuer login via Port 80.which is totally bypassing the corporate proxy. I've been reading about this for days now.and running WireShark to capture packets. I got the test server up and running with no issues but firewall security is much tighter on the production server and I can't get past the Registration step. I'm trying to set up a new On-Premise Gateway as part of a server migration to a new data center.
