How to Enter Network Credentials for File Sharing in Windows 11

Fix the "Enter network credentials" error in Windows 11 and 10. Step-by-step solutions for file sharing, including Credential Manager and SMB fixes.

You double-click a shared folder on your network, and instead of files, you're greeted by a login prompt that rejects every password you try. The "Enter network credentials" popup appears again, even though you're sure you typed the right password. Maybe you've tried three different variations. Maybe you've given up and resorted to USB drives.

I've been there—more times than I'd like to admit. And after years of troubleshooting Windows networks for clients and readers, I can tell you this: the fix is usually simpler than you think, but it requires understanding why Windows is asking in the first place.

This guide walks you through complete, step-by-step solutions for both Windows 11 and Windows 10. We'll cover the root causes, not just the quick fixes, so you can stop this error from recurring every time you reboot.


Close-up view of a mouse cursor over digital security text on display.

What Are Network Credentials and Why Does Windows Ask for Them?

Before we dive into fixes, let's clarify what's actually happening when you see that prompt.

Understanding the "Enter Network Credentials" Prompt

Network credentials, in the context of file sharing, are simply the username and password of an account on the computer you're trying to access. When you attempt to open a shared folder on another PC, Windows needs to verify that you have permission to read or write files there.

Here's the authentication flow:

Your PC (Client) → Requests access to shared folder → Target PC (Server) checks:
  → Does this user have permissions? → Yes → Access granted
  → No → Prompt for credentials → Verify → Access granted or denied

The prompt appears when Windows cannot automatically authenticate you. This happens for several reasons, but the most common is a mismatch between the account you're using locally and the account on the target machine.

One critical distinction: Microsoft account credentials (your email address, like user@outlook.com) are different from local account credentials (a username you created during Windows setup, like JohnPC or Admin). If the target PC uses a Microsoft account, you need to enter that full email address and its password. If it uses a local account, you need the local username and password.

Common Causes of Credential Errors on Windows 11 and 10

Through years of troubleshooting, I've narrowed down the culprits to five main causes:

  1. Incorrect account permissions – The account you're using doesn't have share-level or NTFS permissions on the target PC.
  2. SMB protocol settings – Windows 11 has stricter default security settings than Windows 10, particularly around guest access and older SMB versions.
  3. Stale saved credentials in Credential Manager – Windows remembers old passwords, and when they change, the saved version causes conflicts.
  4. Password protected sharing enabled – This setting forces credential entry even on trusted networks.
  5. Network discovery turned off – If discovery is disabled, Windows may not properly resolve the target PC's identity.

Windows 11, in particular, has tightened security defaults. Microsoft disabled insecure guest logons by default, which breaks connections to older NAS devices and some legacy hardware. We'll get to that in the advanced section.


Image displaying DeepSeek AI interface for messaging and search functionality.

How to Fix Network Credentials Error: Step-by-Step Solutions

Let's work through the fixes in order of likelihood. Start with the prerequisite, then move through each solution. Most users resolve this within the first two or three steps.

Prerequisite: Enable Network Discovery and File Sharing

Before anything else, make sure both PCs have network discovery and file sharing turned on. This sounds basic, but I've lost count of how many "credential errors" were actually just disabled discovery.

On Windows 11:

  1. Open SettingsNetwork & internetAdvanced network settingsAdvanced sharing settings.
  2. Under Private networks, ensure both Network discovery and File and printer sharing are turned on.
  3. Expand All networks and check the Password protected sharing section. We'll come back to this later.

On Windows 10:

  1. Open Control PanelNetwork and Sharing CenterChange advanced sharing settings.
  2. Same options, same layout—just a slightly different path to get there.

The password protected sharing toggle is particularly important. When enabled (the default), Windows requires credentials for every connection. When disabled, it allows guest access—which solves the prompt but introduces security risks. More on that in Solution 3.

Solution 1: Use the Correct Credentials (Microsoft vs. Local Account)

This sounds obvious, but you'd be surprised how often the issue is simply a formatting problem.

If the target PC is set up with a Microsoft account, the username is your full email address. Not John, not JohnDoe—the entire john.doe@outlook.com string.

