I want to use an existing Web server. We only have about 5 people who use Secure Gateway. So load won't be an issue and dedicating a server for this is a total waste of resources. On Thu, Jun 26, 2008 at 1:54 PM, Russell Robertson < russell@xxxxxxxxxxxxxxxxxxx> wrote: > Cherie > > > > You have to be careful with SSL and using host headers if hosting more than > one site on IIS. I think functionality for this in IIS 6.0 works but > haven't tried it. We tend to recommend using a single server for CSG/WI. > > > > Why do you want to avoid using the Default site? > > > > Thanks > > > > Russell > > *Russell Robertson* | Virtual Stream | www.virtualstream.co.uk > > > > > > > > *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On > Behalf Of *cherie.watts Watts > *Sent:* 26 June 2008 12:46 > *To:* thin@xxxxxxxxxxxxx > *Subject:* [THIN] Secure Gateway 3.0 and Web Interface 3.5.1 question > > > > Hi Everyone > > > > I have just about driven myself crazy trying to configure these. > > > > I have no problems connecting with Secure Gateway if Web Interface is > installed into the Default website on the IIS server. But if I create it in > a new website in IIS and set Web Interface site etc... This all works from > the Web Interface links. But Secure Gateway persists in opening the > iistart.htm in the default website. > > > > I am not sure if it is a config problem in Web Interface or Secure > Gateway.. > > > > What am I doing wrong or not doing?? Please help > > > > Thanks > > Cherie >