Networks

Ask something
Question Locked

Can't get FTP to work on Server 2003

0 helpful
2 replies

by lostinwindows

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am having problems setting up ftp on Server 2003 R2. I will explain in detail the steps that I have taken.
Added ftp from the Add Windows Components off of Add/Remove Programs
Administrative Tools -> Active directory Users and Computers from Domain Controller ?
Added User Account
On DC I modified the Account Tab to specify the one computer that has a direct VPN connection to the Internet.
On Server Domain5 I added a directory c:\FTPUser\Dummy
On Server Domain5 Administrative tools -> IIS Manager-> FTP Sites -> Default FTP Site
New Virtual directory Added UserName pointing to CFTPUsers\Dummy
Set Username to have Read and List to FTPUsers and Dummy folder
I went to another external computer

C:\Users\Don>ftp ip.address
Connected to ip.address.
220 Microsoft FTP Service
User (ip.address:(none)): domain\username
331 Password required for domain\username.
Password:
230-
****USAGE WARNING****

230 User domain\username logged in.
ftp> pwd
257 "/username" is current directory.
ftp> bin
200 Type set to I.
ftp> prompt
Interactive mode Off .
ftp> dir
200 PORT command successful. 20 SECOND DELAY
Connection closed by remote host.
ftp>

2 replies

by kreniska

I am having the same problem except in my case it is an external ftp site (that we are paying for) and it was working fine for the past year until the beginning of March.
Since then I get the same error that you are getting - connection refused - whenever I try to get a DIR listing of transfer a file.
I am using the standard ftp,exe that comes with WindowsXP from Microsoft. It runs in active mode and does not support passive mode.
I tried downloading a free ftp client called ftps.exe from MoveItFreely.com
This one works for DIR and get commands, but still fails for a put command.
I tried passive mode and it worked for put commands also.
In active mode, the ftp server has to initiaite a connection back to the ftp client on a high port number (>1024) and some firewalls block that connection. I think that is where the connection refused error comes from.

The other thing I like about ftps.exe is that it supports the same command line switches and script commands as the Microsoft ftp, so it is a drop in replacement.

This discussion is closed to new replies.