Problem with multiple web sites

I have a Windows 2003 server running IIS 6 and WSUS
Wanted to add another web site to be hosted on that machine
Used IIS manager and added additional web site
Am differentiating web sites via host names . ip address are all assigned
and tcp port is 80
WSUS still works by typing in http://strouddomain2/wsusadmin
If I type in http://192.168.7.180 I get page under construction
Home directory is pointing in the right direction
I'm figuring it's a DNS problem but frankly don't know how to add the proper
record to DNS so that this second web site can be seen.
Can anyone help?

"LibbyStew" <LibbyStew@discussions.microsoft.com> wrote in message
news:2A580D70-8B43-4F8F-ADE8-8D189E5681D3@microsoft.com...
> I have a Windows 2003 server running IIS 6 and WSUS
> Wanted to add another web site to be hosted on that machine
> Used IIS manager and added additional web site
> Am differentiating web sites via host names . ip address are all assigned
> and tcp port is 80
> WSUS still works by typing in http://strouddomain2/wsusadmin
> If I type in http://192.168.7.180 I get page under construction
> Home directory is pointing in the right direction
> I'm figuring it's a DNS problem but frankly don't know how to add the
proper
> record to DNS so that this second web site can be seen.
> Can anyone help?

Since the second URL uses an IP address the problem isn't going to be DNS.

If have placed host header recognition on all your sites which site would
you expect the raw IP address to use? The Host header in the request will
be 192.168.7.180 but none of the sites will match that.

If a site can be identified uniquely by an IP address (your server may have
multiple IP addresses but the only that site uses that particular IP) then
remove the host header recognition from that site.

If you only have one IP address and you must identify each site by host
header and for some strange reason you need to access a site via the raw IP
address in the URL then add the IP address as a host header to the site to
which you would like requests directed to.




--
Anthony Jones - MVP ASP/ASP.NET

My server only has one ip address . . . 192.168.7.180. WSUS was installed
first on this server and is the "default web site". The second web site is
only an intranet and when I first added it I didn't give it any unique
identifier. The identifiers were the same for both sites.
Then I read about the host header and I designated the host header field to
be "intranet" for the intranet site and I left the WSUS blank. Can access
WSUS but not the intranet. Previous intranet on another server by itself was
accessed by typing in the ip address . . . that's why I did it that way.
If I make the host header be the ip address, the WSUS site doesn't work and
neither does the intranet site.
Sorry but I'm not well versed on this but appreciate your suggestion.

"Anthony Jones" wrote:

> "LibbyStew" <LibbyStew@discussions.microsoft.com> wrote in message
> news:2A580D70-8B43-4F8F-ADE8-8D189E5681D3@microsoft.com...
> > I have a Windows 2003 server running IIS 6 and WSUS
> > Wanted to add another web site to be hosted on that machine
> > Used IIS manager and added additional web site
> > Am differentiating web sites via host names . ip address are all assigned
> > and tcp port is 80
> > WSUS still works by typing in http://strouddomain2/wsusadmin
> > If I type in http://192.168.7.180 I get page under construction
> > Home directory is pointing in the right direction
> > I'm figuring it's a DNS problem but frankly don't know how to add the
> proper
> > record to DNS so that this second web site can be seen.
> > Can anyone help?
>
> Since the second URL uses an IP address the problem isn't going to be DNS.
>
> If have placed host header recognition on all your sites which site would
> you expect the raw IP address to use? The Host header in the request will
> be 192.168.7.180 but none of the sites will match that.
>
> If a site can be identified uniquely by an IP address (your server may have
> multiple IP addresses but the only that site uses that particular IP) then
> remove the host header recognition from that site.
>
> If you only have one IP address and you must identify each site by host
> header and for some strange reason you need to access a site via the raw IP
> address in the URL then add the IP address as a host header to the site to
> which you would like requests directed to.
>
>
>
>
> --
> Anthony Jones - MVP ASP/ASP.NET
>
>
>

problem solved: removed host header and differentiated web sites on same
machine via port. wsus web site uses port 80; intranet uses port 81. you
can now access the intranet via your browser by typing in
http://strouddomain2:81



"LibbyStew" wrote:

> My server only has one ip address . . . 192.168.7.180. WSUS was installed
> first on this server and is the "default web site". The second web site is
> only an intranet and when I first added it I didn't give it any unique
> identifier. The identifiers were the same for both sites.
> Then I read about the host header and I designated the host header field to
> be "intranet" for the intranet site and I left the WSUS blank. Can access
> WSUS but not the intranet. Previous intranet on another server by itself was
> accessed by typing in the ip address . . . that's why I did it that way.
> If I make the host header be the ip address, the WSUS site doesn't work and
> neither does the intranet site.
> Sorry but I'm not well versed on this but appreciate your suggestion.
>
> "Anthony Jones" wrote:
>
> > "LibbyStew" <LibbyStew@discussions.microsoft.com> wrote in message
> > news:2A580D70-8B43-4F8F-ADE8-8D189E5681D3@microsoft.com...
> > > I have a Windows 2003 server running IIS 6 and WSUS
> > > Wanted to add another web site to be hosted on that machine
> > > Used IIS manager and added additional web site
> > > Am differentiating web sites via host names . ip address are all assigned
> > > and tcp port is 80
> > > WSUS still works by typing in http://strouddomain2/wsusadmin
> > > If I type in http://192.168.7.180 I get page under construction
> > > Home directory is pointing in the right direction
> > > I'm figuring it's a DNS problem but frankly don't know how to add the
> > proper
> > > record to DNS so that this second web site can be seen.
> > > Can anyone help?
> >
> > Since the second URL uses an IP address the problem isn't going to be DNS.
> >
> > If have placed host header recognition on all your sites which site would
> > you expect the raw IP address to use? The Host header in the request will
> > be 192.168.7.180 but none of the sites will match that.
> >
> > If a site can be identified uniquely by an IP address (your server may have
> > multiple IP addresses but the only that site uses that particular IP) then
> > remove the host header recognition from that site.
> >
> > If you only have one IP address and you must identify each site by host
> > header and for some strange reason you need to access a site via the raw IP
> > address in the URL then add the IP address as a host header to the site to
> > which you would like requests directed to.
> >
> >
> >
> >
> > --
> > Anthony Jones - MVP ASP/ASP.NET
> >
> >
> >