Microsoft FTP7 Server configuration - just can't get it to work
I am trying to get a FTP site configured for the sole purpose of backing up cPanel accounts on my domain's fileserver/nas.
I installed IIS and FTP7 on a spare 2008R2 server we have in the office, and performed what I thought was a pretty basic configuration. My current problem is that I cannot get the FTP site to properly use my chosen folder location, located on a shared drive that is actually our NAS. If I have it configured to point to that folder, I get the message "530 User cannot log in, home directory inaccessible."
At first I tried giving full access/owner ship to the user I created for doing backups, then I tried connecting as my domain admin and reverted permissions to administrators, same message every time. I even mimicked the permissions on the default ftp root folder (SYSTEM as owner, then I just gave "everyone" full access)
But if I configure it to use the default FTP folder, c:\inetpub\ftproot, I can connect to the server but it still doesnt work. I get the following happen:
I have set my data port range to 56000-56500 and forwarded those through my network firewall and windows firewall, as well as my ftp port (not standard)
Once I get the FTP Server working *at all* I want to get it configured to use my NAS for storage since this will be for storing backup snapshots and I want plenty of space available.
I want to add also that I was monitoring through Process Monitor and found no real issues, and also my Ftp logs show nothing of note
I installed IIS and FTP7 on a spare 2008R2 server we have in the office, and performed what I thought was a pretty basic configuration. My current problem is that I cannot get the FTP site to properly use my chosen folder location, located on a shared drive that is actually our NAS. If I have it configured to point to that folder, I get the message "530 User cannot log in, home directory inaccessible."
At first I tried giving full access/owner ship to the user I created for doing backups, then I tried connecting as my domain admin and reverted permissions to administrators, same message every time. I even mimicked the permissions on the default ftp root folder (SYSTEM as owner, then I just gave "everyone" full access)
But if I configure it to use the default FTP folder, c:\inetpub\ftproot, I can connect to the server but it still doesnt work. I get the following happen:
Status: Resolving address of ***.****.com
Status: Connecting to 50.**.**.73:****...
Status: Connection established, waiting for welcome message...
Response: 220 Microsoft FTP Service
Command: USER **backupuser**
Response: 331 Password required for **backupuser**.
Command: PASS *********
Response: 230 User logged in.
Command: OPTS UTF8 ON
Response: 200 OPTS UTF8 command successful - UTF8 encoding now ON.
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 (50,**,**,73,229,0).
Command: LIST
Response: 150 Opening BINARY mode data connection.
(5 second pause)
Error: Connection timed out
Error: Failed to retrieve directory listingI have set my data port range to 56000-56500 and forwarded those through my network firewall and windows firewall, as well as my ftp port (not standard)
Once I get the FTP Server working *at all* I want to get it configured to use my NAS for storage since this will be for storing backup snapshots and I want plenty of space available.
I want to add also that I was monitoring through Process Monitor and found no real issues, and also my Ftp logs show nothing of note
Aaron Tomosky
A little off topic but since no one has answered yet: have you looked at FileZilla FTP server? It's ridiculously easy to setup. I use it on all my remote sites to do stuff just like you are trying to do.
Start by upgrading to FTP 7.5. To be honest, though, I also use FileZilla FTP server. It is free and easy.
The log shows this:
227 Entering Passive Mode (50,**,**,73,229,0)
That means the FTP client thinks that it should make an outbound connection to port 58624 on IP address 50.*.*.73 but it can't establish the connection.
So maybe the problem is that the client's firewall does not allow it and maybe the problem is the server's firewall is configured to allow inbound connections on range 56000-56500 but the server is expecting the connection on 58624.
To calculate the port number look at the 5th and 6th number in the PASV response. Multiply the 5th number by 256 and then add the value of the 6th number so in your case:
(229 * 256) + 0 = 58624. Note: The first 4 numbers of the PASV response are the IP address where the client is supposed to connect.
227 Entering Passive Mode (50,**,**,73,229,0)
That means the FTP client thinks that it should make an outbound connection to port 58624 on IP address 50.*.*.73 but it can't establish the connection.
So maybe the problem is that the client's firewall does not allow it and maybe the problem is the server's firewall is configured to allow inbound connections on range 56000-56500 but the server is expecting the connection on 58624.
To calculate the port number look at the 5th and 6th number in the PASV response. Multiply the 5th number by 256 and then add the value of the 6th number so in your case:
(229 * 256) + 0 = 58624. Note: The first 4 numbers of the PASV response are the IP address where the client is supposed to connect.
ASKER
I am on 7.5 I think, I didn't realize at first.
I would love to use Filezilla but for some reason the stupid sourceforge installer wont run on that machine, it cannot detect an internet connection... completely asinine. No other mirror I can find for an installer, either.
I've given up on IIS FTP though. What a crock.
I would love to use Filezilla but for some reason the stupid sourceforge installer wont run on that machine, it cannot detect an internet connection... completely asinine. No other mirror I can find for an installer, either.
I've given up on IIS FTP though. What a crock.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The link aarontomosky supplied is the actual program. No installer required.