FileZilla Forums

Hello.
Downloaded filezilla server last night and started to configure it, a fellow helped me by trying to connect but after ripping half of the hair from my head we figured out he had a router issue that stopped him from getting connected.
Another fellow tried to connect and got right in, could upload files download and all that.
Today i tried to get my sister to connect by using filezilla client and a preconfigured filezilla.xml that she imported.

She's running Win XP - sp2 with builtin firewall
Filezilla client, 3.1.2
No router as i know of, external ip as shown in windows is 82.55.xxx.xxx
Both filezilla and the port are on the firewall exception list.
Tried with the firewall turned off but failed then to.

15:11:47 Status: Connecting to 83.254.xxx.xxx:55755...
15:12:08 Error: Connection timed out
15:12:08 Error: Could not connect to server
15:12:08 Status: Waiting to retry...
15:12:13 Status: Connecting to 83.254.xxx.xxx:55755...
15:12:34 Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
15:12:34 Error: Could not connect to server
15:12:34 Status: Waiting to retry...
15:12:39 Status: Connecting to 83.254.xxx.xxx:55755...
15:13:00 Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
15:13:00 Error: Could not connect to server

What does the above log tell me?
Filezilla server-logs doesnt show any connecton attempt at all from the client, wrong or right to say the problem is in the "client computer" ?
Where is filezilla client logs stored?
Could the antivirus-program she uses be the problem?

Any help would be appreciated as im flying blind here, barely know what ftp stands for.
Im a bit paranoid so edited out parts of my ip-adress.
Regards

A firewall or router at the server side stops the incoming connection before it can arrive at the server. I'd say a firewall, because router port-forwards usually don't reset.

To rule out her client, let her connect to a public server: ftp://ftp.debian.org for example. If that works, it's the server (or an evil ISP blocking ports).

boco wrote:A firewall or router at the server side stops the incoming connection before it can arrive at the server.

Is it possible for a router/firewall to only block some computers while others can login troublefree?

My computer is in Sweden, the fellow that logged in last night also livs in Sweden.
My sister that can't loggin livs in Uk.
Can the location of my sisters computer cause trouble?

EDIT:
Disabled both the firewall on my computer(winxp-sp2 builtin firewall) and the cablemodem firewall.
Still a no go.

My cablemodem/router is a scientific atlanta epc2434 if it matters.

After tearing the rest of my hair off i remembered i had changed port last night so changed the portforwarding in my router and my sister could connect and upload, download, delete files and create folders.

Looked through the log and could se an error comming up quite often, "421 Can't create socket",
Is it a problem or can it be ignored?

I have only 1 port open, does it make any difference to open more?
There will only be 1 user logging on to the ftp-server.

Read the Network Configuration guide for details. It has all the answers.

I'd say 20 ports minimum. In Windows, it takes about 4 minutes before a port can be reused.

I'm having the same problem trying to log in to my site at myweb.tiscali.co.uk. I have no problem logging in with the ftp app in HTML-Kit or using the ftp commands at the dos prompt, nor do I have any problems logging in to my other, non-Tiscali, sites using Filezilla

Got it. One has to include ftp. in front of the myweb.tiscali.co.uk.

Challe wrote: Any help would be appreciated as im flying blind here, barely know what ftp stands for.

ftp stands for file transfer protocol.

I had no problems accessing my websites until I got the latest update for filezilla - now I keep getting a connection timed out error as well. Cannot figure this out.

idaknow wrote:ftp stands for file transfer protocol.

Thats basicly all i knew before i started with the server.

boco wrote:I'd say 20 ports minimum. In Windows, it takes about 4 minutes before a port can be reused.

Raised it from 1 to 4 and works better now, solved the 421, cant create socket problem.

botg wrote:Read the Network Configuration guide for details. It has all the answers.

I have but since english isnt my native language i had a hard time understanding al the technical terms.


I have one last question, the client doesnt update the file-list when login in.
The client logged in, saw the images and logged out.
Added a couple of mp3's(with the server running) and had the client logg in again but could only see the images.
After some fiddling around i updated the filelist manually(small icon with 2 green arrows in a circle) and the mp3 came up.
How can i make the client automaticly update the filelist everytime the user logs in?

Directories are cached (for the session only), all you can do is pressing F5, pushing the button or closing/reopening Filezilla AFAIK.

but how to do it? can u explain more,

even I am facing this problem for all the FTP which are saved in my filezilla.
all connections were working before a month and suddenly it stopped with following error.

pls help....

12:49:55 Status: Resolving address of ftp.xxxxxxxx.com
12:49:55 Status: Connecting to 180.179.174.97:21...
12:49:55 Status: Connection established, waiting for welcome message...
12:49:55 Error: Could not read from socket: ECONNRESET - Connection reset by peer
12:49:55 Error: Could not connect to server
12:49:55 Status: Waiting to retry...
12:50:00 Status: Resolving address of ftp.xxxxxxxx.com
12:50:00 Status: Connecting to 180.179.174.97:21...
12:50:00 Status: Connection established, waiting for welcome message...
12:50:00 Error: Could not read from socket: ECONNRESET - Connection reset by peer
12:50:00 Error: Could not connect to server

Works for me. Check the firewall.