|
Home > Archive > IIS Server > December 2004 > FTP errors
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Hi,
I am getting some problems with my FTP site.
The error is as follows:
"FTP Folder Error
An error occurred opening that folder on the FTP Server. Make sure you
have permission to access that folder.
Details:
200 Type set to A.
227 Entering Passive Mode (10,0,0,3,52,217).
426 Connection closed; transfer aborted."
I know that the permissions are set right. I can access it inside my
network, but from outside it won't let me do anything. The ports are
set right, 20 and 21 forward to the server. I'm at the end of my rope
here.
Thanks,
Conrad
| |
| Alun Jones [MSFT] 2004-12-21, 5:56 pm |
| "CKite" <conradk@duramold.net> wrote in message
news:1103654598.676415.325960@c13g2000cwb.googlegroups.com...
> Hi,
>
> I am getting some problems with my FTP site.
>
> The error is as follows:
>
> "FTP Folder Error
>
> An error occurred opening that folder on the FTP Server. Make sure you
> have permission to access that folder.
>
> Details:
> 200 Type set to A.
> 227 Entering Passive Mode (10,0,0,3,52,217).
> 426 Connection closed; transfer aborted."
>
> I know that the permissions are set right. I can access it inside my
> network, but from outside it won't let me do anything. The ports are
> set right, 20 and 21 forward to the server. I'm at the end of my rope
> here.
Port 20 will not be used for incoming traffic to your FTP server. You can
safely remove that forwarding.
What you're experiencing here is that you haven't opened up your firewall /
NAT router for passive connections. In this particular instance, the port
you'd need open is 52*256+217 = 13529.
The FTP server will use a range of ephemeral ports to listen on for passive
connections, which are established from the FTP client to the FTP server.
Port 20 is used only for active connections, which are made from the FTP
server to the FTP client.
It also looks like your NAT isn't doing its job of translating the IP
address in the passive mode response message - the line starting with "227".
That line should contain the external IP address of your NAT router, not the
internal private IP address you use.
For more information on the ports used by FTP,
http://support.microsoft.com/?id=283679
Alun.
~~~~
--
Software Design Engineer, Internet Information Server (FTP)
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| Conrad Kite 2004-12-21, 5:56 pm |
|
I added the port 13529 but it still is giving me the same details as
before, but 227 has changed to 227 Entering Passive Mode
(10,0,0,3,59,233).
Conrad
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
| |
| Conrad 2004-12-21, 5:56 pm |
| I added the port 13529 but it still is giving me the same details as
before, but 227 has changed to 227 Entering Passive Mode
(10,0,0,3,59,233).
Conrad
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
| |
| Alun Jones [MSFT] 2004-12-21, 5:56 pm |
| "Conrad Kite" <conradk@duramold.net> wrote in message
news:eJLw7H65EHA.128@TK2MSFTNGP15.phx.gbl...
>
>
> I added the port 13529 but it still is giving me the same details as
> before, but 227 has changed to 227 Entering Passive Mode
> (10,0,0,3,59,233).
Yes - as I noted, "The FTP server will use a range of ephemeral ports to
listen on for passive
connections".
I'm more concerned that you're giving out an IP address that isn't likely to
reach your machine - you're seeing 10.0.0.3 as the IP address, but that
should only be available inside your router / firewall. Your NAT router
basically isn't doing the NAT (Network Address Translation) job it's
supposed to do.
Alun.
~~~~
--
Software Design Engineer, Internet Information Server (FTP)
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| Conrad 2004-12-21, 5:56 pm |
|
This is what I've got:
Server 2003 Enterprise Edition 10.0.0.3
Linksys BEFSR41 10.0.0.99
Static IP 123.456.789.101 <-obviously fake for posting
I am in my network ftping to our static ip which is giving me the
problems. I know that outside traffic has the same problems too, at
least I think so. I am going to check tonight when I get home. I don't
know how this problem started to occur, but I know that the FTP worked
flawlessly before and I don't think that I had it set up for passive
either. What should I do?
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
| |
| Conrad 2004-12-23, 7:47 am |
| Would using a different router help this? I need to get this back up
ASAP. Can I just do a default on the router and reset all of my
settings? Do I need to open up all of the ports that are used in
passive, and if so, what are all of those ports?
~Conrad
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
| |
| Alun Jones [MSFT] 2004-12-29, 8:47 pm |
| The fact that you are connecting from inside the network to the FTP server
both explains the IP address you've been given, and also exonerates the
router (because your connection shouldn't be going through the router).
I don't think you really are going through the static IP address, because
that should be refused, unless your router is really clever and reflects
data locally. I have not observed that behaviour myself in consumer
routers, although I will admit that I haven't tested specifically for it in
quite some time.
All that aside, your inability to transfer through a connection on the same
LAN suggests that you may have a firewall turned on on your Windows Server
2003 computer, and while you have port 21 open, you have not as yet opened
up any of the other ports used for the ephemeral ports given out in response
to the PASV command.
Alun.
~~~~
--
Software Design Engineer, Internet Information Server (FTP)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Conrad" <Conrad_no_spam_k@duramold.net> wrote in message
news:e%232$cp65EHA.2804@TK2MSFTNGP15.phx.gbl...
>
>
> This is what I've got:
>
> Server 2003 Enterprise Edition 10.0.0.3
> Linksys BEFSR41 10.0.0.99
> Static IP 123.456.789.101 <-obviously fake for posting
>
> I am in my network ftping to our static ip which is giving me the
> problems. I know that outside traffic has the same problems too, at
> least I think so. I am going to check tonight when I get home. I don't
> know how this problem started to occur, but I know that the FTP worked
> flawlessly before and I don't think that I had it set up for passive
> either. What should I do?
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|
|
|
|
|