I'm trying to configure IIS6 in SBS2003 and I'm stuck of ftp. I know how to
do the host header setup for multiple web sites on the same fixed IP. Now I
am trying to setup ftp sites on more than one of these separate web sites.
I made the naive assumption that the ftp sites would be similarily
differentiated by some kind of host header type functionality. It wont let
me setup the second ftp site because it says it has the same IP and port and
I find nothing equivalent to host headers in ftp setup. How do I get there
from here, please?

Re: FTP & Multiple Sites? by root

root
Wed Jun 30 01:02:05 CDT 2004


"root" <postmaster@buchanangc.com> wrote in message
news:OsfTmImXEHA.1980@TK2MSFTNGP10.phx.gbl...
> I'm trying to configure IIS6 in SBS2003 and I'm stuck of ftp. I know how
to
> do the host header setup for multiple web sites on the same fixed IP. Now
I
> am trying to setup ftp sites on more than one of these separate web sites.
> I made the naive assumption that the ftp sites would be similarily
> differentiated by some kind of host header type functionality. It wont
let
> me setup the second ftp site because it says it has the same IP and port
and
> I find nothing equivalent to host headers in ftp setup. How do I get
there
> from here, please?

I seem to have found at least part of my own answer here:
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/wsa_ftp_createmultsite.asp?sd=gn&ln=en-us&gssnb=1

"Creating Multiple FTP Sites"

This seems to be saying that different IPs or different ports is the only
way.
What ports would be typical for a 2nd or 3rd FTP site.

There's a way for one to get one's ISP to have multiple A-records for
additional subdomains etc for one's web site. The A-records for this IP
already contain entries for the 2 sites in question ex:
www.firstsite.com
ftp.firstsite.com
www.secondsite.com
ftp.secondsite.com

Now does an ISP generally have the capacity to assign to one of those FTP
entires a port different than than the default FTP port 21? If so then that
would appear to solve the problem except possibly for internal LAN access to
the same multiple FTP sites.

Am I on the right track?



Re: FTP & Multiple Sites? by Paul

Paul
Wed Jun 30 03:29:19 CDT 2004

On Tue, 29 Jun 2004 23:02:05 -0700, "root" <postmaster@buchanangc.com>
wrote:

>
>"root" <postmaster@buchanangc.com> wrote in message
>news:OsfTmImXEHA.1980@TK2MSFTNGP10.phx.gbl...
>> I'm trying to configure IIS6 in SBS2003 and I'm stuck of ftp. I know how
>to
>> do the host header setup for multiple web sites on the same fixed IP. Now
>I
>> am trying to setup ftp sites on more than one of these separate web sites.
>> I made the naive assumption that the ftp sites would be similarily
>> differentiated by some kind of host header type functionality. It wont
>let
>> me setup the second ftp site because it says it has the same IP and port
>and
>> I find nothing equivalent to host headers in ftp setup. How do I get
>there
>> from here, please?
>
>I seem to have found at least part of my own answer here:
>http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/wsa_ftp_createmultsite.asp?sd=gn&ln=en-us&gssnb=1
>
>"Creating Multiple FTP Sites"
>
>This seems to be saying that different IPs or different ports is the only
>way.
>What ports would be typical for a 2nd or 3rd FTP site.
>
>There's a way for one to get one's ISP to have multiple A-records for
>additional subdomains etc for one's web site. The A-records for this IP
>already contain entries for the 2 sites in question ex:
>www.firstsite.com
>ftp.firstsite.com
>www.secondsite.com
>ftp.secondsite.com
>
>Now does an ISP generally have the capacity to assign to one of those FTP
>entires a port different than than the default FTP port 21? If so then that
>would appear to solve the problem except possibly for internal LAN access to
>the same multiple FTP sites.
>
>Am I on the right track?

No, you're on the wrong track. You don't need to use different ports
to achieve this; that would be a nightmare to implement and would
cause all kinds of support headaches, especially in an ISP
environment. This is largely the reason MS introduced the User
Isolation feature in the IIS6 FTP service.

All you need to do is point ftp.firstsite.com and ftp.secondsite.com
at the same IP address and then configure user isolation within one
FTP site in IIS. Then your users will be re-directed to their own
directories and will not be aware that other content is being hosted
by what is effectively the same FTP site.

You can find all you need to know about setting this up here :

http://www.microsoft.com/resources/documentation/iis/6/all/proddocs/en-us/wsa_ftp_isolate.mspx


