New to FileZilla, won't connect

[Hume Kading]

Started using FileZilla about 2 weeks ago. At first it worked perfectly and I loved it. Now it won't connect to a Windows server, which it did before.

I haven't changed any FileZilla settings.

I installed it on my wife's computer after it stopped working on mine, and got the same error message.

FileZilla did and does connect to a Unix box at the same host provider.

My other FTP client, WS_FTP Pro will connect to the Windows server but won't upload or download very long without bombing out.

I am using Windows XP Pro and have McAfee firewall. There were no major software changes during the period of time involved, with the possible exception I re-installed MS Visual Studio 6.0.

I think the problem is with the server I am trying to connect to, but the person who manages it can connect with FileZilla so he says it's not.

Below are the log items I get when attempting to connect.

Can anybody help?

Status: Connecting to 209.240.72.16 ...
Status: Connected with 209.240.72.16. Waiting for welcome message...
Response: 220 Serv-U FTP Server v6.2 for WinSock ready...
Command: USER humekading
Response: 331 User name okay, need password.
Command: PASS *******
Response: 230 User logged in, proceed.
Command: FEAT
Response: 211-Extension supported
Response: CLNT
Response: MDTM
Response: MDTM YYYYMMDDHHMMSS[+-TZ];filename
Response: SIZE
Response: SITE PSWD;EXEC;SET;INDEX;ZONE;CHMOD;MSG
Response: REST STREAM
Response: XCRC filename;start;end
Response: MODE Z
Response: MLST Type*;Size*;Create;Modify*;Win32.ea*;
Response: 211 End
Command: SYST
Response: 215 UNIX Type: L8
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: MODE Z
Response: 200 MODE Z ok.
Command: TYPE A
Response: 200 Type set to A.
Command: PASV
Response: 227 Entering Passive Mode (209,240,72,16,5,187)
Command: LIST
Error: Transfer channel can't be opened. Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error: Could not retrieve directory listing
Command: REST 0
Error: Timeout detected!
Status: Waiting to retry... (5 retries left)
Status: Connecting to 209.240.72.16 ...
Status: Connected with 209.240.72.16. Waiting for welcome message...
Response: 220 Serv-U FTP Server v6.2 for WinSock ready...
Command: USER humekading
Response: 331 User name okay, need password.
Command: PASS *******
Response: 230 User logged in, proceed.
Command: FEAT
Response: 211-Extension supported
Response: CLNT
Response: MDTM
Response: MDTM YYYYMMDDHHMMSS[+-TZ];filename
Response: SIZE
Response: SITE PSWD;EXEC;SET;INDEX;ZONE;CHMOD;MSG
Response: REST STREAM
Response: XCRC filename;start;end
Response: MODE Z
Response: MLST Type*;Size*;Create;Modify*;Win32.ea*;
Response: 211 End
Command: SYST
Response: 215 UNIX Type: L8
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: MODE Z
Response: 200 MODE Z ok.
Command: OPTS MODE Z LEVEL 8
Response: 200 MODE Z LEVEL set to 8.
Command: TYPE A
Response: 200 Type set to A.
Command: PASV
Response: 227 Entering Passive Mode (209,240,72,16,5,188)
Command: LIST
Error: Transfer channel can't be opened. Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error: Could not retrieve directory listing
Command: PWD
Error: Timeout detected!
Status: Waiting to retry... (4 retries left)
Status: Connecting to 209.240.72.16 ...
Status: Connected with 209.240.72.16. Waiting for welcome message...
Response: 220 Serv-U FTP Server v6.2 for WinSock ready...
Command: USER humekading
Response: 331 User name okay, need password.
Command: PASS *******
Response: 230 User logged in, proceed.
Command: FEAT
Response: 211-Extension supported
Response: CLNT
Response: MDTM
Response: MDTM YYYYMMDDHHMMSS[+-TZ];filename
Response: SIZE
Response: SITE PSWD;EXEC;SET;INDEX;ZONE;CHMOD;MSG
Response: REST STREAM
Response: XCRC filename;start;end
Response: MODE Z
Response: MLST Type*;Size*;Create;Modify*;Win32.ea*;
Response: 211 End
Command: SYST
Response: 215 UNIX Type: L8
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: MODE Z
Response: 200 MODE Z ok.
Command: OPTS MODE Z LEVEL 8
Response: 200 MODE Z LEVEL set to 8.
Command: TYPE A
Response: 200 Type set to A.
Command: PASV
Response: 227 Entering Passive Mode (209,240,72,16,5,189)
Command: LIST
Error: Transfer channel can't be opened. Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error: Could not retrieve directory listing
Command: TYPE A

[Hume Kading]

or is this a totally new issue nobody esle has experienced before?

[Zythan]

Hello,

Could you tell me which version of the firewall you are using and what antivirus soft you use ? Did you manually update it or did the update run automatically ?

Also, how do you connect to your ISP ?

TIA

Zythan

[Zythan]

Hello,

or is this a totally new issue nobody esle has experienced before?

This is not so new, either you have a firewall that is getting in the way or the server is using a different port range for the passive mode, this your server admin should know by looking in his logs.

But first lets look at you end.

Zythan

[Hume Kading]

using:

Windows XP Pro (firewall is turned off)

McAfee Security Center Suite 8.0 which includes the firewall, privacy service, virus scan and spam killer

Also using a 2 Wire portal (router) for the home network

Thing is, I disconnected the portal and hooked the computer up directly to the DSL modem, the Windows Firewall is always off, and I shut down all the McAfee functions, and I still couldn't connect

If it's at my end how come I can connect to the Unix box at the same provider as the Windows box, and it worked on the Windows server for about 1-2 weeks before it stopped working at that server only.

Anybody got another Windows server I can test connect to?