Re: Faulty 16.5 engine patching, pls help!!!

Rohit1gupta · ‎09-30-2008

is this software compatible with newer norton?

why not use norton parental control its free addon with NIS may b it will solve the problem.

----------------------------------------------------------------

NIS 2011 beta 18.0.0.107 Win 7 7600 RTM 32-bit

OscarL · ‎08-19-2008

philled,

LiveUpdate uses HTTP. Since dansguardian has URL filtering capability, it could be blocking the LiveUpdate traffic.

Did this ever happen before upgrading to 16.5?

galionlibrary · ‎03-24-2009

philled, our Windows systems here are all going through an even older version of Squid than what you have (2.5.STABLE13, no kidding, long story, and yes, we will probably update it some time this year), and the above-linked fix works for me here. The proxy returns an HTTP/1.0 response, but with the fix applied LiveUpdate works. In some cases the updates don't all apply the first time, but after another reboot/LiveUpdate cycle that resolves. Product is NAV 2009 Small Office Pack.

Is it possible you have a different or additional problem? Can you follow it through to the point of getting the error numbers again and see if you're getting different error numbers now?

philled · ‎03-31-2009

Rohit1gupta wrote:
why not use norton parental control its free addon with NIS may b it will solve the problem.

Because dansguardian works at the router level and therefore filters all access devices, not just Windows PCs. Also it means I only have to manage one app rather than a Symantec app on a number of PCs.

philled · ‎03-31-2009

OscarL wrote:
LiveUpdate uses HTTP. Since dansguardian has URL filtering capability, it could be blocking the LiveUpdate traffic.
Did this ever happen before upgrading to 16.5?

No, this never happened before 16.5. The annoying thing is I didn't even know I'd upgraded to 16.5 - it must have auotmatically updated without asking.

Good suggestion, but I checked my Dansguardian log when running live update and nothing appears so I don't think the problem is with Dansguardian. Another reason why I don't think it's with Dansguardian is because I have my account set up to not filter so I think Dansguardian just passes the request straight through to Squid when it's from my logon.

philled · ‎03-31-2009

philled wrote:
OscarL wrote:
LiveUpdate uses HTTP. Since dansguardian has URL filtering capability, it could be blocking the LiveUpdate traffic.
Did this ever happen before upgrading to 16.5?
Good suggestion, but I checked my Dansguardian log when running live update and nothing appears so I don't think the problem is with Dansguardian. Another reason why I don't think it's with Dansguardian is because I have my account set up to not filter so I think Dansguardian just passes the request straight through to Squid when it's from my logon.

I've just changed it so my account now goes through D. I notice that for every web page I visit I get an entry in the log files for squid and DG. But when I run live update I get nothing. So that makes me wonder whether it's not actually talking on port 80. Can anyone confirm what port live update uses?

philled · ‎03-31-2009

Re my problem getting Liveupdate to work through Dansguardian/Squid I have fixed it by changing some proxy settings in Norton:

Settings --> Miscellaneous Settings --> Network Proxy Settings --> Configure [+]. In here I set the name of the server Squid is running on and the port number it's listening on and I ticked the "Use a proxy server for HTP connections" box.

I also had to reconfigure Squid to be able to listen for connections coming from PCs on the network as prior to that it would only accept connections from Dansguardian which runs on the same machine as Squid.

Hope this helps someone in future.

philled · ‎03-31-2009

philled wrote:
Re my problem getting Liveupdate to work through Dansguardian/Squid I have fixed it by changing some proxy settings in Norton:

Settings --> Miscellaneous Settings --> Network Proxy Settings --> Configure [+]. In here I set the name of the server Squid is running on and the port number it's listening on and I ticked the "Use a proxy server for HTP connections" box.

I also had to reconfigure Squid to be able to listen for connections coming from PCs on the network as prior to that it would only accept connections from Dansguardian which runs on the same machine as Squid.

Ps - I also meant to say that I did this on my existing Squid 2.6 version. I didn't have to upgrade to 2.7 or later which has better HTTP 1.1 support.