Regards,

Paul Lynch
MCSE

Re: FTP & Multiple Sites? by root

root
Wed Jun 30 13:02:58 CDT 2004


"Paul Lynch" <paul.lynch@nospam.com> wrote in message
news:n4u4e09e635vg9hu12uo82854n3n1hkt2f@4ax.com...
> On Tue, 29 Jun 2004 23:02:05 -0700, "root" <postmaster@buchanangc.com>
> wrote:
>
> >
> >"root" <postmaster@buchanangc.com> wrote in message
> >news:OsfTmImXEHA.1980@TK2MSFTNGP10.phx.gbl...
> >> I'm trying to configure IIS6 in SBS2003 and I'm stuck of ftp. I know
how
> >to
> >> do the host header setup for multiple web sites on the same fixed IP.
Now
> >I
> >> am trying to setup ftp sites on more than one of these separate web
sites.
> >> I made the naive assumption that the ftp sites would be similarily
> >> differentiated by some kind of host header type functionality. It wont
> >let
> >> me setup the second ftp site because it says it has the same IP and
port
> >and
> >> I find nothing equivalent to host headers in ftp setup. How do I get
> >there
> >> from here, please?
> >
> >I seem to have found at least part of my own answer here:
>
>http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/
proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/sta
ndard/proddocs/en-us/wsa_ftp_createmultsite.asp?sd=gn&ln=en-us&gssnb=1
> >
> >"Creating Multiple FTP Sites"
> >
> >This seems to be saying that different IPs or different ports is the only
> >way.
> >What ports would be typical for a 2nd or 3rd FTP site.
> >
> >There's a way for one to get one's ISP to have multiple A-records for
> >additional subdomains etc for one's web site. The A-records for this IP
> >already contain entries for the 2 sites in question ex:
> >www.firstsite.com
> >ftp.firstsite.com
> >www.secondsite.com
> >ftp.secondsite.com
> >
> >Now does an ISP generally have the capacity to assign to one of those FTP
> >entires a port different than than the default FTP port 21? If so then
that
> >would appear to solve the problem except possibly for internal LAN access
to
> >the same multiple FTP sites.
> >
> >Am I on the right track?
>
> No, you're on the wrong track. You don't need to use different ports
> to achieve this; that would be a nightmare to implement and would
> cause all kinds of support headaches, especially in an ISP
> environment. This is largely the reason MS introduced the User
> Isolation feature in the IIS6 FTP service.
>
> All you need to do is point ftp.firstsite.com and ftp.secondsite.com
> at the same IP address and then configure user isolation within one
> FTP site in IIS.


I don't want to isolate users. I want to isolate ftp sites. In the context
of what you are saying how does one present an annomous ftp user with two
entirely different FTP sites depending on whether that user originally
entered ftp.firstsite.com versus ftp.secondsite.com? What does the concept
of "user" have to do with this?

> Then your users will be re-directed to their own
> directories and will not be aware that other content is being hosted
> by what is effectively the same FTP site.
>
> You can find all you need to know about setting this up here :
>
>
http://www.microsoft.com/resources/documentation/iis/6/all/proddocs/en-us/wsa_ftp_isolate.mspx
>
>
> Regards,
>
> Paul Lynch
> MCSE



Re: FTP & Multiple Sites? by jeff

jeff
Wed Jun 30 13:58:48 CDT 2004

On Wed, 30 Jun 2004 11:02:58 -0700, "root" <postmaster@buchanangc.com>
wrote:

