[NTLUG:Discuss] Re: FTP problem

[Michael B. Lee]

oh yeah. there's another excellent point. it took one friend of mine
months to realize his wu-ftpd wasn't responding properly because he didn't
insmod ip_conntrack_ftp and ip_nat_ftp, which is what he needed to run to
get his particular firewall (monmotha's) to let the data connection get
established with a client.



On Thu, 1 Nov 2001, Robert Fournerat wrote:

> Daniel,
>
> Do you have the ip_masq_ftp module loaded (or whatever ftp module
> that matches your kernel)?
>
> -- Robert
>
>
> Daniel L. Shipman wrote:
> > I am facing problem with ftp.
> >
> >
> >
> > I have a static ip (216.61.196.129)
> >
> >
> >
> > My machines are using internal ip address. Server address 192.168.1.1
> >
> >
> >
> > The LRP routes FTP request to 216.61.196.129 to 192.168.1.1 running wu-ftpd.
> >
> >
> >
> > When most clients try to connect to my ftp server, they are able to
> > establish the connection but not able to do 'ls' or 'get' or 'put'.
> > They are able to do 'cd' and 'pwd'.
> >
> >
> >
> > When they say
> > ftp>ls
> >
> >
> >
> > It says:
> > 227 Entering Passive Mode (192,168,1,1,115,233)
> > ftp: connect: No route to host
> >
> >
> >
> > I am able to do traceroute to the ftp server from a client's machine.
> >
> >
> >
> > Thanks in advance
> >
> >
> >
> > Thanks,
> >
> >
> > Daniel
> > Webmaster for:
> > http://www.srj.net
> > http://www.hometownhospital.com
> > http://www.easyhealthcare.net
> > http://www.ngpa.org
> > http://www.cathedralofhope.com
> > http://www.iusarentals.com
> >
> > <http://hc2.humanclick.com/hc/20922718/?cmd=repstate&site=20922718&imageUrl=http://www.srj.net/humanclick&ver=1>
> > <http://hc2.humanclick.com/hc/20922718/?cmd=file&file=visitorWantsToChat&site=20922718&byhref=1>
> >
> >
> >
> > *** CONFIDENTIALITY NOTICE *** Privileged/Confidential Information may
> > be contained in this message and/or its attachments. This message and
> > its attachments are intended only for use by the individual(s) listed as
> > the recipient(s). If you are not one of the intended recipient(s), or
> > responsible for delivery of the message to such person, you are hereby
> > notified that any disclosure, copying, distribution, or the taking of
> > any action in reliance on the contents of this information is strictly
> > prohibited. If you have received this message in error, please notify
> > the sender by return email and destroy all copies of the email.
> > Opinions, conclusions and other information in this message that do not
> > relate to official company business shall be understood as neither given
> > nor endorsed by the company.
> >
>
>
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>