epike on Mon, 15 Apr 2002 18:50:16 +0200 |
It appears to be sending your local ip....check out the line that says "227 Entering Passive Mode".. its sending out 192.168.0.102 and that is not reachable from the outside. The ssh book I happened to read discusses some of this, supposedly there are ftp-aware router/gateway hardware that listen to this pattern and replace the text with the outside address....OR the wu-ftpd config has some configuration to specify an ip address to send (I dont know how to configure wu-ftpd but it should be possible). ------------------------- ftp 66.149.101.186 Connected to 66.149.101.186. 220 mail.gokart4xmas.com FTP server (Version wu-2.6.2(1) Fri Feb 22 16:34:38 EST 2002) ready. 530 Please login with USER and PASS. 530 Please login with USER and PASS. KERBEROS_V4 rejected as an authentication type Name (66.149.101.186:jondz): anonymous 331 Guest login ok, send your complete e-mail address as password. Password: 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. ftp> ls 227 Entering Passive Mode (192,168,0,102,103,153) receive aborted waiting for remote to finish abort ftp> ------------------------ JondZ > > Ok.... so maybe I'm missing something here, but I'm having some weird > problems accessing my box @ home from outside the network. > > It's a Mandrake 8.2 box running PHP 4.1.2 and wu-ftp 2.6.2. I've got a > D-Link router running on there as well, acting as a firewall. > > Here's the issue, if I'm inside the firewall I can connect to the server @ > www.gokart4xmas.com or by its numeric IP no problem, but when I try, for > instance, to access the ftp server by name, my client says "Failed to > establish data socket." It works fine, if I use the 192.168.x.x address > internally. > > It does, however, give me the welcome message in either case. > > >From outside, I get the welcome message but no "data socket" no matter what. > > Same thing goes for the webserver -- apache is up and running fine, but if I > try and upload, I get the same behavior described above. > > Any ideas? Did I manage to block something I shouldn't have? If that's the > case, why would it fail behind the firewall? Feel free to portscan me, if > that'll help -- 66.149.101.186... > > Thanks a lot, > -- jon > > > ------------- > jon roig > senior manager, online production > epilepsy foundation > > > > ______________________________________________________________________ > Philadelphia Linux Users Group - http://www.phillylinux.org > Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce > General Discussion - http://lists.phillylinux.org/mail/listinfo/plug > ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|