Remote vs Onsite Dental IT Support: What Can Be Fixed Remotely, What Needs a Technician, and How to Tell

The sensor in operatory three stopped capturing mid-appointment, the front desk printer is offline again, and the IT company says it will "remote in." You are left wondering whether someone on a screen can really fix this, or whether you are about to lose the afternoon waiting for a technician who has to drive over.

Alongside our page on remote and onsite IT support for dental practices, which describes how Legend Networking delivers support, this guide sorts 32 real dental office problems into remote, onsite or both, says what your team can safely do while waiting, and shows how secure remote access should work when patient data is on the screen. It is written for the practice owner who has a problem today and wants to know which kind of help to ask for. The security sections draw on the June 2023 Guide to Securing Remote Access Software from CISA, the NSA, the FBI, MS-ISAC and Israel's National Cyber Directorate, and on the HIPAA Security Rule's technical safeguards, all read on 22 October 2026.

What is the difference between remote and onsite dental IT support?

Remote support means an engineer works on your computers, servers and network over a secure connection without coming to the office. Onsite support means a technician is physically in the practice. Most problems start remotely, because diagnosis is faster that way, and move onsite only when something physical has to be touched, replaced or installed.

A few terms come up again and again. Each has a one-line meaning:

• • Remote session: a live connection in which an engineer sees and controls a workstation or server, usually after a member of staff approves it.
• • RMM agent: remote monitoring and management software installed on each computer so the IT provider can watch its health, push updates and connect for support.
• • Unattended access: a remote connection to a machine nobody is sitting at, such as a server, used for maintenance outside patient hours.
• • Remote hands: a person in the office who follows the engineer's instructions to do something physical, such as reading a light on a switch or swapping a cable.
• • Onsite dispatch: a booked visit by a technician to the practice, either to fix a fault or to carry out planned work such as a new operatory.

The two are not rival products. A practice gets remote help for most tickets and onsite visits for the minority that need them. The question that matters on a bad day is which kind this particular problem needs, and that is what the table below answers. How to judge whether a provider can actually reach your address, and on what terms, is a separate decision covered in our guide to evaluating local and onsite dental IT coverage.

Which dental IT problems can be fixed remotely, and which need a technician in the office?

Software, settings, accounts and most performance problems are usually fixed remotely. Failed hardware, damaged or new cabling, network equipment that has died and new installations need someone on site. Many problems sit in between: they are diagnosed remotely, then fixed by a visit or by a person in the office following instructions. How that split is handled day to day is part of what managed IT covers in a dental office, so check it in any agreement you are offered.

Read each row as a starting point, not a promise. "Usually" means a remote engineer resolves it in most cases; "Partly" means diagnosis is remote and the fix may need hands; "No" means a visit or a planned project. The last column says who should get the first call. In every row, "IT provider" means whoever supports your computers and network, whether that is an outside company or an in-house person.

Practice management software and workstations

Printers, scanners and front desk devices

Imaging and clinical devices

Network, internet and phones

Servers, backups and security

Two rows deserve a closer look. Slow practice management software is the most common "can you just remote in?" request, and our guides on why Open Dental is slow and why Dentrix runs slowly and how to trace it show how far remote diagnosis can go before anyone needs to visit. Imaging problems often look physical but turn out to be software; the guide to troubleshooting dental imaging integrations walks through the bridge, driver and network checks in order.

How can you tell in five minutes whether a problem needs someone on site?

Ask five questions in order: does the device power on, is the internet working, is it one device or many, is there physical damage or a new device involved, and can the engineer get a remote session. If the device is dead, damaged or new, or nobody can connect, plan for hands on site.

Work through them with your IT provider on the phone. Each answer narrows the options.

1. 1. Does the device power on? A workstation, printer or switch with no lights and no fan noise cannot be reached remotely. Check the power strip and the battery backup first. If it still shows nothing, a visit or a spare is likely.
2. 1. Is the internet working? Remote tools travel over the internet. If the whole office is offline, the engineer cannot connect to anything inside the building unless your network has a backup connection. Fix or bypass the internet first.
3. 1. Is it one device, one room, or everyone? One computer points at that computer or its cable. One room points at a wall jack or a switch port. Everyone points at the server, the network core or the internet. The wider the problem, the more likely the cause is shared equipment.
4. 1. Is anything physically damaged, unplugged or new? A crushed sensor cable, a cable chewed by a chair base, a new device that has never worked: these need hands. Software cannot repair copper or glass.
5. 1. Can the engineer get a session on the affected machine? If the computer is on, online and the engineer can connect, most problems can at least be diagnosed remotely. If the session fails, the reason (no internet, machine off, agent missing) is itself a clue.

