The Situation
The Whole Building Went Dark
The call came in from a Utah charter school that had been referred by another BoTecha client. Their situation was straightforward and serious: the entire building had lost network connectivity. Internet was down, the VoIP phone system had gone silent, and every piece of teaching software that depended on the network had stopped working mid-day. Staff could not communicate. Classrooms were disrupted. And nobody on-site knew why.
The school did not have a managed IT relationship in place. They were running on a volunteer-supported setup with aging infrastructure that had never been formally reviewed. When something this significant failed, there was no one to call, until another school pointed them to BoTecha.
"None of our volunteers were available to work on the problem for several hours. We called BoTecha on another school's recommendation and Bobby arrived an hour later from Salt Lake."
Russell S., Business Manager, Utah Charter School
The Diagnosis
It Was Not the Server. It Was the Firewall.
When Bobby arrived on-site, the first priority was finding the actual cause rather than guessing. Schools that have grown their technology organically over many years often have setups where one failing component can take down everything else and the failure point is not always obvious.
In this case, the culprit was the firewall. The school had been running an open-source firewall installed on a computer that was over ten years old. The hardware had simply failed. No dramatic event, no cyberattack. The machine had reached the end of its useful life and stopped working. Because all traffic had to pass through it, everything downstream went with it: internet, phones, and every cloud-based teaching platform the staff relied on.
Why this happens more than you might expect
Open-source firewalls like pfSense and OPNsense are excellent, cost-effective solutions for schools and small businesses. The software is not the problem. The problem is running them on aging consumer or office hardware with no monitoring and no replacement plan. When that hardware fails, and it will eventually, everything connected to the network fails with it.
The Fix
No New Hardware Order Required. Just a Smarter Use of What Was Already There.
Rather than ordering replacement hardware and asking the school to wait days for delivery, BoTecha looked at what was already on-site. The school had a newer PC that was not being used for anything critical. That machine became the new firewall host.
An updated version of the open-source firewall was installed on the newer hardware. From there, all of the firewall rules were rebuilt from scratch: VoIP phone traffic, teaching software, classroom devices, administrative systems. Every rule was configured and tested before anything was handed back.
Within an hour of arriving, the network was fully restored. Phones were ringing. Teaching software was loading. Staff could get back to work.
First call
School reaches out on a referral
Referred by another BoTecha charter school client. Total network failure: no internet, no VoIP phones, no teaching software.
Bobby arrives on-site
Root cause identified within minutes
10-year-old PC running open-source firewall had failed. All traffic was routed through it. When it died, everything died with it.
Same visit
Replacement hardware located on-site
A newer, unused PC at the school was identified as a suitable replacement host. No need to order parts or wait for delivery.
Within the hour
Updated firewall installed and fully configured
Open-source firewall installed on the replacement machine. All rules configured: VoIP phones, teaching software, administrative traffic, classroom devices.
Under 1 hour after arrival
Full network restoration
Internet restored. Phones operational. Every piece of teaching software back online. Staff back to work the same day.
Following weeks
Infrastructure review and improvements
BoTecha reviewed the full environment. Security software updated, backup systems established, network infrastructure documented and stabilized.
15+ years later
Still a BoTecha client today
What started as a cold referral on a bad day became one of the longest client relationships in BoTecha's history.
What Changed After
From Reactive to Reliable
The firewall fix got the school back online, but it also revealed a broader picture: this was a technology environment that had never been properly set up, just extended over time by people doing their best without formal IT support. BoTecha stayed involved after the emergency to address the underlying issues.
Modern firewall on reliable hardware
The aging, single-point-of-failure setup was replaced with an updated open-source firewall running on hardware that actually had life left in it. Properly configured, documented, and monitored going forward.
Security software updated and standardized
Virus and spyware protection was brought current across devices. Monitoring put in place to catch threats before they become incidents.
Backup systems established and tested
Regular, verified backups put on a consistent schedule. Data protected and recoverable in the event of hardware failure or attack.
All improvements at a fraction of expected cost
BoTecha worked within the school's budget constraints. Using hardware already on-site for the firewall replacement alone saved hundreds of dollars on day one.
"Our virus and spyware protection has gotten better. Our data is more secure and we now have regular backups. All this has been accomplished for a fraction of the cost of what we thought it would. BoTecha is mindful of budgets and constraints and has been instrumental in getting whatever we need for the best value."
Russell S., Business Manager, Utah Charter School
Why It Worked
Fast Diagnosis. Creative Problem-Solving. No Unnecessary Spending.
Three things made this work. The first was getting to the actual problem quickly. A lot of IT support time gets wasted chasing symptoms rebooting things, replacing things that are not broken, calling vendors. Getting to "the firewall hardware is dead" in minutes, without a lengthy diagnostic process, meant the school lost less time and the fix could start immediately.
The second was using what was already available. Telling a school to wait three days for replacement hardware to arrive, or to buy a $400 firewall appliance, when a suitable machine was already sitting in a storage room. That is called problem-solving. It is just the easier path for the technician. BoTecha looked at the actual situation and worked with what was there.
The third was staying past the fix. The firewall failure was a symptom of a broader problem: no one was watching this infrastructure. BoTecha did not treat the emergency call as a closed ticket. It became the start of a conversation about what the school actually needed going forward. That conversation has now been going on for over 15 years.
"We are very pleased with our relationship with BoTecha and look forward to a long and mutually beneficial association."
Russell S., Business Manager, Utah Charter School
Takeaway
What This Means If Your School Is in a Similar Situation
Most Utah charter schools are running technology that was set up incrementally over years, maintained by volunteers or part-time staff, and never formally reviewed. That works until a single point of failure, a failed switch, an expired certificate.
The specific problem here was a firewall running on decade-old hardware. But the underlying issue is common: no monitoring, no documentation, no replacement plan, and no one whose job it is to catch these things before they become crises.
BoTecha works with charter schools and education organizations across Utah. If your school is relying on aging infrastructure and hoping it holds, a free IT review is the right first step. It costs nothing, takes about 30 minutes, and gives you a clear picture of where your biggest risks are before something fails.