You are saving an estimate when the wired desk drops offline. A few seconds later it reconnects. By the time someone comes to check, the connection looks normal. The next interrupted save is still waiting to happen.
An office Ethernet connection that keeps disconnecting needs a timed fault check, not an automatic order for new cabling. First find out whether the computer actually loses its wired connection, whether only an application stops responding, and whether other desks fail at the same moment. Then have your administrator compare one part of the affected connection at a time.
Ethernet is the wired network connection. A cable can be part of the problem, but so can the laptop dock, the computer's network adapter, the port at the other end or equipment shared by several desks. The useful starting point is what changes during the interruption.
Capture the next drop before it disappears
Write down the time and the desk or wall-socket label. Note the exact message: does the computer say the cable is disconnected, does it remain connected with no internet, or does only the estimating application fail? Take a screenshot if permitted, with customer names, documents and account details removed.
Ask a nearby colleague whether their work stopped at the same time. One affected laptop points the investigation in a different direction from a whole row of desks. Neither observation proves the cause, but both are more useful than a speed test taken after everything has recovered.
- Record whether the laptop was waking, being docked or being moved when the connection failed.
- Note whether a desk phone in the same cable path also stopped working. Do not unplug it to experiment.
- Separate the length of the interruption from the time the application took to recover.
- Keep a short record of repeated incidents rather than collecting unrestricted staff activity or browsing histories.
Do not restart shared network equipment just to see whether the problem goes away. Save the time and message first. A restart may restore service while leaving the cause unknown and interrupting people whose desks were working.
Separate a lost cable connection from a stopped application
Your administrator can compare the computer's connection status with the connected port on the network switch, the box that joins the office's wired devices. Where the equipment records connection events, ask whether the port went down and came back at the reported time. Available records and how long they are retained depend on the installed equipment and configuration.
If the physical connection stays up, investigate the interrupted service instead of declaring the wall cable faulty. An application, internet connection or access rule may need attention. A stable link does not prove that everything beyond the desk is healthy.
Likewise, working Wi-Fi does not convict the Ethernet cable. It may take a different route through the business network. Do not use personal hotspots, disable security software or move company files to another service to get around the fault. Ask for an approved temporary way to keep working.
If the connection remains stable but reports an unexpectedly low speed, that is a different symptom. Our guide to office Ethernet stuck at 100 Mbps explains the speed reading. Here, the question is why the connection or work session disappears and returns.
Give one desk a controlled comparison
Agree on an interruption with the person using the desk and save their work. Have the administrator record the existing route before moving anything: computer, dock or adapter, desk lead, wall socket and cabinet port. A laptop connected through a phone needs that extra step recorded too.
Start with accessible parts. Check that the desk lead is seated and not visibly crushed or damaged. Compare a known working lead while leaving the rest unchanged. If the problem persists, the administrator can compare an approved dock or adapter, or another correctly configured port. Record the result after each change.
A spare port is not automatically a suitable test port. It may carry a different business network or apply different access restrictions. Moving the connection until something works can conceal a configuration difference rather than identify a broken cable.
For an intermittent fault, ask what happened during the next normal work session, not just whether a green light came on.If the fault follows the laptop or dock to an otherwise working connection, ask the support technician to investigate that equipment and its software. If it stays with one cable route across controlled comparisons, ask the installer to investigate that route. These are clues to test, not permission to replace every component in the path.
When several desks drop together, widen the check
Several desks losing service at the same time may share a device, power source or connection back to the rest of the office. Your administrator should compare those shared points and their recorded events before ordering separate repairs at every desk.
Mention recent changes, including furniture moves, new desk equipment or extra cable connections. An accidental network loop, where traffic can circulate through an unintended repeated path, can cause disconnections or blocked ports. If the problem began after someone added a small desk networking box, see why an office network can stop after adding a switch.
Leave loop prevention and other network protections enabled. A blocked port may be protecting the rest of the office. Have the administrator identify the reason before restoring it; do not repeatedly reconnect cables or bypass the protection to keep the light on.
Ask what a commercial cabling repair will actually test
The lead on the desk and the fixed cable inside the wall are separate parts. Before opening walls or replacing a run, ask the installer to identify the socket, cabinet termination and connecting leads, then explain which comparison points toward that route.
Request a test report tied to the actual cable label and the intended cabling performance. A basic check that wires connect end to end is not the same as a performance test. Equally, a passed cable test does not prove that a laptop dock, network port or application is fault-free.
After the repair, repeat the task and circumstances that previously exposed the interruption. If it happened after reconnecting a dock, test that approved sequence. If it happened during ordinary afternoon work, agree on an observation period that covers that use. No recurrence during a brief visit is useful evidence, not a guarantee the problem can never return.
Keep the original symptoms, changes made, labelled test results and observation period together. Ask who to contact if it happens again and which fresh details they need. Our business network handover checklist covers the wider records to keep after installation work.
Bring the interruption record, not a guess about the fix
For a Windsor or Essex County office, start with NeuroDesk's commercial network infrastructure and cabling service. Include the affected desk labels, computer and dock models, when the drops happen and whether one desk or several are affected. Keep passwords and unrestricted logs out of the enquiry.
Ask for a scope that separates desk equipment checks from fixed-cabling tests and ends with a repeat of the interrupted work. That gives you something concrete to approve before anyone proposes replacing cables you cannot see.
Sources and technical scope
These official equipment references support physical-connection checks and the distinction between a damaged link and a network loop. Their controls and reporting are model-specific. The incident record and repair questions above are practical recommendations, not a claim that every system offers the same diagnostics.