1 person found this helpful
It sounds like communication between your security server and connection server is broken. The SS will return with 503 if it's unable to forward the request on to the paired CS. Make sure you check that the health status for the servers are green and confirm that the required firewall ports are open. Note that 503 can also be returned by some proxy servers if they're unable to reach the View server.
Thanks for the reply. Although it should have seemed obvious to check the firewall settings which were fine, I didn't check to see if the Windows Firewall was on(which I disabled on both the security and connection servers). I recently applied new Windows updates which I'm guessing re-enabled the Windows firewall and of course were blocking the ports. After disabling the firewall everything checks out.
Latest Windows patch enabled the firewall on our security server. Once I disabled the Windows Firewall (& of course rebooted)
All connections were operational to the View Desktops.
Thanks for playing, "will we survive this months MSFT pacthes"
I wouldn't recommend disabling the firewall entirely, we do document the specific ports we need open on a security server and by default we use the built-in windows firewall for setting up the ipsec tunnel back to the paired connection server in 5.1+.
It's a good point. We have another firewall in place in our Org which is why we disable the Windows Firewall.