Upgraded and now can't connect

[Perrorist]

I've upgraded today from a previous version 3 to 3.1.0. It retained my configurations but none of them will connect now. See message below.

Status: Connection attempt failed with "ECONNREFUSED - Connection refused by server".
Error: Could not connect to server

Using another FTP program, I had no problems, so it's not a server issue. I've also given FZ a free pass through the firewall.

Any suggestions?

[botg]

Can you run the network configuration wizard?

[Perrorist]

It says, "Connecting to probe.filezilla-project.org" and that's it. I cancelled after waiting ten minutes.

[botg]

The code for the network configuration wizard has not been changed in any way. Your firewall, virus scanner, security solution, whatever keeps blocking FileZilla.

[boco]

I find the term 'security solution' most amusing. Such software is not a solution at all.

[botg]

I wouldn't even go so far and call it software. It's usually just some fancy picture with a lock, telling you you are secure. Good desktop background

[Perrorist]

Like I said before, I've given FZ a free pass. It has more passthrough than the previous version.

Obviously it's being blocked, but why did the previous version work a treat and this one doesn't, when nothing's supposed to have changed regarding configurations?

My modem/router has a firewall but it doesn't have much effect. I'm using ZoneAlarm Pro ISS, and I'm comfortable with configuring what it can and can't allow through.

What I will now do, seeing as the upgrade hasn't worked, is to uninstall it, reboot, re-install as new, reboot, and then see if I can connect. I'll let you know the result. Luckily I have another FTP client that's working.

[boco]

Usually firewalls block applications when the executable has changed, regardless of configuration level for the app in the fw.

[Perrorist]

Maybe, but I've manually set it so that it passes through.

[Perrorist]

I did what I said I would and the problem remains. However, turning off ZA allowed the client to connect (I should have tried that earlier). I still can't see why ZA is blocking it, given that I've removed all constraints on what the program can do. The previous version (3.0.11) didn't have this problem. Weird.

[boco]

Try deleting and re-creating the rule.

[Perrorist]

What I also found interesting is that setting the rule to ask permission for any attempt to connect to the outside world never resulted in a ZA alert. It's as if the request never got that far.

[gibney]

I have the same difficulty. I just let the upgrade happen and now I get connected, but it fails quickly.

Trace: GnuTLS error -9: A TLS packet with unexpected length was received.
Status: Server did not properly shut down TLS connection
Error: Could not read from transfer socket: ECONNABORTED - Connection aborted
Trace: CTransferSocket::TransferEnd(3)
Trace: Skipping socket event 5, no socket or id mismatch.

[boco]

I have the same difficulty. I just let the upgrade happen and now I get connected, but it fails quickly.

Trace: GnuTLS error -9: A TLS packet with unexpected length was received.
Status: Server did not properly shut down TLS connection
Error: Could not read from transfer socket: ECONNABORTED - Connection aborted
Trace: CTransferSocket::TransferEnd(3)
Trace: Skipping socket event 5, no socket or id mismatch.

Completely unrelated problem. Server must be upgraded.

[gibney]

Not at all unrelated. I upgraded my client and now get this failure when connecting to z/OS Server.