Dental Office Network Support in Charlotte: Operatory Drops, Imaging Traffic and What to Do After a Duke Energy Outage

It is 9:40 AM Eastern on a Tuesday. Operatory 6 fired the sensor two minutes ago and the capture is still "acquiring". The front desk says the internet is fine. The imaging vendor says the sensor is fine, so it must be your network.

That one comparison, "what does this room share with the rooms that work, and what does it not", settles more operatory complaints than any reboot. Everything below builds on it: a fourteen-row table that starts from what your staff are seeing and ends at what to check first; the cabling, switch and Wi-Fi standard an older Charlotte suite should meet; how a Duke Energy outage takes the closet down and the sequence that brings it back; a triage for "the internet is down" that separates a cloud practice-management system from a server in your closet; and eleven questions that show whether your current provider has studied the network or only closed tickets about it.

What does a dental office network in Charlotte have to carry?

A dental office network carries five kinds of traffic that do not behave alike: practice-management traffic between workstations and the server, image capture from sensors and the pan or CBCT unit, voice calls, the internet-bound traffic of e-claims, email, cloud services and backup, and whatever patients put on the Wi-Fi. Treat them as one pipe and the operatories fail first.

Each kind of traffic has its own shape, and the shape is why the symptoms in the next section look so different from one another.

• • Practice-management traffic. Dentrix, Eaglesoft and Open Dental installed on a server in your closet talk to every workstation constantly in small bursts: a chart opens, a ledger refreshes, an appointment moves. The traffic is light but it is unforgiving of a flaky cable, which is why "lost connection to the server" appears in one room and not another. A cloud practice-management system such as Denticon, Curve or Archy moves that same traffic out through your internet circuit instead, which changes what an outage does to you (more on that below).
• • Image capture. An intraoral sensor from DEXIS, Carestream or Vatech plugs into the acquisition PC in the operatory, usually by USB; the image then travels over the room's cable to the imaging server or the practice-management image store. A panoramic unit or a CBCT running Planmeca Romexis, Dolphin or the vendor's own software does the same with much larger files, and the consult room that opens the volume pulls it back across the network a second time.
• • Voice. VoIP desk phones put a continuous, small, timing-sensitive stream on the same switch. They do not need much; they need it on time, which is why a phone call breaks up while a CBCT volume is moving unless voice has its own lane.
• • Internet-bound traffic. E-claims, eligibility checks, Microsoft 365, patient-communication platforms, remote backup jobs and any cloud imaging service leave the building through one firewall and one carrier circuit. If the circuit drops, all of these drop together and at once.
• • Guest and staff Wi-Fi. Waiting-room phones streaming video and patient-education screens in the operatories are the least important traffic in the building and, left on the clinical network, the most disruptive.

Keeping those five apart takes a managed switch, a cable to every operatory and a separate lane each for voice and for guests; Legend's dental office network design service page covers that design for practices nationwide. For a build from scratch rather than a repair, the dental office network setup checklist lays out the installation steps in order, and nothing here duplicates it. For the full picture of IT support for Charlotte dental offices, the city page is the place to start; this article stays on the network.

Why do the back operatories drop while the front desk is fine?

The back operatories drop while the front desk works because they sit at the far end of the longest cable runs, furthest from the access point, are the rooms most often added in an expansion on borrowed cabling, and are most often fed through a desktop switch. The front desk sits closest to the closet on the shortest, best-tested runs.

Before anyone reboots anything, read the symptom against the table below. The "first check" column is something your office manager can do in two minutes without a tool. Where a row names a Charlotte condition, it is because the condition is documented, not because it is unique to the city.

Two things stand out in that table. The symptoms that cost you the most chair time, such as the always-slow room and the expansion rooms, are the ones that have been treated as software problems for the longest, because a cable fault looks exactly like a slow program. And the two "internet is down" rows are in different places entirely, one in the walls and one at the edge of the building, which is why a provider who answers both with "reboot the router" has not diagnosed anything.

What should dental office cabling, switches and Wi-Fi look like in an older Charlotte building?

In a Charlotte suite, every operatory should have its own tested cable run home-run to one managed switch in a cooled closet, phones and access points powered over Ethernet from that switch, guest and clinical traffic separated by VLAN, and a firewall someone manages rather than installs and forgets. That is a cabling project and one switch, not a rebuild.

