|
|
You're in the
iis ftp
group:For Lance
iis ftp:
try the Quick 'n Easy FTP Server that you recommended from Pablo Software. Thanks for the heads-up on that package! It certainly LOOKS more promising. I am nevertheless still having some difficulties getting files to transfer. And some difficulty understanding exactly what certain terms used by that program mean. Despite having opened port 21 for all services in the network and having set my router to forward FTP Requests on Port 21 to the FTP host computer's IP Address (using the 192.168.x.x IP address structure,) errors still pop up when I try to access the host from another PC in my LAN. Pablo Software makes only a very fuzzy statement as to the purpose of the user's Home Directory. At first, I presumed that would be the name of the folder containing files available to download. However, the documentation doesn't really say that. I don't have a copy handy from which to quote, but it states some mumbo jumbo about the home directory being the folder where information about the user's account is stored. If that's the case, where and how would I go about directing the user to the FTP Files download folder? Also, Pablo Software's documentation goes into discussion about PASV ports. Do I need to setup forwarding for such a broad range of ports as 1024 - 65535 (or whatever it is)? Or should I only setup port 21? AND should whatever I setup be set to TCP, UDP, or BOTH? I don't seem to be able to get FTP to work at all with Windows XP Pro SP2 Firewall open, even though I've setup Exceptions for Quick 'n Easy FTP Server etc. You've been a terrific help already, and I sincerely appreciate it. I shall be most grateful if you can guide me through the rest of getting this up and running. -- With kindest regards, Dick Smith
Port 21 isn't the only one that's used for FTP. Maybe this description
will be better: http://www.allaboutjake.com/network/linksys/ftp.html I suggest temprarily dropping firewalls on your LAN and try FTP'ing back and forth using just your LAN computers. Once you get FTP working without firewalls, raise the firewalls, make firewall exceptions and troubleshoot it again. You sure you don't want to use a photo service like Photobucket? They even have limited free use: http://photobucket.com/ Lance ***** AA Smith thought carefully and wrote on 7/19/2005 7:33 PM: [quoted text, click to view] > Since I had so much trouble with the first FTP server I tried, I decided to
> try the Quick 'n Easy FTP Server that you recommended from Pablo Software. > Thanks for the heads-up on that package! It certainly LOOKS more promising. > > I am nevertheless still having some difficulties getting files to transfer. > And some difficulty understanding exactly what certain terms used by that > program mean. > > Despite having opened port 21 for all services in the network and having set > my router to forward FTP Requests on Port 21 to the FTP host computer's IP > Address (using the 192.168.x.x IP address structure,) errors still pop up > when I try to access the host from another PC in my LAN. > > Pablo Software makes only a very fuzzy statement as to the purpose of the > user's Home Directory. At first, I presumed that would be the name of the > folder containing files available to download. However, the documentation > doesn't really say that. I don't have a copy handy from which to quote, but > it states some mumbo jumbo about the home directory being the folder where > information about the user's account is stored. > > If that's the case, where and how would I go about directing the user to the > FTP Files download folder? > > Also, Pablo Software's documentation goes into discussion about PASV ports. > Do I need to setup forwarding for such a broad range of ports as 1024 - > 65535 (or whatever it is)? Or should I only setup port 21? > > AND should whatever I setup be set to TCP, UDP, or BOTH? > > I don't seem to be able to get FTP to work at all with Windows XP Pro SP2 > Firewall open, even though I've setup Exceptions for Quick 'n Easy FTP > Server etc. > > You've been a terrific help already, and I sincerely appreciate it. I shall > be most grateful if you can guide me through the rest of getting this up and
Thanks, again, Lance!
One thing that is not abundantly clear in my mind is whether or not normal/regular mode, Port 21 (or 20 & 21,) and PASV Ports ranging from 1024 - 65535 are mutually exclusive. That is, should I setup for PASV mode only if I setup PASV at all or should I setup for both regular and PASV modes? And thanks especially for the heads-up on Pablo. That application works quite well, though I'm still having some problems with users outside my LAN. Works ok inside the LAN. Thanks also for the heads up on photobucket, but services like that (free or otherwise) really don't suit my needs. -- With kindest regards, Dick Smith [quoted text, click to view] "Lance" <lltbhill@link_earth.net> wrote in message news:%23iS4ffajFHA.3256@TK2MSFTNGP12.phx.gbl... > Port 21 isn't the only one that's used for FTP. Maybe this description > will be better: > http://www.allaboutjake.com/network/linksys/ftp.html > > I suggest temprarily dropping firewalls on your LAN and try FTP'ing back > and forth using just your LAN computers. Once you get FTP working without > firewalls, raise the firewalls, make firewall exceptions and troubleshoot > it again. > > You sure you don't want to use a photo service like Photobucket? They even > have limited free use: > http://photobucket.com/ > > Lance > ***** > > AA Smith thought carefully and wrote on 7/19/2005 7:33 PM: >> Since I had so much trouble with the first FTP server I tried, I decided >> to try the Quick 'n Easy FTP Server that you recommended from Pablo >> Software. Thanks for the heads-up on that package! It certainly LOOKS >> more promising. >> >> I am nevertheless still having some difficulties getting files to >> transfer. And some difficulty understanding exactly what certain terms >> used by that program mean. >> >> Despite having opened port 21 for all services in the network and having >> set my router to forward FTP Requests on Port 21 to the FTP host >> computer's IP Address (using the 192.168.x.x IP address structure,) >> errors still pop up when I try to access the host from another PC in my >> LAN. >> >> Pablo Software makes only a very fuzzy statement as to the purpose of the >> user's Home Directory. At first, I presumed that would be the name of >> the folder containing files available to download. However, the >> documentation doesn't really say that. I don't have a copy handy from >> which to quote, but it states some mumbo jumbo about the home directory >> being the folder where information about the user's account is stored. >> >> If that's the case, where and how would I go about directing the user to >> the FTP Files download folder? >> >> Also, Pablo Software's documentation goes into discussion about PASV >> ports. Do I need to setup forwarding for such a broad range of ports as >> 1024 - 65535 (or whatever it is)? Or should I only setup port 21? >> >> AND should whatever I setup be set to TCP, UDP, or BOTH? >> >> I don't seem to be able to get FTP to work at all with Windows XP Pro SP2 >> Firewall open, even though I've setup Exceptions for Quick 'n Easy FTP >> Server etc. >> >> You've been a terrific help already, and I sincerely appreciate it. I >> shall be most grateful if you can guide me through the rest of getting >> this up and running.
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |