BC2 and BC3 hanging on CLNT command from remote server

[paule123]

Got this problem with BC2 and also BC3 ... BC logs in to the remote ServU FTP server ok, BC sends USER, PASS, FEAT command ok, then it looks like the remote server answers back with CLNT. At that point BC hangs and eventually times out. Tried passive mode on/off.
Both machines are running Windows 2003.

9/16/2008 11:12:32 PM Stat> Connected.
9/16/2008 11:12:32 PM Recv> 220 Serv-U FTP Server v6.3 for WinSock ready...
9/16/2008 11:12:32 PM Sent> HOST [1.2.3.4]
9/16/2008 11:12:32 PM Recv> 530 Not logged in.
9/16/2008 11:12:32 PM Sent> USER xxxx
9/16/2008 11:12:32 PM Recv> 331 User name okay, need password.
9/16/2008 11:12:32 PM Sent> PASS ********
9/16/2008 11:12:32 PM Recv> 230 User logged in, proceed.
9/16/2008 11:12:32 PM Sent> FEAT
9/16/2008 11:12:32 PM Recv> 211-Extension supported
9/16/2008 11:12:33 PM Recv> CLNT
9/16/2008 11:12:47 PM Stat> Disconnected.

[Zoë]

Are you able to connect using other FTP clients? If you have BC2 installed, have you tried switching the "FTP Library" setting in the advanced FTP options?

[paule123]

Yes, I can connect with WS_FTP Pro 2007. I tried switching the libraries in BC2, but no difference.

[Zoë]

I can't see any obvious problems with it; it looks like the server isn't returning anything after "CLNT", and BC is waiting for the end of the FEAT listing and timing out. Does WS_FTP send FEAT, and does the log show a valid response to it? Do you know which version of Serv-U the server is running? Have you tried connecting to the server from any other computers?

[paule123]

The Serv-U version is 6.3. I can connect fine from another computer with DOS FTP and WS_FTP Pro, but not BC2 or BC3.

Interesting thing is in WS_FTP if I manually tell it the server type is Serv-U I get an immediate connection, otherwise if I leave it to "Auto detect" server type it will take a long time to connect.

Here's the WS_FTP connection log on a successful connect with server type = Serv-U:

220 Serv-U FTP Server v6.3 for WinSock ready...
Host type (1): Serv-U
USER xxx
331 User name okay, need password.
PASS (hidden)
230 User logged in, proceed.
Host type (I): Serv-U
PWD
257 "/e:" is current directory.TYPE A
200 Type set to A.
PASV
227 Entering Passive Mode (1,2,3,4,19,152)
connecting data channel to 1.2.3.4:19,152(5016)
data channel connected to 1.2.3.4:19,152(5016)
LIST
150 Opening ASCII mode data connection for /bin/ls.
transferred 1321 bytes in < 0.001 seconds, 10568.000 kbps ( 1321.000 kBps), transfer succeeded.
226 Transfer complete.


Here is WS_FTP connection log with server type = Automatic detect:

220 Serv-U FTP Server v6.3 for WinSock ready...
Host type (1): Serv-U
USER xxx
331 User name okay, need password.
PASS (hidden)
230 User logged in, proceed.
Host type (I): Serv-U
PWD
257 "/e:" is current directory.
New connection OK. Reissuing command.
TYPE A
200 Type set to A.
PASV
227 Entering Passive Mode (1,2,3,4,19,153)
connecting data channel to 1.2.3.4:19,153(5017)
data channel connected to 1.2.3.4:19,153(5017)
LIST
150 Opening ASCII mode data connection for /bin/ls.
transferred 1321 bytes in < 0.001 seconds, 10568.000 kbps ( 1321.000 kBps), transfer succeeded.
226 Transfer complete.

[Zoë]

In WS_FTP, how long is a long time? Try increasing the Connection->Read timeout value in the FTP profile to something longer than that.

It doesn't appear WS_FTP sends the FEAT command that's causing the problem. If you have time, can you try Filezilla or WinSCP to see if they have similar problems.

[paule123]

I increased the timeout to 10 minutes, and all it does is increase the time until it fails.

9/23/2008 3:44:00 PM Recv> CLNT
9/23/2008 3:54:00 PM Sent> QUIT
9/23/2008 3:54:00 PM Stat> Disconnected.
9/23/2008 3:54:00 PM Read timed out.

[Zoë]

Have you tried either of the clients I mentioned in my previous post? BC isn't doing anything unusual with regards to the FEAT command, so I'd expect either of those to fail as well. If that's the case you'll need to contact Serv-U's tech support and ask them about it.

[paule123]

I upgraded the server to the latest Serv-U version 7.2.x and now BC2 and BC3 are working fine.