Charlotte practices that took over a suite wired for some earlier tenant, or that grew chair by chair from four operatories to eight over a decade and a half, tend to inherit three eras of cable behind the walls and no record of which run feeds which room. These are the things to settle, and most of them are questions for the low-voltage contractor rather than for your IT provider.

Drops per operatory. Find out how many drops the contractor plans for each operatory, and treat anything under two as something they have to defend. The first drop serves the acquisition PC; the second waits for the next device, whether that turns out to be a second monitor PC, a networked camera, a scanner cart or a patient-education screen. Skip it and someone eventually tucks a desktop switch under the counter, which is behind three of the rows above.

Cable grade. Cat6 at minimum, Cat6A where runs are long or a CBCT is in the plan, every run terminated on a labelled patch panel, every run tested after termination with the result kept. When operatory 6 stalls, a run with a test result on file takes a minute to clear as a suspect.

The switch. A single managed switch, big enough to take every drop as well as the server, phones and access points, and Power over Ethernet (PoE) on the phone and access-point ports so none of those devices hunts for a wall outlet. "Managed" matters because it is what lets a remote engineer see that operatory 6's port is linking at 100 Mb, which is the single most useful fact in diagnosing a slow room.

Wireless. Ceiling-mounted access points above the clinical hallway and the reception area, fed by PoE, positioned by the floor plan rather than by how near they are to the closet. In the Dentrix G7.9 requirements it publishes, Henry Schein One carries this warning: "Wireless networks are to be used at your own risk due to potential interference from X-ray machines and other devices". The same document says such networks "require professional installation to ensure appropriate security and to provide a reliable signal". Where a practice uses wireless anyway, "the network should be Wireless-AC or higher and meet local network speed requirements". Read that as the practice-management vendor's own instruction: wireless carries tablets, staff devices and guests; anything that captures an image sits on a cable.

VLANs. A VLAN is a logical fence inside the switch. Three of them cover most practices: clinical (operatories, server, imaging workstations, front desk), voice (the phones), and guest (the waiting room). Staff devices that need a little clinical access can have a fourth. The point is that a waiting-room phone update never shares a lane with a bitewing.

The firewall. The firewall is the device between your switch and the carrier's equipment, and it should be a managed one: current firmware, logging turned on, remote access limited to named people, and a configuration someone can produce on request. Access controls and audit logging are among the technical safeguards the HIPAA Security Rule asks covered entities to address, and a managed firewall is one place a practice can show them; it is a safeguard, not a certificate. The layered picture beyond the firewall belongs to Legend's dental cybersecurity services page.

What the contractor should leave you. A labelled patch panel; a printed map that says which panel port serves which room; a switch port list that matches it; the test result for every run; and a photo of the closet with everything lit. This is documentation as a deliverable. Without it, the next engineer, remote or on site, starts from zero.

The server side. If the imaging workstations are on good runs and the volume still crawls, the server's disk, memory and network card are the next suspects; Legend's dental server and workstation setup page covers what a practice-management and imaging server should be specified for.

On cost, the registry line matters here more than anywhere on this page: Legend states that hardware procurement, major cabling projects and software licensing are quoted separately. Re-pulling six operatories and installing a new managed switch counts as a cabling project and a hardware purchase at once; a provider who buries that inside a monthly fee has mispriced either the project or the month. For a Charlotte practice still in build-out rather than repair, have the cabling discussion before the drywall goes up, and continue it in the companion piece on IT for a dental startup in Charlotte.

What does a Duke Energy outage do to a Charlotte dental office network?

When the power drops, the devices on a UPS keep running until the battery is exhausted, the devices that are not drop instantly, and what decides whether the practice reopens cleanly is the order in which the closet goes down and comes back up. Nearly every "nothing works after the outage" call is a sequencing problem, not storm damage.

Charlotte's outage pattern is documented, and it is not only hurricane season. During Hurricane Helene, WBTV reported that as of 11:15 p.m. on Friday, September 27, 2024, "more than 1.057 million Duke customers were without power in North Carolina and South Carolina", with outages "most heavily concentrated in the Greenville, Spartanburg, Asheville and Charlotte areas"; three days later, at 3:13 p.m. on September 30, "more than 757,000 Duke customers were without power in the Carolinas", over 307,000 of them in North Carolina. Winter does it on a smaller scale: WJZY reported 2,045 people in Mecklenburg County and 236 in Gaston County without power at 10 a.m. on Saturday, January 11, 2025, after a storm "brought snow and ice to the area", with outages attributed to "extreme weather or fallen trees"; and on January 26, 2026, WBTV reported "more than 37,000 Duke Energy customers in the Carolinas" without power after a winter storm, most of them between Asheville and Greenville, South Carolina. A multi-day regional outage and a Saturday-morning neighbourhood outage put the same questions to a dental office: what is on battery, what order do we shut down, and what order do we bring back.

