Technical Anshu
Tutorials Blog
🏢 Workgroup Sharing

Share Files Between Windows PCs Without a Domain Same Username Trick

A domain and a server are overkill for a three-PC office — but so is typing passwords all day. There is a neat middle path: if both PCs know the same username with the same password, Windows logs you in silently. Here is how that works, and where it stops being a good idea.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute read
🎥 Full video — workgroup sharing set up like an admin

Big companies use a domain: one server holds every account, and any PC trusts it. A small office has a workgroup — every PC keeps its own accounts, and the file PC only trusts logins it knows. The so-called “same username trick” is not a hack at all; it is simply how Windows authentication naturally behaves when the two PCs' account lists happen to match.

How Pass-Through Authentication Works (example)
Staff PC logs in asRavi / password ••••
File PC has an accountRavi / same password ••••
ResultConnected — no prompt MATCH
If passwords differPrompt or Access Denied
✔ Windows presents your current login first when you open a share
✔ The file PC accepts it only if name AND password both match its own list
A simplified view of workgroup authentication. The file PC is always the judge.
1

Set Up the Matching Accounts

  1. On the file PC, create a local account for each person who will connect (Settings → Accounts → Other users, or lusrmgr.msc), each with a real password
  2. Grant those accounts access through groups and permissions, as in the rest of this series
  3. On each person's own PC, either sign in with that same username and password, or save the file-PC credential once in Credential Manager — both routes end the daily prompting
2

Connect Once, Properly

To connect with an explicit account — useful when your daily login is different — use a mapped drive or the command line: net use Z: \\OFFICE-PC\Billing /user:OFFICE-PC\Ravi. Enter the password once; tick remember, or add /persistent:yes, and the drive returns at every sign-in. If a wrong login is stuck from earlier attempts, clear it first with net use * /delete and remove the saved entry in Credential Manager.

3

The Password Change Problem — the Honest Cost

The trick has one maintenance debt: passwords must stay in sync by hand. Change the password on the file PC and every saved copy elsewhere is wrong until updated — expect a round of "access denied" until each PC's stored credential is refreshed. In a two-or-three PC office this is a minor chore once or twice a year. Past roughly eight or ten PCs, the chore becomes the reason offices graduate to a small server or a NAS with its own central accounts.

4

A Cleaner Variant — One Dedicated Sharing Account

Some offices give up per-person accounts on the file PC and create a single account like office-share that everyone connects with. Be honest about what that buys and costs: setup is trivial, but permissions can no longer tell people apart and auditing names one shared account for everyone's actions. For a folder of truly common files that may be acceptable. For billing, HR or anything you would ever need to trace, per-person accounts are worth the extra ten minutes.

🔴 Never solve a workgroup password prompt by turning off password protected sharing or enabling Guest. The prompt is the security working as designed. Matching accounts or one saved credential remove the friction while keeping a name — and accountability — on every connection.

🎥 Watch the Full Video

The video sets up complete workgroup sharing on real PCs — accounts, groups and silent logins, end to end.

▶️ Watch Full Video
❓ Common Questions (FAQ)

Does the same username trick work with Microsoft accounts?

Poorly. Microsoft-account sign-ins do not pass through to a local file PC account in the same clean way. For sharing, create local accounts on the file PC and connect with those (saved credential or net use), whatever the person uses to sign in to Windows itself.

We have five PCs. Is a workgroup still fine?

Yes — five PCs is comfortably workgroup territory if one PC holds the files and accounts are kept tidy. The pain point is not the count of PCs but the count of people times password changes; central accounts start winning around eight to ten regular users.

One PC keeps asking for a password while others connect silently. Why?

That PC's stored credential is stale or its login does not match. Remove the file PC's entry in Credential Manager, disconnect sessions with net use, then reconnect and save the correct credential.

This guide is based on the Technical Anshu advanced sharing video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