Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: kurga on August 27, 2006, 11:48:41 AM

Title: Ftp access problems
Post by: kurga on August 27, 2006, 11:48:41 AM

Hi, I have a problem when I try to connet to the FTP-server from outside I get an error saying that I can't logon with that username and password, but if I do it through my VPN connection there is no errors. It has worked before, and the only thing I have done is moving the server to another location. Any ideas?

Edit: I get this error from Filezilla:

Command:   USER admin
Response:   331 Password required for admin.
Command:   PASS **********
Response:   230 User admin logged in.
Status:   Connected
Command:   REST 0
Response:   350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command:   TYPE I
Response:   200 Type set to I
Command:   TYPE A
Response:   200 Type set to A
Command:   TYPE I
Response:   200 Type set to I
Command:   PWD
Response:   257 "/" is current directory.
Command:   REST 0
Response:   350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command:   PWD
Response:   257 "/" is current directory.
Command:   REST 0
Response:   350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command:   REST 0
Response:   350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command:   PWD
Response:   257 "/" is current directory.
Command:   TYPE I
Response:   200 Type set to I
Command:   PWD
Response:   257 "/" is current directory.
Command:   REST 0
Response:   350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command:   TYPE A
Response:   200 Type set to A
Command:   REST 0
Response:   350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command:   REST 0
Response:   350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
Command:   TYPE A
Response:   200 Type set to A
Response:   421 No Transfer Timeout (300 seconds): closing control connection.

Title: Ftp access problems
Post by: kurga on August 27, 2006, 04:05:50 PM

Found the solution myself, not the right one, but it seems to work. Simply changing the mode from default to passive solved my problem. But something must have changed since the problem occured.