Can"t Run multiple web sites on IIS 6???

Hello,

Sorry, completely frustrated with IIS. I'm not sure why, but I'm finding it
impossible to run multiple web site on my server. The sites are for my own
internal Intranet use, not exposed to the world.

I have read all the help files on using Ports, IP, or host names.

I did not want to use different ports, to hard for employees to remember
port numbers.

Do not want to use different IP'S for same reason.

That leaves me with HOST HEADERS and totally confussed.

I need to mess with DNS to use these I quess and this is where it falls apart.

I do not have my DNS set to my REAL web domain name, I simply used
COMPANY.local in my DNS.

How do I run multiple sites with this? COMPANY.local is not a FULLY
QUALIFIED DOMAIN NAME registered with a domain registrar!

If I use COMPANY.local how do I format the Host headers and what url will my
users need to enter to get to the different sites?

WHat about multiple virtual sites withing a single site? What URL will they
need?

Do I need to change the ports still so I don't get the "can't use the same
port for multiple sites" message?

Thanks much,

Mark

Re: Can"t Run multiple web sites on IIS 6???

"Mrpush" wrote in message
news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
> Hello,
>
> Sorry, completely frustrated with IIS. I'm not sure why, but I'm finding
> it
> impossible to run multiple web site on my server. The sites are for my
> own
> internal Intranet use, not exposed to the world.
>
> I have read all the help files on using Ports, IP, or host names.
>
> I did not want to use different ports, to hard for employees to remember
> port numbers.
>
> Do not want to use different IP'S for same reason.
>
> That leaves me with HOST HEADERS and totally confussed.
>
> I need to mess with DNS to use these I quess and this is where it falls
> apart.
>
> I do not have my DNS set to my REAL web domain name, I simply used
> COMPANY.local in my DNS.

That's OK.


> How do I run multiple sites with this? COMPANY.local is not a FULLY
> QUALIFIED DOMAIN NAME registered with a domain registrar!

Not required.

On your private DNS server, in the company.local forward lookup zone, add
additional hosts, e.g

A record: server1 -> xx.xx.xx.xx (where xx.xx.xx.xx is the IP address of
your IIS server)
CNAME record app1 -> server1
CNAME record app2 -> server1
CNAME record www -> server1
CNAME record justForLaughs -> server1

As long as your client machines are configured to use your private DNS
server, then they will be able to resolve: server1.company.local,
app1.company.local, app2.company.local etc

This part has nothing to do with IIS. It is simply name resolution.

> If I use COMPANY.local how do I format the Host headers and what url will
> my
> users need to enter to get to the different sites?

To get to the above websites, you would configure multiple websites in IIS.

The first website would have the host header value: server1.company.local
The second website would have the host header value: app1.company.local
The third website would have the host header value: app2.company.local

You get the idea?


> WHat about multiple virtual sites withing a single site? What URL will
> they
> need?

You can't have "multiple virtual sites within a single site". A virtual site
is a standalone website.

What exactly are you trying to describe here?

> Do I need to change the ports still so I don't get the "can't use the same
> port for multiple sites" message?

Each website must have a unique combination of IP address + port + host
header. If you want to resue the same IP address and port (port 80), then
each site must have a unique host header value.

Cheers
Ken

>
> Thanks much,
>
> Mark

Re: Can"t Run multiple web sites on IIS 6???

Ken,

Thanks for the quick reply. I appreciate it.

I think I have already treid this, but I will follow your lead here.

As for the virtual sites, I really mean virtual directories. I have a
single site in IIS named Portals, and it has several of the "yellow gears"
under it, all which have different web apps and sites "in" them that all have
worked.

They all run ok from with in the single site.

I'm setting up these new sites for WSS and I'm having all kind of permission
issues as well. It has to do with URL and Kerberos / NTLM not sure what is
wrong there.

I'll try these DNS settings and let you know.

Thanks much,

Mark


"Ken Schaefer" wrote:

>
> "Mrpush" wrote in message
> news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
> > Hello,
> >
> > Sorry, completely frustrated with IIS. I'm not sure why, but I'm finding
> > it
> > impossible to run multiple web site on my server. The sites are for my
> > own
> > internal Intranet use, not exposed to the world.
> >
> > I have read all the help files on using Ports, IP, or host names.
> >
> > I did not want to use different ports, to hard for employees to remember
> > port numbers.
> >
> > Do not want to use different IP'S for same reason.
> >
> > That leaves me with HOST HEADERS and totally confussed.
> >
> > I need to mess with DNS to use these I quess and this is where it falls
> > apart.
> >
> > I do not have my DNS set to my REAL web domain name, I simply used
> > COMPANY.local in my DNS.
>
> That's OK.
>
>
> > How do I run multiple sites with this? COMPANY.local is not a FULLY
> > QUALIFIED DOMAIN NAME registered with a domain registrar!
>
> Not required.
>
> On your private DNS server, in the company.local forward lookup zone, add
> additional hosts, e.g
>
> A record: server1 -> xx.xx.xx.xx (where xx.xx.xx.xx is the IP address of
> your IIS server)
> CNAME record app1 -> server1
> CNAME record app2 -> server1
> CNAME record www -> server1
> CNAME record justForLaughs -> server1
>
> As long as your client machines are configured to use your private DNS
> server, then they will be able to resolve: server1.company.local,
> app1.company.local, app2.company.local etc
>
> This part has nothing to do with IIS. It is simply name resolution.
>
> > If I use COMPANY.local how do I format the Host headers and what url will
> > my
> > users need to enter to get to the different sites?
>
> To get to the above websites, you would configure multiple websites in IIS.
>
> The first website would have the host header value: server1.company.local
> The second website would have the host header value: app1.company.local
> The third website would have the host header value: app2.company.local
>
> You get the idea?
>
>
> > WHat about multiple virtual sites withing a single site? What URL will
> > they
> > need?
>
> You can't have "multiple virtual sites within a single site". A virtual site
> is a standalone website.
>
> What exactly are you trying to describe here?
>
> > Do I need to change the ports still so I don't get the "can't use the same
> > port for multiple sites" message?
>
> Each website must have a unique combination of IP address + port + host
> header. If you want to resue the same IP address and port (port 80), then
> each site must have a unique host header value.
>
> Cheers
> Ken
>
> >
> > Thanks much,
> >
> > Mark
>
>

Re: Can"t Run multiple web sites on IIS 6???

Sorry, but this is just becoming more confusing.