>
>"Paul Lynch" <paul.lynch@nospam.com> wrote in message
>news:n4u4e09e635vg9hu12uo82854n3n1hkt2f@4ax.com...
>> On Tue, 29 Jun 2004 23:02:05 -0700, "root" <postmaster@buchanangc.com>
>> wrote:
>>
>> >
>> >"root" <postmaster@buchanangc.com> wrote in message
>> >news:OsfTmImXEHA.1980@TK2MSFTNGP10.phx.gbl...
>> >> I'm trying to configure IIS6 in SBS2003 and I'm stuck of ftp. I know
>how
>> >to
>> >> do the host header setup for multiple web sites on the same fixed IP.
>Now
>> >I
>> >> am trying to setup ftp sites on more than one of these separate web
>sites.
>> >> I made the naive assumption that the ftp sites would be similarily
>> >> differentiated by some kind of host header type functionality. It wont
>> >let
>> >> me setup the second ftp site because it says it has the same IP and
>port
>> >and
>> >> I find nothing equivalent to host headers in ftp setup. How do I get
>> >there
>> >> from here, please?
>> >
>> >I seem to have found at least part of my own answer here:
>>
>>http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/
>proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/sta
>ndard/proddocs/en-us/wsa_ftp_createmultsite.asp?sd=gn&ln=en-us&gssnb=1
>> >
>> >"Creating Multiple FTP Sites"
>> >
>> >This seems to be saying that different IPs or different ports is the only
>> >way.
>> >What ports would be typical for a 2nd or 3rd FTP site.
>> >
>> >There's a way for one to get one's ISP to have multiple A-records for
>> >additional subdomains etc for one's web site. The A-records for this IP
>> >already contain entries for the 2 sites in question ex:
>> >www.firstsite.com
>> >ftp.firstsite.com
>> >www.secondsite.com
>> >ftp.secondsite.com
>> >
>> >Now does an ISP generally have the capacity to assign to one of those FTP
>> >entires a port different than than the default FTP port 21? If so then
>that
>> >would appear to solve the problem except possibly for internal LAN access
>to
>> >the same multiple FTP sites.
>> >
>> >Am I on the right track?
>>
>> No, you're on the wrong track. You don't need to use different ports
>> to achieve this; that would be a nightmare to implement and would
>> cause all kinds of support headaches, especially in an ISP
>> environment. This is largely the reason MS introduced the User
>> Isolation feature in the IIS6 FTP service.
>>
>> All you need to do is point ftp.firstsite.com and ftp.secondsite.com
>> at the same IP address and then configure user isolation within one
>> FTP site in IIS.
>
>
>I don't want to isolate users. I want to isolate ftp sites. In the context
>of what you are saying how does one present an annomous ftp user with two
>entirely different FTP sites depending on whether that user originally
>entered ftp.firstsite.com versus ftp.secondsite.com? What does the concept
>of "user" have to do with this?

If you *must* use separate sites, then you have a choice of separate
ports or separate IP addresses. Ports have to be specified on the FTP
command if they aren't the default, so separate IP's is usually the
only viable option.

But you can do as Paul has said and use user isolation, with each FTP
"site" pointed at one IP, and when the user logs in they are in thier
own folders. This is done in DNS, so that both domains point to the
same FTP server.

Jeff

>> Then your users will be re-directed to their own
>> directories and will not be aware that other content is being hosted
>> by what is effectively the same FTP site.
>>
>> You can find all you need to know about setting this up here :
>>
>>
>http://www.microsoft.com/resources/documentation/iis/6/all/proddocs/en-us/wsa_ftp_isolate.mspx
>>
>>
>> Regards,
>>
>> Paul Lynch
>> MCSE
>


Re: FTP & Multiple Sites? by root

root
Wed Jun 30 14:07:31 CDT 2004

So it's not possible at the authoritative NS level to say/assign that
ftp.firstsite.com uses port 21 and ftp.secondsite.com uses port 22(what's a
good 2nd ftp port number?) such that an Internet user need only enter
ftp.firstsite.com or ftp.secondiste.com and be directed to the correct ftp
site??