The table below is general practice for a server-based dental office, not a description of any provider's procedure, and the right version for your office is the one your provider writes down with you and tests.

The first-patient checklist after a power event

1. 1. Every switch is lit and every operatory port shows a link light.
2. 1. A wired front-desk PC opens a chart in the practice-management system.
3. 1. An operatory PC opens the same chart and an existing image.
4. 1. One sensor captures a test image in one operatory, and the image reaches the chart.
5. 1. The pan or CBCT unit powers up and its software connects to the server.
6. 1. One phone makes an outside call; one phone receives one.
7. 1. The firewall shows the internet circuit up; e-claims or email loads.
8. 1. The last backup job shows "completed", and the next one is scheduled.
9. 1. The UPS shows that it is charging and no fault light is lit.
10. 1. Note the date, what went wrong and what fixed it, so the next outage starts from this list, not from memory.

Outage planning for the whole practice, including paper schedules and what to tell patients, belongs to our Charlotte dental IT guide; this article stays inside the network closet.

The internet is down in a Charlotte dental office: is it the LAN or the WAN?

Before anyone reboots, find out what still works inside the building. A wired operatory that can open a chart from the server and capture with its sensor proves the local network (LAN) is healthy, which puts the fault on the circuit or firewall (WAN). With cloud-hosted practice management, every room goes dark together, so failover matters.

That split determines who you call and what you can still do with a patient in the chair. Work through it in this order.

1. 1. LAN or WAN? Ask one operatory to open a chart and capture a test image. If both work, your server, switch and cabling are fine and the patient in the chair can be treated. If the practice-management system is cloud-hosted and nothing opens anywhere, move to the hotspot plan from the outage table while someone works the next steps.
2. 1. The carrier's equipment. Look at the carrier's modem or terminal in the closet. Is it powered? Is the light that indicates the circuit solid or flashing? A dark box on a bare outlet during a power flicker is the single most common cause of "internet down with the lights on".
3. 1. The firewall. Is it powered, and does the port facing the carrier show a link? A firewall that is up with a dead outside link points at the carrier; a firewall that is dark points at the closet's power or the device itself.
4. 1. The carrier's status. Check the carrier's outage page or line from a phone before anyone power-cycles anything. If there is a known outage, no amount of rebooting shortens it, and a reboot of the carrier's equipment mid-restoration can make it longer.
5. 1. Failover. If the firewall has a second path, usually a cellular connection, it should have switched already. Know before the outage which systems the failover keeps alive: cloud practice-management, e-claims, email and VoIP, yes; an on-premises server with no closet power, no. A failover connection is sized for the clinical traffic that needs it, not for the waiting room's video.
6. 1. Who calls whom. A circuit that is down goes to the carrier; a silent closet or an unlit firewall goes to IT; a building with no power goes to neither. Decide in advance that one named person makes the carrier call with the account number from the label in the closet, and that your IT provider is told at the same time, so the two are not waiting on each other.

The vendor-authored view of why this matters is blunt. Greg Davis, chief executive of the failover vendor Bigleaf Networks, wrote in Dental Economics in October 2023 that "For an independent dental practice, loss of internet means loss of income and damage to your reputation." That is a vendor's framing of its own market; the operational point survives it. A practice that cannot bill, cannot check eligibility and cannot answer its phones for an afternoon has lost the afternoon, whatever the dollar figure someone puts on it.

How much of the network does dental imaging actually use?

Imaging asks for a wired gigabit route from each acquisition PC to the server, and from the server back out to every room where images are read; the heaviest load comes from CBCT, then panoramic, then intraoral sensors. No single bandwidth number is honest, so the table below converts three vendors' published requirements into design rules.

A few practical notes for a four-to-ten-operatory office:

