Error: Connection got closed prematurely

Mick Dawdy 56 Reputation points
2022-12-28T18:50:30.98+00:00

My ftp site is mickftpsite.com, 99.242.126.196

I messed up some technical thing with my win 10 IIS ftp site. I do not know what it is. I ran ftptest.net with this result...
Status: Resolving address of mickftpsite.com
Status: Connecting to 99.242.126.196
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Error: Connection got closed prematurely

The warning is of no consequence. The various reasons to get the "closed prematurely" message do not seem to apply. After much trying of various things I decided to start over from the beginning.

I started over like this...
I checked...
ports forwarded in router 21, 80, 443, 30000-65000

In firewall...
open those ports both inbound and outbound,
allowed Microsoft ftp server private and public,
allowed ftp traffic in, 4 categories

Also to get a clean new install...
stopped ftp service
removed ftp site from iis
turned ftp off in Windows Features [uninstall]
created a new folder for the ftp root and checked permissions: c:\inetFtp
Re-installed iis ftp [Features on]
restarted IIS and Ftp Service

I meticulously went thru the install steps following 2 or 3 of the many on line blogs
Have gone through all of those settings a few times and they are each OK

A couple of other things..

I do not know what these actually do but I ran them hoping that something in the configuration would get reset...

net stop WAS

net start w3svc

So conclusion, something technical in the background, not necessarily in inetmgr, possibly in the Registry, is messed up. Any suggestions are appreciated :)

Thank you,

Mick

Windows development | Internet Information Services
{count} votes

2 answers

Sort by: Most helpful
  1. Mick Dawdy 56 Reputation points
    2022-12-29T04:47:46.113+00:00

    Yes, I moved past this specific problem on to another which I have posted here.
    Reply: 530 Valid hostname is expected.
    Error: Login refused by server

    I have not solved this one yet so I have also not updated this post. I think I have found the cause of the new error but I have not yet confirmed that. Once I get settled I'll update all of my posts.
    Thank you,
    Mick

    0 comments No comments

  2. Mick Dawdy 56 Reputation points
    2023-01-08T19:10:04.033+00:00

    @Sam Wu-MSFT
    @Anonymous

    The solution, or part of it, to this problem was to use the domain:username format when logging in to the Ftp server, like this...
    mickwebsite.com:Mick
    rather than just the username...
    Mick

    Your idea about using Wireshark or whatever is probably best route to discover this, rather than just going on other forum members experience as I have done, as it would have for me involved yet another deep dive into our technology to learn more of this technical stuff, which we all seem to love :)
    Mick

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.