From: Gary on

Kayman spewed:
> You don't know me, if you group me in some arbitrary fashion, that is
> your own inability to see clearly and not my issue.

What is your technical issue? Or is it merely one of attitude? *yawn*

> Spreading marketing hype instead of sound technical advice?
> Which 'security' software manufacturer do you represent?

None of them. I've been a unix sysadmin for 15+ years. What's your excuse?

-Gary
From: Gary on
Kayman wrote:
> 4. Reconsider the usage of IE and OE.

It would appear that your Usenet bot misread the subject line. Its form
letter response engine is also missing a most crucial step:

Lucky #13. Try opening a support incident with your software vendor before
soliciting biased advice from the the curmudgeons of Usenet.

FYI, not that Cisco haven't made their fair share of missteps over the
years but they actually include the Zone Alarm engine in their IPsec
client. Naturally, it's been stripped of its standard UI and access list
and enforces policies set by the VPN endpoint thus eliminating the newbie
factor from the equation. Of course, this is more restrictive for the end
user but that's the intention.

As for the original poster, I would, unfortunately, have to suggest that
you try the de rigeur of Windows trouble-shooting steps; uninstall and
reinstall it unless advised otherwise by the vendor you're paying to
support your product. Does it have an option to export/import your
existing access policy? If so, be sure to export it first so you can
reimport it after reinstalling.

-Gary
From: Kayman on
On Mon, 05 May 2008 20:15:36 -0000, Gary wrote:

> Kayman wrote:
>> 4. Reconsider the usage of IE and OE.
>
> It would appear that your Usenet bot misread the subject line.

How so? Why is re-evaluation provoking such a comment?

> Its form letter response engine is also missing a most crucial step:
> Lucky #13.

Your superstitious notions are of little importance. You may consider
"Myriads of popular anti-whatever applications and staying ignorant" as
item 13.

> Try opening a support incident with your software vendor before

Yeah right. The makers of commercially driven Illusion Ware are bending
over backwards...

> soliciting biased advice from the the curmudgeons of Usenet.

You don't know me, if you group me in some arbitrary fashion, that is your
own inability to see clearly and not my issue.
But yes, mea culpa, the advice favors common sense over advertisement
driven Phony-Baloney Ware.

> FYI, not that Cisco haven't made their fair share of missteps over the
> years but they actually include the Zone Alarm engine in their IPsec
> client. Naturally, it's been stripped of its standard UI and access list
> and enforces policies set by the VPN endpoint thus eliminating the newbie
> factor from the equation. Of course, this is more restrictive for the end
> user but that's the intention.

Spreading marketing hype instead of sound technical advice?
Which 'security' software manufacturer do you represent?

> As for the original poster, I would, unfortunately, have to suggest that
> you try the de rigeur of Windows trouble-shooting steps; uninstall and
> reinstall it unless advised otherwise by the vendor you're paying to
> support your product.

De rigueur steps are oftentimes inadequate when trying to remove
questionable software. Even Norton/Symantech and others provide speciality
removal tools, oh well.

> Does it have an option to export/import your
> existing access policy? If so, be sure to export it first so you can
> reimport it after reinstalling.

You obviously know little about ZA.
Would you care to meaningfully explain how your response, I guess
you deem it a reasonable explanation, is any except a self-centered
viewpoint expounding a self-centered approach.
--
Arguing with anonymous strangers on the Internet is a sucker's game because
they almost always turn out to be (or to be indistinguishable from)
self-righteous sixteen-year-olds possessing infinite amounts of free time.
(Neil Stephenson, author of "Cryptonomicon")