Hmmm try telnet to both the dedicated and the IIS server on port 21 via cmd line: telnet 192.168.x.(server a) 21 telnet 192.168.x.(server b) 21
you should get something like: 220 %host% X2 WS_FTP Server 5.x.x (4353535345435) On the top of the screen. And see what you come up with. Also, we have one of our ftp servers running on a private IP, and it has a public IP port forwarded to it and it works from outside and inside the network from either IP and we have the WS_FTP Server Host Address set to the Public IP. Also, have you tried the converse of what you explained in your email and setup IIS on port 80 on the FTP server and port forwarded that over? Would be a good test to make sure the routing is working correctly. They probably are, but are both the internal servers on the same subnet? David Knapp Systems, Support & Integration [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of H Jones Sent: Tuesday, December 28, 2004 6:44 PM To: [email protected] Subject: [WS_FTP Forum] Connection Refused Network Layout: 3 machines on a cable connection behind a linksys router, one being a pc, one being a mail server/web server/ftp server (iis, running on port 21000), and the final one being a dedicated ftp server with ws_ftp server 5.04 running on it. The port forwarding is already set on the router to send port 21 to the dedicated ftp server, and for pasv, i have it forwarding port 1100 as well, and that setting is set in ws_ftp firewall options. When I try to connect, either from cmd or from any ftp client, I get a Connection Refused message. Nothing shows up in the router logs, or in the server logs. This happens no matter what machine, or what ISP I am connecting from, even other machines in the network using the private IP. The only time a connection can be established is from the local machine, using either loopback, netbios name, or private ip. I have tried different ftp server software, and the same thing happens, so I know it's not just ws_ftp server that is the problem. If I run it on any other port than 21 there is no problem at all. I have updated the firmware in the router, applied all patches to w2k server, completely uninstalled and reinstalled ws_ftp, and none of it seemed to help. The funny thing is that if I put the other machine's IIS server on port 21 and change the port forwarding, that works just fine, so I have it narrowed down to something on that machine, just don't know what. TIA -HJ Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/wsftp_forum%40list.ipswitch.com/ Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/wsftp_forum%40list.ipswitch.com/