If you are running multiple applications underneath a single website, then
DNS has nothing to do with this.

All DNS does is map a FQDN (e.g. someHost.yourcompany.local) to an IP
address. It has nothing to do with the files, and folders located within
that FQDN.

Now you start mentioning WSS. What does WSS have to do with all of this?

> I'll try these DNS settings and let you know.

NO!!

Do not start making random changes to things that you don't have a firm
grasp of. You'll just break more things than you fix.

Please detail *exactly* what you are trying to accomplish so that the
correct direction can be given.

Cheers
Ken


"Mrpush" wrote in message
news:7822B653-15D9-4690-9574-BC04E24654DD@microsoft.com...
> Ken,
>
> Thanks for the quick reply. I appreciate it.
>
> I think I have already treid this, but I will follow your lead here.
>
> As for the virtual sites, I really mean virtual directories. I have a
> single site in IIS named Portals, and it has several of the "yellow gears"
> under it, all which have different web apps and sites "in" them that all
> have
> worked.
>
> They all run ok from with in the single site.
>
> I'm setting up these new sites for WSS and I'm having all kind of
> permission
> issues as well. It has to do with URL and Kerberos / NTLM not sure what
> is
> wrong there.
>
> I'll try these DNS settings and let you know.
>
> Thanks much,
>
> Mark
>
>
> "Ken Schaefer" wrote:
>
>>
>> "Mrpush" wrote in message
>> news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
>> > Hello,
>> >
>> > Sorry, completely frustrated with IIS. I'm not sure why, but I'm
>> > finding
>> > it
>> > impossible to run multiple web site on my server. The sites are for my
>> > own
>> > internal Intranet use, not exposed to the world.
>> >
>> > I have read all the help files on using Ports, IP, or host names.
>> >
>> > I did not want to use different ports, to hard for employees to
>> > remember
>> > port numbers.
>> >
>> > Do not want to use different IP'S for same reason.
>> >
>> > That leaves me with HOST HEADERS and totally confussed.
>> >
>> > I need to mess with DNS to use these I quess and this is where it falls
>> > apart.
>> >
>> > I do not have my DNS set to my REAL web domain name, I simply used
>> > COMPANY.local in my DNS.
>>
>> That's OK.
>>
>>
>> > How do I run multiple sites with this? COMPANY.local is not a FULLY
>> > QUALIFIED DOMAIN NAME registered with a domain registrar!
>>
>> Not required.
>>
>> On your private DNS server, in the company.local forward lookup zone, add
>> additional hosts, e.g
>>
>> A record: server1 -> xx.xx.xx.xx (where xx.xx.xx.xx is the IP address
>> of
>> your IIS server)
>> CNAME record app1 -> server1
>> CNAME record app2 -> server1
>> CNAME record www -> server1
>> CNAME record justForLaughs -> server1
>>
>> As long as your client machines are configured to use your private DNS
>> server, then they will be able to resolve: server1.company.local,
>> app1.company.local, app2.company.local etc
>>
>> This part has nothing to do with IIS. It is simply name resolution.
>>
>> > If I use COMPANY.local how do I format the Host headers and what url
>> > will
>> > my
>> > users need to enter to get to the different sites?
>>
>> To get to the above websites, you would configure multiple websites in
>> IIS.
>>
>> The first website would have the host header value: server1.company.local
>> The second website would have the host header value: app1.company.local
>> The third website would have the host header value: app2.company.local
>>
>> You get the idea?
>>
>>
>> > WHat about multiple virtual sites withing a single site? What URL will
>> > they
>> > need?
>>
>> You can't have "multiple virtual sites within a single site". A virtual
>> site
>> is a standalone website.
>>
>> What exactly are you trying to describe here?
>>
>> > Do I need to change the ports still so I don't get the "can't use the
>> > same
>> > port for multiple sites" message?
>>
>> Each website must have a unique combination of IP address + port + host
>> header. If you want to resue the same IP address and port (port 80), then
>> each site must have a unique host header value.
>>
>> Cheers
>> Ken
>>
>> >
>> > Thanks much,
>> >
>> > Mark
>>
>>

Re: Can"t Run multiple web sites on IIS 6???

Ken,

I have a website in IIS that a few apps are under as I expalined.

They are using port 80.

I installed WSS 3.0. Install suggestions said to install it with its own
App pool and to create a new site for it to run it in IIS.

With more than one site, I now must some how differentiate the 2 sites so
they will run at the same time. I cannot have more then one site on port 80.

I have to dissable my existing app site to run the WSS sites on port 80.

Or, I need to change the app pool IP or Host name.

I don't want users to have to remember any numbers, so I'm opting for the
host header name.

To use this, it seems I have to add DNS entries.

I simple need to be able to run more than one site at a time using Host
Headers, and had no ides how to set them up.

That is really it.

Thanks,

Mark








"Ken Schaefer" wrote:

