Jump to content

Recommended Posts

Posted

Hi,

 

I'm wondering if anyone could shed any light on this problem we are having. We have a smoothwall filter that has an upstream to our LA internet connection. The LA internet connection is very fast if we go straight through to them, however when we put anyone/anything through smoothwall it is at snail pace. I have checked smoothwall and it doesn't appear to be getting hammered or anything but I just haven't got a clue why it is so slow.

 

Any help on things to check, suggestions etc will be greatly appreciated.

 

Thanks

Adam.

Posted
It varies more commonly there is a 10/15s delay before the page loads all at once. Usually once it has loaded it is a little quicker but not by much.
Posted
Ours seems to be really struggling lately. I've logged a job with Smoothwall but no response yet...... off to moan about the lack of response now!
Posted (edited)
It varies more commonly there is a 10/15s delay before the page loads all at once. Usually once it has loaded it is a little quicker but not by much.

 

It may be a misconfiguration in your DNS then - either on your Smoothwall (Network > Interfaces > Interfaces, I think) or your DNS forwarders on your internal DNS - I had that latter (from switching ISP and forgetting to update the DNS) and it resulted in that pause-then-load behaviour.

 

If it's intermittently just slow, it may be the times it's chugging through the database - the load on the Dashboard should reflect that, though, and there'll be some huge number under Logs & Reports > Database Backup

Edited by sonofsanta
  • Thanks 1
Posted

what Anti virus? also are you seeing the same issues in IE and firefox?

 

we had an issue with sophos safe filtering+IE. it seemed that sophos safe sites filter was failing to contact sophos and would eventually time out and the page would load fine after 10 seconds.

Posted

Hi,

 

Thanks for your responses. It was in fact DNS records pointing to old servers, while the IP addresses were correct the configured host names had changed. Also the MTU on the internal interface was set incorrectly. This has now been resolved.

 

Thanks

Adam.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...