[Ooo, I didn't think of the possibility that they may have upgraded to Vista
with KIS installed, Robert. Nice catch!]
Robert Aldwinckle wrote:
Quote:
> "jimmy3d" <jimingraham@xxxxxx> wrote in message
> news:36160400-4894-4094-b08a-15f061dc2d04@xxxxxx Quote:
>>
>>
>> i too am having this same problem...am running vista home prem with
>> Kapersky Int. Suite installed but with it's firewall disabled.
>
>
> But was it ever enabled? And, to reask another of my questions,
> does it have any diagnostics in it which would clarify what is happening
> when it is enabled? If so, (to repeat) enabling it could prove
> helpful...
> ; o
> Also, this suggests that perhaps Kaspersky was running when the install
> was done (or after the boot needed to install the updated in-use modules)?
> If that was the case and if that product did _anything_ to disrupt the
> install you would have another explanation for your symptom. E.g. that
> could prevent IE from working properly by breaking its configuration in
> the
> registry. Diagnosing that without any knowledge of IE's internals would
> probably be practically impossible. The best you could do then I suspect
> would be using ProcMon to trace file and registry accesses for both good
> and bad cases and then try comparing the two logs.
>
> Quote:
>> the problem is only with IE7 as Firefox and email works fine.
>
>
> Which proves you do have adequate connectivity but doesn't clarify
> whether iexplore.exe is being blocked (assuming now that the install
> was not corrupted in any manner by your security package.)
>
> Quote:
>> Am a little
>> hesitant to uninstall Kapersky as its a little dicey getting keys re-
>> recognized sometimes.
>
>
> So then try the other diagnostics I suggested. ; }
>
> Another approach which may help if a blockage is active in nature
> would be booting in safe mode with networking. E.g. then if the blockage
> was being caused by misconfigured service, that program might be less
> likely
> to be running.
>
> If the blockage is being caused in some other manner, e.g. some kind of
> deliberate modification to the new iexplore.exe module by your security
> apps which prevents it from running properly--unless there is some builtin
> monitoring which shows the reason for the failure of attempts to use the
> program over the network, I don't know how you will be able to detect what
> is causing it. This possibility would just be a hopefully more
> discoverable instance of the
> "broken configuration" hypothesis. Again, running ProcMon and
> comparing
> good and bad traces would be what I would try to provide sufficient clues.
>
>
> Good luck
>
> Robert
> ---