> Sorry, but this is just becoming more confusing.
>
> If you are running multiple applications underneath a single website, then
> DNS has nothing to do with this.
>
> All DNS does is map a FQDN (e.g. someHost.yourcompany.local) to an IP
> address. It has nothing to do with the files, and folders located within
> that FQDN.
>
> Now you start mentioning WSS. What does WSS have to do with all of this?
>
> > I'll try these DNS settings and let you know.
>
> NO!!
>
> Do not start making random changes to things that you don't have a firm
> grasp of. You'll just break more things than you fix.
>
> Please detail *exactly* what you are trying to accomplish so that the
> correct direction can be given.
>
> Cheers
> Ken
>
>
> "Mrpush" wrote in message
> news:7822B653-15D9-4690-9574-BC04E24654DD@microsoft.com...
> > Ken,
> >
> > Thanks for the quick reply. I appreciate it.
> >
> > I think I have already treid this, but I will follow your lead here.
> >
> > As for the virtual sites, I really mean virtual directories. I have a
> > single site in IIS named Portals, and it has several of the "yellow gears"
> > under it, all which have different web apps and sites "in" them that all
> > have
> > worked.
> >
> > They all run ok from with in the single site.
> >
> > I'm setting up these new sites for WSS and I'm having all kind of
> > permission
> > issues as well. It has to do with URL and Kerberos / NTLM not sure what
> > is
> > wrong there.
> >
> > I'll try these DNS settings and let you know.
> >
> > Thanks much,
> >
> > Mark
> >
> >
> > "Ken Schaefer" wrote:
> >
> >>
> >> "Mrpush" wrote in message
> >> news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
> >> > Hello,
> >> >
> >> > Sorry, completely frustrated with IIS. I'm not sure why, but I'm
> >> > finding
> >> > it
> >> > impossible to run multiple web site on my server. The sites are for my
> >> > own
> >> > internal Intranet use, not exposed to the world.
> >> >
> >> > I have read all the help files on using Ports, IP, or host names.
> >> >
> >> > I did not want to use different ports, to hard for employees to
> >> > remember
> >> > port numbers.
> >> >
> >> > Do not want to use different IP'S for same reason.
> >> >
> >> > That leaves me with HOST HEADERS and totally confussed.
> >> >
> >> > I need to mess with DNS to use these I quess and this is where it falls
> >> > apart.
> >> >
> >> > I do not have my DNS set to my REAL web domain name, I simply used
> >> > COMPANY.local in my DNS.
> >>
> >> That's OK.
> >>
> >>
> >> > How do I run multiple sites with this? COMPANY.local is not a FULLY
> >> > QUALIFIED DOMAIN NAME registered with a domain registrar!
> >>
> >> Not required.
> >>
> >> On your private DNS server, in the company.local forward lookup zone, add
> >> additional hosts, e.g
> >>
> >> A record: server1 -> xx.xx.xx.xx (where xx.xx.xx.xx is the IP address
> >> of
> >> your IIS server)
> >> CNAME record app1 -> server1
> >> CNAME record app2 -> server1
> >> CNAME record www -> server1
> >> CNAME record justForLaughs -> server1
> >>
> >> As long as your client machines are configured to use your private DNS
> >> server, then they will be able to resolve: server1.company.local,
> >> app1.company.local, app2.company.local etc
> >>
> >> This part has nothing to do with IIS. It is simply name resolution.
> >>
> >> > If I use COMPANY.local how do I format the Host headers and what url
> >> > will
> >> > my
> >> > users need to enter to get to the different sites?
> >>
> >> To get to the above websites, you would configure multiple websites in
> >> IIS.
> >>
> >> The first website would have the host header value: server1.company.local
> >> The second website would have the host header value: app1.company.local
> >> The third website would have the host header value: app2.company.local
> >>
> >> You get the idea?
> >>
> >>
> >> > WHat about multiple virtual sites withing a single site? What URL will
> >> > they
> >> > need?
> >>
> >> You can't have "multiple virtual sites within a single site". A virtual
> >> site
> >> is a standalone website.
> >>
> >> What exactly are you trying to describe here?
> >>
> >> > Do I need to change the ports still so I don't get the "can't use the
> >> > same
> >> > port for multiple sites" message?
> >>
> >> Each website must have a unique combination of IP address + port + host
> >> header. If you want to resue the same IP address and port (port 80), then
> >> each site must have a unique host header value.
> >>
> >> Cheers
> >> Ken
> >>
> >> >
> >> > Thanks much,
> >> >
> >> > Mark
> >>
> >>
>
>

Re: Can"t Run multiple web sites on IIS 6???

Ken,

One of my other issues is URL's with the sites.

I'd like my WSS site to be accessed with:

http://MyIntranetName

Instead of:

http://MyWebServer/default.aspx

Do I do this in IIS alone or do I need add to the DNS as well?

I believe I need to do something in WSS as well here?

Thanks much,

Mark




"Ken Schaefer" wrote:

> Sorry, but this is just becoming more confusing.
>
> If you are running multiple applications underneath a single website, then
> DNS has nothing to do with this.
>
> All DNS does is map a FQDN (e.g. someHost.yourcompany.local) to an IP
> address. It has nothing to do with the files, and folders located within
> that FQDN.
>
> Now you start mentioning WSS. What does WSS have to do with all of this?
>
> > I'll try these DNS settings and let you know.
>
> NO!!
>
> Do not start making random changes to things that you don't have a firm
> grasp of. You'll just break more things than you fix.
>
> Please detail *exactly* what you are trying to accomplish so that the
> correct direction can be given.
>
> Cheers
> Ken
>
>
> "Mrpush" wrote in message
> news:7822B653-15D9-4690-9574-BC04E24654DD@microsoft.com...
> > Ken,
> >
> > Thanks for the quick reply. I appreciate it.
> >
> > I think I have already treid this, but I will follow your lead here.
> >
> > As for the virtual sites, I really mean virtual directories. I have a
> > single site in IIS named Portals, and it has several of the "yellow gears"
> > under it, all which have different web apps and sites "in" them that all
> > have
> > worked.
> >
> > They all run ok from with in the single site.
> >
> > I'm setting up these new sites for WSS and I'm having all kind of
> > permission
> > issues as well. It has to do with URL and Kerberos / NTLM not sure what
> > is
> > wrong there.
> >
> > I'll try these DNS settings and let you know.
> >
> > Thanks much,
> >
> > Mark
> >
> >
> > "Ken Schaefer" wrote:
> >
> >>
> >> "Mrpush" wrote in message
> >> news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
> >> > Hello,
> >> >
> >> > Sorry, completely frustrated with IIS. I'm not sure why, but I'm
> >> > finding
> >> > it
> >> > impossible to run multiple web site on my server. The sites are for my
> >> > own
> >> > internal Intranet use, not exposed to the world.
> >> >
> >> > I have read all the help files on using Ports, IP, or host names.
> >> >
> >> > I did not want to use different ports, to hard for employees to
> >> > remember
> >> > port numbers.
> >> >
> >> > Do not want to use different IP'S for same reason.
> >> >
> >> > That leaves me with HOST HEADERS and totally confussed.
> >> >
> >> > I need to mess with DNS to use these I quess and this is where it falls
> >> > apart.
> >> >
> >> > I do not have my DNS set to my REAL web domain name, I simply used
> >> > COMPANY.local in my DNS.
> >>
> >> That's OK.
> >>
> >>
> >> > How do I run multiple sites with this? COMPANY.local is not a FULLY
> >> > QUALIFIED DOMAIN NAME registered with a domain registrar!
> >>
> >> Not required.
> >>
> >> On your private DNS server, in the company.local forward lookup zone, add
> >> additional hosts, e.g
> >>
> >> A record: server1 -> xx.xx.xx.xx (where xx.xx.xx.xx is the IP address
> >> of
> >> your IIS server)
> >> CNAME record app1 -> server1
> >> CNAME record app2 -> server1
> >> CNAME record www -> server1
> >> CNAME record justForLaughs -> server1
> >>
> >> As long as your client machines are configured to use your private DNS
> >> server, then they will be able to resolve: server1.company.local,
> >> app1.company.local, app2.company.local etc
> >>
> >> This part has nothing to do with IIS. It is simply name resolution.
> >>
> >> > If I use COMPANY.local how do I format the Host headers and what url
> >> > will
> >> > my
> >> > users need to enter to get to the different sites?
> >>
> >> To get to the above websites, you would configure multiple websites in
> >> IIS.
> >>
> >> The first website would have the host header value: server1.company.local
> >> The second website would have the host header value: app1.company.local
> >> The third website would have the host header value: app2.company.local
> >>
> >> You get the idea?
> >>
> >>
> >> > WHat about multiple virtual sites withing a single site? What URL will
> >> > they
> >> > need?
> >>
> >> You can't have "multiple virtual sites within a single site". A virtual
> >> site
> >> is a standalone website.
> >>
> >> What exactly are you trying to describe here?
> >>
> >> > Do I need to change the ports still so I don't get the "can't use the
> >> > same
> >> > port for multiple sites" message?
> >>
> >> Each website must have a unique combination of IP address + port + host
> >> header. If you want to resue the same IP address and port (port 80), then
> >> each site must have a unique host header value.
> >>
> >> Cheers
> >> Ken
> >>
> >> >
> >> > Thanks much,
> >> >
> >> > Mark
> >>
> >>
>
>

