Dental Software and Imaging Support in Los Angeles: Troubleshooting Dentrix, Eaglesoft, Open Dental & Sensors

It is 10:15 on a Tuesday in a Long Beach practice. The hygienist in operatory three places the sensor, the capture window shows green, the exposure fires, and nothing lands in the patient's chart. Operatories one and two are capturing normally. The office manager calls the imaging company and hears a queue message: call back later or leave a number.

Think of this guide as the practical companion to dental IT support in Los Angeles. It is written for the office manager, with the owner copied, in a two-to-six-operatory practice in Long Beach, Glendale, Burbank, Beverly Hills, Culver City, Sherman Oaks or Irvine, because good dental software and imaging support in Los Angeles starts with the person who sees the problem first. It covers how to tell the layers apart, the safe checks the front desk can make, when each vendor's line is open on a Pacific clock, why software slows as a practice grows, and what to write down before calling anyone. For the wider planning picture, from power and earthquakes to choosing a provider, start with the guide to dental IT in Los Angeles. Nothing here ranks one software product over another.

When software or imaging stops in a Los Angeles dental office, how do you find the layer that failed?

Start with two questions: is the problem in one room or in all of them, and what has changed since it last worked? One room points to that room's computer, cable, sensor driver or USB port. Every room at once points to something shared: the server, the network switch, the internet line, an overnight update or the vendor's cloud service.

Think of the office as a stack. At the base sit the connection from your carrier and the office network: wall cabling, the switch, Wi-Fi and the firewall. The server, or the vendor's cloud if your practice software is hosted, holds the database and usually the image store. Every operatory computer carries Windows, the drivers for its sensor or intraoral camera, your practice management program (the PMS) and the imaging application. A small connector, usually called the imaging bridge, passes the current patient from the PMS to the imaging application and files each finished image under that patient.

In the Long Beach morning above, two rooms are capturing and one is not, and the capture window shows green. That rules out the internet line, the server and the sensor's basic connection for now. The likeliest layers are the bridge on that one workstation, a patient mismatch between the PMS and the imaging window, or a storage path on that machine. Table 1 is built to make that kind of call in two minutes.

Table 1: Layer by layer, from the front desk's side

Two habits come out of that table. First, the count of rooms is the fastest test there is, so ask it before anything else. Second, "who usually owns the fix" is a typical split, not a rule: your contracts decide it. Legend's national article on dental software support vs IT support explains that boundary in general terms, and the deeper guide to dental imaging integration troubleshooting goes further into bridges and capture settings.

What usually breaks imaging in a Los Angeles office, and what can the front desk check first?

Imaging stops tend to trace back to one of four places: the sensor's USB connection and driver, a Windows or program update, the bridge settings that link imaging to the PMS, and the server folder that stores images. The front desk can safely reseat a sensor, restart a PC and reopen a chart. Anything more belongs to your IT provider.

1. The USB connection and driver. An intraoral sensor is a USB device, and Windows only recognises it through the maker's driver. An update to Windows can swap that driver out, and a power-saving setting can turn a USB port off, which looks exactly like a failed sensor. A loose port at the back of a tower, a hub under the counter or an extension cable added during a remodel can do the same.

2. Updates. A PMS update can expect a newer bridge than the imaging program has, and an imaging update can expect a newer Windows build. When updates land unevenly across rooms, some operatories capture and some do not. That is why the room count in Table 1 matters.

3. Bridge settings and paths. The bridge stores settings such as where the imaging program is installed and where images are saved. A new workstation, a renamed server or a reinstalled program can leave one room pointing at an old location.

4. The server share. Images are usually saved to a folder on the office server. If that share is full, offline or no longer mapped on one PC, capture can appear to succeed while the image goes nowhere useful.

Safe for the front desk:

• • Move the sensor's plug to another USB socket on that computer, skipping any hub.
• • Restart the workstation with the sensor unplugged, then reconnect it.
• • Close imaging, reselect the patient in the PMS, and open imaging from inside the chart.
• • Try the same sensor in a room that is capturing, if your clinical team agrees it is safe to move it.
• • Note the exact wording of any message and take a photo of the screen.

Stop and call instead:

