*** Opened trace file at Wed Nov 24 13:06: My FTP-client is trying to connect to a FileZilla server 1.0.1 that is not under my control and runs into trouble when trying to find out if MLSD/MLST is supported by the server (this is done because there are servers out there announcing support in FEAT but actually can't). Pb caractère générique * et ? avec la commande mgetĭepuis un client FTP sur Microsoft Windows server 2012 vers un serveur FTP FileZilla Version 1.1.0 sous Windows server 2012 lors de l'éxcution de la commande mget te*.txt j'obtiens l'erreur suivante :įilezilla returns with "504 UTF8 mode cannot be disabled" when sending an "OPTS MLST type size modify perm" Pb caractère générique * et ? avec la commande mget avec la version 1.1.0 Is it maybe because she is using a vpn to connect to our Server and using wlan that it is too slow. Hello, my Client got an Problem where she couldnt log in in our FTP Server it worked before but now she only gets the error Failed to connect to the server, on other PCs it worked but for her not. Settings dir: C:\Users\glenn\AppData\Roaming\FileZilla\Ĭant connect to my FTP Server trough Filezilla Name: Windows 10 (build 19042), 64-bit editionĬPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi bmi2 adx lm I have no idea what triggers it, not all directory listings seem as incomplete as this one I was trying to access today.Ĭompiled with: x86_64-w64-mingw32-gcc (GCC) 10-win32 20210110Ĭompiler flags: -O2 -g -Wall -Wextra -Wno-deprecated-copy -ffunction-sections -fdata-sections -Wno-cast-function-type This seems like a quite serious bug, disabling FileZilla when the bug is triggered. I can see them all fine by logging in to the server via Putty, and I can't see any variation in the permissions that would prevent the listing.Ĭuriously, of the directory and files that are listed, only one of them actually exists on the server, all the ones from the synchronized client listing (which is accurate) also appear in the server listing (those include the one listed that actually exists on the server), and then there are two listed in the server listing that do not exist on either side. I'm not sure whether this bug is reporting directory listing failures on client-local or server directories, but I'm seeing a very abbreviated server directory listing for one of my server directories.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |