Re: Accessing my home FTP server through a wireless router
From: Ron Lowe (ron.lowe@DELETEMEbakeratlas.com)
Date: 07/30/02
- Next message: God is good: "Administrator site"
- Previous message: BB: "Re: Accessing my home FTP server through a wireless router"
- In reply to: BroKnBonesTM: "Accessing my home FTP server through a wireless router"
- Next in thread: BroKnBones: "Re: Accessing my home FTP... (SUCCESS !!!)"
- Reply: BroKnBones: "Re: Accessing my home FTP... (SUCCESS !!!)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Ron Lowe" <ron.lowe@DELETEMEbakeratlas.com> Date: Tue, 30 Jul 2002 11:04:58 +0100
"BroKnBonesTM" <brokenbone@raketti.net> wrote in message news:urolTu6NCHA.2196@tkmsftngp08...
> Hi there,
>
> I recently switched from a wired LAN, in which I shared files, folders,
> printers and internet connection under WinXP, to a wireless router.
>
> After securing it following the recommendations of a few nice people here, I
> reinstalled IIS5.1 and started my web server. My Router gets a dynamic IP
> from a DHCP server, so I use a redirector, DNS2GO.
>
> I figured out how to open the port to access my webserver and it works fine.
> www.brokenbones.dns2go.com
> (Nothing spectacular there)
>
> I also opened a port for my FTP server (private use from work), but although
> I can login, I cannot see the folders at the root of my server. I tried to
> disable passive mode but that didn't help.
>
> Any idea ??? I really need to remotely access my FTP server from work !
>
> I am using a 3rd party FTP server (Bulletproof FTP 2.15).
> Should I use WinXP's built-in server instead ?
>
> Here is a copy of the login log:
>
> WinSock 2.0
> Connecting to XXXXXXXXXXXXXXXX
> Connected to XXXXXXXXXXXXXXXX Port XXXX
> 220 XXXXXXXXX
> USER XXXX
> 331 Password required for XXXX.
> PASS (hidden)
> 230 User XXXX logged in.
> SYST
> 150 Opening data connection for directory list.
> 425 Cannot open data connection (10060).
>
> Any help appreciated !
You may never get this to work well.
It's very hit-or-miss, and depends on the router firmware at each end.
FTP and NAT don't play well together.
It's to do with the dynamically-negotiated data connection.
Forwarding the control connection ( port21 ) on the server's router is only part of the story.
To understand why, you should read this article:
The File Transfer Protocol (FTP) and
Your Firewall / Network Address Translation (NAT) Router
http://www.ncftp.com/ncftpd/doc/misc/ftp_and_firewalls.html
Using a NAT router at the the client end *may* preclude the use of normal Active mode FTP, and require PASV mode. But not normally. Most routers are inteligent enough to be able to handle an active mode client-side FTP session.
Using a NAT router at the server side *may* precluse the use of PASV mode, and require active mode.
Apart from the incoming port forwarding issue, you may need an FTP server which allows you to specify your external IP address in the PASV response, otherwise it will reply to the PASV request with a non-routable internal IP address.
Using NAT on both sides *may* preclude it from working at all.
Your best chance is to use Active mode FTP ( assuming your work's NAT permits it ) to make it easy for your server;
Use standard port numbers ( eg run it on port 21 ) so that any NAT which is looking out for FTP sessions is not confused;
Forward port 21 on your home router to the FTP server.
Probably not what you wanted to hear.
Best Regards,
Ron
- Next message: God is good: "Administrator site"
- Previous message: BB: "Re: Accessing my home FTP server through a wireless router"
- In reply to: BroKnBonesTM: "Accessing my home FTP server through a wireless router"
- Next in thread: BroKnBones: "Re: Accessing my home FTP... (SUCCESS !!!)"
- Reply: BroKnBones: "Re: Accessing my home FTP... (SUCCESS !!!)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
