filezilla server

December 30, 2010 at 07:28:08
Specs: Windows XP, 4GB
Hello
I am trying to setup filezilla server and the problem is that even though I can use it from the local network with another filezilla client by using the internal server's ip, it does not work from a filezilla client in a remote location outside of the lan.
I am using the dyndns domain to accesss as if I had a static ip. I can ping successfully this artificial static ip address. However, there is an error which does not let me log in the filezilla server.
I get an error like this:

Error: Could not read from socket: ECONNRESET - Connection reset by peer
I made sure that I opened the port 36 in the NAT section of my router addressing it to the internal static address of my server. Moreover, there are no firewalls. The windows xp firewall in the server is disabled and there aren't any other firewalls.
So, am I missing anything?
Any idea?
Thanks

Informatico a domicilio
Soluciones informaticas integrales


See More: filezilla server

Report •


#1
December 30, 2010 at 08:32:35
I think you opened the wrong port. You need ports 20 and 21 for FTP.

Report •

#2
December 30, 2010 at 08:36:11
both tcp and udp 20 and 21?
Thanks

Informatico a domicilio
Soluciones informaticas integrales


Report •

#3
December 30, 2010 at 08:49:12
I think FTP is TCP. Don't hold me to it because I have only used Mozilla to log into an FTP server never to host. I have used IIS in the past.

Report •

Related Solutions

#4
December 30, 2010 at 09:49:00
This is the message I am getting now:
Response: 230 Logged on
Command: SYST
Response: 215 UNIX emulated by FileZilla
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: REST STREAM
Response: SIZE
Response: MLST type*;size*;modify*;
Response: MLSD
Response: UTF8
Response: CLNT
Response: MFMT
Response: 211 End
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,100,4,154)
Status: Server sent passive reply with unroutable address. Using server address instead.
Command: MLSD
Response: 425 Can't open data connection.
Error: Failed to retrieve directory listing
---------------------------------------------
And
According to the port checker tool,
Error: I could not see your service on 83.61.222.55 on port (20)
How could I open this?
There are no firewalls besides win xp firewall. This win xp firewall is disabled, so I do not know what the problem can be.
any idea?

However the port 36 shows up as open.
Port 36 is set up in filezilla server as listening port.
The client is using as well this port.
There are rules in the NAT section of the router to allow connections to the private ip of the server on the ports:
36,20 and 21 just in case, both TCP and UDP.
The thing is that I am still unable to connect successfully like you could see on the message above.
Any idea?
Thanks

Informatico a domicilio
Soluciones informaticas integrales


Report •

#5
December 30, 2010 at 11:42:53
You don't have a firewall on your router? So you are not using NAT? You will still have to setup a port forwarding on your router.

Report •

#6
December 30, 2010 at 11:55:49
My router is comtrend. I have NAT enabled for 20 and 36. I do have NAT enabled for 21 as well just in case.
any other idea?
thanks

Informatico a domicilio
Soluciones informaticas integrales


Report •

#7
December 30, 2010 at 12:21:57
What size is your CIDR Block? If you have more than one static IP provided to you by your ISP and your router supports a DMZ you may want to just setup your server with one of those public IPs and put it in the DMZ so that we can take NAT out of the equation so that way we can identify if the problem is in the router or the server. I am guessing the router because you said it worked fine from the private network just not on the internet. Kinda work backwords. If that does not work then the problem has to be in the server.

Note, I would only do this for testing purposes only because you are exposing your server to the Internet.


Report •

#8
December 30, 2010 at 14:37:59
@thosecars82

try to switch of the PASV mode in the filezilla client and give it a try.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#9
December 31, 2010 at 03:50:47
I just set the private server's ip in the DMZ section of the router but this didn't help either. I am getting this error:

150 Opening data channel for directory list.
Response: 425 Can't open data connection.
Error: Failed to retrieve directory listing
Response: 421 Connection timed out.
Error: Connection closed by server

So I still do not know what to do.
Thanks

Informatico a domicilio
Soluciones informaticas integrales


Report •

#10
December 31, 2010 at 03:51:40
I set the passive mode settings of filezilla client to "Fall back to active mode" but this did not work either.
Any other idea?
Thanks

Informatico a domicilio
Soluciones informaticas integrales


Report •

#11
December 31, 2010 at 06:12:21
I would suggest to pull the Filezilla Server out of the DMZ of the router and simply configure the NAT port forwarding to the private ip address of the Filezilla Server for Port 21.
You don't have to open up port 20 because the routers do have stateful packet inspection and therefore do manage such things by itself.

Then, try to configure the Filezilla Server to use the standard port 21 for FTP.

If this all is done, try to connect from a client outside your local network, to connect to your FTP server.

Should work.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#12
December 31, 2010 at 07:19:27
SOLVED:

When I trIed to set the NAT with port 21, the router prompts with this message:
"Since port 21 is used, the DSL router FTP server port will be moved to port 2121."

Anyways, I still did that, and now it works with filezilla server listening on port 21. I do not know why it now works. The truth is that I also updated filezilla client to the last version as I was offered by a pop up message. Therefore, I do not know if the problem had to do with the fact of not having the last filezilla client update or may be other. I hope the problem had to do with the filezilla client update because otherwise I would not know why it is working now.
Thanks anyways.

Informatico a domicilio
Soluciones informaticas integrales


Report •

#13
December 31, 2010 at 07:37:06
It has to do with the build in FTP of your router, that ran at the same port 21 as the Filezilla server.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#14
December 31, 2010 at 08:14:35
Another question: the filezilla client ftp only shows the home path. But I have several shared folders in filezilla servers. How can access this shared folders that are not the home folder from the filezilla client?
Thanks

Informatico a domicilio
Soluciones informaticas integrales


Report •

#15
December 31, 2010 at 08:41:30
In the site manager of the Filezilla Server, you have to set the Default remote directory to / to see all the shared folders.
Otherwise, the clients are not allowed, to change to an upper level in the directory tree.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#16
December 31, 2010 at 08:52:58
SOLVED.
I just had to edit the aliases in the filezilla server's shared folders.
Thanks

Informatico a domicilio
Soluciones informaticas integrales


Report •

#17
December 31, 2010 at 10:05:27
You are welcome !!!

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •


Ask Question