Can you clarify whether the two scenarios below are supported ?
1) Imagine I have "Default Website", Port 80. I assign this to IP = 1.1.1.1
Then I create a "New Site". I assign such site to IP = 1.1.1.2.
Can I keep using this as Port 80 to both sites, since they are assigned to
different IPs ?

Is this supported and functional ? I am able to see this working and I am
wondering if it is alright.


2) Imagine I have "Default Website", Port 80, Using "All Unassigned IP"
Then I create a "New Site", also using Port 80, "All Unassigned IP".
Is this supposed to work, or have to change the port of the New site to
another port ? I think so, just want to confirm.

Re: Question on need to change port 80 if I create another site in IIS by Jonathan

Jonathan
Sat Oct 29 20:27:48 CDT 2005

Hi,

#1 - Different IPs is all you need, that will work 100% straight forwardly

#2 - You'll need a host header (http://www.visualwin.com/host-header/) on at
least one site. If you make one site "All unassigned" with no host headers
and another site "All unassigned" with a host header, all requests will go
to the first site unless the specific host header is specified. The same
goes in terms of IP addresses

--
--Jonathan Maltz [Microsoft MVP - Windows Server - IIS, Virtual PC]
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
tutorial site :-)
http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004? Find out
here
Only reply by newsgroup. I do not do technical support via email. Any
emails I have not authorized are deleted before I see them.


"Marlon Brown" <MarlonBrown@discussions.microsoft.com> wrote in message
news:980986E6-B6E1-4E49-8C63-5095C98CAA2C@microsoft.com...
> Can you clarify whether the two scenarios below are supported ?
> 1) Imagine I have "Default Website", Port 80. I assign this to IP =
> 1.1.1.1
> Then I create a "New Site". I assign such site to IP = 1.1.1.2.
> Can I keep using this as Port 80 to both sites, since they are assigned to
> different IPs ?
>
> Is this supported and functional ? I am able to see this working and I am
> wondering if it is alright.
>
>
> 2) Imagine I have "Default Website", Port 80, Using "All Unassigned IP"
> Then I create a "New Site", also using Port 80, "All Unassigned IP".
> Is this supposed to work, or have to change the port of the New site to
> another port ? I think so, just want to confirm.


Re: Question on need to change port 80 if I create another site in by MarlonBrown

MarlonBrown
Sat Oct 29 20:46:01 CDT 2005

Thanks !
I am wondering why in the case of Sharepoint sites, they say "I cannot use
discrete IP Addresses..." . If I cannot use different IP addresses, I will
have to use port 8080 and then I need to open 8080 in the firewall as well...



"7. In the TCP port this Web site should use (Default 80) box, type a new
TCP port number. This port number must be unique and cannot be used by any
other Web site in IIS. Because the Default Web Site in IIS already uses TCP
port 80, you must specify a value other than 80, for example, 8080. This step
is required because SharePoint Portal Server cannot use virtual servers that
are bound to discrete IP addresses. For more information, see â??Appendix A:
Known Issues.â??

"Jonathan Maltz [MS-MVP]" wrote:

> Hi,
>
> #1 - Different IPs is all you need, that will work 100% straight forwardly
>
> #2 - You'll need a host header (http://www.visualwin.com/host-header/) on at
> least one site. If you make one site "All unassigned" with no host headers
> and another site "All unassigned" with a host header, all requests will go
> to the first site unless the specific host header is specified. The same
> goes in terms of IP addresses
>
> --
> --Jonathan Maltz [Microsoft MVP - Windows Server - IIS, Virtual PC]
> http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
> tutorial site :-)
> http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004? Find out
> here
> Only reply by newsgroup. I do not do technical support via email. Any
> emails I have not authorized are deleted before I see them.
>
>
> "Marlon Brown" <MarlonBrown@discussions.microsoft.com> wrote in message
> news:980986E6-B6E1-4E49-8C63-5095C98CAA2C@microsoft.com...
> > Can you clarify whether the two scenarios below are supported ?
> > 1) Imagine I have "Default Website", Port 80. I assign this to IP =
> > 1.1.1.1
> > Then I create a "New Site". I assign such site to IP = 1.1.1.2.
> > Can I keep using this as Port 80 to both sites, since they are assigned to
> > different IPs ?
> >
> > Is this supported and functional ? I am able to see this working and I am
> > wondering if it is alright.
> >
> >
> > 2) Imagine I have "Default Website", Port 80, Using "All Unassigned IP"
> > Then I create a "New Site", also using Port 80, "All Unassigned IP".
> > Is this supposed to work, or have to change the port of the New site to
> > another port ? I think so, just want to confirm.
>
>

