Paxton Net2 and Switch2 Door Fault Guide
Working through token errors, ACU faults and software lockouts on Paxton systems
Paxton Net2 or Switch2 fault in Kent or Medway? We can help you narrow it down.
We install and maintain Paxton systems across Chatham, Medway, Kent and South East London and can talk through your fault over the phone first. Call 01634 944161 for friendly advice.
No call centres, a real engineer answers.
Paxton Net2 and the newer Switch2 platform are among the most widely fitted access control systems in offices, schools and blocks of flats across Kent and Medway, largely because the software is straightforward and the hardware is dependable. When something does go wrong, the fault usually sits in one of three places: the token or credential itself, the door controller known as the ACU, or the software and network link that ties everything together.
Switch2 differs from Net2 in that it talks to the cloud directly rather than relying on a permanently connected PC, so a Switch2 fault can sometimes trace back to an internet or router issue rather than the door hardware at all. Net2 systems, by contrast, often develop faults when the host computer running the software is switched off, updated, or loses its connection to the network switch feeding the ACUs.
Before assuming a full system failure, it is worth working through a short list of checks that separate a token problem, a software lockout, or a genuine hardware fault on the ACU. Many calls we attend turn out to be one of these simpler causes rather than a failed control unit.
What You Will Usually Notice
Safe Checks You Can Do Yourself
Check the host PC or server is switched on
On Net2 systems the software usually needs to be running on a dedicated PC for live monitoring and updates to work. If that machine has been switched off or restarted, doors can still open on cached permissions but new changes will not take effect.
Confirm the network switch and cabling are powered
Net2 and Switch2 ACUs communicate over standard network cabling, often carrying power as well as data. Check that the network switch feeding the door controllers has power and that no obvious cable has been pulled loose.
Test a second known-working token at the affected door
If a colleague's fob works fine at the same reader, the problem is likely with the individual token or its record rather than the door hardware, which narrows the fault considerably.
Check the Switch2 app for a connectivity warning
The Switch2 mobile app usually flags when a site has lost its connection to the cloud. If it shows offline, check your internet router before assuming a hardware fault at the door.
Look at the ACU status light pattern
Paxton controllers use different light patterns to indicate normal running, network loss or a fault condition. Note the colour and flash pattern so it can be described accurately if an engineer is needed.
Inspect the reader head for visible damage or loose cabling
Proximity readers are often mounted outside or in high traffic areas where they can be knocked or tampered with. A quick check for physical damage or a cable that has been pulled tight can explain a single door failing while the rest of the system remains healthy.
What Normally Causes It
A deleted or expired token record
Tokens are managed centrally in the Net2 or Switch2 software, so a credential can stop working instantly if it has been removed, its access group changed, or an expiry date has passed without anyone realising.
Loss of network connection between the ACU and the host
Both platforms rely on stable network communication. A faulty cable, a failed switch port or a router issue can leave the door controller isolated, so it falls back to only recognising previously cached credentials.
A power supply or PoE fault at the controller
Many Paxton installations power the ACU over the network cable itself. If the power sourcing equipment fails or a cable is damaged, the controller can lose power intermittently, causing doors to behave erratically.
A software or firmware update that has not completed properly
Updates to the Net2 software or Switch2 firmware occasionally interrupt communication with door controllers until every device has synchronised, which can leave some doors briefly unresponsive.
A failing internal component inside the ACU
Like any electronic controller, the ACU itself can develop an internal fault over time, particularly after a power surge or years of continuous use, which requires diagnosis and likely replacement.
A failed or damaged proximity reader head
The wall-mounted readers that scan fobs are prone to physical wear, moisture ingress, or cable fatigue. If a reader has failed, it may not beep or light up at all, or it could show a permanent red light, preventing any token from being read regardless of its validity.
When to Stop and Call an Engineer
Keeping it from coming back
Keep the Net2 host PC or Switch2 network connection stable and avoid unexpected power cuts to the switch feeding your door controllers, and have the system checked periodically so ageing ACUs are identified before they fail outright.
Other Guides You May Find Useful
- BPT and Comelit Intercom Fault Guide
- Pyronix Enforcer: Common Problems and Fixes
- Dealing with sensor faults, app pairing and tenant changeover on Yale wireless kits
- Replacing the batteries in your burglar alarm
- Alarm Tamper Fault Explained: Causes and Fixes
- Choosing the right reset for Hikvision, Dahua and similar recorders
Frequently Asked Questions
Paxton Net2 and Switch2 Door Fault Guide: common questions
Ready for an installer to take it from here?
See our access control installation serviceNeed Security or WiFi Help Fast?
Alarm installation, CCTV, access control, WiFi and repairs across Kent & South East London. Call, WhatsApp or send a message for a free quote.