Re: Can"t Run multiple web sites on IIS 6???

"Mrpush" wrote in message
news:69FA35E6-C1A8-4005-B839-64B9CD3D386D@microsoft.com...
> Ken,
>
> One of my other issues is URL's with the sites.
>
> I'd like my WSS site to be accessed with:
>
> http://MyIntranetName
>
> Instead of:
>
> http://MyWebServer/default.aspx
>
> Do I do this in IIS alone or do I need add to the DNS as well?
>
> I believe I need to do something in WSS as well here?
>
> Thanks much,

You do that in the properties of the web, under "documents" there's a list
of default files.

Add "default.aspx" to the list (bump it to the top too). Then, when a
browser requests http://servername/ or http://servername/foldername/, if a
file called "default.aspx" is present, it will get sent back. Your users
can neglect to learn the file name, and you can skip it in hyperlinks then.
(I belive that "default.aspx" may already be present after install of some
later versions of .NET. But you should check to see if it is in there
nonetheless.)

Re: Can"t Run multiple web sites on IIS 6???

"Mrpush" wrote in message
news:7822B653-15D9-4690-9574-BC04E24654DD@microsoft.com...
> Ken,
>
> Thanks for the quick reply. I appreciate it.
>
> I think I have already treid this, but I will follow your lead here.

Good idea, I don't think you have an intuitive grasp of this stuff yet and
should stick to the "if then" rules people share with you.

>
> As for the virtual sites, I really mean virtual directories. I have a
> single site in IIS named Portals, and it has several of the "yellow gears"
> under it, all which have different web apps and sites "in" them that all
> have
> worked.

Virtual site IS VERY DIFFERENT THING than virtual directory.

Virtual Site (web) = Method for handling and serving up files and
applications from a server using a well defined set of settings.

Virtual Directory = literally, a folder on the "web server file system"
level that allows you to map the "web server file system" to the "disk file
system" in creative ways. Its sort of like a shortcut sitting on your
desktop, not really where the file is, but works to get you there when you
need it..

The problems you were describing earlier in the thread are related to and
RESTRICTED to a Virtual Site. Then you switched to something very different
here.

So you are working on two problems, my advice is just focus on the
connectivity issues first, then work on your apps once you have that figured
out.


>
> They all run ok from with in the single site.
>
> I'm setting up these new sites for WSS and I'm having all kind of
> permission
> issues as well. It has to do with URL and Kerberos / NTLM not sure what
> is
> wrong there.

That's a new problem, stop adding more to the mix.

>
> I'll try these DNS settings and let you know.
>
> Thanks much,
>
> Mark
>
>
> "Ken Schaefer" wrote:
>
>>
>> "Mrpush" wrote in message
>> news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
>> > Hello,
>> >
>> > Sorry, completely frustrated with IIS. I'm not sure why, but I'm
>> > finding
>> > it
>> > impossible to run multiple web site on my server. The sites are for my
>> > own
>> > internal Intranet use, not exposed to the world.
>> >
>> > I have read all the help files on using Ports, IP, or host names.
>> >
>> > I did not want to use different ports, to hard for employees to
>> > remember
>> > port numbers.
>> >
>> > Do not want to use different IP'S for same reason.
>> >
>> > That leaves me with HOST HEADERS and totally confussed.
>> >
>> > I need to mess with DNS to use these I quess and this is where it falls
>> > apart.
>> >
>> > I do not have my DNS set to my REAL web domain name, I simply used
>> > COMPANY.local in my DNS.
>>
>> That's OK.
>>
>>
>> > How do I run multiple sites with this? COMPANY.local is not a FULLY
>> > QUALIFIED DOMAIN NAME registered with a domain registrar!
>>
>> Not required.
>>
>> On your private DNS server, in the company.local forward lookup zone, add
>> additional hosts, e.g
>>
>> A record: server1 -> xx.xx.xx.xx (where xx.xx.xx.xx is the IP address
>> of
>> your IIS server)
>> CNAME record app1 -> server1
>> CNAME record app2 -> server1
>> CNAME record www -> server1
>> CNAME record justForLaughs -> server1
>>
>> As long as your client machines are configured to use your private DNS
>> server, then they will be able to resolve: server1.company.local,
>> app1.company.local, app2.company.local etc
>>
>> This part has nothing to do with IIS. It is simply name resolution.
>>
>> > If I use COMPANY.local how do I format the Host headers and what url
>> > will
>> > my
>> > users need to enter to get to the different sites?
>>
>> To get to the above websites, you would configure multiple websites in
>> IIS.
>>
>> The first website would have the host header value: server1.company.local
>> The second website would have the host header value: app1.company.local
>> The third website would have the host header value: app2.company.local
>>
>> You get the idea?
>>
>>
>> > WHat about multiple virtual sites withing a single site? What URL will
>> > they
>> > need?
>>
>> You can't have "multiple virtual sites within a single site". A virtual
>> site
>> is a standalone website.
>>
>> What exactly are you trying to describe here?
>>
>> > Do I need to change the ports still so I don't get the "can't use the
>> > same
>> > port for multiple sites" message?
>>
>> Each website must have a unique combination of IP address + port + host
>> header. If you want to resue the same IP address and port (port 80), then
>> each site must have a unique host header value.
>>
>> Cheers
>> Ken
>>
>> >
>> > Thanks much,
>> >
>> > Mark
>>
>>

