[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [K12OSN] Experience with a thin client server connection gettingthrottled?

I hated these boxes, but they can do what you want.  How they do it will depend on the version of FortiNet they are using, but in a nutshell, it is controlled by both the packet shaping module and the firewall module. 
You will need to create a firewall policy for your specific machine - if possible, start by copying the existing global policy as a starting point, otherwise, do your best.  With that new policy created, select packet shaping (I think, it might be traffic shaping...) and make adjustments for the bandwidth (measure your bandwidth with the system set to bypass, and then set it to a high multiple of that).
Good luck (you will need it!)

Steven Santos
Director, Simply Circus, Inc.
Email: Steven SimplyCircus com
 Mail: 14 Pierrepont Road
       Newton, MA 02462
Phone: 617-527-0667
  Web: www.SimplyCircus.com
-----Original Message-----
From: k12osn-bounces redhat com [mailto:k12osn-bounces redhat com]On Behalf Of Todd O'Bryan
Sent: Friday, February 08, 2008 7:24 PM
To: Support list for open source software in schools.
Subject: [K12OSN] Experience with a thin client server connection gettingthrottled?

My district has over 90,000 students and I have the only thin client lab. In my lab we're having a big problem with network connectivity as connections get lost pretty often, especially when lots of users are surfing. The network guy came out and saw how bad the connectivity was when we tried to connect to internet sites like Google, Yahoo, and CNN. We then tried surfing within the district and discovered there were no problems. He set us to bypass the filter box, a FortiNet appliance that filters the whole district, and we had no problems on the internet, so it's apparently the filter that's slowing things down. Unfortunately, for obvious reasons, we can't run without a filter. For political reasons too complicated to go into, we also can't set up an alternate filtering system for just my lab.

I suspect that other users don't see this problem because the filter sees an unreasonable amount of traffic coming from what it thinks is a single computer and throttles the connection. (We also have the remnants of a November virus outbreak on the network that is flooding everything with stray packets, so the filter could be busier than it should be. They're still working on cleaning that up.)

Does anyone have experience with this kind of thing, with either FortiNet or another filter appliance, where thin client labs see a performance degradation compared to single-user systems? If so, did you have any luck solving it?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]