[windows2000] Re: Changing FTP ports
- From: FalconTech <falcontech@xxxxxxxxxxxxx>
- To: windows2000@xxxxxxxxxxxxx
- Date: Wed, 28 Mar 2007 13:07:46 -1000
I've also used "Core FTP" it works fine but has fewer features than
WinSCP. There's also SmartFTP and SFTPplus (has SSH server ability) that
have other options and as many or more features than WinSCP. On the
Linux side theres gFTP.
You might look at this:
http://en.wikipedia.org/wiki/Comparison_of_FTP_clients
Jim
On Wed, 2007-03-28 at 09:21 +0200, Sorin Srbu wrote:
> FalconTech <> wrote on Tuesday, March 27, 2007 11:34 PM:
>
> Is there any other free sftp client for windows than WinSCP? It rules at our
> dept', but I'm always on the lookout for better software. Not that WinSCP is
> bad in any, quite the contrary.
>
> Especially its CLI capabilities is great. I use it to transfer webserver-logs
> from my DMZ:ed linux-webserver to windows and create Analog stat reports.
> It's rock solid.
>
>
>
> > Oh ya, and I would recommend that you use SFTP instead of FTP. Which will
> > require port 22 (uses SSH) to be open instead of port 21. WinSCP is a good
> > client that supports SFTP (SSH).
> >
> > On Tue, 2007-03-27 at 07:51 -0400, Ray Costanzo wrote:
> >
> >
> > Hi group,
> >
> >
> >
> > I have a W2K server behind a home-style D-Link router at home, and I had
> > it setup such that port 21 was forwarded to this server so that I could ftp
> > files between work and home. At the IIS level, I had the FTP site set to
> > only allow connections from my work IP address. This worked fine as far as
> > keeping other people out, but my event logs would still be filled up by all
> > the failed attempts from those bastards out there who are trying to get
> > into any FTP site they can.
> >
> >
> >
> > So, what I did was changed the FTP port to some other arbitrary port
> > number (2025) in IIS and updated my router accordingly. But now, when I
> > ftp in, I can connect, but I can’t transfer any data. I think this may
> > have something to do with that active vs. passive thing where the FTP
> > command communication uses one port and data uses another or something like
> > that. Would anyone know what I can do to get this working again? I tried
> > reforwarding port 21 to the server again in case IIS still needed that port
> > for actual data transfer, but that didn’t help. Previously, I had only
> > port 21 forwarded, not 21 & 22 or anything like that.
> >
> >
> >
> > Sample FTP session:
> >
> >
> >
> > ftp> open home 2025
> >
> > Connected to home.
> >
> > 220 server Microsoft FTP Service (Version 5.0).
> >
> > User (home:(none)): SomeUserAccount
> >
> > 331 Password required for SomeUserAccount.
> >
> > Password:
> >
> > 230 User SomeUserAccount logged in.
> >
> > ftp> dir
> >
> > 500 Invalid PORT Command.
> >
> > 150 Opening ASCII mode data connection for /bin/ls.
> >
> > --Never finishes and just sits here forever; when I break out, this is
> > the
> > error:
> >
> > 425 Can't open data connection.
> >
> >
> >
> > Thanks for anything,
> >
> >
> >
> > Ray at work
>
> *****************************
> New Site from The Kenzig Group!
> Windows Vista Links, list options
> and info are available at:
> http://www.VistaPop.com
> *****************************
> To Unsubscribe, set digest or vacation
> mode or view archives use the below link.
>
> http://thethin.net/win2000list.cfm
Other related posts:
