Connection closed by remote host. -- iis ftp

iis ftp : Connection closed by remote host.

FUBARinSFO
1/8/2008 1:07:31 PM

Hi:

I connect OK locally (over intranet) to ftp server workstation, but
can't connect externally. That is, running out to the internet and
back in to external ip address 69.12.xxx.xxx.

There are no messages in event viewer.

Any suggestions would be appreciated.

-- Roy Zider

------------------------------------------------------------------------------

C:\Documents and Settings\BitBucket>ftp 69.12.xxx.xxx
Connected to 69.12.xxx.xxx.
Connection closed by remote host.

C:\Documents and Settings\BitBucket>
------------------------------------------------------------------------------

System:
Windows XP SP2
IIS 5.1
four workstations on local intranet
intranet behind router connected to ADSL modem as bridge
4-port router set to pass port 21 to ftp host workstation at
192.168.1.102
external IP address (IP Chicken): 69.12.xxx.225
IIS ftp set to connect anonymously, all as default settings
Windows XP firewall set to allow FTP on server workstation
Same result with and without firewall turned on or off in both client
and server workstations.

Rick Barber
1/8/2008 4:36:47 PM

Hi Roy,

I would first check to see if port 21 is open. When you are outside the
network on the Internet, try doing a telnet to that IP address on port 21
(i.e. telnet 66.12.xxx.xxx 21). If it is unable to connect you know that
port 21 is not open and there is something such as a firewall blocking it.
That is the first check that I do.

--
Rick Barber

http://www.orcsweb.com
Managed Complex Hosting
#1 in Service and Support

[quoted text, click to view]

FUBARinSFO
1/8/2008 5:14:14 PM

Rick:

That's good advice, and for anyone not "outside" the network they can
use Shields Up! at www.grc.com to check to see if port 21 (and 20) are
open. I am going to have someone try to access the ftp server from
outside just as soon as I can get my son to return my telephone
call....

I'm now at the point where port 20 (the data port) is open, but port
21 is "closed" but not "stealh". So a probe can detect the port, but
it is not accepting connections. I'm now getting the error ftp:
connect: unknown error number when I try to access it using ftp.exe
from the command line.

I've been playing around with enabling and disabling the ports on the
router, and can see the ports changing from "stealth" (when the port
forwarding is not enebled) to "closed" when the port forwarding for 21
and others is forwarded to the local workstation that hosts the ftp
server. But even with windows firewall turned off it's not clear to
me why the server is not accepting connection attempts (assuming it's
seeing them). It doesn't log failed attempts, and I haven't yet gone
to the extreme of installing a packet sniffer, so I'm running out of
ideas here.

FUBARinSFO
1/9/2008 8:48:48 AM

Rick:

Running netstat -a was not something that had occurred to me
yesterday. Unfortunately, after working all day on this problem
without solving it I had to abandon it. Perhaps sometime later I will
have the time to recable everything and get to the bottom of this
problem. Others all over the web have had the same problem and no one
has resolved it, judging from the abandoned threads on this subject.

Thanks for the suggestion -- one of the machines in which I left the
ftp server installed is indeed listening on ftp

Rick Barber
1/9/2008 9:59:40 AM

Hi Roy,

It looks like you're making progress. You can also run netstat -a from the
command prompt and see if the server is listening on FTP.

--
Rick Barber

http://www.orcsweb.com
Managed Complex Hosting
#1 in Service and Support

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about iis ftp

home · blog · groups

Questions? Comments? Contact the dn