How to: Configure multiple virtual servers on one physical server?

[watsonam]

Hi,

The scenario is this: we have one physical server running Windows 2003, IIS 6.0 & SQL2000. I know there maybe performace issues with this but we will only have 10 users or so at first. The server is located on the internal network and is published via an ISA server using SSL bridging. I want to give users access from the internal network and also externally but would prefer not to use SSL when used internally. To do this I need to configure two virtual servers one using HTTP & windows integrated authentication and the other using HTTPS with basic authentication over SSL both pointing to the same data source. Firstly, have I got this config right or is there something I have missed? is there a better way to implement this type of solution?

I have been looking for a good resource on how to configure this particular setup but cannot find anything. Could someone please help or provide a link to a good resource etc.

Thanks in advance for any help.
Andrew Watson
Internet Security Engineer
Motivano Ltd

 

[Thomas2000]

Hello,

Are you running Windows SharePoint services (WSS) or SharePoint Portal server? SharePoint portal server can handle separate URL's for internal and external access, but pointing to the same content.

We are running an extranet solution with WSS and we are having some 500 usersm, both accessing from inside and outside. We are running SSL through all connections and I can't say we have really seen any performance issues (atleast not yet).

We are running Basic authentication for this extranet, and due to "paranoid" security thinking I also used SSL internally.

I think that SharePoint only supports https to https briding. There is an article describing on how to setup Windows SharePoint services as an extranet solution, if you have not seen it yet you can find it at

http://www.microsoft.com/technet/prodtechnol/sppt/wss/revproxy.mspx

Best Regards,
Thomas

 

[Evilbart]

sidenote :You don't need SPS to do so: all can be done through WSS also - prefered with isa publishing off course ;-)

addalternatedomain
Note New in Windows SharePoint Services Service Pack 2 (SP2).

Configures the incoming URL and maps it to a URL zone. For each HTTP request, Windows SharePoint Services looks up the incoming URL and detmines which zone will be used to format the outgoing response. Note that you can perform a separate zone mapping for each virtual server.

Required parameters Optional parameters
-url
-incomingurl

-urlzone
none

Sample syntax:

stsadm.exe -o addalternatedomain -url

http://existing.sharepointvserver.URLdomain

-urlzone default -incomingurl

http://incoming.url.domain

The following table describes the properties associated with this command line operation.

Property Description
-url URL of the virtual server as it is displayed on the Virtual Server List page in the SharePoint Central Administration site. If the virtual server is bound to a specific IP address or to a specific host header in Microsoft Internet Information Services (IIS), you can also use that IP address or host header as the value for this property.
Note The value of this property is displayed in the Virtual Server List in SharePoint Central Administration.

-urlzone Specifies which one of the five zones with which the outgoing URL is associated. The possible values for this property are: default, internet, intranet, extranet, or custom.
-incomingurl URL for any requests that come from the reverse proxy server or client to the Web server. You can map multiple incoming URLs to the same URL zone.


//Bart

http://sharepointblogs.com/bart