Technician helping troubleshoot Motorola phone screen brightness not working

Steve H.

Reviewed for technical accuracy

Specialities: phone can’t join work Wi-Fi, “unable to connect” errors, wrong password vs 802.1X login, certificate prompts, private MAC address issues.

Work network won’t connect? Common reasons + what to check first (password vs 802.1X, certificates, device policy, private MAC, after update)

Technician avatar Technician
I can help you sort this out safely. Work Wi-Fi can be tricky because it’s often not a “simple password” network — many offices use a login, a security certificate, or a device policy that must be in place first.

Trust moment: we’ll avoid risky steps that wipe saved networks or change lots of settings at once. Let’s only do safe checks, one at a time.

Quick starting point: did this begin today, or after something changed (new phone, Android/iOS update, password change at work, or you’re in a different building)?
Customer
It started this week. I didn’t change anything myself, but my phone updated. Now it keeps failing when I try to join the office Wi-Fi.
Technician avatar Technician
Updates can trigger this, but the exact error message matters. When you tap the work network name, what do you see?

Examples: “Incorrect password”, “Unable to connect”, “Authentication problem”, or a screen asking for things like username, domain, EAP method, or certificate.
Customer
It doesn’t say incorrect password. It says “Authentication problem” and sometimes I see a login screen with username and password.
Technician avatar Technician
That strongly suggests an enterprise Wi-Fi setup (often called 802.1X). In plain terms: the network is checking “who you are” and sometimes “what device you are,” not just a shared password.

Two safe questions to narrow it down:
1) Do coworkers connect using the same Wi-Fi name with their phones right now?
2) Do you sign in with an email-style username (like name@company.com) or a short username (like j.smith)?
Customer
Yes, coworkers connect. My login is usually my work email, but I’m not 100% sure if it needs the full email.
Technician avatar Technician
That “format” detail is a common reason for authentication failures. Some networks require the full email, others require DOMAIN\\username, and some reject anything except the exact format IT expects.

Trust moment: I don’t want you to keep guessing and lock your account. Let’s do checks that don’t risk that.

Safe check: does the phone connect to other Wi-Fi networks (home Wi-Fi, a café) without issues?
Customer
Yes, home Wi-Fi works fine. It’s only the office network that won’t join.
Technician avatar Technician
Good — that points away from hardware and toward the specific work setup.

Work Wi-Fi often depends on one of these:
• A saved Wi-Fi profile your workplace provides (sometimes through a work app/MDM).
• A certificate that proves the network is legitimate (or proves your device is allowed).
• A policy like “only registered devices can join.”

Did your workplace ever have you install a work management app (for example, a company portal) or add a “work profile” on Android?
Customer
I think I have a “work profile” and there’s a company portal app. I don’t really understand it, but it’s there.
Technician avatar Technician
That’s a helpful clue. If the work profile (or its certificates) isn’t active after an update, the phone can fail at the “authentication” step even with the right username and password.

Safe check (no removals): in your Wi-Fi list, when you tap the work network, do you see any mention of certificate, CA certificate, identity, or phase 2 authentication? Even seeing those words tells us it’s the enterprise type.
Customer
Yes, I see “CA certificate” and it’s set to something that says “Do not validate” or “unspecified.” That looks scary.
Technician avatar Technician
You’re right to pause — that’s one of those spots where random changes can make things worse.

Trust moment: I don’t want you to select certificates unless you’re sure they came from your workplace. Picking the wrong option can cause repeated failures and confusion.

Here’s the safe takeaway: if the network expects a specific certificate and the phone doesn’t have it (or the work profile didn’t provide it), you’ll often see authentication problems exactly like this.
Customer
So it might not be my password at all? I tried twice and it still failed.
Technician avatar Technician
Exactly — it can be the password, but it can also be the login format, a missing certificate, or a device policy.

Another simple thing that sometimes blocks work Wi-Fi: Private/Random MAC address (the phone uses a “new identity” for the Wi-Fi). Some workplaces allow only registered devices, so the network sees your phone as “unknown.”

Safe question: did your workplace ever register your device by MAC address, or does the Wi-Fi only work for “approved devices”?
Customer
I remember IT “approved” my phone a long time ago. I didn’t know it could change its identity.
Technician avatar Technician
Many phones now use a random/private MAC by default, and updates can sometimes change how it behaves for a specific network. That can make the office Wi-Fi treat the phone like a new device.

