ZooAdmin connections to port 80 on external servers

Zoo
1

Hello,

Does anyone know why ZooAdmin attempts connections on port 80 of some external servers, which appear to be IPs belonging to Amazon EC2?

The destination IPs are many, here are just a few samples:

3.5.9.14
16.15.219.230
52.216.140.228
52.217.198.1

Our LAN Zoo server was successfully moved to a new environment thanks to the information provided in LAN Zoo port 80 sources and destinations , and at the moment everything seems to be running smoothly, except for a very slow response (a few minutes) when adding/validating a new license.

I’m seeing the connections reported above in the log of the external firewall, and they are blocked now because our security policies do not allow opening port 80 to “any server”, we need to be more specific on the required destinations.

Are those connections needed?
What should be the destination FQDN or IP range?
Can they be the reason for the slow license validation response?

We already opened port 80 from Zoo to all clients, but these are external IPs, not belonging to Rhino workstations in our LAN.

Thank you.

–
Kind regards.

2

Is the McNeel Update Service running? (pre Rhino 8) , that would be hitting the Amazon servers i’m told. Asking the devs for additional details. The update service is optional and can be disabled.

3

Hello Japhy,

should I see it in running services in the Services app?

I only see “Zoo 8” service running, I can’t find any other related services in the list.

Anyway, the connections are initiated by a process named “ZooAdmin.Wpf.exe”.

Thank you.

Kind regards.