Hi everyone, Given the following configuration: WSS 3.0 Site, extended to two zones: http://<internal name>/ - Default Zone with Windows Integrated Security http://<internal name>:81/ - Extranet Zone with FBA Works like a charm. Now, the FBA based Zone shall be provided by means of a reverse proxy. This proxy is a 3rd party product and configured as follows: https://<external name>/ is forwarded to http://<internal name>:81/ Client request are not altered in any way. No link rewriting The strange issue is now that links are scrambled as follows: From the client perspective using the https://<external name>/ URL, links are returned as http://<external name>:81/ So a mixture of both external and internal. The alternate access mappings for the intranet zone is configured as: Internal URL Zone External URL http://<internal name>:81/ Extranet https://<external name>/ http://<external name>/ Extranet https://<external name>/ Can anyone give me an enlightment on this? Thanks everyone, Regards Joerg Fischer Jörg Fischer

Hi Hans-Joerg Fischer, From your post, your issue is related to a third party product. We suggest that you contact the technical support of this product for more help. If you would like to use ISA or Forefront UAG to publish WSS 3.0, please refer to the following articles: How to publish Microsoft Sharepoint services 3.0 with ISA Server 2006 Enterprise http://www.isaserver.org/tutorials/How-to-Publish-Microsoft-Sharepoint-Service-ISA-Server-2006.html Why enable SharePoint extranet access with Forefront UAG? http://technet.microsoft.com/en-us/library/dd861393.aspx Try to add the internal URL from the reverse proxy publishing rule to the Internet zone of your Web application. Then check the effect. For more information about how to add the internal URL from the reverse proxy publishing rule to the Internet zone of your Web application, please refer to the following article: http://technet.microsoft.com/en-us/library/cc288609(office.12).aspxRegards, Rock Wang Microsoft Online Community Support