SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Right now to test the web application on an external site, the web app was extended to a site that is mapped to an external IP address.

When the site goes live, on a different IP address, users will access the site from the url, and the internal firewall will route to the internal IP of my SharePoint server.

My question is, do I need to modify my mappings in anyway, or will redirecting the external user to my internal sharepoint IP be enough?

share|improve this question
up vote 1 down vote accepted

I think you should be more worried about Bindings in IIS rather than Alternate Access Mappings, but even then IIS should take care of them perfectly fine - do you know what firewall is in use? ISA and TMG handled this perfectly OK but I think TMG is now out of support.

share|improve this answer
I'm not sure of the firewall. I think all that really needs to be done is when rerouting from the URL to the SharePoint server, that I include the port (ie. to the actual SharePoint web application. Does that sound like it makes sense? – TeddyRuxpin Nov 28 '12 at 17:34
I set up a staging site, to test. typing in the base url: gives me an unexpected error 'File Not Found' when it routes through the 'VariationRoot.aspx' page. However, if I go to the variation sites directly (ie. the site works as expected. Any ideas as to why that is? – TeddyRuxpin Nov 29 '12 at 17:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.