"Jeff Cochran" <jeff.nospam@zina.com> wrote in message
news:40f50ccb.453663012@msnews.microsoft.com...
> On Wed, 30 Jun 2004 11:02:58 -0700, "root" <postmaster@buchanangc.com>
> wrote:
>
> >
> >"Paul Lynch" <paul.lynch@nospam.com> wrote in message
> >news:n4u4e09e635vg9hu12uo82854n3n1hkt2f@4ax.com...
> >> On Tue, 29 Jun 2004 23:02:05 -0700, "root" <postmaster@buchanangc.com>
> >> wrote:
> >>
> >> >
> >> >"root" <postmaster@buchanangc.com> wrote in message
> >> >news:OsfTmImXEHA.1980@TK2MSFTNGP10.phx.gbl...
> >> >> I'm trying to configure IIS6 in SBS2003 and I'm stuck of ftp. I
know
> >how
> >> >to
> >> >> do the host header setup for multiple web sites on the same fixed
IP.
> >Now
> >> >I
> >> >> am trying to setup ftp sites on more than one of these separate web
> >sites.
> >> >> I made the naive assumption that the ftp sites would be similarily
> >> >> differentiated by some kind of host header type functionality. It
wont
> >> >let
> >> >> me setup the second ftp site because it says it has the same IP and
> >port
> >> >and
> >> >> I find nothing equivalent to host headers in ftp setup. How do I
get
> >> >there
> >> >> from here, please?
> >> >
> >> >I seem to have found at least part of my own answer here:
> >>
>
>>http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard
/
>
>proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/st
a
> >ndard/proddocs/en-us/wsa_ftp_createmultsite.asp?sd=gn&ln=en-us&gssnb=1
> >> >
> >> >"Creating Multiple FTP Sites"
> >> >
> >> >This seems to be saying that different IPs or different ports is the
only
> >> >way.
> >> >What ports would be typical for a 2nd or 3rd FTP site.
> >> >
> >> >There's a way for one to get one's ISP to have multiple A-records for
> >> >additional subdomains etc for one's web site. The A-records for this
IP
> >> >already contain entries for the 2 sites in question ex:
> >> >www.firstsite.com
> >> >ftp.firstsite.com
> >> >www.secondsite.com
> >> >ftp.secondsite.com
> >> >
> >> >Now does an ISP generally have the capacity to assign to one of those
FTP
> >> >entires a port different than than the default FTP port 21? If so
then
> >that
> >> >would appear to solve the problem except possibly for internal LAN
access
> >to
> >> >the same multiple FTP sites.
> >> >
> >> >Am I on the right track?
> >>
> >> No, you're on the wrong track. You don't need to use different ports
> >> to achieve this; that would be a nightmare to implement and would
> >> cause all kinds of support headaches, especially in an ISP
> >> environment. This is largely the reason MS introduced the User
> >> Isolation feature in the IIS6 FTP service.
> >>
> >> All you need to do is point ftp.firstsite.com and ftp.secondsite.com
> >> at the same IP address and then configure user isolation within one
> >> FTP site in IIS.
> >
> >
> >I don't want to isolate users. I want to isolate ftp sites. In the
context
> >of what you are saying how does one present an annomous ftp user with two
> >entirely different FTP sites depending on whether that user originally
> >entered ftp.firstsite.com versus ftp.secondsite.com? What does the
concept
> >of "user" have to do with this?
>
> If you *must* use separate sites, then you have a choice of separate
> ports or separate IP addresses. Ports have to be specified on the FTP
> command if they aren't the default, so separate IP's is usually the
> only viable option.
>
> But you can do as Paul has said and use user isolation, with each FTP
> "site" pointed at one IP, and when the user logs in they are in thier
> own folders. This is done in DNS, so that both domains point to the
> same FTP server.
>
> Jeff
>
> >> Then your users will be re-directed to their own
> >> directories and will not be aware that other content is being hosted
> >> by what is effectively the same FTP site.
> >>
> >> You can find all you need to know about setting this up here :
> >>
> >>
>
>http://www.microsoft.com/resources/documentation/iis/6/all/proddocs/en-us/w
sa_ftp_isolate.mspx
> >>
> >>
> >> Regards,
> >>
> >> Paul Lynch
> >> MCSE
> >
>



Re: FTP & Multiple Sites? by jeff

jeff
Wed Jun 30 15:06:53 CDT 2004

On Wed, 30 Jun 2004 12:07:31 -0700, "root" <postmaster@buchanangc.com>
wrote:

>So it's not possible at the authoritative NS level to say/assign that
>ftp.firstsite.com uses port 21 and ftp.secondsite.com uses port 22(what's a
>good 2nd ftp port number?) such that an Internet user need only enter
>ftp.firstsite.com or ftp.secondiste.com and be directed to the correct ftp
>site??

No.

Jeff


