all groups > iis ftp > november 2005 >
You're in the

iis ftp

group:

Internet FTP Access to 2nd FTP site issue on Windows 2003 DC


Internet FTP Access to 2nd FTP site issue on Windows 2003 DC DickySA1
11/20/2005 3:35:01 PM
iis ftp:
I have two FTP sites running on the same Windows 2003 Server Domain Controller.
I'm having problems accessing one of the sites from the Internet but
successfully able to access both sites via the intranet computers.

ftp://SITE1 (ftp://mywebsite.com) with default port 21 assigned - works
fine via both Internet and Intranet.

ftp://SITE2:5005 (ftp://mywebsite.com:5005) works on the Intranet but when
accessing over the Internet an error message is displayed relating to
location not available/not found....

Port 5005 has been forwarded at the router.

I initially tried confiuring port 22 on the 2nd site but was advised to try
a higher port but this has failed to work. Is it a port issue?

Any ideas where I should start troubleshooting?
Re: Internet FTP Access to 2nd FTP site issue on Windows 2003 DC Todd J Heron
11/20/2005 8:24:21 PM

"DickySA1" <DickySA1@discussions.microsoft.com> wrote...
[quoted text, click to view]

telnet mywebsite.com 5005

What happens?

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
Re: Internet FTP Access to 2nd FTP site issue on Windows 2003 DC jeff.nospam NO[at]SPAM zina.com
11/28/2005 11:57:24 AM
On Sun, 20 Nov 2005 15:35:01 -0800, "DickySA1"
[quoted text, click to view]

Do site1 and site2 resolve to the same IP address? Using passive or
active FTP?

Re: Internet FTP Access to 2nd FTP site issue on Windows 2003 DC Alun Jones
11/28/2005 8:00:16 PM
[quoted text, click to view]

This has all the flavour of being a NAT issue. NAT routers - Network
Address Translators - take the traffic on the FTP channel, which often
includes IP addresses and port numbers, and translates internal values into
external values, sometimes opening a pinhole in the firewall for that
connection.

Note that I said "on the FTP channel" - how does the NAT router know that
you're using FTP on port 5005? It doesn't - you could just as easily be
using HTTP, or telnet, or any of a number of other protocols. It recognises
port 21 (the default FTP port) as appropriate for performing FTP NAT
operations, but unless it's a fancy NAT device with the ability to be told
"5005 is also for FTP traffic", you will not be able to get the NAT to
accept FTP traffic on any port other than 21 without a lot of bother.

Alun.
~~~~
[Please don't email posters, if a Usenet response is appropriate.]
--
Texas Imperial Software | Find us at http://www.wftpd.com or email
23921 57th Ave SE | alun@wftpd.com.
Washington WA 98072-8661 | WFTPD, WFTPD Pro are Windows FTP servers.
Fax/Voice +1(425)807-1787 | Try our NEW client software, WFTPD Explorer.

AddThis Social Bookmark Button