Open Dental Server and Office Network Help, Westerville

Every Open Dental office with more than one computer depends on one machine: the server that holds the database and the shared image folder. When it stops, so does the schedule. ClearMax Labs looks after that server and everything around it, the office network, the workstations and the backups, remotely, for dental practices in Westerville. The program itself stays with its vendor, and when the fault is theirs the ticket goes to them with the evidence already gathered.

Last updated: November 2026

What does the Open Dental server actually do?

It runs the MySQL or MariaDB database every workstation reads and writes, and it shares the OpenDentImages folder where radiographs and scanned documents live. Each workstation runs the program, but the data lives on that one machine. The vendor recommends a dedicated server to protect data, and keeping its name under 15 characters because of a Windows limit.

That makes the server the single point every problem on this site traces back to. Four of them come up often enough to have their own page.

Which server problems bring Westerville offices here?

The server is down

Every computer shows the same error at once, or the program will not open anywhere. The server down page covers the first ten minutes: what to look at on the server, what not to touch, and when a frozen screen is something worse than a crash.

One computer cannot connect

The server is fine and the front desk is working, but one operatory gets "Unable to connect to any of the specified MySQL hosts". The not connecting page works through the firewall, the network path and the connection settings, in the order they usually fail.

Time for a new server

The old box is slow, out of warranty, or still on an operating system the vendor no longer supports. The new server page lays out the plan: matching the database version, shutting the old machine down so nothing writes to it, and what happens to its drives afterwards.

Backups nobody has tested

The vendor's built-in backup tool exists, and so does a monthly reminder that most offices click past. The database backup page covers what a working backup actually needs: a copy that leaves the building, encryption, and a restore that has been tried.

What is different about running it in Westerville?

Two things about the town itself shape the advice.

Which state rules apply to the server?

Two parts of state law change how the work is done.

The state's breach-notice statute, Revised Code 1349.19, explicitly does not apply to an entity that is a covered entity under the federal health-privacy rules, which most dental practices are. A practice's incident plan follows the federal breach rule. Writing it around the state's 45-day clock means writing it around the wrong rule.

The state's Data Protection Act, Revised Code 1354.02, gives an affirmative defense in breach lawsuits to a business that keeps and follows a written cybersecurity program reasonably conforming to a recognized framework. So every change made here comes with a short written note: what was changed on the server, the firewall or the backup, when, and why. Over a year those notes become most of the program.

What does a typical Westerville office run on?

The vendor's own guidance treats ten computers or fewer as a small office, where one workstation is usually designated as the server and, if possible, used only for that. Larger offices typically move to a Windows Server operating system with a domain. Either way the shape is the same: one database, one shared folder, a network carrying both to every room, and a backup that has to work on the worst day of the year.

That shape is why the same few failures repeat across offices. A server doing double duty as the front-desk computer freezes the whole office when the front desk freezes. A workstation that drifted onto Wi-Fi drops connections in one operatory. An update that restarts the server at ten in the morning takes everyone down at once. None of those are program faults, and none of them need the vendor; they need the computer underneath looked after on purpose.

Where does the vendor stop and IT start?

The vendor's support plan covers the program: features, errors the program raises, upgrades and eServices. Its own manual sends Windows updates to "your IT Professional" and says MySQL security setup is the responsibility of the practice or its IT. The server hardware, the operating system, the network, antivirus exclusions, backups and restore tests sit on the IT side.

When a problem turns out to be inside the program, the vendor ticket is opened under the practice's own support plan, with the server and network already ruled out. That is usually the difference between a short ticket and a long afternoon. It also means the practice hears one plain explanation of what broke, instead of two companies each pointing at the other.

How does the first call go?

  1. You call (614) 818-5003 or send the form. If the office cannot see patients, call.
  2. A few questions: is it every computer or one, is the server lit, what changed since yesterday, and is the vendor plan current.
  3. A remote session to the server and the computer that is failing.
  4. The fault is fixed, or handed to the vendor with the evidence attached and followed until it closes.
  5. A short written note for the practice's records.

Nothing is quoted by phone before the server has been seen. Scoped and quoted after a free assessment. The about page says who does the work.

Call (614) 818-5003