>"Jeff Cochran" <jeff.nospam@zina.com> wrote in message
>news:40f50ccb.453663012@msnews.microsoft.com...
>> On Wed, 30 Jun 2004 11:02:58 -0700, "root" <postmaster@buchanangc.com>
>> wrote:
>>
>> >
>> >"Paul Lynch" <paul.lynch@nospam.com> wrote in message
>> >news:n4u4e09e635vg9hu12uo82854n3n1hkt2f@4ax.com...
>> >> On Tue, 29 Jun 2004 23:02:05 -0700, "root" <postmaster@buchanangc.com>
>> >> wrote:
>> >>
>> >> >
>> >> >"root" <postmaster@buchanangc.com> wrote in message
>> >> >news:OsfTmImXEHA.1980@TK2MSFTNGP10.phx.gbl...
>> >> >> I'm trying to configure IIS6 in SBS2003 and I'm stuck of ftp. I
>know
>> >how
>> >> >to
>> >> >> do the host header setup for multiple web sites on the same fixed
>IP.
>> >Now
>> >> >I
>> >> >> am trying to setup ftp sites on more than one of these separate web
>> >sites.
>> >> >> I made the naive assumption that the ftp sites would be similarily
>> >> >> differentiated by some kind of host header type functionality. It
>wont
>> >> >let
>> >> >> me setup the second ftp site because it says it has the same IP and
>> >port
>> >> >and
>> >> >> I find nothing equivalent to host headers in ftp setup. How do I
>get
>> >> >there
>> >> >> from here, please?
>> >> >
>> >> >I seem to have found at least part of my own answer here:
>> >>
>>
>>>http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard
>/
>>
>>proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/st
>a
>> >ndard/proddocs/en-us/wsa_ftp_createmultsite.asp?sd=gn&ln=en-us&gssnb=1
>> >> >
>> >> >"Creating Multiple FTP Sites"
>> >> >
>> >> >This seems to be saying that different IPs or different ports is the
>only
>> >> >way.
>> >> >What ports would be typical for a 2nd or 3rd FTP site.
>> >> >
>> >> >There's a way for one to get one's ISP to have multiple A-records for
>> >> >additional subdomains etc for one's web site. The A-records for this
>IP
>> >> >already contain entries for the 2 sites in question ex:
>> >> >www.firstsite.com
>> >> >ftp.firstsite.com
>> >> >www.secondsite.com
>> >> >ftp.secondsite.com
>> >> >
>> >> >Now does an ISP generally have the capacity to assign to one of those
>FTP
>> >> >entires a port different than than the default FTP port 21? If so
>then
>> >that
>> >> >would appear to solve the problem except possibly for internal LAN
>access
>> >to
>> >> >the same multiple FTP sites.
>> >> >
>> >> >Am I on the right track?
>> >>
>> >> No, you're on the wrong track. You don't need to use different ports
>> >> to achieve this; that would be a nightmare to implement and would
>> >> cause all kinds of support headaches, especially in an ISP
>> >> environment. This is largely the reason MS introduced the User
>> >> Isolation feature in the IIS6 FTP service.
>> >>
>> >> All you need to do is point ftp.firstsite.com and ftp.secondsite.com
>> >> at the same IP address and then configure user isolation within one
>> >> FTP site in IIS.
>> >
>> >
>> >I don't want to isolate users. I want to isolate ftp sites. In the
>context
>> >of what you are saying how does one present an annomous ftp user with two
>> >entirely different FTP sites depending on whether that user originally
>> >entered ftp.firstsite.com versus ftp.secondsite.com? What does the
>concept
>> >of "user" have to do with this?
>>
>> If you *must* use separate sites, then you have a choice of separate
>> ports or separate IP addresses. Ports have to be specified on the FTP
>> command if they aren't the default, so separate IP's is usually the
>> only viable option.
>>
>> But you can do as Paul has said and use user isolation, with each FTP
>> "site" pointed at one IP, and when the user logs in they are in thier
>> own folders. This is done in DNS, so that both domains point to the
>> same FTP server.
>>
>> Jeff
>>
>> >> Then your users will be re-directed to their own
>> >> directories and will not be aware that other content is being hosted
>> >> by what is effectively the same FTP site.
>> >>
>> >> You can find all you need to know about setting this up here :
>> >>
>> >>
>>
>>http://www.microsoft.com/resources/documentation/iis/6/all/proddocs/en-us/w
>sa_ftp_isolate.mspx
>> >>
>> >>
>> >> Regards,
>> >>
>> >> Paul Lynch
>> >> MCSE
>> >
>>
>


Re: FTP & Multiple Sites? by Alun

Alun
Wed Jun 30 15:13:10 CDT 2004

"root" <postmaster@buchanangc.com> wrote in message
news:OGIFAVtXEHA.1144@TK2MSFTNGP10.phx.gbl...
> So it's not possible at the authoritative NS level to say/assign that
> ftp.firstsite.com uses port 21 and ftp.secondsite.com uses port 22(what's
a
> good 2nd ftp port number?) such that an Internet user need only enter
> ftp.firstsite.com or ftp.secondiste.com and be directed to the correct ftp
> site??

