[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
>>> On Mon, Jun 16, 2008 at 9:37 AM, Leigh Duncan <leigh dot duncan at wright dot edu> wrote:
> Interestingly, I had been connecting on port 21 for years--since I began
> using WS_FTP. However, changing the settings to connect on port 1021
> didn't make a difference--I still couldn't connect :-(

Most likely, if 21 used to work and 1021 doesn't work now, it's one of two problems:

1) Firewall (either on your machine or between your machine and the server)

To test it, try accessing the ports directly from a *nix command line (got Mac OS X, Linux?), where you can specify the ports to which you are trying to connect and can use the debug mode. The Windows command line FTP client doesn't allow you to specify a port, but there are few freeware versions for Windows that do. Depending upon the responses you get from a command line client (or a graphical client in debug mode if it has it), you should be able to tell if it's a firewall issue.

Make sure the entries in Limit Network Access for "IIIFTP" are set properly to allow access to the proper ranges.

2) The ports aren't properly configured on your server.

If you have shell access, do a netstat to see if 1021 is listening. If you have shell access, you can also try to FTP to localhost on 1021. If that works, but remote doesn't, it's probably a firewall issue.

HTH,
David



_____________________________________________________________________
David Jones mailto:djones at scu dot edu
Library Systems Manager http://www.scu.edu/library/
University Library fax: 408-551-1805
Santa Clara University phone: 408-551-7167
500 El Camino Real
Santa Clara CA 95053-0500
_____________________________________________________________________
Reality is that which, when you stop believing in it, doesn't go away.
-- Philip K. Dick