Re: Can"t Run multiple web sites on IIS 6???

..._..,

I understand the actual page part, and that work fine. Its the server name
that I do not want in my URL.

With my WSS sites, it demands:

HTTP://MyWebServerName/and the rest of the url

I do not want the web server name in the url.

I want my users to simply type

"http://intranet"

for example to take me to the site.

How do I "mask" the url to do this?

Thanks much,

Mark




".._.." wrote:

>
> "Mrpush" wrote in message
> news:69FA35E6-C1A8-4005-B839-64B9CD3D386D@microsoft.com...
> > Ken,
> >
> > One of my other issues is URL's with the sites.
> >
> > I'd like my WSS site to be accessed with:
> >
> > http://MyIntranetName
> >
> > Instead of:
> >
> > http://MyWebServer/default.aspx
> >
> > Do I do this in IIS alone or do I need add to the DNS as well?
> >
> > I believe I need to do something in WSS as well here?
> >
> > Thanks much,
>
> You do that in the properties of the web, under "documents" there's a list
> of default files.
>
> Add "default.aspx" to the list (bump it to the top too). Then, when a
> browser requests http://servername/ or http://servername/foldername/, if a
> file called "default.aspx" is present, it will get sent back. Your users
> can neglect to learn the file name, and you can skip it in hyperlinks then.
> (I belive that "default.aspx" may already be present after install of some
> later versions of .NET. But you should check to see if it is in there
> nonetheless.)
>
>
>

Re: Can"t Run multiple web sites on IIS 6???

..._..,

I do not have a good handle yet, your are correct.

My connectivity problem is that when trying to access the WSS site (and now
also all my other sites since I installed WSS) it prompts me for username and
pass word for my web server every time.

It defults to webserver/administrator for the user name.

This however will not work and I need to change it to:

MyDoaminName/administrator

to get access.

Why is it prompting me to log in?

Thanks,

Mark


".._.." wrote:

>
> "Mrpush" wrote in message
> news:7822B653-15D9-4690-9574-BC04E24654DD@microsoft.com...
> > Ken,
> >
> > Thanks for the quick reply. I appreciate it.
> >
> > I think I have already treid this, but I will follow your lead here.
>
> Good idea, I don't think you have an intuitive grasp of this stuff yet and
> should stick to the "if then" rules people share with you.
>
> >
> > As for the virtual sites, I really mean virtual directories. I have a
> > single site in IIS named Portals, and it has several of the "yellow gears"
> > under it, all which have different web apps and sites "in" them that all
> > have
> > worked.
>
> Virtual site IS VERY DIFFERENT THING than virtual directory.
>
> Virtual Site (web) = Method for handling and serving up files and
> applications from a server using a well defined set of settings.
>
> Virtual Directory = literally, a folder on the "web server file system"
> level that allows you to map the "web server file system" to the "disk file
> system" in creative ways. Its sort of like a shortcut sitting on your
> desktop, not really where the file is, but works to get you there when you
> need it..
>
> The problems you were describing earlier in the thread are related to and
> RESTRICTED to a Virtual Site. Then you switched to something very different
> here.
>
> So you are working on two problems, my advice is just focus on the
> connectivity issues first, then work on your apps once you have that figured
> out.
>
>
> >
> > They all run ok from with in the single site.
> >
> > I'm setting up these new sites for WSS and I'm having all kind of
> > permission
> > issues as well. It has to do with URL and Kerberos / NTLM not sure what
> > is
> > wrong there.
>
> That's a new problem, stop adding more to the mix.
>
> >
> > I'll try these DNS settings and let you know.
> >
> > Thanks much,
> >
> > Mark
> >
> >
> > "Ken Schaefer" wrote:
> >
> >>
> >> "Mrpush" wrote in message
> >> news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
> >> > Hello,
> >> >
> >> > Sorry, completely frustrated with IIS. I'm not sure why, but I'm
> >> > finding
> >> > it
> >> > impossible to run multiple web site on my server. The sites are for my
> >> > own
> >> > internal Intranet use, not exposed to the world.
> >> >
> >> > I have read all the help files on using Ports, IP, or host names.
> >> >
> >> > I did not want to use different ports, to hard for employees to
> >> > remember
> >> > port numbers.
> >> >
> >> > Do not want to use different IP'S for same reason.
> >> >
> >> > That leaves me with HOST HEADERS and totally confussed.
> >> >
> >> > I need to mess with DNS to use these I quess and this is where it falls
> >> > apart.
> >> >
> >> > I do not have my DNS set to my REAL web domain name, I simply used
> >> > COMPANY.local in my DNS.
> >>
> >> That's OK.
> >>
> >>
> >> > How do I run multiple sites with this? COMPANY.local is not a FULLY
> >> > QUALIFIED DOMAIN NAME registered with a domain registrar!
> >>
> >> Not required.
> >>
> >> On your private DNS server, in the company.local forward lookup zone, add
> >> additional hosts, e.g
> >>
> >> A record: server1 -> xx.xx.xx.xx (where xx.xx.xx.xx is the IP address
> >> of
> >> your IIS server)
> >> CNAME record app1 -> server1
> >> CNAME record app2 -> server1
> >> CNAME record www -> server1
> >> CNAME record justForLaughs -> server1
> >>
> >> As long as your client machines are configured to use your private DNS
> >> server, then they will be able to resolve: server1.company.local,
> >> app1.company.local, app2.company.local etc
> >>
> >> This part has nothing to do with IIS. It is simply name resolution.
> >>
> >> > If I use COMPANY.local how do I format the Host headers and what url
> >> > will
> >> > my
> >> > users need to enter to get to the different sites?
> >>
> >> To get to the above websites, you would configure multiple websites in
> >> IIS.
> >>
> >> The first website would have the host header value: server1.company.local
> >> The second website would have the host header value: app1.company.local
> >> The third website would have the host header value: app2.company.local
> >>
> >> You get the idea?
> >>
> >>
> >> > WHat about multiple virtual sites withing a single site? What URL will
> >> > they
> >> > need?
> >>
> >> You can't have "multiple virtual sites within a single site". A virtual
> >> site
> >> is a standalone website.
> >>
> >> What exactly are you trying to describe here?
> >>
> >> > Do I need to change the ports still so I don't get the "can't use the
> >> > same
> >> > port for multiple sites" message?
> >>
> >> Each website must have a unique combination of IP address + port + host
> >> header. If you want to resue the same IP address and port (port 80), then
> >> each site must have a unique host header value.
> >>
> >> Cheers
> >> Ken
> >>
> >> >
> >> > Thanks much,
> >> >
> >> > Mark
> >>
> >>
>
>
>