Technically, there is such a DNS feature available - DNS SRV records - such
that you'd do a query for an SRV record named "_ftp._tcp.example.com", and
it would return a list of targets - names and ports - with priorities and
weightings so that you can decide which order to try the targets in, and
connect to them.

I don't know of any FTP client that implements this, though.

There is no analog to the HTTP host header in the FTP protocol. Before I
joined Microsoft, I brought it up in a discussion with the FTPEXT working
group of the IETF, but "broad consensus was not achieved" on how it might
work.

So, no, when you connect to an FTP server - any FTP server, not just
Microsoft's - all the FTP server knows is the IP address and port you
connected to, the user name you give, and the password, and it must use that
information to determine what access to give you.

Further reading:
RFCs 959, 1123, and (for the truly masochistic) 3546 section 3.1 for a
potential light at the end of a very long tunnel.

Alun.
~~~~



Re: FTP & Multiple Sites? by root

root
Wed Jun 30 15:46:29 CDT 2004


"Jeff Cochran" <jeff.nospam@zina.com> wrote in message
news:40e41d45.457880747@msnews.microsoft.com...
> On Wed, 30 Jun 2004 12:07:31 -0700, "root" <postmaster@buchanangc.com>
> wrote:
>
> >So it's not possible at the authoritative NS level to say/assign that
> >ftp.firstsite.com uses port 21 and ftp.secondsite.com uses port 22(what's
a
> >good 2nd ftp port number?) such that an Internet user need only enter
> >ftp.firstsite.com or ftp.secondiste.com and be directed to the correct
ftp
> >site??
>
> No.

Having researched the format of the A record and the zone file in the mean
time I came to the same conclusion.

So I guess that the overall conclusion is that separate anonymous FTP sites
require separate IPs. They simplified/eliminated this requirement for www
with the header lookup and I made the naive assumption that the same had
been done with ftp.

