Our Products:   CompleteFTP  edtFTPnet/Free  edtFTPnet/PRO  edtFTPj/Free  edtFTPj/PRO
0 votes
2.6k views
in .NET FTP by (180 points)
Howdy

I've inherited a legacy application (written a number of years ago, and the authors have moved on) which uses edtftpnet.dll for some FTP actions. The version we seem to have is 1.2.1 - which I gather is probably discontinued, but trying my luck here anyway!

We're having some odd problems with the use of the FTPclient.dir() method: From what we can see the API connects to the remote box, gets a response, but then just hangs. Our own code terminates the thread the connection is running in after 10 minutes of idle time.

The remote FTP server is up, and running (it's one of ours). I can connect manually using the same credentials as the application, and from the same machine.

The key thing here is that this is the first time we've tried running the application on a Server 2008 machine. Previously, it's been running on Server 2003 installations without issue.

So, I guess the first question is this - are we pushing our luck trying to get v1.2.1 of the DLL running on a 2008 machine ? Has anyone else had any problems with this ?

Thanks
Z

Apologies if this is the wrong place to post. I'm new around these parts :)

2 Answers

0 votes
by (162k points)
It's the right place to post. 1.2.1 is 7 years old. But I would expect it should work.

Hanging problems like these are usually firewall problems. Are you able to enable logging?
0 votes
by (180 points)
Hi, thanks for the quick response..

I *think* we have logging enabled. In our application logs we have the following - which appears to be coming from FTPClient.dir() - although I can't be sure.

16:30:06 - FTPClient Dir - Start 16:30:06 - FTPClient Dir-FTPDataSocket - SetSocketTimeout Start 16:30:06 - FTPClient Dir-FTPDataSocket - timeout > 0 16:30:06 - FTPClient Dir-FTPDataSocket - SetSocketTimeout End 16:30:06 - FTPClient Dir - set up data channel 16:30:06 - FTPClient Dir - send the retrieve command 16:30:06 - FTPClient Dir - some FTP servers bomb out 16:30:06 - FTPClient Dir - check the control response 16:30:06 - FTPClient Dir - an empty array of files for 450/550 16:30:06 - FTPClient Dir - a normal reply ... extract the file list 16:30:06 - FTPClient Dir - extract the file list 16:30:06 - FTPClient Dir-FTPActiveDataSocket - DataStream Start 16:30:06 - FTPClient Dir-FTPActiveDataSocket - Start 16:30:06 - FTPClient Dir-FTPActiveDataSocket - acceptedSock == null
This is an excerpt from our app log. There's no further activity from FTPClient Dir in the log. Our wrapper to the call to .dir() should output a specific confirmation to say it's back, but we don't see it. Nothing else happens with the thread making the call to .dir() until it's shutdown due to being idle 10 minutes later (a safety catch in our app).

Any pointers on this will be welcome !

Thanks
Z



If this isn't the logging you'd expect to see, can you point me in the direction on some notes on how to enable this ?

Categories

...