First, congratulations on the release of 1.x! It has certainly been a long time coming.
I hope it continues to develop well (I can't wait for the return granular permissions myself!)
Ok, now for the reason for this post: users have reported to me, and this has been verified by myself, that some of their folders are not loading. I have looked into their complaints and noticed that NTFS junction points (a totally different beast than ctrl shifted shortcuts) are apparently not understood by the server, which in turn gives a "550 No such dir" error to clients when accessing a folder by means of an NTFS junction point.
Is this expected behavior? If so, might I ask for reconsideration (return to previous, eg 0.9.x, behavior)?
Thank you again, and I truly appreciate your work.
-a
Version 1.0.1 vs NTFS junction points
Moderator: Project members
Re: Version 1.0.1 vs NTFS junction points
Known issue, there's no solution at this point, it's on our todo list.
Re: Version 1.0.1 vs NTFS junction points
This is true for symbolic links as well. As I have only few Directory Junctions/Symlinks, I just add Mount points for them inside the FileZilla Server User or Group settings (they override the Junctions/Symlinks and don't give double entries). Of course not practicable with many of them.
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
Re: Version 1.0.1 vs NTFS junction points
Congratulations indeed.
So it was a known issue yet you decided to release anyway? And no solution in sight? You didn't think filesystem links is a pretty big feature in an FTP server software??
Guess I'm downgrading then... again. This is becoming a cherished tradition with this software. Downgrading when you mess up the features and then not fixing it.
You should work on a simple upgrade/downgrade button system for the next release, to make this easier.
Has this even been logged as a bug? I can't find it in the bugtracker?
So it was a known issue yet you decided to release anyway? And no solution in sight? You didn't think filesystem links is a pretty big feature in an FTP server software??
Guess I'm downgrading then... again. This is becoming a cherished tradition with this software. Downgrading when you mess up the features and then not fixing it.
You should work on a simple upgrade/downgrade button system for the next release, to make this easier.
Has this even been logged as a bug? I can't find it in the bugtracker?
-
- 500 Command not understood
- Posts: 1
- Joined: 2021-11-13 16:42
- First name: joe
- Last name: man
Re: Version 1.0.1 vs NTFS junction points
I confirm, very annoying pb on a ftp server. It was working so well in previous version.
Re: Version 1.0.1 vs NTFS junction points
Hello everyone,
is there a specific schedule for when the ticket (https://trac.filezilla-project.org/ticket/12582) will be scheduled?
We love working with FileZilla Server, but unfortunately it doesn't work for us without junction links.
Thanks in advance.
is there a specific schedule for when the ticket (https://trac.filezilla-project.org/ticket/12582) will be scheduled?
We love working with FileZilla Server, but unfortunately it doesn't work for us without junction links.
Thanks in advance.