firewall for KazaaLite : wich one ?

[Matteo F.]

Dear friends,

I would like to know (if possible ... ;-) ) if there is any firewall
that correctly handles kazaalite.

I now have Outpost free, but I have to set it (just on kazaa) as
"permit all".
I read that there are similra problems with Norton too.

What about Sygate and ZoneAlarm ?

Any advice / suggestion / idea will be really appreciated.

Best regards,

Teo
------------------------
Matteo F Italy

To reply delete REMOVE from my e-mail address.

[donut]

> If the above doesn't work, you can alter the outgoing TCP rule to
> include a wider range of ports instead of just 1214. I have mine set
> to allow outgoing connections on TCP ports 1214-4000.
>

My experience is that Kazaa Lite will only look for port 1214 the first
time you run it. If it doesn't find it open, it will start looking for open
ports one at a time progressing upwards.

Since the &^%$ thing seems to have a memory about this, once it didn't find
port 1214 open, you are going to have to leave a lot of ports open so it
can find one it likes.

I currently do not have Kazaa Lite installed, so just to test this, I'll
reinstall it this afternoon, allow it to find port 1214, and see where it
goes from there. As most of us probably are, I just plain don't like apps
that are port hogs.

I'll report back what I found.

[donut]

donut <no...@none.com> wrote in
news:Xns93757D6...@216.102.43.227:

Well, my memory was wrong, except for the fact that this program is a
b*tch.

It wants to listen on port 1214, but is not at all happy with that choice
for other functions.

On first startup, it tries port 1030. If that's not open, it seeks upward,
one at a time. It "remembers" where it left off, so the only way to get it
to start back at port 1030 again is to uninstall it, clean the registry,
restart the computer, and reinstall Kazaa Lite.

But even that's not good enough. Once installed and set up, it wants to
bounce around and use different ports. What a b*tch. I left it ports open
to use and it skipped right over them. Also, even though it was connected
out on port 1102, when I tried a download, it then insisted on trying to
jump to port 1106, which of course, was closed. Back to the one at a time
port search. And yes, it ignored the open port 1214.

It appears the only way to make it happy is to leave ports 1032 - 4000 open
and let it decide.

Another way this thing is a b*tch. When you try to enable the app,
kazaalite.kpp doesn't even show in the Kazaa Lite directory as an option!
You have to type it in manually.

I wonder if the port seeking is tied into the missing spyware and adware.
It would have needed a number of ports open for all that crap.