0 Members and 1 Guest are viewing this topic.
Quote from: mdubin on May 02, 2010, 10:11:41 PMStill getting Error 267 which PK is aware of.The fix should be present in one of the upcoming VPS updates, it was not included in this program update.
Still getting Error 267 which PK is aware of.
Removed 507 completely, rebooted and installed 533. Now the Mail Shield refuses to start. Clicking on 'Start' in the UI does nothing. If I try and start the service manually in services.msc it fails to start. Event viewer says:The aswRdr service failed to start due to the following error: The system cannot find the file specified.aswRdr.sys exists in c:\windows\system32\drivers.Tried uninstalling, rebooting, running the standalone removal tool, rebooting and reinstalling but have the same problem.Any ideas?
AIS firewall: I had trouble installing an adobe air application because apparently the firewall was blocking Akamai...I had to deactivate the firewall briefly to achieve the operation (the blocking of Akamai was logged in AIS)
Quote from: Logos on May 03, 2010, 09:25:22 PMAIS firewall: I had trouble installing an adobe air application because apparently the firewall was blocking Akamai...I had to deactivate the firewall briefly to achieve the operation (the blocking of Akamai was logged in AIS)Can you post what was logged?
Oh, and they forgot to translate a line.Greetz, Red.
Quote from: lukor on May 03, 2010, 10:51:48 PMQuote from: Logos on May 03, 2010, 09:25:22 PMAIS firewall: I had trouble installing an adobe air application because apparently the firewall was blocking Akamai...I had to deactivate the firewall briefly to achieve the operation (the blocking of Akamai was logged in AIS)Can you post what was logged?the IP that was blocked then was 92.123.84.25 (remote port 443)
Quote from: Logos on May 03, 2010, 11:19:25 PMQuote from: lukor on May 03, 2010, 10:51:48 PMQuote from: Logos on May 03, 2010, 09:25:22 PMAIS firewall: I had trouble installing an adobe air application because apparently the firewall was blocking Akamai...I had to deactivate the firewall briefly to achieve the operation (the blocking of Akamai was logged in AIS)Can you post what was logged?the IP that was blocked then was 92.123.84.25 (remote port 443)application column empty? local port empty? local address empty?edit: Logos, I am afraid I can not help you from the description you have given. Avast by default definitely does not block akamai IP range. So if there is a problem there might be some bug which depends on your configuration - by which I mean config.xml and rules.xml files. Also, the more details about the log you specify, the more possible it is that we will guess which component is giving you the trouble.
Yeah, I agree with Logos. The firewall log bug is very irritating Greetz, Red.
Rednose, Logos, sorry to admit, but I am still not able to find the cause for it. I would like to acknowledge and fix it, but don't know why it is happening.L.