Zone Alarm

From VuzeWiki
Jump to: navigation, search

Zone Alarm 5.0 vs. BitTorrent![edit]

The Zone Labs firewall products Zone Alarm 5.0, Zone Alarm Pro 5.0, and Zone Alarm Security Suite 5.0 are not compatible with Azureus due to an issue with their TCP filter, ~TrueVector (vsmon.exe) Usual symptoms of this issue include but are not limited to 100% CPU usage, slow transfer speeds, corrupted files, trouble establishing incoming and outgoing transfers, complete network outages, complete system freezes, random reboots, and blue screens of death. Disabling Zone Alarm's firewall protection will not solve the problem as its filter will still be running in the background. A complete uninstallation is required. This issue is not limited to Azureus, and has been confirmed by users of many other filesharing clients including ~BitTornado, ABC, Shad0w's Experimental, EMule/Gnutella, and Shareaza.

Bottom line, don't use Zone Alarm 5.0. This is just one of the many many problems people are having with it. If you want examples, check their forums: http://forum.zonelabs.org/zonelabs

So you're left with two options

  • Downgrade to Zone Alarm 4.5
  • Get a different firewall (recommended)

If you want to try out a different firewall, there are many good ones to choose from.

Free for personal use:

Here are some fairly recent reviews if you're interested in a commercial firewall application or security suite

Feel free to add your own firewall recommendations.




Back to the Azureus FAQ



Update on using Azureus with ZoneAlarm 5.5[edit]

I just wanted to report that I've been using Azureus with ZoneAlarm 5.5 (5.5.062.011) with no problem. Download speeds are the same as before.

See this forum thread for info on how to config ZoneAlarm to allow your bittorrent client to access the net.

Note: The forum post was deleted, for whatever reason.

How to configure

Update on using Azureus with ZoneAlarm 6.0631[edit]

I just wanted to report that I've been using Azureus with ZoneAlarm 6.0631 with no problem. Download speeds are the same as before.

Update on using Azureus 2.5.0.4 with ZoneAlarm 6.5.737.000 Free under Windows XP[edit]

Azureus works quite well under these circumstances.

However, after several days of running, ZoneAlarm will freeze up, and I get Windows errors with a code 0xC0000142 (which appears to be related to lack of heap space, and I can't run any more programs, not even the task manager). In short, something chews up the heap memory over time, and it's a mess. Rebooting takes forever, probably because no heap space is available. It's the only time I have ever had to do hard shutdown in Windows XP.

The ZoneAlarm forum has a thread that mentions the 0xC0000142 error with Azureus, but there's no precise support that explains what to do. The recommendation is to zap the ZoneAlarm database files (which erases your ZoneAlarm permissions, and you have to re-allow everything). The explanation on the page seems to indicate that this clears up a lot of problems, much like re-installing the software. Memory leaks are hard to diagnose and correct.

I have tried this for now, but will see what happens. Likely this is only a temporary fix.

I suppose another work-around is to reboot every day or so, since the problem doesn't occur until after more than 2 days of running Azureus, probably because the memory leak in the heap is slow. Again, this problem could be other things that chew up the heap, such as virus scanners that run overnight (AVG) or the Java virtual machine. All I can say is that I never had this problem until I installed ZoneAlarm 6.5 Free, and I never had any previous version of it.

OutPost[edit]

Azureus (2.2.0.0) works with Outpost (2.5.370) with these rules for javaw.exe:

Torrent HTTP Connection Rule Where the protocol is TCP and Where the direction is Outbound and Where the remote port is HTTP Allow it

Torrent HTTPS Connection Rule Where the protocol is TCP and Where the direction is Outbound and Where the remote port is HTTPS Allow it

Torrent Network TCP Inbound Rule Where the protocol is TCP and Where the direction is Inbound and Where the local port is 6881 Allow it

Torrent Network TCP Outbound Rule Where the protocol is TCP and Where the direction is Outbound and Where the remote port is 1024-65535 Allow it

Torrent Network UDP Inbound Rule Where the protocol is UDP and Where the direction is Inbound and Where the local port is 6881 Allow it

Torrent Network UDP Outbound Rule Where the protocol is UDP and Where the direction is Outbound and Where the remote port is 1024-65535 Allow it

Localhost Loopback Inbound Rule Where the protocol is TCP and Where the direction is Inbound and Where the remote host is 127.0.0.1 Allow it

Application UDP DNS Resolution Where the protocol is UDP and Where the remote host is the IP address for your DNS server and Where the remote port is DNS Allow it

TCP Inbound Blockall Coverage Rule Where the protocol is TCP and Where the direction is Inbound Block it

TCP Outbound Blockall Coverage Rule Where the protocol is TCP and Where the direction is Outbound Block it

UDP Blockall Coverage Rule Where the protocol is UDP Block it

Stolen from http://www.outpostfirewall.com/forum/showthread.php?s=e89eee7e04a1491c10a6e2a6159ffd51&t=12542&page=1&pp=15


I also run ZA 5.5 and Az 2.3 (Beta B3) without problems but will have to look into ISPs blacklisting ports and the relationship to UPnP at the router level. I had not considered the Torrent Network UDP Outbound Rule described above


One more thing regarding ZoneAlarm users - please be sure to set program security on "Medium" and not "High".