If the answers are "yes, yes, one device, no, yes," expect a remote fix. If any answer is "dead," "damaged," "new" or "cannot connect," expect the fix to need someone in the room, either a technician or a member of your team following instructions.

Why doesn't remote support work when the internet is down?

Remote tools need a working internet connection at both ends. When the practice's internet fails, the engineer cannot reach the computers inside, so diagnosis falls back on what your staff can see and read out. Practices that keep a second connection, such as a cellular backup on the firewall, keep the remote route open during an outage.

This is the most common gap in a remote-first plan. The connection that carries the remote session is the same connection that has just failed. Three things narrow the gap:

• • A second internet path. A backup line from a different carrier, or a cellular backup on the firewall, lets the provider keep watching and reaching the network while the main circuit is down.
• • Out-of-band access to network equipment. Some firewalls and switches support a separate management connection, so the provider can reach them even when the main path is broken. Ask whether yours do.
• • A person who can read lights and labels. With the network down, the fastest diagnosis is often a phone call in which someone in the office reads the lights on the modem, firewall and switch, and says which cables are plugged where.

If your practice software or phones are in the cloud, an internet outage stops more than remote support: it stops scheduling and calls too. Our guide on what to do when the dental office internet goes down covers the outage plan in detail, including which route has failed and how to keep the day going.

What can your team safely do while waiting for a technician?

Keep the day moving around the fault, record what you see, and touch only what the engineer asks you to. Move work to another workstation, use another sensor or printer, write down exact error messages, and leave servers, network cabinets and security software alone. When ransomware is suspected, unplug the affected computer's network cable and leave it switched on.

Most of the damage in an IT problem comes from guesswork in the first hour. The steps below keep patients moving and give the engineer clean evidence.

Do these

• • Write down the exact words of any error, the computer name and the time. A photo of the screen helps, but cover or crop patient details first.
• • Note what changed in the last day or two: an update, a new device, a moved desk, a power cut, a new staff member.
• • Use the workaround in the table for your problem: another room, another sensor, another printer, the imaging program without the bridge.
• • Restart a single workstation once if the engineer agrees, after closing the practice software. One restart is a test; five restarts destroy the evidence.
• • Keep one person as the contact for the engineer, so instructions are not relayed through three people.

Do not do these

• • Do not restart the server, the firewall or the switches unless the engineer asks. A server restart during a backup or update can make a small problem large.
• • Do not unplug or re-plug cables in the network cabinet. Moving one cable can take down a different room.
• • Do not disable antivirus, firewalls or security alerts to make something work. If security software is blocking a program, the engineer needs to see that.
• • Do not install anything a website, pop-up or unknown caller suggests, including remote support tools.
• • Do not power off a computer you suspect is infected. The CISA #StopRansomware Guide advises isolating affected systems and, where the whole network cannot be taken offline, unplugging affected devices from the network. It treats powering devices down as a fallback, because it can destroy evidence the investigation needs.

If you have a cyber insurance policy, find its incident phone number before you need it. Insurers often expect to be told early, and some name the responders they want involved.

How should secure remote access to dental office computers work?

Secure remote access means one approved tool, named accounts for every engineer, multifactor authentication on every account that can reach your systems, session logs you can see, and no remote desktop service exposed to the open internet. Staff approve sessions on computers in use, and access is removed when someone leaves.

Remote access is the reason most problems can be fixed without a visit. It is also one of the most abused doors into small businesses. In January 2023, CISA, the NSA and MS-ISAC warned in advisory AA23-025A that criminals had used phishing emails to get staff to download legitimate remote tools, then ran them as portable programs that need no installation or administrator rights. In June 2023, CISA, the NSA, the FBI, MS-ISAC and Israel's National Cyber Directorate published a full guide to securing remote access software, with a section addressed to customers of managed service providers. The checklist below turns those documents and the HIPAA Security Rule's technical safeguards into questions a practice can check.

Secure remote access checklist for a dental practice

