Custom Query (8036 matches)
Results (253 - 255 of 8036)
|#4184||rejected||425 Can't open data connection.|
I have set the server to explicit TLS and encrypted data connection. I have opened port TCP 21 and TCP data port 990 to the server machine. The client connects just fine but I get the above error and the client cannot retrieve the file list. I copy below the log from the client: "Quote" Status: Resolving address of ???.dyndns.org Status: Connecting to ???.???.?54.?91:21... Status: Connection established, waiting for welcome message... Response: 220-FileZilla Server version 0.9.29 beta Response: 220 get out of here Command: AUTH TLS Response: 234 Using authentication type TLS Status: Initializing TLS... Status: Verifying certificate... Command: USER ??? Status: TLS/SSL connection established. Response: 331 Password required for ??? Command: PASS * Response: 230 Logged on Command: PBSZ 0 Response: 200 PBSZ=0 Command: PROT P Response: 200 Protection level set to P Status: Connected Status: Retrieving directory listing... Command: PWD Response: 257 "/" is current directory. Command: TYPE I Response: 200 Type set to I Command: PASV Response: 227 Entering Passive Mode (???,???,???,???,6,229) Status: Server sent passive reply with unroutable address. Using server address instead. Command: LIST Response: 425 Can't open data connection. Error: Failed to retrieve directory listing "Unquote"
I have added the "?" marks for privacy.
|#9873||outdated||425 Unable to get local socket name|
I'm getting the following error running the newest version of the software and connected to an FTP with settings "active" transfer, and trying to LIST the contents of a directory.
425 Unable to get local socket name (getsockname) [126 The specified module could not be found.]
I installed FileZilla roughly 8 months ago and have been performing all regular updates to the software.
|#948||450 error when home directory is mapped network drive|
Using FileZilla server 0.9.10 beta. Works fine when user home directory is on a local drive. However, simply changing directory to R:, for example, which is a mapped network drive (mapped with different user name which is a domain\user for user and password), the server always gets error 450, cannot access file. Same error is reported at client system. I am able to copy files into this mapped network drive, so there doesn't SEEM to be an access problem.