A safe approach is to check whether the work network has “Private address / Randomized MAC” turned on for that network — without changing other Wi-Fi settings. If IT whitelisted your old identity, that mismatch alone can explain sudden failures.
Customer
This is starting to make sense. Is there anything else that could trigger it after an update?
Technician avatar Technician
Yes — a few common “environment” triggers:
• The office network security settings changed (WPA2 ↔ WPA3, or a new certificate).
• The phone’s date & time is off (secure logins can fail silently).
• A work profile temporarily paused, so its certificate isn’t available.
• The network requires a specific username format (email vs DOMAIN\\username).

If you want a calm next step: check whether your time/date is automatic, and whether the work profile shows as active — those checks are safe and don’t “erase” anything.
Customer
Thank you. I feel better knowing it’s not necessarily the phone being broken. I’ll check the work profile and those settings.

Quick answer: the accepted fix

Accepted first fix for phone can’t join work Wi-Fi: confirm what type of network it is (simple password vs enterprise login), then check the most common “non-obvious” blockers before any resets.

What usually helps most (safe checks):
• Note the exact error (password vs authentication vs certificate prompt) to identify enterprise Wi-Fi (802.1X).
• Confirm your username format matches what work uses (email vs DOMAIN\\username) and avoid repeated guesses that could lock accounts.
• Check whether a work profile / MDM is active and whether certificates are present (don’t pick random certificates).
• Look at the work network’s Private/Random MAC setting if IT “approved” your device in the past.
• Save “reset network settings” for later only if the safe checks don’t change anything.


Why a phone can’t join a work network (simple explanation)

Work Wi-Fi is often built to allow only trusted people and trusted devices. That’s why you may see a login screen, certificate choices, or “authentication problem” instead of a simple password box. If a work profile, certificate, or device approval is missing (or changed after an update), the phone can look “fine” on other Wi-Fi but fail only at the office. In some offices, a private/random MAC address makes your phone look like a brand-new device, so the network rejects it.

What to check first (without breaking anything)

Start with the safest checks: confirm other Wi-Fi networks work, then look at the exact message your phone shows when joining work Wi-Fi. If you see certificate or EAP options, treat it as an enterprise network and avoid random changes. Check that date/time is automatic, the work profile is active, and the login format matches what your workplace uses. If the device was “approved” before, review the network’s private/random MAC setting for that Wi-Fi name.

Phone can’t join work Wi-Fi — gentle tips for seniors

Most cases are about login type, certificates, or device approval — not a broken phone.

Try to avoid rapid guessing. Work networks can lock accounts after too many attempts. If you see certificate options, pause and confirm the work profile (or company portal app) is active, and check that the phone’s date/time is correct. A private/random MAC setting can also make the office Wi-Fi treat your phone as “new.”

Disclaimer: This information is AI-generated and intended for general guidance only. Avoid making multiple system changes at once. For device-specific steps, consult your phone maker’s support pages or your workplace IT instructions.

Additional troubleshooting options


Getting Started Is Easy

Start with safe checks

First, confirm your phone connects to home Wi-Fi or another network. Then watch the exact message you get at work (password vs authentication vs certificate). That tells you which kind of work Wi-Fi you’re dealing with.

Don’t guess repeatedly

If the network asks for username, domain, or certificates, it’s not a “normal password” Wi-Fi. Avoid repeated tries that could lock your work account, and check the login format your workplace expects.

Know what matters most

For work Wi-Fi, the usual “big three” are: the correct login format, an active work profile/certificate, and whether the network recognizes your device (private/random MAC can change that).

FAQ

Why did my phone stop joining the work network all of a sudden?

This can happen after a phone update, a workplace Wi-Fi security change, or an expired/changed certificate. It can also happen if the phone starts using a private/random MAC address and the office only allows approved devices. If coworkers can connect, the network is likely working and your device setup is the key. Try safe checks before any resets.

Did this happen after an iOS/Android update?

It often can. Updates may change Wi-Fi security behavior or how work profiles and certificates load. Sometimes the update also changes the “private address” setting for a Wi-Fi network. Check date/time, work profile status, and the exact error message first. Avoid repeated login attempts while you’re unsure.

Is this a settings issue or something wrong with my phone?

If your phone connects to home Wi-Fi, the hardware is usually fine. Work networks commonly use enterprise login (802.1X), certificates, and device approval rules. A missing work profile or wrong username format can block access even with a strong signal. Hardware issues are more likely if Wi-Fi won’t turn on or fails on every network.

Can I check this safely at home before I ask IT?

Yes. You can confirm other Wi-Fi networks work, check that date/time is automatic, and note the exact error message you see on the work network. You can also check whether a work profile is active without deleting anything. Avoid “reset network settings” as a first step because it can remove saved Wi-Fi details. If you see certificate options, don’t choose random ones.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant