Windows 10, static IP, on LAN side of router/NAT 192.168.3.10
Custom hardware design, static IP, on LAN size of router/NAT 192.168.3.201
Immediate disconnect of Filezilla client by Windows 10 upon receipt of PASV response. Internet search shows it's a common problem, but haven't seen a workaround or why.
Famous last words, used to work, just fired up an old XP box on the same LAN with a very earlier version of Filezilla 3.0.7.1 - still works.
I'm trying to understand the logic of requiring an external IP address of the router/NAT in the PASV response. If I were to somehow implement this in the custom hardware, it seems that the router/NAT would need a port forwarding rule?
Any input or pointers? The control port access works fine using the LAN static IP addresses, just not the PASV (192.168.3.201,0,20).
Is there a registry or policy setting to disable this 'feature' ?
Thank you !
Disconnect after PASV response
Moderator: Project members
Re: Disconnect after PASV response
Please post a complete log of this happening.
-
- 500 Command not understood
- Posts: 2
- Joined: 2022-01-12 01:52
- First name: Steven
- Last name: Ackerman
Re: Disconnect after PASV response
2 logfiles and screen capture attached.
- Attachments
-
- Wireshark_2022-01-12_13-26-08.png (44.67 KiB) Viewed 2096 times
-
- NETWORK.LOG
- Log file from custom hardware
- (742 Bytes) Downloaded 43 times
-
- filezilla.log
- (4.71 KiB) Downloaded 47 times
Re: Disconnect after PASV response
The reply to the PASV command never makes it to the client. Instead the client gets handed a socket error by the TCP stack.
Some badly behaving firewall?
Some badly behaving firewall?