Open Dental Server and Office Network Support in NYC

Open Dental Software owns the program. Someone else has to own the Windows server it lives on, the MySQL service under it, the shared image folder, the switch in the closet, the twelve workstations and the backup nobody has tested. In New York City that second company is usually the one that also ran the cabling when the office was built, and it is rarely the one answering the phone at 7:40 in the morning when the front desk cannot open a chart. ClearMax Labs takes the second job, remotely, for practices across the five boroughs and the commuter counties around them.

Last updated: October 2026

How is this different from calling the vendor?

The vendor's support plan covers the program: how a feature works, a database that will not convert, an eService that stopped. It does not cover the server's failing disk, the firewall rule that blocks the database port, the antivirus that quarantines the data folder, or the workstation that fell off the domain. The manual says so in plain words for Windows updates: they are "outside of the scope of Open Dental support" and belong to "your IT Professional".

The vendor's support plan also has a floor under it: the practice has to be current on the subscription, and the first thing a vendor technician will ask is whether the server and network have been ruled out. So when a practice calls here, the first question is not "what version are you on". It is "is the server answering". Everything the program needs is checked in the order it fails: power, the MySQL service, the data share, the network path from the operatory to the server, the version on each machine. Only when all of that is proven healthy does the problem get handed to the vendor, with the evidence attached, under the practice's own support subscription.

What does a New York practice run into?

Four problems come up more here than in a one-floor suburban office, and each has its own page on this site.

Charts needed from somewhere else

A second location across the river, a dentist reviewing a case from home in Westchester, a hygienist covering two offices in a week. The program supports remote desktop, a replicated or Middle Tier setup for multi-location groups, and the mobile eServices, and each one asks something different of the server. The remote access page walks through which one fits and what breaks it.

The cloud question

Every lease renewal and every dead server raises it: move to the vendor's hosted cloud, or buy another box for the closet. The answer for a Manhattan office with one building internet circuit is not the answer for a group with its own fiber. The cloud or server page lays out what each choice changes.

The program cannot reach the server

"Unable to connect to any of the specified MySQL hosts" on one chair, or on every chair at 7:40 in the morning. The cause is the server, the service running on it, the firewall or the cable, almost never the program. The not connecting page separates the one-machine case from the whole-office case and lists what is checked in the first ten minutes.

A server that has to be replaced

A lease renewal, a dead disk, or a box that has failed twice. The vendor publishes the migration steps for advanced IT users and requires the same database version on both machines. The server migration page covers that rule, the copy, the shutdown of the old machine, and what New York expects to happen to its drives.

Why does the location change the advice?

Three New York rules sit underneath every one of those pages, and they change what the right fix is.

• New York's breach law requires notice to affected residents within thirty days of discovering a breach. That is the clock an incident plan runs on. A practice that needs a week to work out whether the backup is readable has already spent a quarter of it.
• The same law counts medical information, meaning any information about a person's medical history, as private information when it sits beside a name. A take-home drive with a copy of the database on it is a reportable loss if it goes missing, so remote access has to be designed around that, not around convenience.
• New York requires prescriptions to be issued electronically, with a documented exception for temporary technological or electrical failure. When the server or the internet is down, every prescription written that afternoon becomes an exception the prescriber has to note. Uptime is a prescribing matter here, not only a scheduling one.

Records must also be kept for at least six years, and a minor's record until a year after the patient turns 21, which is longer than most servers live. The backup plan has to outlast the hardware it runs on.

What does a New York City building change?

Most of this site's readers work in a multi-tenant building, not a standalone office with its own parking lot. That shapes the advice. The internet circuit is often whatever the landlord's riser carries, with no second carrier and a public address that changes when the building switches providers. The server sits in a closet the practice shares with the HVAC panel, on a circuit nobody labelled, and a replacement server has to come up in a freight elevator on a day the building allows it. The imaging room may sit on a different floor from the front desk, with a cable run nobody has a drawing of.

None of that can be fixed from a laptop, and this service does not pretend it can. What it does is design around it: two internet paths where one is all the building offers, a server that tolerates a dirty power circuit, remote access that does not depend on the building's public address, and a written record of what is where, so the next person to open the closet door does not start from zero.

What a first call looks like

1. You call (332) 241-0622 or send the form. If the practice cannot work, call.
2. Five questions: one computer or all of them, is the server lit, what changed today, which version, and whether the vendor subscription is current.
3. A remote session to the server and the affected workstations. The plumbing is proven first.
4. If the fault is inside the program, the vendor ticket is opened with the evidence attached, and ClearMax Labs stays on it until it is closed.
5. A short written note of what was found and changed, for the practice's file.

Nothing is quoted by phone before the server has been seen; a practice with two locations and one with six operatories on one floor are not the same job, and a number given blind is a number that gets corrected later. Scoped and quoted after a free assessment. The about page says who does the work and what is left to the vendor.