What to do when nobody in the company knows the router or server password
Don’t reset the device as a first step. Find out what role it plays, who owns it, whether a configuration backup exists and what outage a reset would cause. Then use the official recovery procedure or prepare a controlled replacement.
Rather talk it through?
Describe the situation and I will suggest a first step and an estimate of the scope.
Let’s talkFirst, stop any hasty changes
A router may handle the internet connection, DHCP, VPN, telephony and the links between branch offices. A server may host a database, accounting, files, authentication and backups. A factory reset without a saved configuration can therefore turn an access problem into a company-wide outage.
- Identify the device and its role.Manufacturer, model, serial number, IP address, location and the services that pass through it.
- Record the working state.What works now, who is connected and which services must not be interrupted.
- Verify ownership.An invoice, a contract, a registration with the manufacturer or a cloud tenant will help with legitimate recovery.
- Find a safe window.If a restart or replacement is needed, set a date, inform users and prepare a way back.
The right procedure is based on documented ownership, the manufacturer’s documentation and authorised recovery. If a system belongs to someone else or its ownership is unclear, the work stops.
Where access or a way to recover it may exist
- the company password manager, sealed emergency access or a handover record
- a named account belonging to another authorised administrator
- the mailbox and phone number used for account recovery
- the cloud console of the manufacturer or the hosting provider, or Microsoft 365 / Google Workspace
- a configuration backup of the router, hypervisor, server or application
- the contract with the previous supplier and a secure channel for a formal handover
Before you send anyone a request for a password, verify their identity and authorisation. Secrets should not be sent by unencrypted email or ordinary chat. A temporary account, a secure vault or a controlled password reset is better.
The procedure depends on the type of system
Router, firewall and Wi‑Fi
First capture the current addresses, connections, VPNs and rules. If access cannot be recovered, prepare a replacement configuration and swap the device during a maintenance window.
Operating system and hypervisor
Check whether there is another admin, a provider console or a legitimate recovery procedure. Changing a local password can affect encryption or running services.
Domain, email and SaaS
The key is control over the registration and billing account. The provider may require verification of the company, the domain or the identity of an authorised person.
Accounting and business software
Involve the vendor or an authorised partner. Before you intervene, secure a copy of the data and the licence details.
Sometimes it is safer to keep a system running for the time being and prepare its replacement than to experiment with the only working device. The deciding factors are whether it can be backed up, the impact of an outage and whether a supported procedure is available.
How to prevent it happening again
A company needs at least two authorised ways to gain control: regular named accounts and separate emergency access. Neither the second factor nor the recovery email should be tied exclusively to a supplier’s private phone. The domain, licences and cloud tenants should be registered to the company.
Once control is restored, create an inventory, store configuration backups, record the owner of each service and set up regular checks of the emergency access. The next step is the checklist of IT documentation for a small company. If the situation arose after a technician left, also follow the procedure for taking over IT from a previous administrator. You will find more practical topics in the IT guides.
First, we map out the impact of a safe procedure.
In your message, include the type of device or service, what currently works, who owns it and whether any documentation or configuration backup exists.