Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 22 replies
  • Subscribers 1 subscriber
  • Views 8598 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Broken filtering antivirus scanning?

watnemoe1@comcast.net
I keep a tight firewall, using dual scan engine for web filtering. However this morning when I went to download applications, the proxy no longer intercepted the download and did a virus scan. Is this just me or has anyone else seen this problem today?


This thread was automatically locked due to age.
Parents
  • 0
    first of all Astaro can only use 4 gigs max(really about 3.5 with the 32 bit wraparound effects).  So I would remove 4 gigs until v8 officially comes out.  Secondly 500 megs is a bit excessive..I would go down to anything below 100 megs(with 25 being a good average).  Also head to my it's time to solve the http proxy thread and state exactly how you ahve dns in the Astaro and how you have dns on your server.  Need to know the chain(read my initial post for an example).  also since apges are timing out try doing a trace to cff1.astaro.com and see if it resolves..if it doesn you'll get pings back.  That'll let us know it isn't dns perse.

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

  • 0 in reply to William Warren
    It resolved out to the IP, but during the trace it sits on one of the Open DNS servers ([208.69.36.132]) and never makes a connection to astaro. (I use Open DNS versus the unreliable Comcast DNS servers).

    I did a search for your original post but I couldn't find it.

    Yes, I do realize the box is a tad excessive, but I knew I was going to tax the box harder than normal [:)]
  • 0 in reply to watnemoe1@comcast.net
    Ok, I also switched to the Comcast DNS servers, then did a nslookup on that FQDN and I now get that it can't resolve (both on the FW and client after a flush DNS resolver on both client and firewall).
  • 0 in reply to watnemoe1@comcast.net
    Ok, I also switched to the Comcast DNS servers, then did a nslookup on that FQDN and I now get that it can't resolve (both on the FW and client after a flush DNS resolver on both client and firewall).


    checkout my linked thread for something i am trying

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

Reply
  • 0 in reply to watnemoe1@comcast.net
    Ok, I also switched to the Comcast DNS servers, then did a nslookup on that FQDN and I now get that it can't resolve (both on the FW and client after a flush DNS resolver on both client and firewall).


    checkout my linked thread for something i am trying

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

Children