A first or rebuilt Open Dental server is set up in four parts: the program and its database engine from the vendor's installer, port 3306 opened on the server's own firewall, the shared OpenDentImages folder, and the data paths every computer will use. The vendor's network guidance opens with a recommendation to work with a networking professional for the network and computers. That part is done remotely here.
Last updated: November 2026
What has to be on the server?
- .NET. The program needs Microsoft .NET, which most current Windows versions already include.
- The database engine. MySQL or MariaDB, installed by the vendor's installer on the server only. Workstations never get it.
- A firewall exception for port 3306 on the server, so workstations can reach the database. On the server, not on the router: the vendor is explicit that the database port must never be opened to the internet.
- The shared image folder. OpenDentImages, shared on the network so every computer can read and write it.
How is the image folder shared?
The vendor's steps for a Windows share are short: on the server, open the OpenDentImages folder's properties, share it with Everyone at read and write, and give Everyone full control on the Security tab as well. The network path then reads \\SERVER\OpenDentImages. The vendor's own steps share it with Everyone. In practice that is narrowed to the office's own accounts once the share works, because everyone on the network includes any device that joins it.
Then, inside the program, Setup, Data Paths points the program at that share. The vendor's instruction is to verify every path before pointing other computers at the server. A path that only works on the server is the most common reason a new workstation shows charts but no images.
Should the database have a password?
The installer asks for a MySQL user name and password and warns if it is left blank. The vendor recommends setting one, while noting it is a second layer behind the network and server protection, not a replacement for them. Massachusetts expects passwords that are not vendor-supplied defaults and access limited to active users, so the database password, the Windows administrator password and the server's sign-in are all set, unique and recorded in a safe place on the first day.
One more instruction from the vendor deserves a line in the practice's records: do not give database credentials to third-party vendors. Read-only access is generally safe; full control is dangerous and goes around the program's own user security. The state's rule is that any outside provider handling the data is chosen for its security and held to it by contract, and a breach that exposes Social Security numbers can oblige the business to offer at least 18 months of free credit monitoring to each affected resident. A full-control login handed to an integration is how that happens.
What gets checked before the office uses it?
- A workstation connects with the server name or IP address, the database and the MySQL login.
- An image saved on one workstation opens on another.
- The first backup runs and a test restore opens on a separate machine.
- The server is set never to sleep, and Windows updates reboot it after hours.
The hardware itself is covered on the server requirements page, and the choice between keeping a server and moving to the cloud on the server or cloud page.
Questions practices ask
Can the vendor install the server for us?
The vendor provides the installer and supports the program. The network, the share permissions and the firewall are the practice's IT side.
How long does a rebuild take?
It depends on the size of the image folder and the backup. It is planned for an evening or a weekend, never a clinic morning.
