http://blogs.technet.com/wbaer/archive/2007/02/04/securing-sharepoint-products-and-technologies-for-the-extranet.aspx

There is more and more demand for this kind of ability, putting SharePoint Server on the web should be easier.

Here is a good link to explain these steps.

http://www.sharepointblogs.com/rrfreeman/archive/2007/02/07/19132.aspx

If an authentication system like Kerberos was readily adopted by everone, it would make moving between applications on the web and in software so much easier. One day, I hope websites and software programs would just know who you where and what you were allowed to do.

This document explains how to deploy SharePoint Portal Server 2003 across an extranet. The white paper discusses how to configure a SharePoint Portal Server deployment so that users outside an external corporate firewall/proxy server can access information on a portal site that is inside an external corporate firewall/proxy server. It specifically discusses using Microsoft Internet Security and Acceleration (ISA) Server 2000 and ISA Server 2004 in what is generally considered to be a reverse proxy configuration.

http://www.microsoft.com/downloads/details.aspx?FamilyId=4C5BF9DD-3EFB-451D-B213-98ED039190BF&displaylang=en

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/sharepoint/revproxy.mspx

http://go.microsoft.com/fwlink/?LinkId=28245

Click here to view this On Demand Webcast http://www.placeware.com/cc/mseventsbmo/view?id=1032251937&pw=webcast

If you have everything all set for an extranet, and you have run the proxycfg command, and you are still receiving the proxycfg error, then this might be your answer.

MS has a KB article (Q305032) describing this. If you have a NAT occuring between the extranet client and the SPS, then the client (and the SPS) are resolving the FQDN (via DNS) to the external IP address. The SPS however, needs to resolve the FQDN to the internal IP address.

The quick fix is to add a hosts file entry into the SPS containing the FQDN with the internal IP address of the SPS. This immediately fixed my issue.

Bryan

“Deploying SharePoint Portal Server Across an Extranet” whitepaper, available at http://www.microsoft.com/technet/prodtechnol/sppt/sharepoint/reskit/part3/c12spprk.mspx. This paper is not necessary for Intranet-ONLY implementations with servers referenced by NetBIOS names.

Mapping the external IP to the internal one works for me, but have you run
the winhttp proxy configuration utility? (proxycfg) , you have to do that.
Go from a command line to the Sharepoint Portal server\Bin directory and
enter a command like: proxycfg -d -p fake-proxy-name:80 "<local>;*"
Depending on what you need, so be careful. Here's the full details on this
tool

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk30/ht
m/serverxmlhttpproxy.asp

As regards not using a FQDN, I've read a few posts saying this creates
problems, but I'd check that out, I've only ever done it with them,



proxycfg -d -p fake_proxy_name:80 "*.server_name.com;<local>"

You can also enter the settings in Internet Explorer on the Server and using the -u switch: proxycfg -u

Restart the server