Core FTP

I have an issue with CoreFTP seemingly being unable to write to a directory. I believe I have all the settings correctly configured in terms of CoreFTP setup (via PASV) and user permissions on the shared folder in question. Here's the background information.

I am using Core FTP Server (version 1.0 build 294) on Windows 2003 standalone server. Core FTP is installed as a service, I have a range of ports setup for PASV (12000 - 12100), have replicated those ports on my router/firewall for port forwarding to my Windows 2003 server. My server is accessible via a domain name I have registered (for example purposes I'll call it blahblahblah.com).

Here are the settings from the 'domain properties' section of Core FTP setup (if I don't mention a setting below assume that it is unchecked or otherwise not configured differently than the default):
Domain Name: blahblahblah.com
Domain IP/Address: blahblahblah.com (resolve is checked, port is 21)
Base directory: c:\Temp\FTPTest
PASV Port Range: 12000 thru 12100
PASV address/IP: blahblahblah.com
All logging options checked, set to "hourly"

Here are the settings from the 'user details' section (if I don't mention a setting below assume that it is unchecked or otherwise not configured differently than the default):
username: blahblahblah
password: blahblahblahpassword
Home directory: c:\Temp\FTPTest (permissions RWADELCRI)
Always allow login: checked

Here is what information is available in the log file:
[20090427 09:50:09] [IP address] connected
[20090427 09:50:09] [username] USER username success
[20090427 09:50:09] [username] PASS ********* success
[20090427 09:50:09] [username] PWD success
[20090427 09:50:09] [username] FEAT success
[20090427 09:50:10] [username] TYPE A success
[20090427 09:50:10] [username] PASV success
[20090427 09:50:50] [username] TYPE I success
[20090427 09:50:50] [username] PASV success
[20090427 09:51:10] [ip address] username disconnected

I'm primarily going to use a program called Fling File Transfer with the Core FTP Server. Fling synchronizes directories remotely. Here is the log file I receive from Fling:
Server Address - Success
Log in - Success
Change Directory - Success
Get working folder - Success
Passive mode - Unsuccessful
Write - Unsuccessful

So, from CoreFTP's log file it looks like PASV mode is successful, but from Fling's log files it looks like PASV is unsuccessful.

I do a similar test from FileZilla FTP client and receive the following information via log file:
Response: 220 Core FTP Server Version 1.0, build 294, installed 3 days ago Registered
Command: USER username
Response: 331 password required for username
Command: PASS *******
Response: 230-Logged on
Response: 230
Command: SYST
Response: 215 UNIX Type: L8
Command: FEAT
Response: 211-Extensions supported
Response: AUTH SSL
Response: MODE Z
Response: 211 END
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory
Command: TYPE I
Response: 200 MODE set to I
Command: PASV
Response: 227 Entering Passive Mode (ipaddress,19,137).
Command: LIST
Response: 150 Opening ASCII mode data connection
Error: Connection timed out
Error: Failed to retrieve directory listing


So, I have more evidence to show that PASV mode isn't successfully being setup. Is there a way to get a more verbose log from Core FTP? ?Is there any other troubleshooting I can try to get this to work?

Thanks....

[quote="CP"]
To prove this, you can go to the computer that Core FTP Server is running on, and connect to it with any FTP client (from the same computer). You shouldn't have any issues unless you've assigned an IP to it that doesn't exist (in the server's "Domain IP/address" field and it's not binding on startup, etc).[/quote]

Thanks for the reply. I performed the test you suggested (establishing an FTP session within the local server), and saw the same types of problems. What you mentioned about binding made me think that my issue existed somewhere in the domain name I'm using. I have a domain (somethingsomething.com) that's tied to my home network, and the external IP address of my cable modem is tied to that domain name. In the domain/IP field of Core FTP Server I use the domain name, and I also use it in the PASV IP field. I found that the issue was resolved once I use only the local machine's IP address in the domain/IP field (but I can leave the domain name in the PASV settings).

So, it looks like my issue has something to do with domain name resolution somewhere in the process of establishing and utilizing PASV connectivity. Do I somehow have to find a way to tell my machine where Core FTP Server is running that somethingsomething.com actuially maps back to that local machine?

Setting all of the IP/domain fields to be the LOCAL address of my server (10.0.0.x) instead of my domain name (somethingsomething.com) resolved my issue. I'm now able to successfully establish a PASV connection using Core FTP. Thanks for your help!