Sign in to follow this  
Followers 0

Filezilla Problems: "550 Cwd Failed. "/": Permission Denied"

1 post in this topic

Posted · Report post

Good day to all.

I am trying to get FileZilla Server running on my Acer H340 WHS v1 box but am running into problems. I am hoping that some kind soul can tell me what I've missed doing.

I followed two different step-by-step installation tutorials: the best of the two is from Computing On Demand at http://computingondemand.com/filezilla-ftp-server-on-whs/ , the other is from Tested.com at http://www.tested.com/news/how-to-add-an-ftp-server-to-your-windows-home-server/403/

Although both tutorials are quite similar, there are small differences. I've tried both ways.

What I see on my WHS box when trying to initiate a FTP transfer is:

(000026)1/14/2012 23:46:19 PM - (not logged in) (75.158.6.224)> Connected, sending welcome message...

(000026)1/14/2012 23:46:19 PM - (not logged in) (75.158.6.224)> 220-FileZilla Server version 0.9.40 beta

(000026)1/14/2012 23:46:19 PM - (not logged in) (75.158.6.224)> 220-written by Tim Kosse (Tim.Kosse@gmx.de)

(000026)1/14/2012 23:46:19 PM - (not logged in) (75.158.6.224)> 220 Please visit http://sourceforge.net/projects/filezilla/

(000026)1/14/2012 23:46:19 PM - (not logged in) (75.158.6.224)> USER dwayne

(000026)1/14/2012 23:46:19 PM - (not logged in) (75.158.6.224)> 331 Password required for dwayne

(000026)1/14/2012 23:46:20 PM - (not logged in) (75.158.6.224)> PASS *****

(000026)1/14/2012 23:46:20 PM - dwayne (75.158.6.224)> 230 Logged on

(000026)1/14/2012 23:46:22 PM - dwayne (75.158.6.224)> SYST

(000026)1/14/2012 23:46:22 PM - dwayne (75.158.6.224)> 215 UNIX emulated by FileZilla

(000026)1/14/2012 23:46:22 PM - dwayne (75.158.6.224)> PWD

(000026)1/14/2012 23:46:22 PM - dwayne (75.158.6.224)> 257 "/" is current directory.

(000026)1/14/2012 23:46:22 PM - dwayne (75.158.6.224)> CWD /

(000026)1/14/2012 23:46:22 PM - dwayne (75.158.6.224)> 550 CWD failed. "/": Permission denied.

Using a different FTP client gives me:

Sending settings, please wait...

Done sending settings.

(000023)1/14/2012 23:28:14 PM - (not logged in) (62.75.138.232)> Connected, sending welcome message...

(000023)1/14/2012 23:28:14 PM - (not logged in) (62.75.138.232)> 220-FileZilla Server version 0.9.40 beta

(000023)1/14/2012 23:28:14 PM - (not logged in) (62.75.138.232)> 220-written by Tim Kosse (Tim.Kosse@gmx.de)

(000023)1/14/2012 23:28:14 PM - (not logged in) (62.75.138.232)> 220 Please visit http://sourceforge.net/projects/filezilla/

(000023)1/14/2012 23:28:14 PM - (not logged in) (62.75.138.232)> CLNT http://ftptest.net on behalf of 68.150.195.186

(000023)1/14/2012 23:28:14 PM - (not logged in) (62.75.138.232)> 200 Don't care

(000023)1/14/2012 23:28:14 PM - (not logged in) (62.75.138.232)> USER dwayne

(000023)1/14/2012 23:28:14 PM - (not logged in) (62.75.138.232)> 331 Password required for dwayne

(000023)1/14/2012 23:28:14 PM - (not logged in) (62.75.138.232)> PASS *****

