Privatefirewall Now Free!

[bo.elam]

Originally Posted by wolfstr

Works well with SBIE, Avast, FF,IE8. Very pleased with it Bo. The trick is I think you have to let it(PFW) get used to your system for a few days (training) then you can harden up the control to "manual" instead of "auto" and everything still works fine including the avast auto updates. But yes, it works well with sandboxie in firefox which PCTFW beta did not. Not on my system anyway which is XP Pro SP3.

Your system is same as mine. I did try Private a few weeks ago and it did
not worked out, most likely because I also had Defense Wall. Since, I have
uninstalled DW and I will try Private again, mostly because of what you are
saying here.
Thanks, bro.

Bo

[wolfstr]

Originally Posted by bo.elam

Your system is same as mine. I did try Private a few weeks ago and it did
not worked out, most likely because I also had Defense Wall. Since, I have
uninstalled DW and I will try Private again, mostly because of what you are
saying here.
Thanks, bro.

Bo

Y.W. bro. I also run Dropmyrights when running firefox when not in sandboxie http://cybercoyote.org/security/drop.shtml I forgot to mention that. Along with Dropmyrights I have the following firefox addons.....keyscramber, noscript, wot, FTzilla, and addblock. I was using Prevx Safe Online as well but since have unstalled it. I think Sandboxie should do the job in itself. Good luck with PFW.

[bo.elam]

Originally Posted by wolfstr

Y.W. bro. I also run Dropmyrights when running firefox when not in sandboxie http://cybercoyote.org/security/drop.shtml I forgot to mention that. Along with Dropmyrights I have the following firefox addons.....keyscramber, noscript, wot, FTzilla, and addblock. I was using Prevx Safe Online as well but since have unstalled it. I think Sandboxie should do the job in itself. Good luck with PFW.

Alright wolfstr, got it running for 20 minutes and its moving good, just like the
first time I installed it. That time I uninstalled it because I thought it messed
up my IE, but I was wrong then.

Bo

[bo.elam]

I use it for a few hours last night and today and can not see any
reason why it wont stay on my computer.
Any advices on changes to the settings are welcome. The training
disabled itself ( when I right click the icon in the taskbar) but it was
on when first installed Private. I can see that training mode is on for
System anomaly when I go into settings in the main GUI but not for
process and firewall monitor settings.

Bo.

[wolfstr]

Originally Posted by bo.elam

I use it for a few hours last night and today and can not see any
reason why it wont stay on my computer.
Any advices on changes to the settings are welcome. The training
disabled itself ( when I right click the icon in the taskbar) but it was
on when first installed Private. I can see that training mode is on for
System anomaly when I go into settings in the main GUI but not for
process and firewall monitor settings.

Bo.

I left the settings as is for the first couple of days. I set Internet Security and Network Security both on High. After a couple days I went into settings by clicking on File at the top and clicked Manual Control and Disable auto response. I left System Anomaly Detection go through it's training period for 7 days. PFW runs smooth here everything snappy fast with avast with no lags whatsoever. More details here http://www.privacyware.com/pf_product_tour.html
If you have any problems you can post them here http://www.privacyware.com/support_ticket.html

Also this is interesting from Stem....firewall expert from Wilders plz. not re port 135. I followed his advice on this as well.

Stem Stem is offline
Firewall Expert

Join Date: Oct 2005
Location: UK
Posts: 4,688
Default Re: Privatefirewall VERSION 7.0.20.47
Quote:
Originally Posted by drakhil
firewall tends to leave port 135 open any solutions

You will need to check your settings.

I presume you are connected directly to the Internet?
I have only looked at this on an XP setup, so there may be some difference for other OS?

Open PF and on the "Main Menu" make sure that both "Internet Security" and "Network Security" are set to "High". Under "Network Security" press "Sites", any IP range you see should be set as "Untrusted Network"

On the "Applications", double click "Generic Host Process"(svchost) Find the rules(there are 2) that are for "Location service" select one of those rules and then select "Modify" In the popup window, change the rule to "This rule will Deny Traffic", press OK, do the same for the other rule. Then check to see if there are any other rules that are showing port 135, if yes, then make sure they are set to "Deny".



- Stem

Hope this all helps Bo and maybe MC can give some advice on PFW as well, as he was the one that initially announced it's "freeware status" inauguration here in the forum.

[MidnightCowboy]

Port 135 is linked to the RPC service but as I always disabled DCOM when I had XP this is maybe why I never saw this issue with Privatefirewall. My last version of XP was also pre-tweaked which again maybe accounted for this although I never dissected the OS services to find out exactly what had been changed from the default format.

[wolfstr]

DCOM in services here is set on "started" and "automatic". Is it better to set it at manual? Also RPC is set to "started" and "automatic" and some of the programs that depend on it are avast, privacyware, windows installer, audio, Print spooler, network connections etc. etc. just to name a few. Found this to be interesting http://blogs.techrepublic.com.com/10...60&tag=tr-left
As far as the PFW goes the settings as is seem to working quite well along with avast with the way it is set up so I think I'll stand pat for now.
MC would like some more info on DCOM plz.

[MidnightCowboy]

Everyones needs (and views) are different and I never advise anyone to go around "tweaking" or disabling things unless they are certain of what they are doing.

A couple of alternative views here

http://www.grc.com/freeware/dcom.htm
http://www.grc.com/unpnp/unpnp.htm

[wolfstr]

Thanks for the info MC. Universal plug and play was already set on manual. DCOM on manual as well with port 135 blocked.

[vasa1]

Is this DCOM thing an issue on WinXP3? Is there anyway I can tell if my PC is suffering from it without using GRC's DCOMbobulator?

Will I see it in the task manager?