I am giving up on this one - port forwarding (I guess) issue on DSL with Linksys RV 85

this network is soo simple:
static IP DSL line in bridge mode from Embarq with internal box ip
192.168.50.1
Linksys router with ip 192.168.50.10
my FTP server on port 21 with ip 192.168.50.20
ip, gateways, dns all set up correctly
all traffic open through linksys.
http linksys conf web page works through static IP address (tested
from outside of my internal network).
I can ping it too.
>From linksys I can ping any ip and domain names.
all traffic on port 21 goes to 192.168.50.20.
there is not firewall on 192.168.50.20 (I even turned off firewall on
linksys)

and still when trying to ftp to my static ip... "uknown error".
linksys logs show nothing.
this is a killer for me.

any ideas???

On Thu, 27 Sep 2007 10:35:12 -0700, Joe <(E-Mail Removed)> wrote:

>all traffic on port 21 goes to 192.168.50.20.
>there is not firewall on 192.168.50.20 (I even turned off firewall on
>linksys)
>
>and still when trying to ftp to my static ip... "uknown error".
>linksys logs show nothing.
>this is a killer for me.
>
>any ideas???


If you're trying to establish an active connection it might be blocked
by a firewall at the client end. If you're trying to establish a
passive connection you need to forward more ports than just 21.

This page has an excellent description of the various connections.
http://slacksite.com/other/ftp.html


Jim.

On Sep 27, 2:09 pm, James Egan <je...@jegan.com> wrote:
> On Thu, 27 Sep 2007 10:35:12 -0700, Joe <joe1...@tlen.pl> wrote:
> >all traffic on port 21 goes to 192.168.50.20.
> >there is not firewall on 192.168.50.20 (I even turned off firewall on
> >linksys)
>
> >and still when trying to ftp to my static ip... "uknown error".
> >linksys logs show nothing.
> >this is a killer for me.
>
> >any ideas???
>
> If you're trying to establish an active connection it might be blocked
> by a firewall at the client end. If you're trying to establish a
> passive connection you need to forward more ports than just 21.
>
> This page has an excellent description of the various connections.http://slacksite.com/other/ftp.html
>
> Jim.

even opening ALL port and forwarding them all to the ftp server did
not resolve this issue.

On Sep 27, 11:16 am, Joe <joe1...@tlen.pl> wrote:
> On Sep 27, 2:09 pm, James Egan <je...@jegan.com> wrote:
>
>
>
>
>
> > On Thu, 27 Sep 2007 10:35:12 -0700, Joe <joe1...@tlen.pl> wrote:
> > >all traffic on port 21 goes to 192.168.50.20.
> > >there is not firewall on 192.168.50.20 (I even turned off firewall on
> > >linksys)
>
> > >and still when trying to ftp to my static ip... "uknown error".
> > >linksys logs show nothing.
> > >this is a killer for me.
>
> > >any ideas???
>
> > If you're trying to establish an active connection it might be blocked
> > by a firewall at the client end. If you're trying to establish a
> > passive connection you need to forward more ports than just 21.
>
> > This page has an excellent description of the various connections.http://slacksite.com/other/ftp.html
>
> > Jim.
>
> even opening ALL port and forwarding them all to the ftp server did
> not resolve this issue.- Hide quoted text -
>
> - Show quoted text -

Maybe the Linksys hardware is failing?
I still have a Linksys 5 port hub (model EW5HUB) that I originally
used for connecting home network thru cable modem to Internet. I still
keep it powered us as a hot standby although I only use it stand in
for the Router when my anti-virus (AV) is down or my file sharing is
set just for home networking and not suited to screening Internet
traffic. I replaced it with a Netgear RP614 Router/Gateway and
Linksys BEFCMU version 3 modem. These last two have worked well in
this environment for about 3 years. Occasionally (once every few
months) connections fail and I end up cycling power to the modem or
the router to restablish the connection. If that doesn't fix it, calls
to the Cable Company always find they are changing things and, when
they finish, things are OK again. I suppose life is not so simple for
you.

By the way, I just discovered and reported in the WinME general NG
that putting WinME into hibernate mode works well at cleaning up WinME
memory leaks. And running with the System Monitor on 24/7 is a good
way to catch those leaks before they choke you so bad the systems
begins to fail.

Hope that helps.
Bob