[windows2000] Re: Changing FTP ports
- From: "Sorin Srbu" <sorin.srbu@xxxxxxxxxxxxx>
- To: <windows2000@xxxxxxxxxxxxx>
- Date: Tue, 27 Mar 2007 15:39:43 +0200
Jon Spriggs <> wrote on Tuesday, March 27, 2007 3:29 PM:
Good info!
> Hi Ray,
>
> In between password and dir, type pasv, that should solve it. I've seen
> other posts which explain how to solve the issue in various browsers which
> should fix access from there...
>
> HOWEVER - I'd strongly recommend moving away from using FTP as it's awfully
> insecure. Try CopSSH ( http://www.google.com/search?q=copssh
> <http://www.google.com/search?q=copssh> ) and winscp (winscp.net
> <http://winscp.net/> ) to provide server and client parts. Or, have a
> self-signed SSL based protected web directory and use a web form to upload
> files (as suggested on the security-basics list just recently). It was also
> suggested there that using a publicly exposed webdav folder is the
> preferred Microsoft solution.
>
> Rgds,
>
> Jon
>
>
> On 27/03/07, Ray Costanzo < rcostanzo@xxxxxxxxxxxxxxx> 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:
