Both websites using port 80 in IIS
I have two programs that created websites in IIS. One was created in default and the other made its own site. Only one can run at a time because they are both set to use port 80. How can I get both sites to run so that people can access the information the programs put out?
Lee W, MVP
Provide different names for them - using Host Header files. For Example, create "Website1" and "Website2" in your DNS. Then put those names in as the host headers, one for each.
some references:
http://www.visualwin.com/host-header/
http://support.microsoft.com/default.aspx?scid=kb;en-us;308163
And of course, you can always change the port on one site and then you'd have to access it by entering:
http://server.domain.com:xxxx/ where xxxx is a different port number (people often use port 8080 or 8888)
http://www.visualwin.com/host-header/
http://support.microsoft.com/default.aspx?scid=kb;en-us;308163
And of course, you can always change the port on one site and then you'd have to access it by entering:
http://server.domain.com:xxxx/ where xxxx is a different port number (people often use port 8080 or 8888)
ASKER
I read in one of the articles that it is not wise to use host headers in the default website. So should I take the files and move them to another new site?
What if DNS is not running on the internal LAN. Can this still be done?
What if DNS is not running on the internal LAN. Can this still be done?
you can create another website(s) that is not the default
apply host headers to that
for example where it shows default web (this you don't touch)
create a brand new for your immediate host
www.mydomain.com (then use host headers.. .make sure you have at least 2 entries, www.mydomain.com, and mydomain.com)
next, create your secondary site
www.mydomain2.com (host headers.... www.mydomain2.com, & mydomain.com)
It would be best to have DNS running. Else, you will have to tell your upstream provider to point to you and you need to offer them your configuration
apply host headers to that
for example where it shows default web (this you don't touch)
create a brand new for your immediate host
www.mydomain.com (then use host headers.. .make sure you have at least 2 entries, www.mydomain.com, and mydomain.com)
next, create your secondary site
www.mydomain2.com (host headers.... www.mydomain2.com, & mydomain.com)
It would be best to have DNS running. Else, you will have to tell your upstream provider to point to you and you need to offer them your configuration
It depends on what else the server is hosting - if you are running Exchange and OWA, then use, it's not wise. But if the only web services your running are these two programs, it's fine.
And you CAN simply assign ONE web site with host headers and leave the other blank with no headers defined. If you request the header based site, it will respond. If you don't the default site will respond. So only one site needs to have host headers configured.
You would need a DNS server for this - or you could setup a manual hosts file on each machine. Do you have a windows domain?
And you CAN simply assign ONE web site with host headers and leave the other blank with no headers defined. If you request the header based site, it will respond. If you don't the default site will respond. So only one site needs to have host headers configured.
You would need a DNS server for this - or you could setup a manual hosts file on each machine. Do you have a windows domain?
ASKER
Yes but I dont use the DNS because the machine is hooked up to 3 differeent networks.
What does that have do to with it?
Do you use a Windows 2003 or 2000 domain? If so, you MUST use DNS - there's no option in it. Active Directory requires DNS. Besides, ultimately, it makes little difference to the web server. In the past I've had my servers in 3 different DNS servers with 3 different names on each of the DNS servers - Why don't you want to setup something in DNS? IT's the only way short of changing the port. Perhaps you are not understanding how DNS works?
Do you use a Windows 2003 or 2000 domain? If so, you MUST use DNS - there's no option in it. Active Directory requires DNS. Besides, ultimately, it makes little difference to the web server. In the past I've had my servers in 3 different DNS servers with 3 different names on each of the DNS servers - Why don't you want to setup something in DNS? IT's the only way short of changing the port. Perhaps you are not understanding how DNS works?
ASKER
Ok I guess I am not getting it. If I have two sites in IIS that are using the same port number it will only start one of them.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.