Re: Symantec corporate AV & Firewall co-existence problems?

On 7/13/06, Jones, John (US) <John.Jones@xxxxxxxxxx> wrote:

No experience with it; we don't do anything Symantec here except the
smattering of pcAnywhere when Windows Remote Desktop won't suffice.
That Symantec wouldn't be compatible across their own product lines
shows how bad their product lines have gotten (lots of complaints on
various forums like the Gripe Line ( http://www.gripe2ed.com/scoop/ ).

First, Norton AV goes down the tubes, then Symantec's AV/firewall.  How does
a company with that kind of experience let that happen?  John, what is your
company using for enterprise AV/firewall?

Can you put on your own software?


Is that a question of permission or capability?  ;-)  Ultimately, since I am
somewhat responsible for overall safety of my laptop, I *will* install
software that will protect it, and answer questions later.

 If so, get Kerio firewall

http://www.sunbelt-software.com/Kerio.cfm - there are free & paid
versions; the differences are on the link.  The free version is probably
sufficient.

That's my thinking, too.  I'll have to check to see if the free license
allows usage on corporate PCs.

Or get Zone Alarm, although gripes about them & their

support have been on the rise lately.

Given the non-support I've gotten from them ON THEIR PAID PRODUCT, ZoneAlarm
is not a product I want to deal with anymore.

Also, do what you can to tighten down Windows in general - turn off

services you don't use like file sharing, etc.  Make sure your wireless
doesn't work on ad-hoc (peer to peer) networking; access point should be
the only way you ever use it.

Navigating to Wireless Network Connection Properties, then Advanced, I have
the "Access point (Infrastructure) network only" selected, yet the ad-hoc
networks keep showing up on the available networks to choose from.  (If
anyone can suggest a replacement for Microsoft's Wireless Network Connection
app, which is a total POS, please advise.)  BTW, I never connect via ad-hoc.

Apply all security patches except the WGA

update (which was pushed as 'critical' but is really a strong-arm tactic
by MS to invalidate questionable XP installs).

Probably another topic but...  Even though I detest MS trying to push WGA as
a critical patch (cuz who knows what else that will lead to), since I *know*
my XP install is legit, I am inclined to allow it.  I haven't yet, in the
hope that it sends a signal to MS that the Windows community won't accept
this crap.  I know, I know, 98% of the XP home users don't know any better
than to just let MS automagically "secure" their PC.

I've bypassed the need for public WiFi as long as my cel phone works.

My new Treo 700p      <snip>

Whoa, way outta my league dude.  Now, if the company wants to pick up the
tab on that...

- Dan