> >"Jeff Cochran" <jeff.nospam@zina.com> wrote in message
> >news:40f50ccb.453663012@msnews.microsoft.com...
> >> On Wed, 30 Jun 2004 11:02:58 -0700, "root" <postmaster@buchanangc.com>
> >> wrote:
> >>
> >> >
> >> >"Paul Lynch" <paul.lynch@nospam.com> wrote in message
> >> >news:n4u4e09e635vg9hu12uo82854n3n1hkt2f@4ax.com...
> >> >> On Tue, 29 Jun 2004 23:02:05 -0700, "root"
<postmaster@buchanangc.com>
> >> >> wrote:
> >> >>
> >> >> >
> >> >> >"root" <postmaster@buchanangc.com> wrote in message
> >> >> >news:OsfTmImXEHA.1980@TK2MSFTNGP10.phx.gbl...
> >> >> >> I'm trying to configure IIS6 in SBS2003 and I'm stuck of ftp. I
> >know
> >> >how
> >> >> >to
> >> >> >> do the host header setup for multiple web sites on the same fixed
> >IP.
> >> >Now
> >> >> >I
> >> >> >> am trying to setup ftp sites on more than one of these separate
web
> >> >sites.
> >> >> >> I made the naive assumption that the ftp sites would be
similarily
> >> >> >> differentiated by some kind of host header type functionality.
It
> >wont
> >> >> >let
> >> >> >> me setup the second ftp site because it says it has the same IP
and
> >> >port
> >> >> >and
> >> >> >> I find nothing equivalent to host headers in ftp setup. How do I
> >get
> >> >> >there
> >> >> >> from here, please?
> >> >> >
> >> >> >I seem to have found at least part of my own answer here:
> >> >>
> >>
>
>>>http://www.microsoft.com/resources/documentation/WindowsServ/2003/standar
d
> >/
> >>
>
>>proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/s
t
> >a
> >> >ndard/proddocs/en-us/wsa_ftp_createmultsite.asp?sd=gn&ln=en-us&gssnb=1
> >> >> >
> >> >> >"Creating Multiple FTP Sites"
> >> >> >
> >> >> >This seems to be saying that different IPs or different ports is
the
> >only
> >> >> >way.
> >> >> >What ports would be typical for a 2nd or 3rd FTP site.
> >> >> >
> >> >> >There's a way for one to get one's ISP to have multiple A-records
for
> >> >> >additional subdomains etc for one's web site. The A-records for
this
> >IP
> >> >> >already contain entries for the 2 sites in question ex:
> >> >> >www.firstsite.com
> >> >> >ftp.firstsite.com
> >> >> >www.secondsite.com
> >> >> >ftp.secondsite.com
> >> >> >
> >> >> >Now does an ISP generally have the capacity to assign to one of
those
> >FTP
> >> >> >entires a port different than than the default FTP port 21? If so
> >then
> >> >that
> >> >> >would appear to solve the problem except possibly for internal LAN
> >access
> >> >to
> >> >> >the same multiple FTP sites.
> >> >> >
> >> >> >Am I on the right track?
> >> >>
> >> >> No, you're on the wrong track. You don't need to use different ports
> >> >> to achieve this; that would be a nightmare to implement and would
> >> >> cause all kinds of support headaches, especially in an ISP
> >> >> environment. This is largely the reason MS introduced the User
> >> >> Isolation feature in the IIS6 FTP service.
> >> >>
> >> >> All you need to do is point ftp.firstsite.com and ftp.secondsite.com
> >> >> at the same IP address and then configure user isolation within one
> >> >> FTP site in IIS.
> >> >
> >> >
> >> >I don't want to isolate users. I want to isolate ftp sites. In the
> >context
> >> >of what you are saying how does one present an annomous ftp user with
two
> >> >entirely different FTP sites depending on whether that user originally
> >> >entered ftp.firstsite.com versus ftp.secondsite.com? What does the
> >concept
> >> >of "user" have to do with this?
> >>
> >> If you *must* use separate sites, then you have a choice of separate
> >> ports or separate IP addresses. Ports have to be specified on the FTP
> >> command if they aren't the default, so separate IP's is usually the
> >> only viable option.
> >>
> >> But you can do as Paul has said and use user isolation, with each FTP
> >> "site" pointed at one IP, and when the user logs in they are in thier
> >> own folders. This is done in DNS, so that both domains point to the
> >> same FTP server.
> >>
> >> Jeff
> >>
> >> >> Then your users will be re-directed to their own
> >> >> directories and will not be aware that other content is being hosted
> >> >> by what is effectively the same FTP site.
> >> >>
> >> >> You can find all you need to know about setting this up here :
> >> >>
> >> >>
> >>
>
>>http://www.microsoft.com/resources/documentation/iis/6/all/proddocs/en-us/
w
> >sa_ftp_isolate.mspx
> >> >>
> >> >>
> >> >> Regards,
> >> >>
> >> >> Paul Lynch
> >> >> MCSE
> >> >
> >>
> >
>



Re: FTP & Multiple Sites? by root

root
Wed Jun 30 16:27:21 CDT 2004

Thanks to you , Jeff and Paul.

"Alun Jones [MSFT]" <alunj@online.microsoft.com> wrote in message
news:%23pAS3EuXEHA.1356@TK2MSFTNGP09.phx.gbl...
> "root" <postmaster@buchanangc.com> wrote in message
> news:OGIFAVtXEHA.1144@TK2MSFTNGP10.phx.gbl...
> > So it's not possible at the authoritative NS level to say/assign that
> > ftp.firstsite.com uses port 21 and ftp.secondsite.com uses port
22(what's
> a
> > good 2nd ftp port number?) such that an Internet user need only enter
> > ftp.firstsite.com or ftp.secondiste.com and be directed to the correct
ftp
> > site??
>
> Technically, there is such a DNS feature available - DNS SRV records -
such
> that you'd do a query for an SRV record named "_ftp._tcp.example.com", and
> it would return a list of targets - names and ports - with priorities and
> weightings so that you can decide which order to try the targets in, and
> connect to them.
>
> I don't know of any FTP client that implements this, though.
>
> There is no analog to the HTTP host header in the FTP protocol. Before I
> joined Microsoft, I brought it up in a discussion with the FTPEXT working
> group of the IETF, but "broad consensus was not achieved" on how it might
> work.
>
> So, no, when you connect to an FTP server - any FTP server, not just
> Microsoft's - all the FTP server knows is the IP address and port you
> connected to, the user name you give, and the password, and it must use
that
> information to determine what access to give you.
>
> Further reading:
> RFCs 959, 1123, and (for the truly masochistic) 3546 section 3.1 for a
> potential light at the end of a very long tunnel.
>
> Alun.
> ~~~~
>
>