Almost every small office we look after in Loanhead has, at some point, phoned us about the same thing: the shared printer keeps disconnecting. One person's laptop suddenly says "Printer offline" while the machine next to them prints fine, or the whole office queues up ten jobs on Monday morning and nothing comes out. It is one of the most quietly disruptive faults a small business can have, and — as we'll go through below — it is almost never actually the printer.
If you'd rather skip the diagnostics and have someone sort it on site, our small-business IT support covers Loanhead, Bonnyrigg, Dalkeith, Roslin and Lasswade the same working day for issues like this.
1. First: Rule Out the Simple Stuff
Before assuming something clever is wrong, walk over to the printer. Is the display showing an error, a paper jam, or a low toner warning? Is the network cable actually plugged into the wall, and is the wall port live? Nine times out of ten a "shared printer disconnecting" call in a small office really is one of these, and it just presents oddly because half the team hasn't tried to print yet.
If the printer is genuinely online at its own display but every workstation says otherwise, the fault is in the network path between them — which is where the interesting causes start.
2. The Number-One Cause — Your Printer's IP Keeps Changing
This is, by a mile, what we find on site most often. When you first set the printer up, the router handed it an IP address — say 192.168.1.42 — and every PC's printer driver was configured to talk to 192.168.1.42. Then, one evening, there was a power cut, or the router auto-restarted for a firmware update, and when everything came back the router handed the printer a different address — 192.168.1.87. Now every workstation is politely calling out to 192.168.1.42 and getting silence back.
Windows sometimes hides this by mapping the printer by hostname or by using WSD (Web Services for Devices), but on the older mixed networks we typically see in Midlothian small offices, IP-based ports are still the norm and this is what breaks. The proper fix is a DHCP reservation on the router: you tell the router "whenever this specific printer MAC address asks for an IP, always give it 192.168.1.42". After that, restarts and firmware updates stop mattering. Setting a static IP on the printer itself works too, provided you pick an address outside the router's DHCP range or you'll get an address clash weeks later.
3. When the Print Spooler Service Gives Up
The Windows Print Spooler is the background service that queues jobs and hands them to the printer. When a single corrupted print job lodges in the queue — a truly enormous PDF, a document from an app with a badly-behaved driver — the whole spooler can hang, and the printer immediately shows as offline on that PC. Sometimes a corrupted job on one office machine even bleeds across to a shared print queue and affects everyone.
The reliable fix is a spooler reset: stop the Print Spooler service in Services (services.msc), empty the folder C:\Windows\System32\spool\PRINTERS\, then start the service again. You lose whatever was queued, which is exactly what you want, and the printer comes back within a few seconds.
4. The Wi-Fi Printer That Keeps Falling Off the Mesh
Wi-Fi printers hate mesh networks. A typical Loanhead office might have a mesh system with two or three nodes for coverage. The printer joins whichever node had the strongest signal on the day it was set up — often not the main one — and then over time the mesh optimises itself, forcing the printer to hop between bands and re-authenticate. Each hop looks to Windows like a disconnection.
An accountancy office we help in the Straiton area had exactly this: the printer worked perfectly for weeks, then would randomly vanish for ten minutes at a time. The mesh dashboard showed the printer had jumped from the ground-floor node to the upstairs one during a busy print run. Moving the printer to wired Ethernet on the main router ended the problem in one afternoon. If Ethernet genuinely isn't possible, at least pin the printer to a fixed SSID (2.4 GHz only) and disable band-steering for that device — our networking and Wi-Fi team does this on the ISP router when the setup allows it.
5. Driver Drift Between Windows 10 and Windows 11 Machines
Most small offices we walk into have some machines on Windows 10 and some on 11, plus perhaps a MacBook the boss uses. Modern print drivers come in two families: Type 3 (the classic per-model driver) and Type 4 (the newer universal one). Windows 11 tends to auto-pick Type 4 from Windows Update, while an older machine might still be running a Type 3 driver installed manually years ago. Two computers point at the same printer with two different drivers, and one of them silently generates broken jobs that jam the queue for everyone.
The tidy answer is to standardise the driver — pick one, install it manually from the manufacturer's site on every workstation, and remove all the "duplicate" printer entries Windows tends to accumulate. Where a stale driver is the underlying cause of repeated crashes, our software troubleshooting service handles this end-to-end so you don't have to sit on each machine yourself.
6. The USB-Sharing Setup That Made Sense in 2015
We still see this in a surprising number of Midlothian offices: the printer is plugged into the receptionist's PC via USB, and Windows shares it out to the rest of the office. It works — until the receptionist goes to lunch and their PC sleeps, or reboots for updates, or is off sick on Tuesday. Every other workstation then loses the printer without warning, because there is no printer on the network at all; there is only "Karen's PC pretending to be a printer".
The fix is small hardware, not a service call: either a printer with a proper Ethernet port (most business models already have one that's simply not been used), or a small print server that plugs the USB printer directly into the network. Either way the printer becomes independent of any one workstation and stops disappearing at 12:30 every day.
7. What a Reliable Small-Office Print Setup Looks Like
After enough of these callouts, the pattern of a print setup that just works becomes very consistent. It's usually all of the following at once:
- The printer sits on a wired Ethernet connection into the main router or switch, not Wi-Fi.
- The router has a DHCP reservation tied to the printer's MAC address, so its IP never changes.
- Every workstation uses the same driver version, installed from the manufacturer rather than whatever Windows Update served up.
- There is no PC "sharing" it to the rest of the office — it's a first-class device on the network in its own right.
- A quick test print is part of the office opening routine on Monday, so faults get caught before someone urgently needs an invoice at 4pm.
None of this needs a server room, and it can all be done in an afternoon on a working day without shutting the office down.
Getting Help Locally in Loanhead
If the print queue is stuck right now and someone can't email out a client PDF, our on-site help in Loanhead can usually get to you the same day from the workshop in Edinburgh, and we cover Bonnyrigg, Dalkeith, Roslin and Lasswade on the same route. For the wider small-business piece — deciding when to switch to a proper print server, or getting the office network tidied so a new printer will actually stay online — our business IT support works well alongside our home and office callouts. If you're weighing up whether the fix should be handled remotely or on-site, our post on remote vs on-site IT support covers the trade-offs, and our small-business IT checklist puts the printer question in its wider context.
Last updated: 25 July 2026