CoreFTP not handling permissions properly -550 at wrong time

Report bugs or issues with Core FTP Server here
Post Reply
cjard
Posts: 7
Joined: Wed Oct 08, 2008 3:14 pm

CoreFTP not handling permissions properly -550 at wrong time

Post by cjard »

I note with interest that windows FTP client isnt able to use CoreFTP properly because CoreFTP first says OK, then dsays DENY to a folder where there is no list permission.

As such we see this in FileZilla:
Command: CWD /tst
Response: 250 CWD command successful
Command: PORT 10,0,0,51,12,16
Response: 200 PORT command successful
Command: LIST
Response: 150 Opening ASCII mode data connection
Response: 550 Access is denied...
Error: Failed to retrieve directory listing


Note that the server agrees to start the LIST, with a 150 response, then issues a 550 denied.
Why does it not say "550" to the LIST? there is no list permission!

Windows FTP hangs, because it has received a 150 OK, and then it just sits and waits for the server to connect, but it never will.

Press Ctrl+C in windows FTP, and THEN we see the 550 denied message

If core had send the 550 denied earlier (i.e. in response to the LIST, windows FTP would not have hung)
kenrucker
Posts: 1
Joined: Wed Sep 30, 2020 10:02 pm

Re: CoreFTP not handling permissions properly -550 at wrong time

Post by kenrucker »

Basically same here. No matter what I do, I get

Command: LIST
Response: 550 Access is denied...
Error: Failed to retrieve directory listing

Doesn't matter if I do standard FTP, SSL, anything. Running Core FTP Server as a service with login to NETWORK

I've setup plenty of FTP servers before. This one just won't go. Kind of regretting buying it :(.

Did you ever get this figured out?
ForumAdmin
Site Admin
Posts: 987
Joined: Mon Mar 24, 2003 4:37 am

Re: CoreFTP not handling permissions properly -550 at wrong time

Post by ForumAdmin »

Things to check:

* Make sure the directory exists

* Check permissions on the Windows account running Core FTP Server for permissions

* Choose the directory again via the "..." buttons and double check user permissions.
Post Reply