GNOME Bugzilla – Bug 581971
Microsoft FTP Service shows no listing
Last modified: 2009-05-13 16:10:50 UTC
Please describe the problem: Nautilus just doesn't display the files of the target FTP. Steps to reproduce: 1. Open nautilus and type in the location: "ftp://gnome@dev-1.conexaossl.com.br/" 2. Password is "gnome" Actual results: Nautilus just displays a blank screen Expected results: I was expecting the application to list the FTP contents Does this happen every time? Yes. Other information: You can test the same (address,login,password) with filezilla to be sure the FTP is there and it's working fine. There are also a lot of topics in forums reporting this same error.
Created attachment 134300 [details] Bug screenshot Here's a screenshot showing the bug
To be more precise, the following steps produce the same empty listing: gvfs-mount ftp://gnome@dev-1.conexaossl.com.br (password 'gnome') gvfs-ls ftp://gnome@dev-1.conexaossl.com.br Doing the same with for example lftp seems to work fine. Can this be a problem with either TLS support, or a listing format the ftp backend does not support yet?
I just noticed that if I configure another FTP without using Default FTP Site at another port than 21, the whole thing works. So, this is a good tip for the lucky guys who have direct access to the server.
em@amd64:~$ /usr/lib/gvfs/gvfsd-ftp host=dev-1.conexaossl.com.br user=gnome pass=gnome <-- 220 Microsoft FTP Service --> FEAT <-- 530 Please login with USER and PASS. error: Permission denied If the above is the only problem (which I doubt since Microsoft FTP server isn't near RFC compliant), then this should be fixed already (duplicate of existing bugreport which was resolved by clearing errors returned from FEAT requests). Please try latest gvfs git version or 2.27.x release and report the problem to Microsoft.
See bug 580125 and commit 22c55fb6df556517cac030fd4fafce46c9aa0342 for possible fix. http://git.gnome.org/cgit/gvfs/commit/?h=gnome-2-26&id=f73de6140a0b52acbaf1406075df227ef42cb8af
(In reply to comment #5) > See bug 580125 and commit 22c55fb6df556517cac030fd4fafce46c9aa0342 for possible > fix. > > http://git.gnome.org/cgit/gvfs/commit/?h=gnome-2-26&id=f73de6140a0b52acbaf1406075df227ef42cb8af > It doesn't seems to be the same bug for me... I'm currently working with 2.26 and the access NEVER happens, even if you try 1, 2, 3 or more times... FileZilla and other clients are working fine since ever. Also, imho, it doesn't matter that MS FTP Server isn't near RFC compliant, it has more than 1/3 of the servers in the global marketshare and other OS projects runs fine with it (as it should be. 33% is always 33% after all).
Could you please provide a log of what is happening in your case? See my previous comment for how to do that.
(In reply to comment #7) > Could you please provide a log of what is happening in your case? > > See my previous comment for how to do that. > Sorry, I don't have this gvfsd-ftp command file oO;;
I've tested with the latest code and it work against the site you provided. Thanks for providing a test account! (See previously pointed out commit if you're having problems, or update to latest code from git.) Please keep in mind that nautilus always browses from the root directory, which is empty on your site (even though a "gnome" subdirectory exists.) This got me as well... lftp starts in /gnome while nautilus starts in /. Try: gvfs-ls ftp://gnome@dev-1.conexaossl.com.br/gnome The command "gvfs-ls ftp://gnome@dev-1.conexaossl.com.br" returns nothing because the / is empty (according to the server list reply). Entering "invisible" directories was fixed recently as well, so if you're not running 1.2.x you need to upgrade for that as well. For nautilus browsing press ctrl-l and enter the address to the gnome directory or specify the location ftp://gnome@dev-1.conexaossl.com.br/gnome when first mounting. Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 580125 ***