Michael,

Ok, our instance is shown as relay server “relay://instance-xat0wr-“. So my guess is instance-xat0wr-relay.screenconnect.com is the right url . I tried whitelisting the URL instance-xat0wr-relay.screenconnect.com but it didn’t work. I had to whitelist the ip again. Nslookup shows the ip as 54.85.232.136 . Wire Shark shows the server as server-aws0e1f5ba4-relay.screenconnect.com which goes to the same ip address, 54.85.232.136 . It looks like the server is hosted on Amazon. Appreciate you helping me to figure this out. It will be a lot quicker to find the right ip the next time it changes. Hope this helps someone else.

I'd still like to see a good fix for this. When it happens our Helpdesk stops until they run me down and I can change the ip.

Thanks, Joe

Happened to me to. I've opened another ticket with screen connect. Waiting on their reply. In the meantime I opened wireshark packet sniffer and determined the ip address to add to the exceptions. I compare that ip address to the list of all servers for the command nslookup servers.screenconnect.com. I verified the match, made the exception and it's working now. I don't understand why they can't give us a heads up when they change ip's for our instances. An e-mail would do it.