• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1153
  • Last Modified:

IIS 6.0 : host header not being recognised - default website displayed instead

I have SBS 2003 SP1
IIS 6.0
I have created a new website (SharePoint 3) and it appears in IIS
I've created an entry at my ISP of library.mydomain.com and pointed it to my public IP
My router forwards all port 80 traffic on to 192.168.1.2 (my SBS box)
in IIS I've added a host header value of library.mydomain.com and an SSL port of 10444 (http port is 80)
However, when I type https://library.mydomain.com I get a 403.6 error, becuase I'm being directed to the default website which has all but 192.168.1.2 and 127.0.0.1 denied.
Therefore looks like the host header value is being ignored.
What am I doing wrong?

0
ComputerFundi
Asked:
ComputerFundi
1 Solution
 
chuckyhCommented:
Have you tried https://library.mydomain.com:10444 ?
0
 
ComputerFundiAuthor Commented:
that gives me a 404 - page not found
0
 
CGI_PortalPracticeCommented:
Try running the excluder utility on the server:

"C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN\stsadm.exe" -o addpath -url https://library.mydomain.com -type exclusion

The same functionality can be done in the SharePoint Central Administration by excluding the path.
0
 
ComputerFundiAuthor Commented:
This question is being closed ... transferred question to previous associated question here ...
http://www.experts-exchange.com/Software/Server_Software/Web_Servers/Microsoft_IIS/Q_22580236.html
0
 
navyjax2Commented:
SSL has to run under port 443, and to accomplish this onto a SharePoint site you have to do a few things:

When you create the Web Application, you have to assign a host header, tell it to use port 443, and use SSL.  If you didn't do that before, you can delete the existing Web App, but leave the Content Database.  You can re-create a Web App and point it to that same Content DB and you'll be fine - it will not overwrite the content with new content.

When it completes, insert the certificate into the Web App under the Directory Security tab of the Web Application's properties in IIS, tell it to "Require secure channel (SSL)" and "Require 128-bit encryption".  You have to put in a host header into the Web Application's "Web Site" tab, Advanced button section.  Edit the port 80 instance (trust me) and add the name of your host header you put in the Web App config from within SharePoint when you were creating the Web App.

After you've clicked all of your OKs, go to the "Web Sites" folder in the directory structure of IIS.  Find the identification number of your web app.

Open a command window.  Navigate to C:\inetpub\AdminScripts.  Type this:

cscript.exe adsutil.vbs set /w3svc/ID_number_you_were_supposed_to_find/SecureBindings ":443:myhostheader.domain.com"

but, of course, replace the applicable stuff.

You should be good after all that.

-Tom
0

Featured Post

Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now