Re: Intermittent E_NOINTERFACE error, possibly RPC related


"Eugene Gershnik" <gershnik@xxxxxxxxx> wrote in message
news:uVk7HSjWHHA.1200@xxxxxxxxxxxxxxxxxxxxxxx

.... < snip > ...

AV and other "security" products work by inserting filters and hooks into
normal Windows kernel and user-mode operation.Theoretically this can be
done
safely but in practice the people who do this stuff usually end up
breaking
something. I've seen it many times myself (especially with Symantec
products) and according to other posts here and in programmers'kernel I am
definitely not the only one.

--
Eugene
http://www.gershnik.com



I just want to echo this thought. From what I have seen, the Symantec
products are especially susceptible to poor coding practices that break
network expectations. As one truly despicable example that bit me,
Symantec's "Norton Internet Security (NIS)" is so brain-dead that it can't
figure out HTTP content that has been gzip-compressed. The Symantec
solution, astoudingly, was to change the request header, so that if your
browser (or, in my case, the client app that I had written) sent a request
with a "Accept-Encoding: gzip, deflate" header, Symantec changed it to
"Accept-Encoding: ----, -------" (literally, with the dashes), before it let
the request out onto the wire, so as to suppress the server's return of
gzip'ed content. Their current version of NIS is almost worse: "WARNING:
New Norton Internet Security Issue" at
http://www.port80software.com/200ok/archive/2006/01/04/901.aspx

Steer clear of Symantec.


.