• • Uninstalling or reinstalling drivers, imaging software or the PMS.
• • Changing bridge settings, storage paths or drive letters.
• • Running a database "repair" option.
• • Restarting the server during clinic hours.

Trial-and-error reinstalls can turn a ten-minute fix into an afternoon. If you run DEXIS, Legend has a page on DEXIS IT support; Dolphin, Vatech, Carestream and Planmeca/Romexis each have their own page on the Legend site too. Offices that also run intraoral scanners or 3D imaging face the same four layers, with larger files at the storage step.

When does your software vendor's support close in Pacific time?

On the pages we opened on October 26, 2026, most imaging lines publish Eastern hours, so they close between 3:00 and 5:00 p.m. on a Los Angeles clock. Open Dental and Dolphin Imaging publish Pacific hours. Dentrix lists Mountain hours. Write your vendors' hours in Pacific time and keep the list at the front desk.

California and the Eastern states move their clocks on the same weekends, so an Eastern-time line runs three hours ahead of Los Angeles in every season. Per NIST's daylight saving time page, U.S. clocks spring forward at 2 a.m. on March's second Sunday and fall back at 2 a.m. on November's first Sunday; this autumn that is November 1, 2026.

We took every row below from that vendor's own support or contact page on October 26, 2026. Where the page names no days, the table says so. Where we could not open a page with published hours, the row says that rather than guessing. Hours change, so treat this as a starting list and confirm the line your contract names.

Table 2: Published vendor support hours, converted to Pacific time

What the table means for an office that sees patients until 6:00 p.m. in Culver City or Sherman Oaks: an imaging fault that shows up at 3:30 p.m. may already be past a DEXIS line's published hours and close to the end of Carestream's. Morning faults are easier, because most of these lines open at 5:00 or 6:00 a.m. Pacific, well before a 7:00 a.m. first patient.

Do this once, this week:

1. 1. List every vendor you call: practice software, imaging, phones, e-claims, the card terminal and any lab portal.
2. 1. Open each vendor's support page and write its hours in Pacific time, with the date you checked.
3. 1. Note which lines publish weekend hours and which do not.
4. 1. Keep a printed copy by the front-desk phone and a digital copy in the practice's shared folder.
5. 1. Add both clock-change Sundays to the office calendar, with a reminder to recheck any row not published in Pacific or Eastern time.

Your own IT layer does not have to follow vendor hours. Legend Networking is headquartered in Dallas, two hours ahead of Los Angeles all year, and its helpdesk is staffed 24/7 at 1-800-794-1588, alongside 24/7 monitoring. Its published delivery wording is: "Onsite dispatch by appointment across served dental markets; remote-first nationwide." Day-to-day software and support issues are handled remotely; cabling, installations, equipment moves and new-office build-outs are scheduled onsite by appointment. A fault inside the vendor's program still needs that vendor's line and hours. Before that line opens, an IT provider can clear the workstation, network and server as suspects, so the vendor call starts with the right facts.

If the table shows your office depending on lines that close mid-afternoon, a Free Dental IT Assessment is one way to have your setup looked at before the next stop.

What should the front desk write down before calling about software or imaging?

Write down where it happened, exactly what the screen said, when it last worked, what changed, how many rooms or users it affects and which patients were scheduled in that room. A screenshot and a PC name save the most time. Keep patient names, birth dates and images out of email.

The log below is designed to be printed or copied into a shared note and filled in by whoever is nearest the problem. Twelve short lines take a few minutes, and they answer the questions every support line asks first.

The ticket-ready symptom log

Line 9 decides most cases. Line 8 is the one people skip, and it is often the answer. Line 10 matters for the owner's day as much as for the technician: it turns "imaging was down" into a clear cost in rescheduled patients.

Legend publishes a national dental IT support ticket checklist with a template the front desk can copy; this log is the software-and-imaging version of the same habit.

Why does practice software slow down as a Los Angeles practice grows?

Growth adds load to parts of the office that were sized for a smaller practice. More operatories mean more users in the database, more images saved and opened, and more devices on the same switch and Wi-Fi. An older server, wireless workstations and hosted software sharing the office internet line are the usual places the slowdown appears.

