Re: [NTISP] IIS 4.0 FTP hosting on a single IP

Adam Greene ( (no email) )
Fri, 19 Mar 1999 11:13:47 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_0098_01BE71F9.8F6EC7F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I run WWW off multiple IP's, but I don't think the FTP part would be any =
different for you and for me (I may be wrong, of course). =20

I have a single FTP site using the IP address of the Default Web Site =
(my ISP's website). In IIS, this FTP site is mapped to a specific =
directory on the web server. =20

Whenever I set up an FTP account for a customer, I create a new virtual =
directory under the single FTP site in IIS. I map this virtual =
directory to the folder that stores that customer's webfiles. =20

I then set up a Windows NT user for the customer and allow that user to =
write to the folder containing the webfiles. All the customer has to do =
is FTP to the hostname ftp.isp'sdomain.net (if using CuteFTP, for =
example) with his username and password. He is taken automatically to =
his folder and can update his website. =20

The same procedure works for customers with their own domains =
(www.customer'sdomain.com) and for customers with subdomains off the =
ISP's domain (www.isp'sdomain.net/customersite) -- the single FTP site =
which uses the same IP address as the Default Website allows both types =
of customers to FTP successfully.=20

Regards,
Adam

-----Original Message-----
From: Terry Bomersbach <terryb@the-cia.net>
To: ntisp@iea-software.com <ntisp@iea-software.com>
Date: Thursday, March 18, 1999 8:35 PM
Subject: [NTISP] IIS 4.0 FTP hosting on a single IP
=20
=20
Does anyone have any advice here, or am I out of luck. We are =
running WWW off of one ISP, what we need is FTP for each of these =
domains to update their web pages. What are others doing?

------=_NextPart_000_0098_01BE71F9.8F6EC7F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

I run WWW off multiple IP's, but I =don't think=20the FTP part would be any different for you and for me (I may be wrong, =of=20course). 
 
I have a single FTP site using the IP address of the =Default=20Web Site (my ISP's website).  In IIS, this FTP site is mapped to a =specific=20directory on the web server. 
 
Whenever I set up an FTP account for a customer, I =create a=20new virtual directory under the single FTP site in IIS.  I map this =virtual=20directory to the folder that stores that customer's=20webfiles.  
 
I then set up a Windows NT user for the customer and =allow=20that user to write to the folder containing the webfiles.  All the =customer=20has to do is FTP to the hostname ftp.isp'sdomain.net (if using CuteFTP, =for=20example) with his username and password.  He is taken automatically =to his=20folder and can update his website.  
 
The same procedure works for =customers with=20their own domains (www.customer'sdomain.com) =and for=20customers with subdomains off the ISP's domain (www.isp'sdomain.net/cust=omersite)=20-- the single FTP site which uses the same IP address as the Default =Website=20allows both types of customers to FTP successfully.
 
 
Regards,
Adam
 
-----Original =Message-----
From:=20 Terry Bomersbach <terryb@the-cia.net>
To: =ntisp@iea-software.com =<ntisp@iea-software.com>
=Date:=20 Thursday, March 18, 1999 8:35 PM
Subject: [NTISP] IIS =4.0 FTP=20 hosting on a single IP

Does anyone have any advice =here, or am I=20 out of luck.  We are running WWW off of one ISP, what we need =is FTP=20 for each of these domains to update their web pages.  What are =others=20 doing?
------=_NextPart_000_0098_01BE71F9.8F6EC7F0--