Re: "Get" command fails

From: Paul Lynch (paul.lynch_at_nospam.com)
Date: 08/03/04 

Date: Tue, 03 Aug 2004 10:13:06 +0100

On Mon, 2 Aug 2004 17:03:31 -0500, Bill B.
<Bill.B..1adux6@mail.webservertalk.com> wrote:

>
>I am running IIS 5.1 on an XP Pro machine from behind a USR Router.
>
>I really am not sure exactly where the problem I am experiencing stems
>from so i apologize if I am posting to the wrong topic.
>
>When I attempt to access the FTP server from a browser it fails. The
>error I am getting tells me to check the permissions.
>
>So before digging thru all of permission settings I figured it best to
>attempt to access it from the command prompt. First attempt I tried as
>follows:
>
>>FTP (ISP assigned IP)
>>anonymous
>>(enter)
>FTP>dir
>200 PORT Command Successful
>150 Opening ASCII mode data connection for /bin/ls
>
>After about 15 seconds it is coming back with:
>>ftp: get :Connection reset by peer
>
>Next I attempted to access the server as follows:
>>FTP (Router assigned IP)
>>anonymous
>>(enter)
>FTP>dir
>200 PORT ......
>
>Using this method it executes the "get" command correctly and lists the
>directories. After hours of browsing forums I finally decided to
>contact my ISP (Comcast) and inquire as to whether they block port 21
>commands. I was told they do not.
>
>I have checked and rechecked that the port 21 setting within the router
>is set to direct to my PC's IP address.
>
>Even so, if it were the router would I be correct in assuming that I
>would not have been able to log in to the server during my first
>command line attempt?
>
>At the same time if it is because of permissions would I be able to see
>the directory listing at the command line and not in the browser?
>
>Seriously at a loss here and in need of some assistance!
>
>Thank you
>
>Bill B.

Bill,

Testing the connection from the command prompt is always the best
first step. However, reading through the steps you have taken, it
looks like you haven't got your router configured correctly.

The fact that you have established a connection on port 21 proves that
the port is open. However, a typical FTP session requires uses other
ports (depending on the mode of transfer) to function correctly.

Read this KB article for a detailed explanation of the process :

Information About the IIS File Transmission Protocol (FTP) Service
http://support.microsoft.com/?id=283679

Also, you didn't specify which model of router you have so I couldn't
find the exact instructions but there is some quite useful support
information here, particularly on configuring NAT which is probably
the cause of your problem :

http://www.usr.com/support/s-main-menu.asp

Regards,

Paul Lynch
MCSE

Relevant Pages

  • Re: RWW Issue From the Internet (Port 4125)
    ... At a command prompt, if the following does not return a result, it should ... Port 4125 has to be open in your routers, ... then try to RWW into the SBS server. ... This will take the router ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW Issue From the Internet (Port 4125)
    ... At a command prompt, if the following does not return a result, it should ... Port 4125 has to be open in your routers, ... then try to RWW into the SBS server. ... This will take the router ...
    (microsoft.public.windows.server.sbs)
  • RE: FTP Server on SBS 2003
    ... You connect the SBS to a third party Router and forward port 21 to the SBS ... the FTP does not work. ...
    (microsoft.public.windows.server.sbs)
  • Re: Question: FTP via alternate port
    ... The problem with FTP is that it requires two ports to operate. ... FTP command stream in order to dynamically open that port for the data ... Ideally the attacker would want to upload another tool onto the ...
    (Pen-Test)
  • Re: getting vsftpd into active mode
    ... Is the an FTP command? ... but the client has to comply. ... Active ftp requires an incoming port open at the router ...
    (alt.os.linux)