Hello,

I am having problems with Windows 8.1 and FTP clients.

I am using Syncback (just takes forever)  and Filezilla 3.7.3 Portable, the last one gives after some time the following error "The maximum number of clients (10) for this user are already connected".

Setting the maximum number of clients on the server form 10 to 15 has no noticeable result.

When using the same network, computer and software, but now Windows 8 (different partition on the same computer), the FTP job just runs fine with no problems.

Should Windows 8.1 have special settings to be able to use FTP?

Thanks, Wouter

Hi Wouter,

I'm seeing similar issues, and it looks like a lot of people are having trouble with FTP in Windows 8.1. It seems to be a problem with wininet, as described here:

http://www.wysiwygwebbuilder.com/forum/viewtopic.php?f=10&t=58619

I don't have a solution, nor do I currently have a way around it. Active FTP connections seem to work for me, but passive connections typically fail. Since the server I'm connecting to doesn't support Active connections, I'm stuck and looking for a solution as well.

Does anyone know of a work-around for this, or do we have to wait for Microsoft to issue a fix? (and do they even think it's "broken"--probably not).

Byron

Please try these steps:

Reducing simultaneous connections for incorrectly configured servers

https://wiki.filezilla-project.org/Using#Reducing_simultaneous_connections_for_incorrectly_configured_servers

Make sure that you close connection as soon as you are done with them, as some ftp clients will generally leave their connection open unless told otherwise. Additionally, some clients such as Filezilla will allow multiple connections for any new activity, which uses up connections quickly. While this does make for faster transfers.

I use mostly Cute FTP and I have been sometimes doing it to just close ftp software (Alt+F4) and not closing connection; but the point is that when you have been connected then you must close connection properly as well.

Hello Kate,

I tried this:

I set the maximum number of connections to 8 where the server allows 10.

Downloading from the server is no problem (10000+ files downloaded without problems). Uploading stays a problem, Filezilla asks to login again and then complains about to many connections.

I think it is strange that Windows 8 doesn't give problems and windows 8.1 does give problems.

Even in Windows 8 in a VirtualBox under Windows 8.1 (host) Filezilla gets into the same trouble as in Windows 8.1.

Regards, Gewout.

PS. I tried Windows 7 in a VirtualBox under Windows 8.1 and than Filezilla seemed to work fine, but it gets the same problems.

The only solution is to reboot under Windows 8 to backup and then reboot again to work under Windows 8.1. Not very user frendly, but I am happy that I left my Windows 8 partition unchanged..

• Edited by Wouter57 Saturday, November 09, 2013 10:46 AM

Hello Kate,

I tried this:

I set the maximum number of connections to 8 where the server allows 10.

Downloading from the server is no problem (10000+ files downloaded without problems). Uploading stays a problem, Filezilla asks to login again and then complains about to many connections.

I think it is strange that Windows 8 doesn't give problems and windows 8.1 does give problems.

Even in Windows 8 in a VirtualBox under Windows 8.1 (host) Filezilla gets into the same trouble as in Windows 8.1.

Regards, Gewout.

PS. I tried Windows 7 in a VirtualBox under Windows 8.1 and than Filezilla seemed to work fine, but it gets the same problems.

The only solution is to reboot under Windows 8 to backup and then reboot again to work under Windows 8.1. Not very user frendly, but I am happy that I left my Windows 8 partition unchanged..

• Edited by Wouter57 Saturday, November 09, 2013 10:46 AM

Hello Kate,

I tried this:

I set the maximum number of connections to 8 where the server allows 10.

Downloading from the server is no problem (10000+ files downloaded without problems). Uploading stays a problem, Filezilla asks to login again and then complains about to many connections.

I think it is strange that Windows 8 doesn't give problems and windows 8.1 does give problems.

Even in Windows 8 in a VirtualBox under Windows 8.1 (host) Filezilla gets into the same trouble as in Windows 8.1.

Regards, Gewout.

PS. I tried Windows 7 in a VirtualBox under Windows 8.1 and than Filezilla seemed to work fine, but it gets the same problems.

The only solution is to reboot under Windows 8 to backup and then reboot again to work under Windows 8.1. Not very user frendly, but I am happy that I left my Windows 8 partition unchanged..

• Edited by Wouter57 Saturday, November 09, 2013 10:46 AM

I'm 99% certain this is a Windows 8.1 problem.  I run a number of computers under W8 and W7 and just one that's been upgraded to 8.1 for development purposes and that's the only machine with FTP issues.

On that machine I run Dreamweaver CC (64 bit) and use its internal FTP client extensively as part of development workflow.  Under W8.1 it mostly doesn't work when uploading files - I say mostly because from time to time it seems to work but if uploading multiple files or a directory it all sort of slows down and eventually fails.  I have the same issue on the same machine using an external FTP client (Filezilla) which exhibits problems but is much better at handling re-tries than Dreamweaver is.

I suspect that something inside IE11 is to blame - IE11 is so embedded into Windows that it has influence over all I/O and something, somewhere deep in the bowls is causing this FTP problem.  I'm sure if you've searched for "Windows 8.1 FTP problems" you'll see threads on various forums and tech support sites reporting similar issues.  I'm in the position of having multiple computers and operating systems to help with fault finding, along with my own servers, so I've been able to isolate the issue quite comprehensively.  Trouble is, I can't find any sort of reliable resolution.

Hello All,

Have FTP problems too after the upgrade to 8.1 and today the same problems are happening on the last updates for Server 2008.

Problem is the new update from IE11 (wininet.dll) FTP command like STOR and RETR are failed because de FTP server response gives a double answer, example:

after the FTP command 'STOR test.file' the FTP server responds is '150 Connection accepted' AND followed by the respons '226 Transfer OK'

Windows (wininet) received only the first respons '150 Connection accepted' and if you want to send (STOR) a second file the client receives the wrong answer (the second last response '226 Transfer OK')

I hope this will give anybody more information about the MS wininet bug

Same problem for me using internet Explorer 11 (it's not a Windows 8.1 problem, but  related to the latest build of ie11 that is available from Microsoft update since last Sunday and marked as important).

Wininet.dll distributed with ie11 seems to have a lot of problem.

For example using wininet ftp function and try to create an existing directory you will get ok, then try to change to that directory and you will get the error that you cannot create a file (or just try to create the directory twice the first one the result will be ok the second time the result will be wrong, and i aspected Always a wrong result code), and there are many of this kind of problem to make impossible to use any wininet ftp related function.

It seems that the return code of the previous ftp function will be reported in the next call of any wininet function.

Hope to have a fix really soon, in the meanwhile we reversed to previous internet Explorer.

Regards

Flavio

The updated WinInet that comes with IE 11 has a major bug when an FTP Application uses FtpFileOpen()/InternetWriteFile() in PASV mode (producible at will with THAT combination, there may be others).
Reason: WinInet will get out of synch with server responses, always lagging ONE behind.

The result is that any subsequent commands that require a certain server response (such as a RNFR/RNTO combo for a FtpFileRename(), or a second file transfer waiting to parse the next data port from the PASV response) will either time out or fail with a completely non-sensical error condition.

I recommend you add yourself to the existing bug report to amp up the "urgency":

https://connect.microsoft.com/IE/feedback/details/808279/ftpopenfile-and-internetwritefile-broken-changed-in-ie11#tabs

I have ftp problems too since I have installed Windows 8.1.
I can download files but uploads fail (with FileZilla, FlashFXP, SmartFTP and other clients).
Please fix ASAP. It's very important

Amping up the urgency might be nescessary.

I logged a call at Microsoft NL.

Some time later I received an email that they will close the call because they don't have a solution yet and the calls can't stay open longer than a certain time...

I can't offer a direct solution beyond the suggestion to use a commercial program I have been using successfully for years called WebDrive.

I have been using it over the past several weeks with Windows 8.1 x64 Pro and it runs rather well. 

Basically WebDrive "maps" a drive letter to the FTP site, then you just use Explorer to drag/drop, cut/paste, or even just save files to a path on that drive letter via any application - basically anything you can with a hard drive or mapped network drive.  Quite slick, actually.

 

 I had same problem with filezilla and the following resolved it.

Change your transfer settings in site manager from either default or passive to active it will then work.

• Edited by -GRWi- Friday, December 06, 2013 12:30 PM
• Proposed as answer by noby-squidron Tuesday, December 10, 2013 9:02 AM

 I had same problem with filezilla and the following resolved it.

Change your transfer settings in site manager from either default or passive to active it will then work.

• Edited by -GRWi- Friday, December 06, 2013 12:30 PM
• Proposed as answer by noby-squidron Tuesday, December 10, 2013 9:02 AM

 I had same problem with filezilla and the following resolved it.

Change your transfer settings in site manager from either default or passive to active it will then work.

• Edited by -GRWi- Friday, December 06, 2013 12:30 PM
• Proposed as answer by noby-squidron Tuesday, December 10, 2013 9:02 AM

Correct to some degree.

In Passive Mode, the initiation of a file transfer by the client sends the PASV command and then waits for a server response indicating an open port number - which the WinInet bug in IE 11 is preventing from being recognized. A "Port" mode connection (sometimes incorrectly referred to as "active") does not require that exchange of information, as the connection initiation is reversed for data (the server connects the client!). The PORT command already includes the open port number that the server should use so no further information exchange is needed.

Soooo, IF your own firewall/cable modem/gateway/router does have an stateful firewall, THEN you should be able to switch from PASV to PORT mode as a work-around without problems. However, for many end users, the precise REASON for being limited to PASV mode is, that with PORT mode the necessary inbound data connection from the server to the client are promptly blocked at the customer's "border" device (which may just be a simplistic access-list firewall, or one that hasn't been configured appropriately).

The result is that directory listings don't seem to complete and that file transfers "time out".

In summary - switching the connection settings from PASV to PORT mode is a valid, but limited, work-around.

I too am having FTP issues whereby I cannot download Adobe files.

What are we suppose to do?

Is MS going to fix this?

Peter

I have used 3 browsers and still have trouble downloading some sites such as Dell Manuals.

There is a possibility that the Comcast gateway is blocking port 20 ftp on the medium setting as the download works on the lower setting.

Quote: "The result is that directory listings don't seem to complete and that file transfers "time out"."

That's exactly my problem and it's very annoying.

Currently I do my FTP upload work on an old Windows 7 box, just to be able to actually upload anything!
But I need this to work on my Windows 8.1 development machine as well.

My Windows 8.1 laptop is up-to-date with every available Microsoft update, but it's still not working.
What can I do on my Windows 8.1 system to fix this situation?

It really is time that this problem was fixed - Microsoft, get off your backside and sort this problem!

This is a big problem and when  forced to update to Win 8.1 it is disappointing to see this old bug, that is still not fixed by Microsoft.

The problem seems to be specific if the computer is associated with a microsoft account.

If you have a local account the upload works just fine. I have realised the problem only started after associating my computer with windows account.

I have tried filezilla and native ftp through explorer and both break at some point without uploading the complete file.

I think this should narrow it down for MS to figure out the changes the association is making.

Thanks - Naman

I have 8.1 and my problem is a bit different--my customers need program file updates as we hone the final version.  When I make a change, I upload it to our ftp site and alert the users to download again.  Nobody opens it on the ftp site--we use windows explorer (or file explorer in the case of win8.1) to transfer back and forth.  To download, they have been dragging or copying and pasting to replace the new version (Win7).  Now a user has a new 8.1 machine to deal with.  The first download (meaning copy and paste to desktop) worked without a problem.  Then I uploaded an update to the ftp site.  A copy (of the new version on the ftp) and paste (to 8.1 desktop)  acted like it was working, but the original file remained unchanged.  I tried deleting that original file and then copying and pasting the new one.  Strangely, the original reappeared.  I then repeated that, except that I deleted all copies from the trash can before I downloaded the new one.  Strangely the original reappeared again.  Next, I rebooted.  This time I could download and replace without a problem.

I can upload to ftp from win8.1 but the only way I can download a file from ftp is if it has never been on that computer with the same name or if I have rebooted immediately prior to the download and replace.  I have a notepad test.txt on the 8.1 desktop.  If I make a change, I can upload the changed .txt to ftp.  The changed file can be downloaded on another computer and the changes are there intact.  Back on the 8.1 I can download the file I just uploaded, and the original reappears (without the changes that had been saved and uploaded).

I have carefully documented as follows:

I have updated the file in question on my development computer (Win 7).  I then saved it to a network drive.  I then uploaded it to the ftp.  Next, I went back to the Win 8.1 machine.  I opened the ftp and copied the file.  I then pasted it to the desktop.  I then opened the file and verified that it was not updated.  I then accessed the network drive and copied the file, then pasted on the desktop.  Voila!  It was updated.  Conclusion: Cannot copy and paste from ftp (unless it had never been present) but can update from other source.

On the Win 8.1:  Next, I reopened the ftp, copied the file.  Returned to the desktop (which now contained the identical updated version previously copied from network drive).  Pasted.  Opened the file.  Alas, it had reverted to the version prior to copying from the network file.  I next deleted the file, then downloaded from ftp again.  The previous version reappeared! Conclusion:  Anytime an update is attempted from ftp, the version reverts to something it finds in a cache somewhere.  I did try rebooting at this point, but the previous version was still there.

After a reboot of the Win 8.1 machine, I could copy and paste successfully from ftp to desktop.  

Note that users using Win 7 never have a problem.

Hi,

The best fix for FTP issue is to downgrade your FileZilla client version to 3.9.x. This will work absolutely fine with Windows 8.1. The downgraded version software is available on Filehippo website.

Thanks,
Jairam

• Proposed as answer by Jairam92 12 hours 45 minutes ago

Hi,

The best fix for FTP issue is to downgrade your FileZilla client version to 3.9.x. This will work absolutely fine with Windows 8.1. The downgraded version software is available on Filehippo website.

Thanks,
Jairam

• Proposed as answer by Jairam92 Saturday, May 30, 2015 6:36 PM