Cannot connect for the life of me.

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
LillithKane
500 Command not understood
Posts: 2
Joined: 2009-07-15 01:54
First name: Lillith
Last name: Kane

Cannot connect for the life of me.

#1 Post by LillithKane » 2009-07-15 01:58

So I'm trying to connect to a friend's server to upload some things I've coded for them. I've got the right username, url, & password, but the process keeps repeating:

Status: Resolving address of home.comcast.net
Status: Connecting to 216.87.188.9:80...
Status: Connection established, waiting for welcome message...
Error: Connection timed out
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of home.comcast.net
Status: Connecting to 216.87.188.9:80...
Status: Connection established, waiting for welcome message...
Error: Connection timed out
Error: Could not connect to server

& so on.

I've tried to read through the network configuration, the FAQ, etc., but I'm not heavily into this stuff so I don't understand it. I need simple terms for a non-tech girl. Could someone please help with that?

Cypress
226 Transfer OK
Posts: 121
Joined: 2008-09-13 19:39
First name: J

Re: Cannot connect for the life of me.

#2 Post by Cypress » 2009-07-15 04:16

LillithKane wrote:So I'm trying to connect to a friend's server to upload some things I've coded for them. I've got the right username, url, & password, but the process keeps repeating:

Status: Resolving address of home.comcast.net
Status: Connecting to 216.87.188.9:80...
Status: Connection established, waiting for welcome message...
Error: Connection timed out
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of home.comcast.net
Status: Connecting to 216.87.188.9:80...
Status: Connection established, waiting for welcome message...
Error: Connection timed out
Error: Could not connect to server

& so on.

I've tried to read through the network configuration, the FAQ, etc., but I'm not heavily into this stuff so I don't understand it. I need simple terms for a non-tech girl. Could someone please help with that?
connect on port 21 would fix it.. 216.87.188.9:21

LillithKane
500 Command not understood
Posts: 2
Joined: 2009-07-15 01:54
First name: Lillith
Last name: Kane

Re: Cannot connect for the life of me.

#3 Post by LillithKane » 2009-07-15 15:38

That works! Thanks so much! :D But I've got a new problem:

The directory listing failed...?

Status: Retrieving directory listing...
Command: PASV
Response: 227 Entering Passive Mode (216,87,188,9,221,125)
Command: LIST
Response: 150 Opening BINARY mode data connection for /bin/ls.
Response: 426 Data connection: No child processes.
Error: Failed to retrieve directory listing

Edit: I found the answer. I'll post it here in case anyone runs into the same problem...
webzilla wrote:
starmanjb wrote:I have been unable to get Filezilla to work with my Comcast Personal Web Page. Comcast even gives a setup procedure for Filezilla but it doesn't work. I can't get WS_FTP to work either and it's as basic an FTP utility as you can get. When I try to log in with Filezilla, below is what I get. I've blanked out my username and password for my own safety. Can anyone help? Thanks.
...
Response: 426 Data connection: No child processes.
Error: Failed to retrieve directory listing
This is a frequently reported problem with Comcast, that has been going on for quite a while.

