Re: ISS problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 07/08/04


Date: Thu, 8 Jul 2004 03:04:08 -0700

It sounds like you are running Small Business Server. If so, please post
your question to:
microsoft.public.windows.server.sbs

IIS will keep backup copies of its configuration (check in the IIS Manager
UI for this). If it hasn't aged-off already, it can help you revert your
changes.

Otherwise, you probably need to reinstall the server to obtain those
settings again, and remember to back up your IIS settings this time before
you go and mess up your websites. Read IIS help (maybe SBS help includes
this as well) on how to do this.

Now, you should realize that "Default Web Site" is geared toward the
external facing interface (i.e. it's got Exchange, OWA, etc), while the
"Companyweb" is geared toward the internal facing interface (it's got
Sharepoint on it). Since they are independent websites, you need to make
sure that both websites do NOT share the same IP, Port, and Host header.
Default installation will make sure they are different.

In other words, it is impossible to have DWS and "companyweb" to both listen
to port 80 on the same IP with the same host header. If you configure this,
you will see an error in the event log and one of the websites won't run.

If your server has one network card (so you only have one IP), the only way
you can have both websites listen on port 80 is to use Host header. One or
both websites need to have a Host header -- they cannot both have NO host
header.

If your server has two or more network cards (so you can have two or more
IPs), you can have either website listening on port 80 with no Host headers
for DIFFERENT IPs.

-- 
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Marcus" <msn@msn.com> wrote in message
news:ObhHDFGZEHA.3944@tk2msftngp13.phx.gbl...
Hi
I have messed up my web sites in IIS and need the original settings for
"Default web Site (DWS)" and "companyweb".
I think its somthing with the ports ?
If i put my "companyweb" on port 80 then i can not connect to the "DWS" for
example the OWA, and vice versa.
Can anyone help me with the original settings to get both the DWS and
companyweb to work together ?
Thanks


Relevant Pages

  • Re: DNS or IIS issue?
    ... the advanced tab in IIS than the CNAME in DNS. ... your server administrator." ... >>default Host header value and created a new one with the ...
    (microsoft.public.inetserver.iis)
  • Re: Maximum subwebs on Windows 2003/IIS6 web server
    ... IIS 6.0 should not have this. ... I have not tried running this many websites on a single server, ... encounter any limitations with subwebs numbering in the thousands as far as ...
    (microsoft.public.windows.server.setup)
  • Re: IIS 6 SLOW response. Reboot needed.
    ... Moved over a few websites that use Access to a brand new more powerful W2K3 ... server from a W2K server. ... 'ASP unhealthy because 100% of executing requests ... > IISRESET or restarting IIS does, except it's better in that connections ...
    (microsoft.public.inetserver.iis)
  • Re: IIS Stopped working properly.
    ... SBS 2003 brings a full working IIS, and it even includes some default websites like the Remote Web Workplace or the Outlook Web Access that are meant to be used from the outside. ... You can easilly configure other websites and publish them to be access from the outside, despite the advised action would be having another server inside running IIS and having the SBS 2003 machine forwarding these extra webistes requests to it. ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS 6.0 - no host header value - Are host header requests proc
    ... The packets may not be malformed - it may be that the end client is using a DNS server that is incorrectly configured. ... In the case that a request comes in with a host header that matches none of the websites on your machine, then IIS will look for a site that is listening with no host header value *and* specifically bound to the IP address that the request came in on. ...
    (microsoft.public.inetserver.iis.security)