Outpost Mapquest Problem

Discussion in 'other firewalls' started by blazr63, Oct 4, 2006.

Thread Status:
Not open for further replies.
  1. blazr63

    blazr63 Lurker

    Joined:
    Oct 9, 2005
    Posts:
    58
    Location:
    Danvers, MA
    Recently I noticed after installing Outpost 4.0 mapquest.com didn't work properly, only in IE. It works fine in Opera. When clicking on the Get Directions button the browser would hang. I disabled the IE Quick Tune option and added mapquest to the DNS exceptions list, but still no luck.

    Since 4.0 was consuming huge amounts of ram, I removed it and installed 3.5. My system runs better now but still having the problem with mapquest. Not a huge deal since there's plently of other map sites, but I'm curious why this is happening and other browsers aren't effected. I know Outpost is causing the problem because if I close it out, mapquest works fine. I did not have this problem with the 2.7 version.
     
  2. Paranoid2000

    Paranoid2000 Registered Member

    Joined:
    May 2, 2004
    Posts:
    2,839
    Location:
    North West, United Kingdom
    If Outpost is blocking anything, then it will be logged. Therefore checking the logs (Blocked, Attack Detection, Alerts Tracker plus Active Content for web page issues) is the best way to find out the underlying cause. If you still need assistance, please post copies of any related log entries.
     
  3. blazr63

    blazr63 Lurker

    Joined:
    Oct 9, 2005
    Posts:
    58
    Location:
    Danvers, MA
    Here's the log from attempting to visit mapquest:

    8:36:56 PM n/a IN REFUSED UDP 222.35.53.101 9100 Packet to closed port
    8:36:47 PM n/a IN REFUSED UDP 208.122.68.237 45604 Packet to closed port
    8:36:47 PM n/a IN REFUSED UDP 208.122.68.237 45604 Packet to closed port
    8:36:47 PM n/a IN REFUSED UDP 208.122.68.237 45604 Block incoming UDP activity
    8:36:47 PM n/a IN REFUSED UDP 208.122.68.237 45604 Packet to closed port
    8:36:47 PM n/a IN REFUSED UDP 208.122.68.237 45604 Packet to closed port
    8:36:45 PM n/a OUT REFUSED UDP 68.2.16.25 DNS DNS cache used instead
     
  4. Paranoid2000

    Paranoid2000 Registered Member

    Joined:
    May 2, 2004
    Posts:
    2,839
    Location:
    North West, United Kingdom
    I doubt that the connection attempts from 208.122.68.237 are related to Mapquest. How about the Active Content log?
     
  5. blazr63

    blazr63 Lurker

    Joined:
    Oct 9, 2005
    Posts:
    58
    Location:
    Danvers, MA
    Through random experimentation I figured out the problem. If I deselect Block Private Data Transfer from the Anti-Spyware plugin, then mapquest works perfectly. It doesn't make a lot of sense to me, but apparently it was preventing something on mapquest.com from loading.
     
  6. Paranoid2000

    Paranoid2000 Registered Member

    Joined:
    May 2, 2004
    Posts:
    2,839
    Location:
    North West, United Kingdom
    If you had entered anything in the Private Data Transfer section, then yes it will block any network traffic matching those entries (and can result in a lot of false positives if you entered a short item). However any such block should trigger both a visible alert plus a log entry in the Alerts Tracker section.
     
Loading...
Thread Status:
Not open for further replies.