UAG 2010 – Problems with Custom Trunk Ports and Failing Redirects
UAG 2010 prior to Service Pack 1 Update 1 did not support publishing trunks on custom ports – only 80 and 443 were supported. That meant each UAG trunk required a separate IP address per trunk. With SP 1 Update we could publish UAG trunks on custom ports on a single IP address, although it doesn’t seem many people actually did this. For a customer recently where UAG 2010 was required with 5 trunks, there was an existing network architecture restriction that required the UAG servers to use public IP addresses.… [Keep reading] “UAG 2010 – Problems with Custom Trunk Ports and Failing Redirects”