A practice that opens two new operatories in a Glendale suite, or takes over the next unit in a Burbank medical building, rarely changes the server on the same day. The server that ran four rooms comfortably now handles six, along with a backup job that has grown with the image store. The symptoms creep in: the schedule takes longer to load at 8:00 a.m., charts hesitate when a hygienist opens a full-mouth series, and the end-of-day backup now runs into the morning.

Where the slowdown usually comes from, and how to check it:

Vendors publish minimum and recommended specifications for the server and workstations, and those numbers rise with new versions. Legend's guide to dental software system requirements explains how to compare your hardware against a vendor's current list. For program-specific causes, read why Dentrix is slow and why Open Dental is slow.

A useful note for the owner: slowness has a cost even when nothing is "down." Time lost on every chart adds up over a full hygiene column. Recording the times for a week (line 1 and line 9 of the log above) gives you something firm to discuss with whoever owns the server.

How should imaging, cloud software and backups share the office internet?

Measure what your office actually uses during clinic hours, ask each vendor for its published requirements, keep large uploads and backups away from the hours patients are scheduled, and give hosted clinical software a second internet path that takes over by itself. This guide gives no speed figures, because the right numbers depend on your vendors and your volume.

Three kinds of traffic compete for the same line in many Los Angeles offices:

1. 1. Hosted practice software. If your PMS runs in the vendor's cloud, every chart, schedule change and claim crosses the internet. An outage stops the front desk.
2. 1. Imaging. Images captured locally may also be copied to a cloud archive or shared with a lab or specialist. Large files compete with everything else, especially the upload side of the connection.
3. 1. Backups. Offsite backups copy the database and image store to another location. A backup that starts during the day takes capacity from the first two.

What to do, in order:

• • Measure. Ask your IT provider to show you the office's upload and download use at a busy morning hour and during the nightly backup, so you have your own numbers rather than an estimate.
• • Ask the vendors. Each hosted software and imaging vendor publishes, or will give you, its connection requirements. Keep those answers in writing with your vendor-hours list.
• • Schedule the heavy work. Backups and large uploads belong after the last patient, set in Pacific time, with the morning start checked.
• • Separate clinical traffic. The network can be set so the practice software is not slowed by guest Wi-Fi, streaming in the break room or a large file copy. Ask how your network handles this.
• • Add a second path. A second business connection on a different technology or provider, with automatic failover, keeps a hosted PMS running when the main line fails.

The same questions apply whether the office is a single suite in Santa Monica or a larger practice in Irvine: what runs over the line, when, and what happens if the line stops.

Who should own software and imaging problems for your practice?

That is the owner's decision, and there are three common answers: a staff member who handles it with vendor help, the software vendors alone, or a dental IT company that handles the computers, network and server and works alongside the vendor when the fault crosses layers. Choose by who answers the 3:30 p.m. call.

The third row is where the details matter. Some providers open the vendor ticket and stay on the call; others hand the problem back to the practice once they have ruled out their layer. Neither is wrong, but you should know which you are buying. Whoever you speak with, ask for that answer in writing. Legend's metro page is written for practices comparing a dental IT company in Los Angeles.

The ongoing side, such as tested patching, driver checks after updates and backup verification, belongs in a managed plan rather than in the day something breaks. You will find that side in the guide to managed IT for dental practices in Los Angeles.

About the byline: "Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps." The company behind this guide, Legend Networking, has "Served over 3,500 practices since 2004", and its Google profile shows a "4.8 rating · 173 Google reviews."

What should you check before a practice-software upgrade or migration?

Copy the database and every image, and prove a restore works. Record every path, bridge setting and driver version. Check the vendors' notes that the new versions belong together. Start with a single workstation after hours, and capture a trial X-ray in each operatory before the next day's first patient.

Before

• • [ ] A fresh copy of the practice database and every stored image, plus a trial restore of a handful of charts and X-rays to a separate folder.
• • [ ] Notes, with screenshots, of where images are saved, which drive letters are mapped, how the bridge is configured, and which driver version each room's sensor uses.
• • [ ] The vendors' published compatibility notes: which PMS version works with which imaging version and which Windows build.
• • [ ] Administrator passwords for the PMS, imaging program and server, held by the practice and tested.
• • [ ] A start time once the last patient has left, with hours in hand to undo the change if it fails. Friday evening leaves the weekend to recover; Monday at dawn leaves none.
• • [ ] The vendor's support hours for that window, in Pacific time (Table 2), so you know who can answer if it stalls.