• • One approved remote tool, named in writing. Your provider names the tool it uses. Other remote tools are removed or blocked. CISA's guide recommends auditing the remote access software on your devices and allowlisting approved tools.
• • Portable and unknown remote tools are blocked. AA23-025A advises application controls that stop both installation and execution of portable versions of unauthorised remote tools.
• • A named account for every engineer. No shared "support" login. The HIPAA Security Rule's access control standard includes unique user identification: "Assign a unique name and/or number for identifying and tracking user identity" (45 CFR 164.312(a)(2)(i)).
• • Multifactor authentication on every provider account. CISA's guide says providers "should also implement MFA on all accounts that have access to customer environments and should treat those accounts as privileged."
• • Different administrator credentials for your practice. The same guide tells providers not to reuse admin credentials across customers. Ask whether yours are unique to you.
• • Session logs you can see. Who connected, to which computer, when and for how long. The Security Rule's audit controls standard calls for mechanisms "that record and examine activity" (45 CFR 164.312(b)). CISA advises customers to make sure contracts give them visibility of the provider's presence, activities and connections.
• • Logs the remote tool cannot erase. CISA recommends keeping direct access to log servers, and the ability to delete or alter logs, out of reach of remote management tools.
• • Staff approve sessions on computers in use. An engineer joining a front desk or operatory computer asks first. Unattended access is kept for servers and maintenance outside patient hours, as written in your agreement.
• • No remote desktop open to the internet. The CISA #StopRansomware Guide says: "Do not expose services, such as remote desktop protocol, on the web." Remote access goes through the approved tool or a secured connection.
• • Least privilege. The provider's tools have the access the job needs and no more. CISA suggests "reduced privilege" configurations for routine uses such as read-only monitoring.
• • Remote tools are patched. The remote software and its agents are updated on a schedule, because they face the internet.
• • Vendor sessions go through a known path. Imaging and practice software vendors often run their own remote support. Know which vendor tools are on which computers, and start vendor sessions from your side.
• • Access ends when people leave. When an engineer leaves the provider, or you change providers, their access is removed. The Security Rule's administrative safeguards include procedures for terminating access to electronic patient information (45 CFR 164.308(a)(3)(ii)(C)).
• • Incident notice is in the contract. CISA's guide says contracts should detail how and when providers notify the customer of an incident affecting the customer's environment.
• • A business associate agreement is in place. A provider that can reach patient data on your systems usually handles it on your behalf. Under 45 CFR 164.308(b)(1) a covered entity obtains "satisfactory assurances" from a business associate. Ask your provider and your compliance adviser whether your agreement covers remote access.
• • Screens are tidied before a session. Close patient charts that the fix does not need before approving a connection.

Nothing on this list makes a practice safe on its own, and this is not legal advice. It is a set of questions with checkable answers. A provider that can show you each item, with a log extract or a configuration screen, is running remote access deliberately. For the wider set of controls, our dental cybersecurity risk assessment checklist covers the rest of the practice.

How can staff tell a real remote support request from a scam?

A genuine session starts with your practice contacting its known provider, or with your provider following up a ticket you recognise. Be suspicious of anyone who calls unexpectedly, sends a pop-up with a phone number, asks you to install a tool, or pushes urgency. Hang up and call your provider on the number you already have.

Fake support calls work because remote access is normal in a dental office. Staff are used to someone "connecting in." Three official sources give rules that are easy to teach:

• • The FTC's tech support scam guidance says: "Legitimate tech companies won't contact you by phone, email, or text message to tell you there's a problem with your computer." It also says real security pop-ups "will never ask you to call a phone number."
• • Microsoft's Quick Assist documentation advises users to "Never allow a connection to your device by someone claiming to be 'IT Support' unless you initiated the interaction with them."
• • CISA's advisory AA23-025A describes a refund scam in which criminals used a remote tool to change what a victim saw in a bank account, then asked the victim to send back a supposed overpayment.

Put the rule on a card at the front desk: we only allow remote sessions from our own IT provider, for a problem we reported or a ticket we recognise, using the tool our provider named. If someone pushes back, that is the signal to hang up. If a session is already running and anything feels wrong, disconnect it and call your provider.

What does a remote-first support model mean for a dental practice?

Remote-first means every ticket starts with remote diagnosis and remote repair where possible, and onsite visits are booked when something physical has to be done. For the practice, it usually means quicker starts on software problems, and a need to plan hardware, cabling and installations rather than expect someone to appear the moment they are needed.

The model has clear strengths and clear limits. Understanding both helps you set up the office so it works.