Re: Question on need to change port 80 if I create another site in by Jonathan

Jonathan
Sun Oct 30 20:44:02 CST 2005

Hi,

I'd post that in the SharePoint group as it sounds like a limitation of
SharePoint. IIS most certainly works as I described

--
--Jonathan Maltz [Microsoft MVP - Windows Server - IIS, Virtual PC]
http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
tutorial site :-)
http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004? Find out
here
Only reply by newsgroup. I do not do technical support via email. Any
emails I have not authorized are deleted before I see them.


"Marlon Brown" <MarlonBrown@discussions.microsoft.com> wrote in message
news:E245415E-21A5-47DF-ABBE-58597BD92D40@microsoft.com...
> Thanks !
> I am wondering why in the case of Sharepoint sites, they say "I cannot use
> discrete IP Addresses..." . If I cannot use different IP addresses, I will
> have to use port 8080 and then I need to open 8080 in the firewall as
> well...
>
>
>
> "7. In the TCP port this Web site should use (Default 80) box, type a new
> TCP port number. This port number must be unique and cannot be used by any
> other Web site in IIS. Because the Default Web Site in IIS already uses
> TCP
> port 80, you must specify a value other than 80, for example, 8080. This
> step
> is required because SharePoint Portal Server cannot use virtual servers
> that
> are bound to discrete IP addresses. For more information, see â??Appendix A:
> Known Issues.â??
>
> "Jonathan Maltz [MS-MVP]" wrote:
>
>> Hi,
>>
>> #1 - Different IPs is all you need, that will work 100% straight
>> forwardly
>>
>> #2 - You'll need a host header (http://www.visualwin.com/host-header/) on
>> at
>> least one site. If you make one site "All unassigned" with no host
>> headers
>> and another site "All unassigned" with a host header, all requests will
>> go
>> to the first site unless the specific host header is specified. The same
>> goes in terms of IP addresses
>>
>> --
>> --Jonathan Maltz [Microsoft MVP - Windows Server - IIS, Virtual PC]
>> http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
>> tutorial site :-)
>> http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004? Find
>> out
>> here
>> Only reply by newsgroup. I do not do technical support via email. Any
>> emails I have not authorized are deleted before I see them.
>>
>>
>> "Marlon Brown" <MarlonBrown@discussions.microsoft.com> wrote in message
>> news:980986E6-B6E1-4E49-8C63-5095C98CAA2C@microsoft.com...
>> > Can you clarify whether the two scenarios below are supported ?
>> > 1) Imagine I have "Default Website", Port 80. I assign this to IP =
>> > 1.1.1.1
>> > Then I create a "New Site". I assign such site to IP = 1.1.1.2.
>> > Can I keep using this as Port 80 to both sites, since they are assigned
>> > to
>> > different IPs ?
>> >
>> > Is this supported and functional ? I am able to see this working and I
>> > am
>> > wondering if it is alright.
>> >
>> >
>> > 2) Imagine I have "Default Website", Port 80, Using "All Unassigned IP"
>> > Then I create a "New Site", also using Port 80, "All Unassigned IP".
>> > Is this supposed to work, or have to change the port of the New site to
>> > another port ? I think so, just want to confirm.
>>
>>