Quote:
|
Originally Posted by teq
:read:
sFTP is set up already on most of the servers. If you let us know what your domain is or what server you are on, I can tell you for sure.
You don't really have to know beforehand if the server you are on has it or not. Choosing to use sFTP would be a preference in your FTP program.
Here is one that has the ability:
http://winscp.sourceforge.net/eng/
:atom: |
Thanks for the quick response.
I am on pass2.
I figured out the problem. Apparently my FTP client (which supports sFTP) by default uses port 21 for everything. sFTP uses a different port, apparently, and blanking out the port allowed me to connect (I guess Transmit, my FTP client, knew which port to use automatically). I'm using
Transmit, the best OS X FTP client which I highly recommend to Mac OS X users.
According to online help, port 115 is the default sFTP port, not 21 which is used for non-secure FTP. However, putting in port 115 in Transmit, my client, gave me an error, which leads me to believe you're using a different port for sFTP. It might be worthy of a FAQ entry to list exactly which port is used (in fact, I would compile a list of every port for every feature you offer, to save someone like me time in the future).
Thanks again.