×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Mark,
Am 09.02.2024 um 21:05 schrieb mlazarus <mlazarus@xxxxxxxxxxxx>:
- This is via a VPN and according to the network admin all the ports are open.
Ow, yes. I clearly dis miss that point! Sorry!
- I can connect to the FTP server and log in.
- After logging in I run:
ftp> quo pasv 1
227 Entering Passive Mode (10,15,7,203,83,239).
- Return message after a while (or it just hangs) is:
Could not connect to port.
- I have tried EPSV as well, with the same results.
This still sounds like a network issue, but because of VPN I agree more with the other contributors about a firewall issue *somewhere*. Because the data port is negotiated dynamically (no matter if active or passive FTP is used), firewalls usually need to analyze FTP control traffic and dynamically poke holes according to the protocol exchange.
Does the i have multiple network interfaces? It might be that the data port is referring to the "wrong" interface, but this is a wild guess at this point. To solve this and know what's going on, a good start would be to run a packet sniffer such as Wireshark, sniff the FTP control connection and see what the PORT command exchanged between client and server looks like. The result will determine further route of action.
:wq! PoC
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
