Chaps, I've spent 30 solid minutes checking every option in sight and
following links to the end of the Internet I've made one possible step
forward.

In the IIS ftproot bindings I noticed the IP address was present, so I
changed it to *All Unassigned*.

Now ftp.exe is working nicely. FileZilla connects but times out listing the
user's folder contents. IE prompts for a user/password and seems to connect
but soon says "page can't be displayed".

So it's neither fixed nor broken now, I'm left in a bewildered state where
I don't know what's right or wrong. What else would you expect?!

*Greg K*


On 12 March 2014 14:59, Paul Evrat <[email protected]> wrote:

>
> Router port open and port fowarding set up?
>
>
>
>
>
> -------- Original message --------
> From: Stephen Price <[email protected]>
> Date:
> To: ozDotNet <[email protected]>
> Subject: Re: [OT] FTP diagnosis
>
>
> Ah yes, you did try that...
>
> This link here has some stuff on it regarding permissions (file based -
> step 3) so might help?
>
>
> http://www.iis.net/learn/publish/using-the-ftp-service/configuring-ftp-firewall-settings-in-iis-7
>
>
>
>
> On Wed, Mar 12, 2014 at 11:21 AM, Stephen Price <[email protected]
> > wrote:
>
>> Have you tried FTP from command line?
>>
>> might give more info?
>>
>>
>> On Wed, Mar 12, 2014 at 11:12 AM, Greg Keogh <[email protected]> wrote:
>>
>>> Folks, for the first time in a couple of years I have to get FTP working
>>> on a Win2008R2 Server. IIS seems to configured correctly (I think), I can
>>> see port 21 open to the world via Shields-Up, tcpmon shows 21 is listening,
>>> FTP is set to use basic authentication. So it "looks" alright, but all
>>> attempts to connect fail.
>>>
>>> IE says "The page can't be displayed". Filezilla says "can't connect to
>>> the server". Ftp.exe says "Connection closed by the remote host".
>>>
>>> I just can't get any reason why it's failing? IIS FTP says it's logging
>>> but there are no files. Can anyone think of any trick to get more useful
>>> information about why it's failing?
>>>
>>> *Greg K*
>>>
>>
>>
>

Reply via email to