-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oops - I think its time to hit me with that bat! :-) You are correct. The remote host (or something before it) is 'dropping' your syn packets. Or, for some reason you are not getting the 'Ack' packets.Now a really wild guess - If they say they are not 'dropping' these packets...
How big are 'ack' packets? Could it be that you have a small MTU? and that their 'brilliant' gateway 'drops' all icmps, so that they don't the PMTU information?
Just a REALLY wild guess... Andrew On 29/08/2006, at 8:50 PM, martin f krafft wrote:
What's non-passive about this? As I understand passive FTP to work
is that the server passively waits for another connection, whereas
in active mode it would actively try to connect to the server.
When the client sent the PASV command, the server replied with
socket to use:
23.286210 local -> remote FTP Request: PASV
23.309130 remote -> local FTP Response: 227 Entering
Passive Mode (212,117,207,139,5,175).
That 5 and 175 encode the port to which the client should connect:
5*256 + 175 = 1455.
Feel free to take a massive clue bat and whack me massively, but in
the mean time, I still think something's fishy.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE9JSmW126qUNSzvURAmRdAJwOERh/X/7/glPVpruwqorxlNAzFACbBZxw fwI0yb/+rDYi4+8AcGPx8U8= =LuW8 -----END PGP SIGNATURE-----