Bug 11623 - Troubleshooter.exe needs to be update with the latest Firewall/Security Services
: Troubleshooter.exe needs to be update with the latest Firewall/Security Services
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Installer
: 7.3.2
: PC Windows XP
: P5 normal (vote)
: 8.0.0
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-02 19:16 UTC by Walker LaRon
Modified: 2012-03-09 07:24 UTC (History)
5 users (show)

See Also:
Category: Task


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Walker LaRon 2009-04-02 19:16:58 UTC
Hello All,

Per Dan, I am creating this bug to make sure that we update the Troubleshooter.exe to check for the latest Firewall/Security Applications that may cause problems with SqueezeCenter (e.g. Norton Internet Security 2009, Mcafee, etc)


Thanks,

LaRon
Comment 1 Michael Herger 2009-04-03 06:45:46 UTC
I don't know of an official resource for that information. Somebody has to collect it. I then can implement it. I've been collecting that information from bug reports and the community.

As I'm working on the control panel right now, have you been using the troubleshooter actively with helping clients?
Comment 2 Dan Evans 2009-04-03 08:37:36 UTC
Michael-- we can gather info on the new firewalls, if needed.  Another avenue is we should contact WiLife engineering again to see if they have an updated list.

Support-- please chime in here about you're using the Troubleshooter applet and what you experiences have been.
Comment 3 Walker LaRon 2009-04-03 09:04:01 UTC
Hello All,

I used the Troubleshooter.exe last night (4/2/09) on a customer's Window's Vista Machine.  When I ran it, it did find that the ports were blocked, but it did not pick up Norton Internet Security.  The troubleshooter actually crashed, and then a Windows Error came up.  When we tried to launch Norton Internet Security to get the version, the customer stated that it would not open.  

This may have been because Norton was actually corrupt in the first place, and the customer is now in the process of correcting this issue.  I will post more as I receive more information.


Thanks,

LaRon
Comment 4 Pat Ransil 2009-07-30 17:40:52 UTC
LaRon - is this still an issue? I am moving it to target 8.0.
Comment 5 Walker LaRon 2009-07-30 20:03:17 UTC
Hello Pat,

I have tested this with Norton Internet Security 2009, and the troubleshooter seems to work fine.  I believe that this was an isolated issue with the customer's Norton being corrupt.  At this point, I do believe that the Squeezebox Server Control Panel is currently being worked on, which in essence will replace the Troubleshooter.exe

Thanks,

LaRon
Comment 6 Michael Herger 2009-07-30 22:37:19 UTC
> At this point, I do believe that the
> Squeezebox Server Control Panel is currently being worked on, which in essence
> will replace the Troubleshooter.exe

That's correct. And they're both using the same XML data file. 

I think this isn't a real bug, but rather a task - this needs to be done continually. 

Dan - didn't you get that file from WiLife originally? Any chance we could get an update from them?
Comment 7 Anoop Mehta 2009-10-07 15:26:27 UTC
Dan - any update on a new file from WiLife?
Comment 8 Dan Evans 2009-10-07 17:02:28 UTC
Yes, but not helpful unfortunately.

From WiLife Dev: "Unfortunately that file hasn't gotten any attention since last [year]. If you have updates to it, we'd be happy to have you send those along :-) I think we might be getting back to detecting more and growing that file, but that wouldn't be for a [while] at least."

So, we're on our own.  According to the same developer, they gathered their data by just buying up all the firewalls and anti-virus software and getting their hands dirty.  So this would necessarily take someone's time to update.