(000023)1/14/2012 23:28:14 PM - dwayne (62.75.138.232)> 230 Logged on

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> SYST

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> 215 UNIX emulated by FileZilla

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> FEAT

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> 211-Features:

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> MDTM

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> REST STREAM

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> SIZE

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> MLST type*;size*;modify*;

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> MLSD

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> UTF8

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> CLNT

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> MFMT

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> 211 End

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> PWD

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> 257 "/" is current directory.

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> TYPE I

(000023)1/14/2012 23:28:15 PM - dwayne (62.75.138.232)> 200 Type set to I

(000023)1/14/2012 23:28:17 PM - dwayne (62.75.138.232)> PASV

(000023)1/14/2012 23:28:17 PM - dwayne (62.75.138.232)> 227 Entering Passive Mode (68,150,195,186,195,83)

(000023)1/14/2012 23:28:17 PM - dwayne (62.75.138.232)> MLSD

(000023)1/14/2012 23:28:17 PM - dwayne (62.75.138.232)> 550 Permission denied

(000023)1/14/2012 23:28:17 PM - dwayne (62.75.138.232)> disconnected.

Both of these lead me to believe that this is NOT a port-forwarding or firewall issue at the WHS box because the FileZilla server is seeing all of the communications from the client and vice-versa. Rather, I think that I somehow messed up the settings within FileZilla.

What I've done:

Created a directory right off the root of C drive called FTPusers (C:\FTPusers)

Told FileZilla to use Port 21 and 50000 - 50100 and to use my homeserver.com address (passive mode)

Set up a group called Admin and, under Group Shared Folders, set up my home directory as C:\FTPusers, added a couple of shared folders (one is \\DW0\Music, the other is D:\shares\Public).

For the shared folder aliases, I tried several different techniques. For the test where I had renamed my home directory to C:\FTPusers\:u , I used /Music and /Public. For the test where I omitted the "/:u" (C:\FTPusers), I tried C:\FTPusers\Music

Finally, I added a user (Dwayne) to the Users settings and told FileZilla to include that user in the Admin group (selected from the drop-down box).

What I see when I go looking at the C:FTPusers directory is that FileZilla created a child directory called Dwayne - but the Dwayne directory is empty.

I'm positive that I've made some silly mistake but I just can't see it. I'm hoping that someone can point me in the right direction.

Many thanks!

dwayne

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0



Upgrade to a WGS Supporter Account to remove this ad.



  • Latest Posts

    • Does WHS Launchpad need to be running to monitor?
      By Tinus · Posted
      No, Launchpad is not required to be running.
    • Server stopped waking up on a Sunday
      By Tinus · Posted
      Please verify that "Allow wake timers" is still enabled here
      http://www.green-it-software.com/help/stdalone/en/requirements_power_plan.htm Next verify that the wake-up task still exists. Open Windows task scheduler and look for a task called LoS-xxxx.
    • Server stopped waking up on a Sunday
      By Fozzie Bear · Posted
      I have had lights out working beautifully on my win7 64 bit Pro server for at least 6 months. Its scheduled to go to sleep at midnight and wake up every day at 6:00am. I have scheduled all other tasks (backup, updates etc) to happen during the day so the sleep period is not affected. However recently it has stopped waking up on a Sunday morning. Nothing on the server has really changed and I had not previously updated the software. However when I started getting this problem I did update the software to the latest version but the problem persists. Any advice would be appreciated Fozzie
    • Windows 10 And Whs V1
      By DaveL · Posted
      Should add that I have backed up GPT which my current laptop has installed, just don't have a spare drive to test a full system restore for it at this stage
    • Windows 10 And Whs V1
      By DaveL · Posted
      thought I'd add here. I'm still running WHS V1, server running under VMware ESXi 5.5, client PC's updated to Win-10 with no issues, including installing the connector on a fresh install. Tested backup and restore to MBR disk with no issues at all. Can't vouch that UEFI/GPT will work successfully direct booted off the restore CD, so that may need to be achieved via a.n.other PC hosting the drive to be restored.
  • Recently Browsing

    No registered users viewing this page.