0
votes

We have a newly-configured Sharepoint 2013 server installation, which serves our company Intranet. The new Intranet is now in service and operational.

Next, we need to create another top-level site which will serve as an Extranet portal for clients. Sharepoint Central Administration does not provide a method by which a separate IP address can be selected for a new site; instead, it provides port selection or entry only.

We need to route external traffic to the extranet site, which requires either a mapped internal IP address or a different port. The main limitation we face is that most of our public-sector clients cannot use a non-standard port due to their firewall restrictions. So, this means a unique IP.

In the exhaustive research conducted concerning this issue, it appears that the "best practice" receommended by Microsoft themselves is nothing but a workaround, where part of the process is performed in SP Central Admin and the other half in IIS.

We have found many articles and blogs mentioning alternative ports, but none which address this situation directly.

Now we're trying to contend with Alternate Access Mappings, which are confusing our admins.

We really need the voice of experience from someone who has actually done this before.

Question: what is the correct way of achieving our goal?

1

1 Answers

0
votes

Your users will access the site based on a host name I guess, not on an IP address? So, you will have an intranet under http://intranet and you now want to create an extranet under http://extranet. The fact that extranet is on another IP address and routed to your SharePoint farm is not really an issue.

What you need to do, is to create another web application with as host name http://extranet Your firewall / network hardware must then forward http://extranet to your SharePoint servers. IIS will see "extranet" and serve the extranet.

If your users will access it via the IP-address, it's similar. Instead of http://extranet, you enter http://ext.ip.addr as the host name.