通过

Trunk cannot be activated due to Invalid External Port address

  • 项目

Users who upgraded their UAG server to Update 1 may receive an error upon activation “Error: Trunk <Trunk name> cannot be activated due to the following: Invalid External Port address. Please choose a different port.”

This situation may happen if you are running a UAG array, and the array has a redirect trunk (from HTTP to HTTPS) configured. With Update 1, UAG now allows the user to select any external port on a trunk, but this functionality has not been fully enabled for a redirect trunk in Array mode and this may lead to this error being shown.

If you run into this situation, please open a support case with Microsoft CSS, and a support engineer will help you deal with the situation.

Comments

  • Anonymous
    January 01, 2003
    Hi Ben In addition to the above mentioned situation, we experienced another issue. Some users were unable to login to the portal (certificate authentication). After doing some research, we found that CN returned from LDAP query was replacing special characters with some others and consiquently the certificate CN and AD CN comparison was failing. We solved the problem by modifying the inc file. Is this a know issue, or am I missing something else? Kind regards, Grega

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    November 09, 2011
    Hi Ben, I saw this the other day when trying to create a HTTP-to-HTTPS redirect trunk on a new install, and assumed it was a bug introduced by the changes in U1 to provide customised trunk ports. Thanks for the heads up! ;) Cheers JJ

  • Anonymous
    November 24, 2011
    Hello Ben, I had a similar problem when introducing a replacement array member following a hardware failure. I was not using custom ports, but got the same error. Deleting the redirect trunk, activating, then re-creating the redirect trunk fixed my problem. Regards, Colin

  • Anonymous
    December 09, 2011
    Hi Ben, You guys any closer to releasing this as a public fix? Cheers JJ

  • Anonymous
    December 20, 2011
    I am now running into this issue.  Any word on a public fix?

  • Anonymous
    December 20, 2011
    An official fix for this should be available soon, and will be announced on my blog, and the product team's blog.

  • Anonymous
    March 01, 2012
    Hi Grega, The blog is not the appropriate platform to report or discuss issues. Please post your question in the public UAG forum. If that doesn't lead to a resolution, you can contact me directly via the "email blog author" above.

  • Anonymous
    July 24, 2012
    Hello, Was a bug fix ever released for this? Thanks, Simon

  • Anonymous
    July 24, 2012
    Yes, Simon, this issue is addressed with Rollup 1 for UAG SP1 U1. You can read more about it here: blogs.technet.com/.../uag-sp1-update-1-rollup-1-is-out.aspx Ben