Fastest fix
From a working front-desk PC, confirm Dolphin still opens. On the failing PC, ping the Dolphin server by name and by IP. If ping fails, fix network/DNS first. If ping works, reopen Dolphin and verify the server/host field still points at that same name — Windows updates and profile rebuilds often blank or revert it.
Causes (most common first)
1 · Most common
Wrong or blank server name on the client
Check: On the Dolphin login/connection screen, confirm Server / Host matches a known-good workstation. Typical on-prem setups use a short hostname or FQDN — not “localhost” on a clinical PC.
Healthy: Same server value as working PCs; connection succeeds within a few seconds.
If not: Enter the correct host, save if prompted, relaunch. If the field won’t stick, launch Dolphin “as Administrator” once to write the setting, then test as the normal user.
2
DNS / name resolution after network change
Check: Command Prompt: ping DOLPHINSERVER then ping 192.168.x.x (your server IP). If IP works and name fails, DNS or hosts file is wrong. ipconfig /all — confirm DNS servers are the practice DCs/router you expect, not a random public DNS that can’t resolve internal names.
Healthy: Hostname resolves to the correct LAN IP; ping replies (if ICMP allowed).
If not: Set DNS back to internal servers, or add a temporary hosts entry only as a bridge while DNS is fixed properly. Flush DNS: ipconfig /flushdns.
3
SQL Server or Dolphin services stopped on the host
Check: On the server, open services.msc. Confirm SQL Server (instance name varies — often MSSQLSERVER or SQLEXPRESS) is Running. Start related Dolphin services if your install lists them. Check Event Viewer → Application for SQL startup errors (disk full is common).
Healthy: SQL Running; clients authenticate; recent patient records open.
If not: Start SQL; if it stops again immediately, free disk space on the data volume and check the SQL error log before restarting in a loop.
4
Firewall / SMB blocked after a security tool update
Check: From the client, Test-NetConnection or telnet to the SQL port your site uses (often 1433 for default instances — confirm with IT; named instances may differ). Confirm Windows Firewall on the server still allows the Dolphin/SQL rules on the Domain profile.
Healthy: Port reachable; Explorer can open the image share if Imaging uses one.
If not: Re-enable the documented firewall rules. Don’t turn the whole firewall off permanently to “make Dolphin work.”
If stations lose Dolphin after every network tweak, it’s usually DNS, SQL lifecycle, or firewall rules — that’s the kind of thing we set up properly for orthodontic practices. Free 15-minute look at it: 615.821.0000.