Re: Can"t Run multiple web sites on IIS 6???

See answers interspersed.

"Mrpush" wrote in message
news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
> Hello,
>
> Sorry, completely frustrated with IIS. I'm not sure why, but I'm finding
> it
> impossible to run multiple web site on my server. The sites are for my
> own
> internal Intranet use, not exposed to the world.

That's fine, this will work the way you want. (It's not impossible to do, as
pretty much everybody posting here is doing it.)

>
> I have read all the help files on using Ports, IP, or host names.

Stop thinking about ports. Just stop. Do not add it to any troubleshooting
you do. They are not going to solve this problem and are just confusing
you.

>
> I did not want to use different ports, to hard for employees to remember
> port numbers.

See above.
>
> Do not want to use different IP'S for same reason.

That's ok, it can be done with 1 IP. I have one server running 74 sites on
the same IP address (these are outside, internet commercial sites). It's
simple to do once you know a few bits of information.

>
> That leaves me with HOST HEADERS and totally confussed.

Yup.

>
> I need to mess with DNS to use these I quess and this is where it falls
> apart.

You do need some DNS to do this. But it's not hard.

What you need to do is get the client (computers on your network) to send
the proper request, you already know the IP. So you need to distinquish
using host headers. Host headers are a MATCHUP between an IP address DNS
hostname. The server literally looks at the packet and says, IP for me?
Yup! Ok, which site? And determines which site based on DNS.

Think of the IP and networking as a city. Your friend's street is your IP
address on your network card. You tell the cab driver, "i want 1st street
where my friend lives" and you get there, but don't know which doorbell to
ring. Unless, your friend says "the blue houes on 1st street", in which
case you go to the street and have the cab driver find the blue house. So,
the cab is the packet of information, the red house vs. blue house is DNS.

So, all you need to do is get some hostnames (make them up if you want) to
match up.

To do that;

OPTION A; Find out what DNS servers serve your network. It will be one of
the following; your ISP (if that is the case, stop here and go to option B),
your domain controller (with DNS running on it), or the "master browser"
thing built into Windows peer-to-peer networks (if you have no domain
controller, skip to option b). If it's your domain controller, get on it,
go in the DNS area, and make some new entries using the IP address you have,
and a name you make up. (app1.yourdomain.local, app2.yourdomain.local,
etc.)

OPTION B;

Use a hosts file. This is a "low tech DNS". There's a file on every
computer called "HOSTS", (no file extension, but it is text).

In Windows, it is here: c:\windows\system32\drivers\etc\HOSTS.

Open it in notepad, note the line

127.0.0.1 localhost

Under, ADD the lines

#.#.#.# yourappname

Where, # is the IP address. And "yourappname" is any domain name, any DNS
formatted name you want (stick to numbers, letters, dots, and dashes.)

Repeat for each virtual server.

Save.

Ping the server to make sure the proper IP comes back.

If it does, stop, you are done, DNS is now set up. Repeat for each computer
that needs to connect to the apps, including the server itself.

Now, you have several IP address DNS pairs. Which is the two essential
components for using host headers.

Next, create your virtual webs, do not use "all assigned" for the IP.
Instead, specify the IP, and then the host header DNS name. (Which will be
prompted in the setup wizard.) Set all the rest of the stuff you need for
your apps and you are good to go. Repeat for each virtual web you have.
The virtual webs all "listen" to the traffic that comes in on that IP, but
will only "grab" the traffic with the DNS name set in the host header that
matches the ones set up in the web.

Re: Can"t Run multiple web sites on IIS 6???

Set each WSS site to it's own unique IP and DNS entry (this will get rid of a good chunk of your frustration)

here's an option...

Your WSS Extended Virtual Servers list could look like this

Default Web Site http://servername -the default WSS installation
Site1 http://site1 - a website Extended to WSS functionality
Site2 http://site2 - another website Extended to WSS functionality
Site3 http://site3 - plain old website


So make Site1 your bread and butter WSS site
Stop the Default Web Site
4 IP's and 4 DNS entries( Add more CNAME DNS records if you want to chop up the Site3 with host headers)


