grahamperrin Posted September 3, 2010 Report Share Posted September 3, 2010 Different from nearby http://forum.immunet.com/index.php?/topic/304-201512-code-19010-unable-to-install-updates-following-application-of-an-extended-plus-key-on-a-second-computer/ — the security layer on this computer includes Sophos Endpoint Security and Control — so I don't expect support on this one. Yesterday, AFAIR logged on to XP as administrator 'centrimadmin' I applied a key then the resulting update/upgrade, including TETRA, succeeded. Today, logged on to XP as administrator 'gjp22' (also a member of the SophosAdministrator group): > Unable to install updates I tried logging out, logging on as centrimadmin to apply updates but still, no go. Sophos Anti-Virus is currently configured to alert (not quarantine), plus both of profos.sys and tufos.sys are explicitly authorised in all three areas (Suspicious files | Suspicious behaviour | Buffer overflow). Link to comment Share on other sites More sharing options...
grahamperrin Posted September 3, 2010 Author Report Share Posted September 3, 2010 When I used the Support Diagnostic Tool a .zip was created but again, ipsupporttool.exe crashed — that's http://forum.immunet.com/index.php?/topic/303-20152-extended-plus-ipsupporttoolexe-crashing/ If you'd like the zip sent to the e-mail address for support, just say. Link to comment Share on other sites More sharing options...
grahamperrin Posted September 3, 2010 Author Report Share Posted September 3, 2010 In a little more detail, with screen shots … Sophos Anti-Virus is currently configured to alert (not quarantine), plus both of profos.sys and tufos.sys are explicitly authorised in all three areas (Suspicious files | Suspicious behaviour | Buffer overflow). http://www.wuala.com/%23%23ClamAV/009 shot 001 reminds me that when this machine first failed to update: * it broadly coincided with installation of the high priority Microsoft Update to Sliverlight, AFAIR the completion of that one installation preceded the eventual failure of the update. * the Sophos shield was missing from the system tray notification area, and I saw no alerts (probably because of the shield's absence) * AFAIR I then found both profos.sys and tufos.sys not yet authorised in the Suspicious files and Buffer overflow areas; and only profos.sys (not tufos.sys) authorised in the Suspicious behaviour area — and so I in Sophos I relaxed the HIPS behaviour and completed the authorisations. Screen shots 002 and 003 capture the failures whilst later logged in as centrimadmin, with both profos.sys and tufos.sys fully authorised in the three areas, and no new alerts, and nothing new in Sophos quarantine following the failures. Link to comment Share on other sites More sharing options...
grahamperrin Posted September 3, 2010 Author Report Share Posted September 3, 2010 Right now we do not have Proxy support as such. That's probably the issue. Neither http://support.immunet.com/tiki-searchresults.php?highlight=proxy&boolean=on&search=Go nor http://support.immunet.com/tiki-searchresults.php?highlight=proxies&boolean=on&search=Go find anything so maybe you should add a note to the list of known issues, http://support.immunet.com/tiki-read_article.php?articleId=20 Thanks Link to comment Share on other sites More sharing options...
grahamperrin Posted September 4, 2010 Author Report Share Posted September 4, 2010 As expected, this VM had no trouble with updates after I moved the host laptop * from a campus environment (transparent proxy) * to home. Link to comment Share on other sites More sharing options...
grahamperrin Posted January 7, 2011 Author Report Share Posted January 7, 2011 Continuing under http://forum.immunet.com/index.php?/topic/273-proxy-server/page__gopid__3413#entry3413 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.