Core FTP server disconnecting
Posted: Sat Jun 27, 2009 12:19 pm
Hi there! Please forgive me for the vast amount of text I'm about to send forth.
I have a persistent problem which I can't seem to fix on my own. I am using Core FTP Build 297 and is hosting an SFTP server with it. I can log in and LIST throughout the server and UPLOAD files but I am unable to DOWNLOAD files because the server instantly disconnects me (giving me a "timeout" message, a "server disconnected" message or a "software caused transfer to abort" message). In fact, it goes so far as to disconnect me from the Remote Desktop I have running at the same time. The whole server seems to get a hiccup from the attempted download.
The server is a Windows 2003 rig and I am using a Vista 32bit rig to connect with. The clients I have been using to try downloading is FileZilla, Tunnelier, WinSCP.
Now here comes the kicker: this weird thing happens to every single SFTP server software I have tried: Core FTP Server, Sysax, freeFTPd, Crush FTP. If I'm hosting the SFTP server on my Vista machine just to check it out it can be reached without any problems from the outside but on my win2003 machine I get disconnected.
Turning the firewall and/or AV software off completely on both the client and the server doesn't help. Changing ports doesn't help.
And this is where it gets REALLY weird: I am actually able to connect and download files if i use the Core FTP client (although only in the devastating speed of 146kbps on a 100mbit wire, both in and out). The Core FTP client can even handle downloading files from Sysax FTP server! Your client seems to be able to handle it all, albeit slowly. The thing is, I would like it to work with other clients as well but I can't find what causes any SFTP server to disconnect every other client except for the Core FTP client.
So I guess my question is: what do you think might be causing this error? And how come your Core FTP client can "bypass it" when no other client can do that? Is there some sort of inherent configuration in your client that no other client has by default? Or is there some weird thing I have failed to account for when setting up the Core FTP server which unables other clients to connect to it?
Thanks for reading my question and I hope it makes sense. It was a lot of info in one go here.
I have a persistent problem which I can't seem to fix on my own. I am using Core FTP Build 297 and is hosting an SFTP server with it. I can log in and LIST throughout the server and UPLOAD files but I am unable to DOWNLOAD files because the server instantly disconnects me (giving me a "timeout" message, a "server disconnected" message or a "software caused transfer to abort" message). In fact, it goes so far as to disconnect me from the Remote Desktop I have running at the same time. The whole server seems to get a hiccup from the attempted download.
The server is a Windows 2003 rig and I am using a Vista 32bit rig to connect with. The clients I have been using to try downloading is FileZilla, Tunnelier, WinSCP.
Now here comes the kicker: this weird thing happens to every single SFTP server software I have tried: Core FTP Server, Sysax, freeFTPd, Crush FTP. If I'm hosting the SFTP server on my Vista machine just to check it out it can be reached without any problems from the outside but on my win2003 machine I get disconnected.
Turning the firewall and/or AV software off completely on both the client and the server doesn't help. Changing ports doesn't help.
And this is where it gets REALLY weird: I am actually able to connect and download files if i use the Core FTP client (although only in the devastating speed of 146kbps on a 100mbit wire, both in and out). The Core FTP client can even handle downloading files from Sysax FTP server! Your client seems to be able to handle it all, albeit slowly. The thing is, I would like it to work with other clients as well but I can't find what causes any SFTP server to disconnect every other client except for the Core FTP client.
So I guess my question is: what do you think might be causing this error? And how come your Core FTP client can "bypass it" when no other client can do that? Is there some sort of inherent configuration in your client that no other client has by default? Or is there some weird thing I have failed to account for when setting up the Core FTP server which unables other clients to connect to it?
Thanks for reading my question and I hope it makes sense. It was a lot of info in one go here.