"Mrpush" wrote in message news:0634814F-EE26-4A0D-BB7D-E38DFE6AE2FD@microsoft.com...
> .._..,
>
> I do not have a good handle yet, your are correct.
>
> My connectivity problem is that when trying to access the WSS site (and now
> also all my other sites since I installed WSS) it prompts me for username and
> pass word for my web server every time.
>
> It defults to webserver/administrator for the user name.
>
> This however will not work and I need to change it to:
>
> MyDoaminName/administrator
>
> to get access.
>
> Why is it prompting me to log in?
>
> Thanks,
>
> Mark
>
>
> ".._.." wrote:
>
>>
>> "Mrpush" wrote in message
>> news:7822B653-15D9-4690-9574-BC04E24654DD@microsoft.com...
>> > Ken,
>> >
>> > Thanks for the quick reply. I appreciate it.
>> >
>> > I think I have already treid this, but I will follow your lead here.
>>
>> Good idea, I don't think you have an intuitive grasp of this stuff yet and
>> should stick to the "if then" rules people share with you.
>>
>> >
>> > As for the virtual sites, I really mean virtual directories. I have a
>> > single site in IIS named Portals, and it has several of the "yellow gears"
>> > under it, all which have different web apps and sites "in" them that all
>> > have
>> > worked.
>>
>> Virtual site IS VERY DIFFERENT THING than virtual directory.
>>
>> Virtual Site (web) = Method for handling and serving up files and
>> applications from a server using a well defined set of settings.
>>
>> Virtual Directory = literally, a folder on the "web server file system"
>> level that allows you to map the "web server file system" to the "disk file
>> system" in creative ways. Its sort of like a shortcut sitting on your
>> desktop, not really where the file is, but works to get you there when you
>> need it..
>>
>> The problems you were describing earlier in the thread are related to and
>> RESTRICTED to a Virtual Site. Then you switched to something very different
>> here.
>>
>> So you are working on two problems, my advice is just focus on the
>> connectivity issues first, then work on your apps once you have that figured
>> out.
>>
>>
>> >
>> > They all run ok from with in the single site.
>> >
>> > I'm setting up these new sites for WSS and I'm having all kind of
>> > permission
>> > issues as well. It has to do with URL and Kerberos / NTLM not sure what
>> > is
>> > wrong there.
>>
>> That's a new problem, stop adding more to the mix.
>>
>> >
>> > I'll try these DNS settings and let you know.
>> >
>> > Thanks much,
>> >
>> > Mark
>> >
>> >
>> > "Ken Schaefer" wrote:
>> >
>> >>
>> >> "Mrpush" wrote in message
>> >> news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
>> >> > Hello,
>> >> >
>> >> > Sorry, completely frustrated with IIS. I'm not sure why, but I'm
>> >> > finding
>> >> > it
>> >> > impossible to run multiple web site on my server. The sites are for my
>> >> > own
>> >> > internal Intranet use, not exposed to the world.
>> >> >
>> >> > I have read all the help files on using Ports, IP, or host names.
>> >> >
>> >> > I did not want to use different ports, to hard for employees to
>> >> > remember
>> >> > port numbers.
>> >> >
>> >> > Do not want to use different IP'S for same reason.
>> >> >
>> >> > That leaves me with HOST HEADERS and totally confussed.
>> >> >
>> >> > I need to mess with DNS to use these I quess and this is where it falls
>> >> > apart.
>> >> >
>> >> > I do not have my DNS set to my REAL web domain name, I simply used
>> >> > COMPANY.local in my DNS.
>> >>
>> >> That's OK.
>> >>
>> >>
>> >> > How do I run multiple sites with this? COMPANY.local is not a FULLY
>> >> > QUALIFIED DOMAIN NAME registered with a domain registrar!
>> >>
>> >> Not required.
>> >>
>> >> On your private DNS server, in the company.local forward lookup zone, add
>> >> additional hosts, e.g
>> >>
>> >> A record: server1 -> xx.xx.xx.xx (where xx.xx.xx.xx is the IP address
>> >> of
>> >> your IIS server)
>> >> CNAME record app1 -> server1
>> >> CNAME record app2 -> server1
>> >> CNAME record www -> server1
>> >> CNAME record justForLaughs -> server1
>> >>
>> >> As long as your client machines are configured to use your private DNS
>> >> server, then they will be able to resolve: server1.company.local,
>> >> app1.company.local, app2.company.local etc
>> >>
>> >> This part has nothing to do with IIS. It is simply name resolution.
>> >>
>> >> > If I use COMPANY.local how do I format the Host headers and what url
>> >> > will
>> >> > my
>> >> > users need to enter to get to the different sites?
>> >>
>> >> To get to the above websites, you would configure multiple websites in
>> >> IIS.
>> >>
>> >> The first website would have the host header value: server1.company.local
>> >> The second website would have the host header value: app1.company.local
>> >> The third website would have the host header value: app2.company.local
>> >>
>> >> You get the idea?
>> >>
>> >>
>> >> > WHat about multiple virtual sites withing a single site? What URL will
>> >> > they
>> >> > need?
>> >>
>> >> You can't have "multiple virtual sites within a single site". A virtual
>> >> site
>> >> is a standalone website.
>> >>
>> >> What exactly are you trying to describe here?
>> >>
>> >> > Do I need to change the ports still so I don't get the "can't use the
>> >> > same
>> >> > port for multiple sites" message?
>> >>
>> >> Each website must have a unique combination of IP address + port + host
>> >> header. If you want to resue the same IP address and port (port 80), then
>> >> each site must have a unique host header value.
>> >>
>> >> Cheers
>> >> Ken
>> >>
>> >> >
>> >> > Thanks much,
>> >> >
>> >> > Mark
>> >>
>> >>
>>
>>
>>

Re: Can"t Run multiple web sites on IIS 6???

Create a DNS entry for the hostname "Intranet", and point it to the IP
address that your WSS site is listenting on.

Ensure that the host-header for the WSS site is "Intranet". YOu may,
additionally, need ot configure some things in WSS so that it recognises
that web site name. You'll need to ask in a WSS group about that though.

Cheers
Ken

"Mrpush" wrote in message
news:BB458684-E5C3-409D-BB77-148D22DF9571@microsoft.com...
> .._..,
>
> I understand the actual page part, and that work fine. Its the server
> name
> that I do not want in my URL.
>
> With my WSS sites, it demands:
>
> HTTP://MyWebServerName/and the rest of the url
>
> I do not want the web server name in the url.
>
> I want my users to simply type
>
> "http://intranet"
>
> for example to take me to the site.
>
> How do I "mask" the url to do this?
>
> Thanks much,
>
> Mark
>
>
>
>
> ".._.." wrote:
>
>>
>> "Mrpush" wrote in message
>> news:69FA35E6-C1A8-4005-B839-64B9CD3D386D@microsoft.com...
>> > Ken,
>> >
>> > One of my other issues is URL's with the sites.
>> >
>> > I'd like my WSS site to be accessed with:
>> >
>> > http://MyIntranetName
>> >
>> > Instead of:
>> >
>> > http://MyWebServer/default.aspx
>> >
>> > Do I do this in IIS alone or do I need add to the DNS as well?
>> >
>> > I believe I need to do something in WSS as well here?
>> >
>> > Thanks much,
>>
>> You do that in the properties of the web, under "documents" there's a
>> list
>> of default files.
>>
>> Add "default.aspx" to the list (bump it to the top too). Then, when a
>> browser requests http://servername/ or http://servername/foldername/, if
>> a
>> file called "default.aspx" is present, it will get sent back. Your users
>> can neglect to learn the file name, and you can skip it in hyperlinks
>> then.
>> (I belive that "default.aspx" may already be present after install of
>> some
>> later versions of .NET. But you should check to see if it is in there
>> nonetheless.)
>>
>>
>>

Re: Can"t Run multiple web sites on IIS 6???

OK,

This is much clearer.

As you say - you need to enter the new names into the DNS. But all that does
is allow "yourNewSiteName" to resolve to an internal IP address.