Remote-first does not mean remote-only. A good model has a written path from a remote ticket to an onsite visit, and both are run by people who can see the same ticket history. How that path works in your area, how visits are arranged and what they cost belong in the agreement; our guide to what a dental IT support SLA should define covers how to write those terms down and measure them, and the complete guide to dental IT support puts the support model in the context of everything else a provider should do.

How can you set up your office so more problems are fixed remotely?

Give the engineer eyes and hands in the building: label every computer, cable and port, keep a small kit of spares, name one person as the in-office contact, keep a second internet path, and keep an up-to-date list of devices and vendor contacts. Each of these turns a would-be visit into a phone call.

Practices that rarely need a technician are not lucky. They have made physical problems easy to describe and easy to fix by someone on site with instructions.

The remote-hands kit

• • Labels on everything: each computer named for its room ("OP3-PC"), each patch cable labelled at both ends, each wall jack numbered to match the switch port.
• • A few spares: two or three patch cables of the right length, a spare keyboard and mouse, a spare USB cable for the label printer, and a spare power strip.
• • A spare workstation, if you can: a configured computer that can replace a dead one in an operatory while the failed one is repaired.
• • A printed contact sheet: your IT provider's number, internet carrier account number and outage line, phone provider, imaging and practice software vendors, and your cyber insurer's incident line.
• • A simple network picture: where the modem, firewall, switches and server are, and which closet or cabinet holds them.

The in-office contact

Choose one person, usually the office manager, who is comfortable reading a device label, describing lights, unplugging and re-plugging a single named cable when asked, and approving remote sessions. That person does not need to be technical. They need to be calm, available and allowed to make the call.

The office records the provider should hold

• • A device list with names, rooms, serial numbers and warranty dates.
• • Which software and which bridges run on each computer.
• • Which devices are cloud services and which are on site.
• • Where every vendor's own remote tool is installed.

When those records exist, a remote engineer can often tell your contact exactly which cable to check and which light to read. When they do not, the first visit is spent finding out what is in the building.

When should onsite work be planned rather than called in?

Plan onsite work whenever you know it is coming: new operatories, new imaging equipment, a server replacement, a network refresh, cabling, an office move or opening a new location. Planned visits can be prepared remotely beforehand, scheduled around patients and finished in one trip.

Called-in visits are for faults. Planned visits are for change, and most physical work in a practice is change you can see coming weeks ahead. Treat these as projects with a date:

• • New operatory or room change: network drops, a workstation, sensor and camera connections, and testing every device in the room.
• • New pan, CBCT or scanner: the acquisition workstation, its network connection and the bridges to the practice software, agreed with the imaging vendor before installation day.
• • Server replacement or move to the cloud: a cutover plan, a verified backup before the switch and a test day before patients.
• • Network refresh: switches, firewall and access points replaced together, with labels updated as the work is done.
• • Office move or new location: cabling, internet ordering lead times, phones and the opening-day test.

Ask your provider whether hardware, cabling projects and software licences are quoted separately from monthly support, and get a written quote before the work is booked.

What to ask your IT provider about remote and onsite support

These questions test how remote and onsite work actually happens in your practice, not how a brochure describes it. Ask for a short demonstration or a document for each answer. Questions about service area, dispatch staffing and travel fees are in our guide to evaluating onsite coverage; this list covers the work itself.

How does Legend Networking handle remote and onsite support?

Legend Networking's model is onsite dispatch by appointment across served dental markets; remote-first nationwide. Behind it sit 24/7 monitoring and in-house engineers; no outsourced first-level triage. Legend's operations are led by Ian Lynch: 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps.

Legend Networking at a glance:

• • Onsite dispatch by appointment across served dental markets; remote-first nationwide.
• • Helpdesk staffed 24/7 at 1-800-794-1588.
• • 24/7 monitoring.
• • In-house engineers; no outsourced first-level triage.
• • The practice software platforms whose IT environment we support: Dentrix, Eaglesoft, Open Dental, Archy.
• • The imaging platforms whose IT environment we support: DEXIS, Vatech, Carestream, Planmeca/Romexis, Dolphin Imaging.
• • 22+ years in dental IT (since 2004).
• • Served over 3,500 practices since 2004.
• • 4.8 rating · 173 Google reviews.
• • Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps.

Whether onsite dispatch is standard at your address is a question to ask directly, for your own location. Our page on how Legend Networking delivers dental IT support describes the service.