Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 32 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 34220 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

Slow access to webpages.

riegens
Hi ,

We recently changed our ASG220 with 2xASG320 in HA (Master->Slave)
We setup the ASG320 with a backup configuration of ASG220, and everything beside accessing some webpages works perfectly.

The webpages involved are really really slow to access, around 10 min pr page.
The log doesnt indicate any problems at all.

I have found out that if i put specific hosts/groups under Web Security -> Web filtering -> Advanced -> Transparent mode skiplist it works perfectly, but this is not a solution im happy with because it the skips the security.

Have you had any similar problems or do you have a solution for this?


This thread was automatically locked due to age.
Parents
  • 0

    Dear All,

    maybe i am facing the similar problem right now, our Customers office can't connect to dropbox.com;yahoo.com and some websites (such as TRAVELS sites) normally. The device is ASG320 and current firmware is 9.403.4.

    At first it only happened when the web filtering activated, but now it's happened without web filtering enabled. I have tried to add those sites to transparent skiplist destination, but can't solved that problem.

    I am waiting if someone have a solution for this, 

  • 0 in reply to YeniPramono

    Have you tried flushing the DNS caches in the UTM, internal servers and the workstations?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    today we've found the source problem, this is happened because there is another router behind UTM. This router act as a firewall too and it masquerade all traffic to UTM.

    I guess that cause UTM to detect strange behaviour from a single IP address (that is router's IP address).

    Thank you All ;)

Reply
  • 0 in reply to BAlfson

    today we've found the source problem, this is happened because there is another router behind UTM. This router act as a firewall too and it masquerade all traffic to UTM.

    I guess that cause UTM to detect strange behaviour from a single IP address (that is router's IP address).

    Thank you All ;)

Children
No Data
Unfiltered HTML