If it's a local account, the username is whatever was created during setup. Here's a quick reference:

Target PC Account TypeCorrect Username FormatIncorrect Format
Microsoft accountjohn.doe@outlook.comJohn or JohnDoe
Local accountDESKTOP-ABC123\John or Johnjohn.doe@outlook.com
Local account (with PC name)PC_NAME\UsernameUsername alone (sometimes fails)
Pro tip: Use the format PC_NAME\Username when connecting to a local account. For example, if your PC is named OFFICE-PC and the username is Mike, type OFFICE-PC\Mike in the credential prompt. This explicitly tells Windows which machine the account belongs to, bypassing any domain resolution confusion.

To find your PC name: SettingsSystemAboutDevice name.

Solution 2: Clear or Add Credentials in Windows Credential Manager

Windows Credential Manager is a built-in vault that stores login information for network resources. When it holds outdated or conflicting credentials, you'll see the prompt loop even with the correct password.

Here's how to fix it:

Step 1: Open Credential Manager

  • Press Win + S, type "credential manager," and select the app.
  • Or go to Control PanelUser AccountsCredential Manager.

Step 2: Remove stale credentials

  1. Click Windows Credentials.
  2. Look for entries under Generic Credentials or Windows Credentials that match the target PC's name or IP address.
  3. Click the entry and select Remove.

I've seen cases where an old entry from a previous network setup—maybe from a different router or a changed password—kept overriding the new credentials. Removing it forces Windows to ask fresh.

Step 3: Manually add a Windows credential

If removing doesn't help, try adding the credential manually:

  1. In Credential Manager, click Add a Windows credential.
  2. Enter the target PC's IP address (e.g., 192.168.1.50) or hostname.
  3. Enter the username and password for the target PC.
  4. Click OK.

This is particularly useful when connecting to a NAS or a PC that doesn't appear in network discovery. The manual entry tells Windows exactly what to use, bypassing the discovery process entirely.

Solution 3: Modify Advanced Sharing Settings for Windows 11

If you're still stuck, the issue might be the password protected sharing setting. Disabling it allows guest access, which means no credential prompt—but it also means anyone on your network can access shared folders without authentication.

Security warning: Only do this on a trusted network (your home or office). On public Wi-Fi, this is a bad idea.

To disable password protected sharing:

  1. Go to Advanced sharing settings (same path as the prerequisite section).
  2. Expand All networks.
  3. Select Turn off password protected sharing.
  4. Click Save changes.

This is the quickest way to skip the credential prompt entirely. But I'll be honest: it's a band-aid, not a cure. If you need password protection (and you probably should), use Solution 1 or 2 instead.

Solution 4: Use the Computer's IP Address Instead of Hostname

Sometimes the issue isn't credentials at all—it's name resolution. Windows can't find the target PC by its hostname, so it fails to authenticate properly.

Step 1: Find the target PC's IP address

On the target PC, open Command Prompt and run:

ipconfig

Look for the IPv4 Address under your active network adapter. It'll look something like 192.168.1.50.

Step 2: Connect via IP address

On your current PC, open File Explorer and type:

\\192.168.1.50

Press Enter. If the shared folders appear, you've confirmed a name resolution issue. You can also connect directly to a specific share:

\\192.168.1.50\SharedFolder

This bypasses DNS and NetBIOS name resolution, which are common failure points on home networks with mixed devices or misconfigured routers.


Advanced Fix: Disable Insecure Guest Logins via Group Policy

If you're connecting to an older NAS device or a legacy Windows machine, you might hit a wall even with correct credentials. This is where Windows 11's stricter security defaults come into play.

What is the "Insecure Guest Logons" Policy?

Windows 11 disables guest logons in SMB by default. This is a security improvement—guest logons allow unauthenticated access, which is a vector for malware and unauthorized data theft. However, older devices (particularly NAS units from before 2017) often rely on guest access for SMB connections.

The SMB protocol has evolved significantly. SMB1 (from the Windows 95 era) is notoriously insecure and disabled by default in modern Windows. SMB2 and SMB3 are much safer, but some legacy devices still negotiate using SMB1 or expect guest logon support.

