locked
Inter-Trunk hypertext links not working RRS feed

  • Question

  • Ran,

    I wonder if you'd be so kind and return to the scenario you tested for us a few days ago:

    • Publishing multiple SharePoint applications on a single port, with identical internal and public host addresses, using the same backend MOSS server
    • So when you publish your apps in the different trunks, all settings are the same, except their Host Headers

    Now, the above is doable, however...the following problems arise:

    1st Trunk: HTTP

    • Trunk public hostname: uag1.company.com
    • Unique trunk IP address (eg 192.168.1.1)
    • Anonymous access
    • Publish an "Application specific hostname" IIS application with public hostname & host header set to www.company.com
    • Application web address: IP address IIS/MOSS server (please try IP first, then FQDN - 10.1.1.1 same MOSS server for all published MOSS applications on all trunks) 
    • Path: /
    • On this www.company.com webpage create a URL link to https://secure.company.com

    2nd Trunk: HTTPS

    • Trunk public hostname: uag2.company.com
    • Unique trunk IP address (eg 192.168.1.2)
    • Authenticated access
    • Publish a "Sharepoint 2007" application with public hostname & host header set to secure.company.com
    • Application web address: IP address IIS/MOSS server (please try IP first, then FQDN - 10.1.1.1)
    • Path: /

    Now open http://www.company.com (from an Internet client) and hover over the hypertext link to https://secure.company.com

    Do you see how https://secure.company.com is HAT'ed to https://uag1.company.com/uniquesig.../... ?

    Regards

    • Edited by D Wind Tuesday, May 25, 2010 8:44 PM
    Friday, May 21, 2010 2:54 PM

Answers

  • Spoke too soon. a few days later, without any Activation, the hypertext links are not working again.

    Logging a bug with Microsoft asap.

    • Marked as answer by James Kilner Wednesday, June 9, 2010 11:04 AM
    Monday, May 31, 2010 3:50 PM

All replies

  • There is one more thing I need to point out. we are using 2 x Celestix devices..and these have 8 NICs in total.

    So we have a few more trunks in addition to the above:

    3rd Trunk: HTTPS

    • Trunk public hostname: uag3.company.com
    • Unique trunk IP address (eg 192.168.1.3)
    • Authenticated access
    • Publish a "Sharepoint 2007" application with public hostname & host header set to finance.company.com
    • Application web address: IP address IIS/MOSS server (please try IP first, then FQDN - 10.1.1.1)
    • Path: /

    4th Trunk: HTTPS

    • Trunk public hostname: uag4.company.com
    • Unique trunk IP address (eg 192.168.1.4)
    • Authenticated access
    • Publish a "Sharepoint 2007" application with public hostname & host header set to sales.company.com
    • Application web address: IP address IIS/MOSS server (please try IP first, then FQDN - 10.1.1.1)
    • Path: /

    So on the http://www.company.com there are hypertext links to:

    None of the home page hypertext links work, they all are being HAT'ed.

    • the first 2 DIPs from the devices make up the first VIP,
    • the second 2 DIPs, are the next VIP
    • etc for 3rd and 4th VIP

    2 trunks are actually running as UAG webparts within MOSS 2007.

    Also I just read in another post by Tom Shinder that UAG only supports 2 NICs, 1 internal and 1 external....the Celestix devices have 8 NICs, and most of them are planned on being used, that's why the company bought them.

    Please can you help and clarify matters.

    Monday, May 24, 2010 6:49 PM
  • I have answered in the other thread and got a Celestix friend to confirm the bad news :(
    Jason Jones | Forefront MVP | Silversands Ltd | My Blogs: http://blog.msedge.org.uk and http://blog.msfirewall.org.uk
    Monday, May 24, 2010 10:52 PM
  • That would explain the potential for issues in the Celestix live deployment. I will reconfigure it and test it today.

    However, this does not explain our virtual environment, where we do not have UAG array, no NLB whatsoever, and a single external and single internal interface.

    Will feedback to forum.

    Tuesday, May 25, 2010 4:51 AM
  • So I reconfigured the appliances as per recommendation - only 2 NICs per Celestix device, with a VIP for NLB.

    However exactly the same problem exists.

    So the config is exactly like what I described above (except its 1 external and 1 internal NIC - as opposed to 8)

    UAG HATs the hypertext links - so we can not cross-link from a HTTP trunk to a HTTPS trunk - please help

    Thank you

    Tuesday, May 25, 2010 4:36 PM
  • So I tried one last thing....

    on the HTTP trunk, I removed the Web Application that was published with "Application specific hostname" template....

    then republished the Web App using the MOSS 2007 template.

    lo and behold....it seems to have done the trick....the hypertext do not HAT anymore.....

    so that's kind of going against the UAG/MS recommendations (http://blogs.technet.com/b/edgeaccessblog/archive/2010/01/15/what-happened-to-basic-and-webmail-trunks.aspx) ....but since its working we are stoked !

    will keep everyone informed if things suddenly stop.

    • Marked as answer by D Wind Wednesday, May 26, 2010 1:10 PM
    • Unmarked as answer by D Wind Monday, June 7, 2010 1:46 PM
    Wednesday, May 26, 2010 8:17 AM
  • Spoke too soon. a few days later, without any Activation, the hypertext links are not working again.

    Logging a bug with Microsoft asap.

    • Marked as answer by James Kilner Wednesday, June 9, 2010 11:04 AM
    Monday, May 31, 2010 3:50 PM
  • I have marked this as answered since the resolution is to open a bug with Microsoft.

    James.

    Wednesday, June 9, 2010 11:05 AM