During

• • [ ] The server first, if the vendor's instructions say so, then one workstation.
• • [ ] A test chart opened, a test image captured and filed, and an old image opened on that workstation before the rest are touched.
• • [ ] Old workstations switched off but kept intact, not wiped, until the new setup has run for a full week.

After

• • [ ] A test image from every sensor in every room, filed in a test chart.
• • [ ] A look at the next morning's backup report, to confirm the new setup is included.
• • [ ] The symptom log ready at the front desk for the first week.

A move to a different PMS, or from a server to a hosted product, adds data conversion and a cutover day. Legend's dental software migration checklist covers that longer path.

A practice that is not upgrading but opening, such as a startup in a second-generation suite, sets up imaging in a different order: cabling, network and server first, then each operatory tested before patients are booked. That sequence is in IT for a new dental office in Los Angeles.

Which systems does Legend list for dental software and imaging support in Los Angeles?

Legend Networking publishes two lists. For practice software: Dentrix, Eaglesoft, Open Dental, Archy. For imaging: DEXIS, Vatech, Carestream, Planmeca/Romexis, Dolphin Imaging. Each has its own page on the Legend site. Any other program, including hosted products and other sensor brands, is treated here as a system you may run.

The lists, as published:

• • Practice software (PMS): Dentrix, Eaglesoft, Open Dental, Archy.
• • Imaging: DEXIS, Vatech, Carestream, Planmeca/Romexis, Dolphin Imaging.

The overview of how that work is described sits on Legend's national page for practice management software and imaging support.

If your office runs something not on those lists, such as a hosted PMS like Denticon, Dentrix Ascend or Curve, or a sensor brand not named above, the layers in Table 1 are the same and the questions below still apply. No claim is made in this guide about support for those systems; ask any provider about them by name.

Usually stays with the software or imaging maker, however your IT is arranged:

• • Faults inside the program, database repairs and licensing.
• • Sensor and scanner hardware warranty and repair.
• • Clinical training on the product's features.

Usually handled by the practice's IT provider:

• • Operating system patches, device drivers and updates on every computer and the server.
• • The network: wall cabling, switches, Wi-Fi, the firewall and the carrier handoff.
• • Backups of the database and image store, with test restores.
• • Windows and Microsoft 365 accounts and administrator rights.
• • The links between programs, such as where images are saved and how the bridge is set, whenever something is updated or moved.

What to ask your IT provider about software and imaging

Put these to any provider before signing, and repeat them once a year. Specific answers in writing are the goal.

For a written reference to compare answers against, see Legend's national dental IT support page.

Key takeaways

• • Count the rooms first: one room points to that room's computer, cable or driver; every room points to something shared.
• • Reseat, restart and reopen the chart; leave reinstalls, path changes and database repairs to whoever runs your IT.
• • Several imaging lines publish Eastern hours and close mid-afternoon in Los Angeles; keep a Pacific-time list at the front desk.
• • Growth slows software in predictable places: the server, wireless rooms, a stray switch and the shared internet line.
• • Before any upgrade, back up and test a restore, record paths and bridge settings, and test every room before patients arrive.

Sources

Legend Networking's own facts aside, every vendor hour and time rule above comes from these pages, each opened on October 26, 2026:

• • Open Dental, contact page: support hours, stated in Pacific Time.
• • Dentrix (Henry Schein One), support page: phone and chat hours, labeled MST.
• • DEXIS, US contact page: technical support hours, Eastern Time.
• • Vatech America, support page: phone and email hours, Eastern Time.
• • Carestream Dental, support page: extraoral and intraoral imaging systems line hours, Eastern.
• • Dolphin Imaging, support page: phone, chat and weekly training hours, Pacific Time.
• • Archy, contact page: support through the in-app Help Center; no hours published.
• • NIST, Daylight Saving Time page: the dates U.S. clocks change.

Eaglesoft and Planmeca hours are not shown because we could not open a vendor page that published them.