On IIS, you need to configure the "host header" for the site. The host
header is the same as the DNS name (e.g. yourNewSiteName). When a client
(e.g. browser" makes a HTTP v1.1 request to a webserver, it sends a HTTP
header called "Host:" with the name of the website that it wants to access,
e.g.

GET /default.aspx HTTP/1.1
HOST: yourNewSiteName

IIS matches up what the client sends with the various different website
definitions it has. If there is a website that has the host header
"yourNewSiteName" defined, and is listening on the same IP address/port that
the request comes in on, then the request is routed to that website.

Cheers
Ken


"Mrpush" wrote in message
news:67394C0D-EDCF-4258-9C2E-8C08D0FBC1CB@microsoft.com...
> Ken,
>
> I have a website in IIS that a few apps are under as I expalined.
>
> They are using port 80.
>
> I installed WSS 3.0. Install suggestions said to install it with its own
> App pool and to create a new site for it to run it in IIS.
>
> With more than one site, I now must some how differentiate the 2 sites so
> they will run at the same time. I cannot have more then one site on port
> 80.
>
> I have to dissable my existing app site to run the WSS sites on port 80.
>
> Or, I need to change the app pool IP or Host name.
>
> I don't want users to have to remember any numbers, so I'm opting for the
> host header name.
>
> To use this, it seems I have to add DNS entries.
>
> I simple need to be able to run more than one site at a time using Host
> Headers, and had no ides how to set them up.
>
> That is really it.
>
> Thanks,
>
> Mark
>
>
>
>
>
>
>
>
> "Ken Schaefer" wrote:
>
>> Sorry, but this is just becoming more confusing.
>>
>> If you are running multiple applications underneath a single website,
>> then
>> DNS has nothing to do with this.
>>
>> All DNS does is map a FQDN (e.g. someHost.yourcompany.local) to an IP
>> address. It has nothing to do with the files, and folders located within
>> that FQDN.
>>
>> Now you start mentioning WSS. What does WSS have to do with all of this?
>>
>> > I'll try these DNS settings and let you know.
>>
>> NO!!
>>
>> Do not start making random changes to things that you don't have a firm
>> grasp of. You'll just break more things than you fix.
>>
>> Please detail *exactly* what you are trying to accomplish so that the
>> correct direction can be given.
>>
>> Cheers
>> Ken
>>
>>
>> "Mrpush" wrote in message
>> news:7822B653-15D9-4690-9574-BC04E24654DD@microsoft.com...
>> > Ken,
>> >
>> > Thanks for the quick reply. I appreciate it.
>> >
>> > I think I have already treid this, but I will follow your lead here.
>> >
>> > As for the virtual sites, I really mean virtual directories. I have a
>> > single site in IIS named Portals, and it has several of the "yellow
>> > gears"
>> > under it, all which have different web apps and sites "in" them that
>> > all
>> > have
>> > worked.
>> >
>> > They all run ok from with in the single site.
>> >
>> > I'm setting up these new sites for WSS and I'm having all kind of
>> > permission
>> > issues as well. It has to do with URL and Kerberos / NTLM not sure
>> > what
>> > is
>> > wrong there.
>> >
>> > I'll try these DNS settings and let you know.
>> >
>> > Thanks much,
>> >
>> > Mark
>> >
>> >
>> > "Ken Schaefer" wrote:
>> >
>> >>
>> >> "Mrpush" wrote in message
>> >> news:F01E9C28-D816-43AC-BCB8-4D0DC08BB5F2@microsoft.com...
>> >> > Hello,
>> >> >
>> >> > Sorry, completely frustrated with IIS. I'm not sure why, but I'm
>> >> > finding
>> >> > it
>> >> > impossible to run multiple web site on my server. The sites are for
>> >> > my
>> >> > own
>> >> > internal Intranet use, not exposed to the world.
>> >> >
>> >> > I have read all the help files on using Ports, IP, or host names.
>> >> >
>> >> > I did not want to use different ports, to hard for employees to
>> >> > remember
>> >> > port numbers.
>> >> >
>> >> > Do not want to use different IP'S for same reason.
>> >> >
>> >> > That leaves me with HOST HEADERS and totally confussed.
>> >> >
>> >> > I need to mess with DNS to use these I quess and this is where it
>> >> > falls
>> >> > apart.
>> >> >
>> >> > I do not have my DNS set to my REAL web domain name, I simply used
>> >> > COMPANY.local in my DNS.
>> >>
>> >> That's OK.
>> >>
>> >>
>> >> > How do I run multiple sites with this? COMPANY.local is not a FULLY
>> >> > QUALIFIED DOMAIN NAME registered with a domain registrar!
>> >>
>> >> Not required.
>> >>
>> >> On your private DNS server, in the company.local forward lookup zone,
>> >> add
>> >> additional hosts, e.g
>> >>
>> >> A record: server1 -> xx.xx.xx.xx (where xx.xx.xx.xx is the IP
>> >> address
>> >> of
>> >> your IIS server)
>> >> CNAME record app1 -> server1
>> >> CNAME record app2 -> server1
>> >> CNAME record www -> server1
>> >> CNAME record justForLaughs -> server1
>> >>
>> >> As long as your client machines are configured to use your private DNS
>> >> server, then they will be able to resolve: server1.company.local,
>> >> app1.company.local, app2.company.local etc
>> >>
>> >> This part has nothing to do with IIS. It is simply name resolution.
>> >>
>> >> > If I use COMPANY.local how do I format the Host headers and what url
>> >> > will
>> >> > my
>> >> > users need to enter to get to the different sites?
>> >>
>> >> To get to the above websites, you would configure multiple websites in
>> >> IIS.
>> >>
>> >> The first website would have the host header value:
>> >> server1.company.local
>> >> The second website would have the host header value:
>> >> app1.company.local
>> >> The third website would have the host header value: app2.company.local
>> >>
>> >> You get the idea?
>> >>
>> >>
>> >> > WHat about multiple virtual sites withing a single site? What URL
>> >> > will
>> >> > they
>> >> > need?
>> >>
>> >> You can't have "multiple virtual sites within a single site". A
>> >> virtual
>> >> site
>> >> is a standalone website.
>> >>
>> >> What exactly are you trying to describe here?
>> >>
>> >> > Do I need to change the ports still so I don't get the "can't use
>> >> > the
>> >> > same
>> >> > port for multiple sites" message?
>> >>
>> >> Each website must have a unique combination of IP address + port +
>> >> host
>> >> header. If you want to resue the same IP address and port (port 80),
>> >> then
>> >> each site must have a unique host header value.
>> >>
>> >> Cheers
>> >> Ken
>> >>
>> >> >
>> >> > Thanks much,
>> >> >
>> >> > Mark
>> >>
>> >>
>>
>>