"Jett" <Jett@discussions.microsoft.com> wrote in message
news:90859876-A587-4ACA-914F-D3C5943AD8A6@microsoft.com...
> Pardon the No0ob question but how can I tell if its bound or not? Did you
> mean in the TCPIP Properties? If so, then no, I can't see any FTP bound to
> TCPIP.
>
> "Bernard" wrote:
>
> > To get another ftp site, make sure the site is either binding to a new
IP
> > address or different port.
> > first - ensure you can start both sites, before further testing,
> > then - use ftp.exe to access both sites locally at command prompt,
> > then - move on to remote clients.
> >
> > --
> > Regards,
> > Bernard Cheah
> >
http://www.tryiis.com/ > >
http://support.microsoft.com/ > >
http://www.msmvps.com/bernard/ > >
> >
> >
> > "Jett" <Jett@discussions.microsoft.com> wrote in message
> > news:3995140C-F649-419F-8699-84942E4B87CB@microsoft.com...
> > > Our IT department recently installed Windows 2003 Server w/the IIS6
> > snap-in
> > > and FTP on two seperate Dell blades. The problem is that whenever we
> > create
> > > another FTP site (other than the default one) no one can log into it.
If I
> > > configure the Default FTP site w/an IP address and port 21, it works
great
> > ..I
> > > then ensured all he settings in the second FTP page's properties were
the
> > > same as the Default site. But when I stop the default site and start
the
> > > second FTP instance, no one can log into it either locally or from
another
> > > computer on the same network. However, If I rename the Default FTP
site,
> > > everything is just peachy, users can logon, get files, etc etc. Could
> > someone
> > > please tell me why I can't get another instance of FTP to work besides
the
> > > default site?
> > >
> > > Thanks in advance,
> > >
> > >
> > > Jett
> > > Can only get the Default FTP site working
> > >
> >
> >
> >
