425 error; cause possibly novel

[J N Winkler]

Today I installed FileZilla Server, intending to create a small and simple FTP server on an old XP machine connected wirelessly to a home LAN. I set it up for passive FTP with 21 as the listening port, 50000-50200 as the data ports, and a fully qualified domain name as the external server name. I am able to load a directory listing from any computer on my LAN, but I get 425 errors when I attempt to do it via ftptest.net. Logs (unedited except to remove the FQDN) are as follows:

* FileZilla Server

Code: Select all

(000040)1/7/2014 19:17:27 PM - (not logged in) (62.75.138.232)> Connected, sending welcome message...
(000040)1/7/2014 19:17:27 PM - (not logged in) (62.75.138.232)> 220-FileZilla Server version 0.9.42 beta
(000040)1/7/2014 19:17:27 PM - (not logged in) (62.75.138.232)> 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
(000040)1/7/2014 19:17:27 PM - (not logged in) (62.75.138.232)> 220 Please visit http://sourceforge.net/projects/filezilla/
(000040)1/7/2014 19:17:27 PM - (not logged in) (62.75.138.232)> CLNT https://ftptest.net/ on behalf of 68.102.51.166
(000040)1/7/2014 19:17:27 PM - (not logged in) (62.75.138.232)> 200 Don't care
(000040)1/7/2014 19:17:27 PM - (not logged in) (62.75.138.232)> USER anonymous
(000040)1/7/2014 19:17:27 PM - (not logged in) (62.75.138.232)> 331 Password required for anonymous
(000040)1/7/2014 19:17:27 PM - (not logged in) (62.75.138.232)> PASS ***
(000040)1/7/2014 19:17:27 PM - anonymous (62.75.138.232)> 230 Logged on
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> SYST
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> 215 UNIX emulated by FileZilla
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> FEAT
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> 211-Features:
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)>  MDTM
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)>  REST STREAM
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)>  SIZE
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)>  MLST type*;size*;modify*;
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)>  MLSD
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)>  UTF8
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)>  CLNT
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)>  MFMT
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> 211 End
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> PWD
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> 257 "/" is current directory.
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> TYPE I
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> 200 Type set to I
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> PASV
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> 227 Entering Passive Mode (92,242,140,2,195,115)
(000040)1/7/2014 19:17:28 PM - anonymous (62.75.138.232)> MLSD
(000040)1/7/2014 19:17:39 PM - anonymous (62.75.138.232)> 425 Can't open data connection for transfer of ""
(000040)1/7/2014 19:17:39 PM - anonymous (62.75.138.232)> disconnected.

* Ftptest.net

Code: Select all

Status: Resolving address of (fully qualified domain name)
Status: Connecting to 68.102.51.166
Status: Connected, waiting for welcome message
Reply: 220-FileZilla Server version 0.9.42 beta
Reply: 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
Reply: 220 Please visit http://sourceforge.net/projects/filezilla/
Command: CLNT https://ftptest.net/ on behalf of 68.102.51.166
Reply: 200 Don't care
Command: USER anonymous
Reply: 331 Password required for anonymous
Command: PASS ***
Reply: 230 Logged on
Command: SYST
Reply: 215 UNIX emulated by FileZilla
Command: FEAT
Reply: 211-Features:
Reply: MDTM
Reply: REST STREAM
Reply: SIZE
Reply: MLST type*;size*;modify*;
Reply: MLSD
Reply: UTF8
Reply: CLNT
Reply: MFMT
Reply: 211 End
Command: PWD
Reply: 257 "/" is current directory.
Status: Current path is /
Command: TYPE I
Reply: 200 Type set to I
Command: PASV
Reply: 227 Entering Passive Mode (92,242,140,2,195,115)
Command: MLSD
Reply: 425 Can't open data connection for transfer of ""
Error: Listing failed

I have read the Network Configuration page and exhausted its suggested remedies. I have checked and double-checked that the firewall on the XP PC has exceptions for the FileZilla Server program (yes, not the interface) and for ports 21 and 50000-50200. I have checked that the router has been configured with port forwarding to the correct LAN IP for these ports as well. Canyouseeme.org reports "I can see your service" for port 21, but "Connection refused" for randomly chosen ports in the 50000-50200 range. (I don't know if "Connection refused" is relevant in this context.)

I wonder if a DNS problem could be involved, since nslookup at the command prompt gives odd results. For the FQDN I use, it returns:

Code: Select all

Server:  Paris
Address:  192.168.1.1

Non-authoritative answer:
Name:    (FQDN)
Address:  68.102.51.166

For the IP address associated with the directory listing request (92.242.140.2), it returns:

Code: Select all

Server:  Paris
Address:  192.168.1.1

Name:    unallocated.barefruit.co.uk
Address:  92.242.140.2

I am reasonably sure these issues are not a result of port blocking by my ISP (Cox). None of the ports involved are on their list of blocked ports. I got similar results (directory listing loads for computers on the LAN, external computers get 425 errors) when I experimented with 2021 as the listening port.

The router is a Linksys E4200.

I'd be much obliged for any advice on how to resolve these 425 errors--I am at my wits' end.

[botg]

What do you have configured on the passive mode page in the settings dialog of FileZilla Server?

[J N Winkler]

Passive settings page:

* Use custom port range (checked): 50000-50200

* External server IP: Use the following IP address (radio button checked): (FQDN)

* Don't use external IP for local connections (not checked)

[botg]

Status: Resolving address of (fully qualified domain name)
Status: Connecting to 68.102.51.166
[...]
Reply: 227 Entering Passive Mode (92,242,140,2,195,115)

That's the problem, IP addresses don't match.

Did you use a different hostname in the server configuration compared to the one the client uses to connect to the server?

[J N Winkler]

The FQDN I used in the server configuration matches the one I use to access the site on Ftptest.net, and at login it resolves to the correct numeric IP address, so I don't understand where this second IP address has been coming from. In any event, the problem now seems to have resolved itself spontaneously in the last hour or so.

As an experiment, I changed the FileZilla server configuration to the numeric IP (68.102.51.166), and tried the same numeric IP in Ftptest.net. Success!

example.com provides DNS service to the FQDN and has a page (myip.example.com) that can be used with the lookup option in the FileZilla server settings. When I tried this yesterday, I got the same errors reported in the OP. I tried it just now in Ftptest.net . . . success!

As yet another experiment, I returned to the precise configuration described in the OP (FQDN specified in server settings)--exactly the one that was not working. I tried it just now, again in Ftptest.net . . . success!

I am beginning to wonder if the errors I was having were a result of DNS changes being slow to propagate, and my original setup would have worked just fine if I had been patient for 24 hours instead of raising the issue on this forum. (I created the FQDN in example.com around 24 hours ago.) If that is the case, then I apologize for the redundant efforts on my behalf.

[botg]

Quite possible.

[rebelwolf]

I had a similar problem with using the ###.mooo.com free DYNDNS host service. To resolve it I told FZS to use the DNS server as my external ip address--actually in the outside IP address field, not the website/http field. That might work for you too? I don't know...

[boco]

Differences between the "Retrieve" and the "Custom IP" fields:

Retrieve: Expects a website literally printing the IPv4 (and only the IPv4).

Custom IP: Resolves the given hostname into an IPv4.



IPv6 is not affected at all.