ftp network drive behind a wireless router

Hi:

Thanks for reading.

My friend bought a networkdrive that he needs to access from outside his
lan.
The drive has an ftp server build in.

He can set it up so that he can use the drive from within his lan, but
accessing from the outside wold doesnt work out.

What am I doing wrong (or forgetting) if I do these things

1 redirect the ftp port 21 in the router to the local ip number of the
network drive
2 exit all firewala (just for testing ;-)
3 try to access the ftp server from outside the lan using IE7 and the
URL: ftp://ipaddress or ftp://ipaddress:21
Where the ip adress is of course the ipadress privided by the provider.

Thanks for any help

Gerard

G. Verhoef wrote:
> Hi:
>
> Thanks for reading.
>
> My friend bought a networkdrive that he needs to access from outside his
> lan.
> The drive has an ftp server build in.
>
> He can set it up so that he can use the drive from within his lan, but
> accessing from the outside wold doesnt work out.
>
> What am I doing wrong (or forgetting) if I do these things
>
> 1 redirect the ftp port 21 in the router to the local ip number of the
> network drive
> 2 exit all firewala (just for testing ;-)
> 3 try to access the ftp server from outside the lan using IE7 and the
> URL: ftp://ipaddress or ftp://ipaddress:21
> Where the ip adress is of course the ipadress privided by the provider.
>
> Thanks for any help
>
> Gerard

Sorry: I forgot to mention that the error I get is the standard "webpage
not foubd error" (IE7)

Soni tempori elseu romani yeof helsforo nisson ol sefini ill des Mon, 08 Oct
2007 20:43:16 +0200, sefini jorgo geanyet des mani yeof do
uk.comp.home-networking, yawatina tan reek esk "G. Verhoef"
<(E-Mail Removed)> fornis do marikano es bono tan el:

>Sorry: I forgot to mention that the error I get is the standard "webpage
>not foubd error" (IE7)

Try using a proper FTP client (like Filezilla) and try toggling the passive
connection options. Also, it's possible his ISP is blocking access on that
port (some do).

Oh, and does it work from within the LAN (to the drive's local IP)?

deKay
--
Lofi Gaming: www.lofi-gaming.org.uk [Gamertag: deKay 01]
Gaming Diary: www.lofi-gaming.org.uk/diary/
My computer runs at 3.5MHz and I'm proud of that
"Zomoniac is wrong"

"G. Verhoef" <(E-Mail Removed)> wrote in message
news:vQuOi.4583$Hv4.1958@amstwist00...
> Hi:
>
> Thanks for reading.
>
> My friend bought a networkdrive that he needs to access from outside his
> lan.
> The drive has an ftp server build in.
>
> He can set it up so that he can use the drive from within his lan, but
> accessing from the outside wold doesnt work out.
>
> What am I doing wrong (or forgetting) if I do these things
>
> 1 redirect the ftp port 21 in the router to the local ip number of the
> network drive
> 2 exit all firewala (just for testing ;-)
> 3 try to access the ftp server from outside the lan using IE7 and the URL:
> ftp://ipaddress or ftp://ipaddress:21
> Where the ip adress is of course the ipadress privided by the provider.
>
You'll have more luck if you also redirect port 20 to the network drive



--
Alex

New laptop - Sig missing

deKay wrote:
> Soni tempori elseu romani yeof helsforo nisson ol sefini ill des Mon, 08 Oct
> 2007 20:43:16 +0200, sefini jorgo geanyet des mani yeof do
> uk.comp.home-networking, yawatina tan reek esk "G. Verhoef"
> <(E-Mail Removed)> fornis do marikano es bono tan el:
>
>> Sorry: I forgot to mention that the error I get is the standard "webpage
>> not foubd error" (IE7)
>
> Try using a proper FTP client (like Filezilla) and try toggling the passive
> connection options. Also, it's possible his ISP is blocking access on that
> port (some do).
>
> Oh, and does it work from within the LAN (to the drive's local IP)?
>
> deKay

Thanks,

I tried your suggestion and used filezilla with passive connection...
No luck.
It works fine from within the lan.

Next try: checkout if the ISP allows ftp servers. They might have
blocked it.

Gerard

Dr Zoidberg wrote:

> You'll have more luck if you also redirect port 20 to the network drive
>
>
>

Thanks,

Tried that as well... No luck.

Gonna look if the isp blocks ftp servers. I should have thought about
that earlier.

And than.. wait till the guys comin home again, he just left on a
holiday ;-).

Gerard

Soni tempori elseu romani yeof helsforo nisson ol sefini ill des Tue, 09 Oct
2007 09:44:47 +0200, sefini jorgo geanyet des mani yeof do
uk.comp.home-networking, yawatina tan reek esk "G. Verhoef"
<(E-Mail Removed)> fornis do marikano es bono tan el:

>I tried your suggestion and used filezilla with passive connection...
>No luck.

What errors did Filezilla throw up?

>It works fine from within the lan.
>
>Next try: checkout if the ISP allows ftp servers. They might have
>blocked it.

Try temporarily redirecting port 80 on the router to port 21 on the drive,
then ftping to your_ip:80. If this works, then the ISP blocks traffic on port
21, so you'll need to find another port that is open (8000, 8080 and 1080
often are, as is 110 if you don't need it for POP3) and use that.

deKay
--
Lofi Gaming - http://lofi-gaming.org.uk
Gaming Diary - http://lofi-gaming.org.uk/diary
Blog - http://lofi-gaming.org.uk/blog
My computer runs at 3.5MHz and I'm proud of that

"G. Verhoef" <(E-Mail Removed)> wrote in message
news:vQuOi.4583$Hv4.1958@amstwist00...
[snip]
> My friend bought a networkdrive that he needs to access from outside his
> lan.
> The drive has an ftp server build in.
>
> He can set it up so that he can use the drive from within his lan, but
> accessing from the outside wold doesnt work out.

Running an FTP server behind a NAT router is a real pain... I could write a
sizeable essay on the subject. That said, in general, (assuming default
ports) forwarding port 21 on the router to port 21 on the server is probably
enough to allow "active" transfers to work. Also forwarding port 20 may be
necessary in some cases, and does no harm.

The main problem is getting "passive" transfers to work, often the default
in clients because of greater perceived chance of working when the client is
behind a NAT router and/or firewall. To get working "passive" transfers for
a server behind a NAT router requires that either the router is suitably
"intelligent", or that you can specify (on the server) a port range to use
for such transfers. In the latter case, you would then configure the router
to forward that port range to the server.

Did you configure IP settings on the server itself (to ensure its address
won't change), and if so, did you provide a default gateway (the router's
internal IP address)? Without one, connecting to the server will be
impossible (the connection attempt will just time out; probably
indistinguishable from the port being blocked by a firewall, eg by the ISP).

Alex

In article <olGOi.4641$Hv4.3165@amstwist00>, G. Verhoef says...
> Dr Zoidberg wrote:
>
> > You'll have more luck if you also redirect port 20 to the network drive
> >
> >
> >
>
> Thanks,
>
> Tried that as well... No luck.
>
> Gonna look if the isp blocks ftp servers. I should have thought about
> that earlier.
>
Set the FTP server to run on Port 80 then.


--
Conor

I'm not prejudiced. I hate everyone equally.

"Conor" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In article <olGOi.4641$Hv4.3165@amstwist00>, G. Verhoef says...
[snip]
>> Gonna look if the isp blocks ftp servers. I should have thought about
>> that earlier.
>
> Set the FTP server to run on Port 80 then.

If the ISP blocks port 21, is there not a good chance port 80 will also be
blocked?

Alex