Ce jour Mon, 15 Nov 2004, Francisco Castillo a dit: > > > Hello, > > > when i connect from a cuteftp client from a 192.168.0.Y ip the client get > the correct pasive port to get data (40000) from the proftpd server but > if i try to access from a public client ip (with cuteftp too) the server > said to get a aleatorious port and not in the range 40000-40010 > COMANDO:> PASV > 227 Entering Passive Mode (217,00,00,214,238,235)). > > > 238,235 = 238*256 + 235 != 40000-40010 > > so i ask > > what could be happening? > How could i solve my problem? you can always set the daemon "ACTIVE" and allow traffic on port 20. i can't remember what i did to fix that passive, but ordinarily a client should be able to get data from the server about what the server expects, and go on from there. proftpd-doc package has more details; the Configure.html (or something like that) has that stuff. but it's easier for packet filtering purposes to just allow port 20 and 21 traffic on your gateway to the internal server. it could also be that cuteftp is a brain-dead client implementation. i don't use windoze s/w and haven't had a need to look that kind of stuff up, but google might have more info on that. othrewise, good luck :) > Thanks in advance. > Francisco. > > > -- > To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org > -- Cold pizza and cold coffee, second best thing to cold pizza and warm beer.
Attachment:
signature.asc
Description: Digital signature