• • Hybrid storage for CBCT. The volume the surgeon opens in the consult room should come from a server or imaging workstation in the building, not from the cloud, with the cloud as the offsite copy. Done that way, the biggest transfers stay on the in-house gigabit LAN rather than crossing the carrier circuit, which is the reasoning behind the "cloud dead, local fine" row.
• • Intraoral scanners. No scanner vendor's requirement page is cited on this page, so this article does not put a number on them. Ask the scanner vendor for its network sheet and treat the cart as a wired device that moves a large case file at the end of every scan.
• • Reading rooms count. When the doctor reviews CBCT volumes somewhere other than the capture room, that reading room's run has to be as good as the capture room's. The second room is the one practices forget.
• • The vendor's page beats the rumour. Every figure in the table is a vendor's published requirement, dated and linked in this page's sources. A provider who quotes you a "dental office needs X Mbps" number should be able to show you where it came from.

Sensor drivers, practice-management-to-imaging integrations and the rest of the software layer are covered in the companion article on dental software and imaging support in Charlotte and, for practices anywhere, on Legend's practice management software and imaging IT support page.

Who notices first when a dental office network in Charlotte starts failing?

In a practice without monitoring, the hygienist in operatory 6 notices first, at 9:40 with a patient in the chair. With monitoring, a switch port that drops to 100 Mb, a UPS that reports a battery fault or a closet that passes a temperature threshold raises an alert before anyone feels it and before the first patient.

Three different things get sold under the word "support", and it helps to buy them by name.

• • Monitoring watches the switch, firewall, circuit, server and UPS and raises an alert when something changes: a port drops its link speed, a backup fails, a temperature rises, a circuit goes down at 6 AM before anyone arrives.
• • Management acts on it: firmware on the firewall and switch, configuration changes, the VLAN that separates guests, the backup window that got moved out of clinic hours, the disabled power-management setting on a workstation's network card.
• • Projects cover cable pulls, replacing a switch or rebuilding a closet, and Legend states that this kind of work is quoted separately.

Legend Networking states its coverage as 24/7 monitoring with staffed help desk Mon–Sat and a 24/7 emergency line. The staffed hours, as published, are Help desk Mon–Fri 7 AM–7 PM CT, Saturday 8 AM–2 PM CT; 24/7 critical/emergency line. A Charlotte front desk runs an hour ahead of Central time, so on your office clock that is 8 AM–8 PM ET on weekdays and 9 AM–3 PM ET on Saturday. A Saturday hygiene day that opens at 8 AM Eastern opens an hour before the staffed desk does, which is a fact to know rather than a problem to hide: the 24/7 critical/emergency line is the published route outside staffed hours, and what any provider counts as critical is a question to get answered in writing. Legend also states: in-house engineers; no outsourced first-level triage. Ask any provider whether whoever first opens a ticket about operatory 6 would recognise the term "acquisition PC".

Flat monthly plans $399.99–$1,200 per practice per month is the published range for Legend's plans; a network project sits outside it, as above. Legend's dental help desk page explains what the desk takes on and how a ticket travels. What a Charlotte practice should expect from managed IT overall, and how to change providers without losing a week, is for managed IT for Charlotte dental practices.

What can Legend show a Charlotte practice?

Legend's published facts are national, and this page claims nothing local beyond them: 22+ years in dental IT (since 2004), 3,500+ practices supported, and a 4.8 rating · 173 Google reviews. Its headquarters are in Dallas, Texas, and Legend describes its model as onsite dispatch by appointment across served dental markets; remote-first nationwide.

Monitoring at Legend sits under a named person, Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps. Put the same question to every provider you consider: whose desk does a switch alert from your closet reach at 7:10 on a Tuesday morning, and who chooses between fixing it remotely and sending someone?

For cabling work in particular, the onsite question is the one to settle before you sign. Whoever you are talking to, Legend included, get it in writing: how a Charlotte onsite visit is booked and priced, which pieces of a cabling job the provider handles and which fall to the low-voltage contractor, and how the project work is kept apart from the monthly service. The city page for dental IT support in Charlotte is where Legend's Charlotte detail lives.

What to ask your IT provider about your Charlotte dental office's network

Ask these in writing. What comes back shows whether anyone has actually examined your network, or just worked through your tickets.

A provider who can answer all eleven without walking into the closet or opening the monitoring already knows your network; keep them. One who manages fewer than half is not supporting the network, only rebooting it.