Filezilla lockup with Windows 2000 Pro

[posTech]

Win2000 Pro w/current updates
Filezilla 3.0.11.1

I was tring to connect to port 990 on the server (ftps)

Filezilla shows

resolving "servername":990

The program locks up and cannot be closed by any method known to myself. General OS instability follows. Hard reboot becomes the only option to return the system to its "normal" state.

What am I overlooking?

2/27/09 12:37pm - This issue is following a Filezilla upgrade accross multiple computers that do not share a network or geographic location.

2/27/09 12:47pm - 1st computer upgraded to 3.2.2.1 is having the same issue.

[botg]

If your entire system goes down it cannot possibly be a bug in FileZilla. Check your hardware for errors and reinstall Windows.

[posTech]

Filezilla is not crashing the system. Filezilla locks up and cannot be closed. The system must be restarted to get it off of the screen.

Is this occuring anywhere else?

[botg]

If you cannot kill a task other than through reboot, the system is broken. Back to my previous solution.

[ken0069]

I got a similar problem with Filezilla and Win 2K Pro but I can connect to a regular ftp. I can also connect to an sftp running SSH but I got two sftps that are running <FTPES-FTP over explicit TLS/SSL> and if I try to connect to either of those two my computer does the exact same thing this guy is reporting? And this IS a "current" load of Win2K with ALL updates by the way!

I'm currently running v3.0.8.1 but I did try the newest version when I first loaded Win2K on this system and it did the same thing as it's doing now.

??

[boco]

http://forum.filezilla-project.org/view ... 565#p25565

Read the posts above, Win2K support has been dropped with version 3.1.0, last officially working Win2K version is 3.0.11.1 .

From the download page:

Windows XP and Vista are supported.