How to Enable Insecure Guest Logons (For Legacy Devices Only)

Strong warning: This weakens security. Only do this if you're connecting to a device that requires it, and disable it afterward.

Step 1: Open Group Policy Editor

Press Win + R, type gpedit.msc, and press Enter. (Note: Group Policy Editor is only available on Windows 11 Pro, Enterprise, or Education editions. If you're on Home, skip this section.)

Step 2: Navigate to the policy

Computer Configuration → Administrative Templates → Network → Lanman Workstation

Step 3: Enable the policy

  1. Double-click Enable insecure guest logons.
  2. Select Enabled.
  3. Click OK.

Step 4: Restart your PC for the change to take effect.

After connecting to your legacy device, go back and set this policy back to Disabled or Not Configured. Leaving it enabled exposes your system to potential SMB attacks.


How to Find Network Credentials for File Sharing on a NAS or Mac

The credential prompt isn't limited to Windows-to-Windows connections. NAS devices and Macs have their own quirks.

Accessing a Synology NAS

NAS devices like Synology have their own user accounts, completely separate from Windows accounts. The credentials you need are the ones you created in the NAS's operating system (DSM for Synology).

To find or create credentials:

  1. Log into your Synology DSM web interface.
  2. Go to Control PanelUser & Group.
  3. You'll see a list of users. If you haven't created a dedicated share user, do so now—using the admin account for everyday file sharing is a security risk.
  4. Use that username and password when Windows prompts for network credentials.

A dedicated share user with limited permissions is the right approach. I've seen too many home users running everything as admin and wondering why their NAS gets compromised.

Connecting from a Mac to a Windows Shared Folder

If you're on a Mac trying to access a Windows share, the process is slightly different but uses the same underlying credentials.

  1. In Finder, press Cmd + K to open Connect to Server.
  2. Enter the SMB path: smb://192.168.1.50/SharedFolder (replace with your IP and share name).
  3. Click Connect.
  4. When prompted, select Registered User and enter the Windows PC's credentials.

The credentials are the same as what you'd use on a Windows machine—the username and password of an account on the target PC. Mac doesn't care whether it's a Microsoft account or local account; it just passes the credentials through.


FAQ

Why does Windows keep asking for network credentials?

Windows repeatedly prompts for network credentials when it can't authenticate you automatically. The most common causes are: incorrect account permissions on the target PC, stale saved credentials in Windows Credential Manager, password protected sharing being enabled, or SMB protocol mismatches. Check Solutions 1 through 3 above to resolve each of these.

How do I find my network credentials for file sharing?

Your network credentials are simply the username and password of an account on the computer you're trying to access. If that PC uses a Microsoft account, the username is the full email address. If it uses a local account, the username is the local account name. You can also use the format PC_NAME\Username to specify the target machine explicitly.

How to skip enter network credentials?

The quickest way to skip the credential prompt is to disable Password Protected Sharing in Advanced Sharing Settings. Navigate to Advanced sharing settingsAll networks → select Turn off password protected sharing. This allows guest access without authentication. However, this is a security trade-off—only do this on trusted networks.

How to clear saved network credentials in Windows?

Open Credential Manager from the Control Panel, click Windows Credentials, and look for entries under Generic Credentials or Windows Credentials that match the target PC's name or IP address. Select them and click Remove. This clears any stale or conflicting saved credentials that might be causing the prompt loop.


Conclusion

The "Enter network credentials" prompt is frustrating, but it's rarely a dead end. In most cases, the fix comes down to one of three things: using the correct username format, clearing stale credentials from Windows Credential Manager, or adjusting the password protected sharing setting.

Remember that Windows 11 has stricter defaults than Windows 10. If you recently upgraded, that alone could explain why file sharing that used to work now demands credentials. Start with the simplest fix—double-checking your username format—before diving into Group Policy edits or disabling security features.

If you're still facing issues after trying these solutions, drop a comment below with your Windows version and the exact error message. Our community is here to help you get your files shared in no time.

← Back to Home