It turns out that the problem only occurs when you have a certain number of files in the directory that you are trying to open on Comcast. In a post on another thread ( http://forum.filezilla-project.org/view ... ast#p38337 ), jellotrees was able to narrow it down to 104 files works okay and 105 files in the directory generates the above error.

So if you can push some of your files into sub-directories and keep all of them below 105 files, then you should be able to see your directories on your Comcast ID.

chollidge
500 Command not understood
Posts: 2
Joined: 2009-07-17 02:25
First name: Cheryl
Last name: Hollidge

Re: Cannot connect for the life of me.

#4 Post by chollidge » 2009-07-17 02:30

Having the same trouble as Lillith, but port 21 isn't working for me. My firewall is configured to accept filezilla, but I am also connected to a router. Can anyone help me with settings? (also in teckie-by-necessity-only speak, please).

Cypress
226 Transfer OK
Posts: 121
Joined: 2008-09-13 19:39
First name: J

Re: Cannot connect for the life of me.

#5 Post by Cypress » 2009-07-17 02:36

chollidge wrote:but port 21 isn't working for me.
Ask your host provider or server admin for the correct port.

chollidge
500 Command not understood
Posts: 2
Joined: 2009-07-17 02:25
First name: Cheryl
Last name: Hollidge

Re: Cannot connect for the life of me.

#6 Post by chollidge » 2009-07-22 23:25

Just when I think I have everything sorted, I get this message:

Connecting to probe.filezilla-project.org
Response: 220 FZ router and firewall tester ready
USER FileZilla
Response: 331 Give any password.
PASS 3.2.6.1
Response: 230 logged on.
Checking for correct external IP address
Retrieving external IP address from http://ip.filezilla-project.org/ip.php
Checking for correct external IP address
IP 24.231.81.46 ce-cdb-ib-eg
Response: 200 OK
PREP 50068
Response: 200 Using port 50068, data token 1207069170
PORT 24,231,81,46,195,148
Response: 200 PORT command successful
LIST
Response: 150 opening data connection
Response: 503 Failure of data connection.
Server sent unexpected reply.
Connection closed

Can anyone help?

User avatar
boco
Contributor
Posts: 26935
Joined: 2006-05-01 03:28
Location: Germany

Re: Cannot connect for the life of me.

#7 Post by boco » 2009-07-23 02:25

No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org

pokerdude
500 Command not understood
Posts: 1
Joined: 2009-10-07 17:27
First name: John
Last name: Earl

Re: Cannot connect for the life of me.

#8 Post by pokerdude » 2009-10-07 17:40

The "fix" is not a fix, but a workaround. You should be able to have more than 104 files in a directory. WsFTP, command line..etc. works fine, but FileZilla does not. I believe it to be that FileZilla uses binary mode for 'LIST' and other clients typically use ascii mode.

Ironically, in an old (2.2.4a) version of FileZilla it works fine:

Status: Connecting to upload.comcast.net ...
Trace: FtpControlSocket.cpp(990): OnConnect(0) OpMode=1 OpState=-1 caller=0x003ebaf4
Status: Connected with upload.comcast.net. Waiting for welcome message...
Trace: FtpControlSocket.cpp(812): OnReceive(0) OpMode=1 OpState=-1 caller=0x003ebaf4
Response: 220 FTP server (Version 5.339PWS/AI) ready.
Command: USER XXXXXX
Trace: FtpControlSocket.cpp(812): OnReceive(0) OpMode=1 OpState=0 caller=0x003ebaf4
Response: 331 Password required for XXXXXXX
Command: PASS ********
Trace: FtpControlSocket.cpp(812): OnReceive(0) OpMode=1 OpState=3 caller=0x003ebaf4
Response: 230 User XXXXXX logged in.
Command: SYST
Trace: FtpControlSocket.cpp(812): OnReceive(0) OpMode=1 OpState=-14 caller=0x003ebaf4
Response: 215 UNIX Type: L8
Command: FEAT
Trace: FtpControlSocket.cpp(812): OnReceive(0) OpMode=1 OpState=-13 caller=0x003ebaf4
Response: 500 'FEAT': command not understood.
Status: Connected
Trace: FtpControlSocket.cpp(3975): ResetOperation(1) OpMode=1 OpState=-13 caller=0x003ebaf4
Trace: FtpControlSocket.cpp(1202): List(FALSE,0,"","",1) OpMode=0 OpState=-1 caller=0x003ebaf4
Status: Retrieving directory listing...
Command: PWD
Trace: FtpControlSocket.cpp(812): OnReceive(0) OpMode=4 OpState=0 caller=0x003ebaf4
Response: 257 "/" is current directory.
Trace: FtpControlSocket.cpp(1202): List(FALSE,0,"","",0) OpMode=4 OpState=0 caller=0x003ebaf4
Status: Directory listing successful
Trace: FtpControlSocket.cpp(3975): ResetOperation(1) OpMode=4 OpState=0 caller=0x003ebaf4


Version 3.2.8 it fails:

Status: Connecting to 216.87.188.9:21...
Status: Connection established, waiting for welcome message...
Response: 220 FTP server (Version 5.339PWS/AI) ready.
Command: USER XXXXXXXXXXXXXX
Response: 331 Password required for XXXXXXXXXXXXX.
Command: PASS ********
Response: 230 User XXXXXXXX logged in.
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 (216,87,188,9,238,55)
Command: LIST
Response: 150 Opening BINARY mode data connection for /bin/ls.
Response: 426 Data connection error: No child processes.
Error: Failed to retrieve directory listing
Error: Connection closed by server


----------------------------------
LillithKane wrote:That works! Thanks so much! :D But I've got a new problem:

The directory listing failed...?

Status: Retrieving directory listing...
Command: PASV
Response: 227 Entering Passive Mode (216,87,188,9,221,125)
Command: LIST
Response: 150 Opening BINARY mode data connection for /bin/ls.
Response: 426 Data connection: No child processes.
Error: Failed to retrieve directory listing

Edit: I found the answer. I'll post it here in case anyone runs into the same problem...
webzilla wrote:
starmanjb wrote:I have been unable to get Filezilla to work with my Comcast Personal Web Page. Comcast even gives a setup procedure for Filezilla but it doesn't work. I can't get WS_FTP to work either and it's as basic an FTP utility as you can get. When I try to log in with Filezilla, below is what I get. I've blanked out my username and password for my own safety. Can anyone help? Thanks.
...
Response: 426 Data connection: No child processes.
Error: Failed to retrieve directory listing
This is a frequently reported problem with Comcast, that has been going on for quite a while.

It turns out that the problem only occurs when you have a certain number of files in the directory that you are trying to open on Comcast. In a post on another thread ( http://forum.filezilla-project.org/view ... ast#p38337 ), jellotrees was able to narrow it down to 104 files works okay and 105 files in the directory generates the above error.

So if you can push some of your files into sub-directories and keep all of them below 105 files, then you should be able to see your directories on your Comcast ID.

User avatar
botg
Site Admin
Posts: 35562
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: Cannot connect for the life of me.

#9 Post by botg » 2009-10-07 18:40

Response: 426 Data connection error: No child processes.
Broken server. You have to contact the server administrator.

rvc1
500 Command not understood
Posts: 3
Joined: 2009-05-17 16:31
First name: Richard
Last name: Chidlow

Re: directory listing fails with Comcast personal web pages

#10 Post by rvc1 » 2009-11-09 02:51

I encountered the "Failed to retrieve Directory Listing" error last year and could not figure it out. It seems like it might be triggered by a specific number of files as it just happened again when I loaded some files which took the total over 100+. The only advice I could get previously was that it was a Comcast server problem and I should talk to them. I opened cases with Comcast and followed them through their escalation process (not for the faint hearted) but the end result was that they said they could upload a file (which was not the problem) and they could view the files from the Comcast web based admin page (which is true). Accordingly they would do nothing else and said they could not troubleshoot 3rd party software.

I dropped the subject as I had spent a significant amount of time going through Comcast tech support and needed to move on. I "solved" the problem by switching to a different ftp program which works fine.
However it is interesting that others are still running into this issue - can someone with more influence than an individual user approach Comcast?

rvc

pokerdude wrote:The "fix" is not a fix, but a workaround. You should be able to have more than 104 files in a directory. WsFTP, command line..etc. works fine, but FileZilla does not. I believe it to be that FileZilla uses binary mode for 'LIST' and other clients typically use ascii mode.
Last edited by boco on 2009-11-09 03:36, edited 1 time in total.
Reason: Added missing tag

Post Reply