"Herm" <mighty_herm@hotmail.com> wrote in message
news:%237Zn8sk7EHA.1300@TK2MSFTNGP14.phx.gbl...
> I have successfully setup the FTP service on my Windows 2003 Server.
> Everything works fine.
> Now I am not happy with FTP using Port 21. In IIS I was able to change the
> default Port 21 to another one, for example 2121. Guess whats happening...
> FTP doesnt work anymore :-( The following error will occur;
>
> 500 Invalid PORT Command
>
> I did read Microsoft TID Q281193. I do understand the problem here, but I
> do
> not know what action has to be done to get it work!

> "Herm" <mighty_herm@hotmail.com> wrote in message
> news:%237Zn8sk7EHA.1300@TK2MSFTNGP14.phx.gbl...
> > I have successfully setup the FTP service on my Windows 2003 Server.
> > Everything works fine.
> > Now I am not happy with FTP using Port 21. In IIS I was able to change
the
> > default Port 21 to another one, for example 2121. Guess whats
happening...
> > FTP doesnt work anymore :-( The following error will occur;
> >
> > 500 Invalid PORT Command
> >
> > I did read Microsoft TID Q281193. I do understand the problem here, but
I
> > do
> > not know what action has to be done to get it work!
>
>
> All the NAPTs that I have seen will only do correct FTP translation if the
> FTP server is running on port 21.
>
> The action to be done to get it to work consists of either:
> 1. Using only port 21 for FTP
> or
> 2. Complaining to the NAPT vendor and asking them to offer a feature to
> support FTP on ports other than 21.
>
> I doubt that approach 2 will result in success.
>
> Another thing you can try is to configure your FTP client to use passive
> mode (using the "PASV" command). For some FTP clients, this is not
> possible, so it may not be the best approach for you.
>
> What is the reason for wanting a port other than 21?
>
> Alun.
> ~~~~
> --
> Software Design Engineer, Internet Information Server (FTP)
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>

"Herm" <mighty_herm@hotmail.com> wrote in message
news:OSX7Q$w7EHA.2452@TK2MSFTNGP14.phx.gbl...
> Hi Alan,
>
> I guess you are right. The reason for me to change the port is security!
> It
> seems that the common ports are the most scanned ports. Specially posrt
> 21!
>
> Herman
>
> "Alun Jones [MSFT]" <alunj@online.microsoft.com> schreef in bericht
> news:eIIPoio7EHA.3416@TK2MSFTNGP09.phx.gbl...
>> "Herm" <mighty_herm@hotmail.com> wrote in message
>> news:%237Zn8sk7EHA.1300@TK2MSFTNGP14.phx.gbl...
>> > I have successfully setup the FTP service on my Windows 2003 Server.
>> > Everything works fine.
>> > Now I am not happy with FTP using Port 21. In IIS I was able to change
> the
>> > default Port 21 to another one, for example 2121. Guess whats
> happening...
>> > FTP doesnt work anymore :-( The following error will occur;
>> >
>> > 500 Invalid PORT Command
>> >
>> > I did read Microsoft TID Q281193. I do understand the problem here, but
> I
>> > do
>> > not know what action has to be done to get it work!
>>
>>
>> All the NAPTs that I have seen will only do correct FTP translation if
>> the
>> FTP server is running on port 21.
>>
>> The action to be done to get it to work consists of either:
>> 1. Using only port 21 for FTP
>> or
>> 2. Complaining to the NAPT vendor and asking them to offer a feature to
>> support FTP on ports other than 21.
>>
>> I doubt that approach 2 will result in success.
>>
>> Another thing you can try is to configure your FTP client to use passive
>> mode (using the "PASV" command). For some FTP clients, this is not
>> possible, so it may not be the best approach for you.
>>
>> What is the reason for wanting a port other than 21?
>>
>> Alun.
>> ~~~~
>> --
>> Software Design Engineer, Internet Information Server (FTP)
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>>
>
>

> If you run a server on any port that is reachable from the Internet, it
will
> get scanned. The secret is to take appropriate protective measures (the
big
> FTP-related one being that you should not allow anonymous uploads).
>
> Alun.
> ~~~~
> --
> Software Design Engineer, Internet Information Server (FTP)
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "Herm" <mighty_herm@hotmail.com> wrote in message
> news:OSX7Q$w7EHA.2452@TK2MSFTNGP14.phx.gbl...
> > Hi Alan,
> >
> > I guess you are right. The reason for me to change the port is security!
> > It
> > seems that the common ports are the most scanned ports. Specially posrt
> > 21!
> >
> > Herman
> >
> > "Alun Jones [MSFT]" <alunj@online.microsoft.com> schreef in bericht
> > news:eIIPoio7EHA.3416@TK2MSFTNGP09.phx.gbl...
> >> "Herm" <mighty_herm@hotmail.com> wrote in message
> >> news:%237Zn8sk7EHA.1300@TK2MSFTNGP14.phx.gbl...
> >> > I have successfully setup the FTP service on my Windows 2003 Server.
> >> > Everything works fine.
> >> > Now I am not happy with FTP using Port 21. In IIS I was able to
change
> > the
> >> > default Port 21 to another one, for example 2121. Guess whats
> > happening...
> >> > FTP doesnt work anymore :-( The following error will occur;
> >> >
> >> > 500 Invalid PORT Command
> >> >
> >> > I did read Microsoft TID Q281193. I do understand the problem here,
but
> > I
> >> > do
> >> > not know what action has to be done to get it work!
> >>
> >>
> >> All the NAPTs that I have seen will only do correct FTP translation if
> >> the
> >> FTP server is running on port 21.
> >>
> >> The action to be done to get it to work consists of either:
> >> 1. Using only port 21 for FTP
> >> or
> >> 2. Complaining to the NAPT vendor and asking them to offer a feature to
> >> support FTP on ports other than 21.
> >>
> >> I doubt that approach 2 will result in success.
> >>
> >> Another thing you can try is to configure your FTP client to use
passive
> >> mode (using the "PASV" command). For some FTP clients, this is not
> >> possible, so it may not be the best approach for you.
> >>
> >> What is the reason for wanting a port other than 21?
> >>
> >> Alun.
> >> ~~~~
> >> --
> >> Software Design Engineer, Internet Information Server (FTP)
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >>
> >
> >
>
>

"Herm" <mighty_herm@hotmail.com> wrote in message
news:eRXw2gW8EHA.1264@TK2MSFTNGP12.phx.gbl...
> Thanks Alun,
>
> First a very happy new yeasr!
>
> I did not allow anonymous down- and uploads :-) But in de Log-file i can
> see
> that foreign IP adresses try to login onto my server...
>
> Herman
>
>
> "Alun Jones [MSFT]" <alunj@online.microsoft.com> schreef in bericht
> news:uOmkxy17EHA.3504@TK2MSFTNGP12.phx.gbl...
>> If you run a server on any port that is reachable from the Internet, it
> will
>> get scanned. The secret is to take appropriate protective measures (the
> big
>> FTP-related one being that you should not allow anonymous uploads).
>>
>> Alun.
>> ~~~~
>> --
>> Software Design Engineer, Internet Information Server (FTP)
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>>
>> "Herm" <mighty_herm@hotmail.com> wrote in message
>> news:OSX7Q$w7EHA.2452@TK2MSFTNGP14.phx.gbl...
>> > Hi Alan,
>> >
>> > I guess you are right. The reason for me to change the port is
>> > security!
>> > It
>> > seems that the common ports are the most scanned ports. Specially posrt
>> > 21!
>> >
>> > Herman
>> >
>> > "Alun Jones [MSFT]" <alunj@online.microsoft.com> schreef in bericht
>> > news:eIIPoio7EHA.3416@TK2MSFTNGP09.phx.gbl...
>> >> "Herm" <mighty_herm@hotmail.com> wrote in message
>> >> news:%237Zn8sk7EHA.1300@TK2MSFTNGP14.phx.gbl...
>> >> > I have successfully setup the FTP service on my Windows 2003 Server.
>> >> > Everything works fine.
>> >> > Now I am not happy with FTP using Port 21. In IIS I was able to
> change
>> > the
>> >> > default Port 21 to another one, for example 2121. Guess whats
>> > happening...
>> >> > FTP doesnt work anymore :-( The following error will occur;
>> >> >
>> >> > 500 Invalid PORT Command
>> >> >
>> >> > I did read Microsoft TID Q281193. I do understand the problem here,
> but
>> > I
>> >> > do
>> >> > not know what action has to be done to get it work!
>> >>
>> >>
>> >> All the NAPTs that I have seen will only do correct FTP translation if
>> >> the
>> >> FTP server is running on port 21.
>> >>
>> >> The action to be done to get it to work consists of either:
>> >> 1. Using only port 21 for FTP
>> >> or
>> >> 2. Complaining to the NAPT vendor and asking them to offer a feature
>> >> to
>> >> support FTP on ports other than 21.
>> >>
>> >> I doubt that approach 2 will result in success.
>> >>
>> >> Another thing you can try is to configure your FTP client to use
> passive
>> >> mode (using the "PASV" command). For some FTP clients, this is not
>> >> possible, so it may not be the best approach for you.
>> >>
>> >> What is the reason for wanting a port other than 21?
>> >>
>> >> Alun.
>> >> ~~~~
>> >> --
>> >> Software Design Engineer, Internet Information Server (FTP)
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >>
>> >>
>> >
>> >
>>
>>
>
>

> That will happen no matter what port you put it on. There are a lot of
> curious people out there, intent on finding "hidden" machines. If you
want
> to be more careful about hiding your machine, you might want to put it
> behind a VPN that requires an extra step of authorisation before it lets
you
> connect.
>
> Alun.
> ~~~~
> --
> Software Design Engineer, Internet Information Server (FTP)
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Herm" <mighty_herm@hotmail.com> wrote in message
> news:eRXw2gW8EHA.1264@TK2MSFTNGP12.phx.gbl...
> > Thanks Alun,
> >
> > First a very happy new yeasr!
> >
> > I did not allow anonymous down- and uploads :-) But in de Log-file i can
> > see
> > that foreign IP adresses try to login onto my server...
> >
> > Herman
> >
> >
> > "Alun Jones [MSFT]" <alunj@online.microsoft.com> schreef in bericht
> > news:uOmkxy17EHA.3504@TK2MSFTNGP12.phx.gbl...
> >> If you run a server on any port that is reachable from the Internet, it
> > will
> >> get scanned. The secret is to take appropriate protective measures
(the
> > big
> >> FTP-related one being that you should not allow anonymous uploads).
> >>
> >> Alun.
> >> ~~~~
> >> --
> >> Software Design Engineer, Internet Information Server (FTP)
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >>
> >> "Herm" <mighty_herm@hotmail.com> wrote in message
> >> news:OSX7Q$w7EHA.2452@TK2MSFTNGP14.phx.gbl...
> >> > Hi Alan,
> >> >
> >> > I guess you are right. The reason for me to change the port is
> >> > security!
> >> > It
> >> > seems that the common ports are the most scanned ports. Specially
posrt
> >> > 21!
> >> >
> >> > Herman
> >> >
> >> > "Alun Jones [MSFT]" <alunj@online.microsoft.com> schreef in bericht
> >> > news:eIIPoio7EHA.3416@TK2MSFTNGP09.phx.gbl...
> >> >> "Herm" <mighty_herm@hotmail.com> wrote in message
> >> >> news:%237Zn8sk7EHA.1300@TK2MSFTNGP14.phx.gbl...
> >> >> > I have successfully setup the FTP service on my Windows 2003
Server.
> >> >> > Everything works fine.
> >> >> > Now I am not happy with FTP using Port 21. In IIS I was able to
> > change
> >> > the
> >> >> > default Port 21 to another one, for example 2121. Guess whats
> >> > happening...
> >> >> > FTP doesnt work anymore :-( The following error will occur;
> >> >> >
> >> >> > 500 Invalid PORT Command
> >> >> >
> >> >> > I did read Microsoft TID Q281193. I do understand the problem
here,
> > but
> >> > I
> >> >> > do
> >> >> > not know what action has to be done to get it work!
> >> >>
> >> >>
> >> >> All the NAPTs that I have seen will only do correct FTP translation
if
> >> >> the
> >> >> FTP server is running on port 21.
> >> >>
> >> >> The action to be done to get it to work consists of either:
> >> >> 1. Using only port 21 for FTP
> >> >> or
> >> >> 2. Complaining to the NAPT vendor and asking them to offer a feature
> >> >> to
> >> >> support FTP on ports other than 21.
> >> >>
> >> >> I doubt that approach 2 will result in success.
> >> >>
> >> >> Another thing you can try is to configure your FTP client to use
> > passive
> >> >> mode (using the "PASV" command). For some FTP clients, this is not
> >> >> possible, so it may not be the best approach for you.
> >> >>
> >> >> What is the reason for wanting a port other than 21?
> >> >>
> >> >> Alun.
> >> >> ~~~~
> >> >> --
> >> >> Software Design Engineer, Internet Information Server (FTP)
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> > rights.
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>