Windows cannot Access......<computer name>

• Both PCs run either Windows 10 or Windows 11.
• Both are wired to the same switch and router.
• You can't access shared files or see computers across the network, despite the file-sharing settings appearing to be enabled.
• You noticed the network names are different on each PC.

Common Causes (and Solutions) for "Windows Cannot Access" Network Errors​

1. Network Type: Private vs Public​

1. Go to: Settings > Network & Internet > Ethernet (or Wi-Fi)
2. Click your network.
3. Ensure “Network profile type” is set to Private.

2. Enable Network Discovery & File Sharing​

1. Turn ON:
   • Network discovery
   • File and printer sharing
   • Allow Windows to manage homegroup connections

3. Password Protected Sharing​

1. Same place as above (“All Networks” section)
2. Set "Turn off password protected sharing."

4. Check for SMB1 Support (especially between W10 and W11)​

• Go to: Control Panel > Programs and Features > Turn Windows features on or off
• Check "SMB 1.0/CIFS File Sharing Support"
• Click OK and reboot

5. Test by IP Address​

• Open File Explorer
• In the address bar, type:
  \\<IP_Address_of_other_PC>
  If this works, the issue is probably related to name resolution (NetBIOS, DNS).

6. Firewall Settings​

7. "Function Discovery Provider Host" Services​

• Function Discovery Provider Host
• Function Discovery Resource Publication

Handy Quick Checklist:​

• [ ] Both PCs set to Private network
• [ ] Network discovery & file/printer sharing ON
• [ ] Password-protected sharing OFF (for testing)
• [ ] Try IP address access (\\192.168.x.x)
• [ ] Temporarily disable AV/firewall for a test
• [ ] Check SMB 1.0 support if shares are old
• [ ] Both Function Discovery services running

• [ ] Both PCs set to Private network
• [ ] Network discovery & file/printer sharing ON
• [ ] Password-protected sharing OFF (for testing)
• [ ] Try IP address access (\\192.168.x.x)
• [ ] Temporarily disable AV/firewall for a test
• [ ] Check SMB 1.0 support if shares are old
• [ ] Both Function Discovery services running

1. Network Visibility vs. Access​

• Seeing the computers but not even being prompted for credentials (and not even able to browse to them via \\IP_or_Name\Sharename) suggests:
  • Network protocols may be disabled (SMB1, SMB2/3).
  • A "hard block" (policy, service not running, etc. is interfering beyond just permissions.

2. Pinging Success, File Access Failure​

• Since ping works both ways, basic TCP/IP between the PCs is intact—firewall and routing are likely fine.

3. No Login Prompt​

• If you never even see a username/password popup, Windows often can’t reach the SMB service at all, which strongly hints at either SMB being disabled, or sharing subsystems not functioning.

4. Potential "Linux item" on W10​

• If you ever installed something like "Windows Subsystem for Linux (WSL)", Samba, or another third-party networking tool, it could have tweaked firewall or sharing settings. Usually that doesn’t break Windows File Sharing, but strange things can happen.

Immediate Recommendations (with Next Diagnostic Steps)​

A. Check that SMB1 AND SMB2 are enabled​

1. On both Windows 10 and 11:
   • Run optionalfeatures.exe (Windows Features)
   • Scour for BOTH:
     • SMB 1.0/CIFS File Sharing Support (should at least have "Automatic Removal"/"SMB Direct" checked)
     • SMB Direct
   • Ensure at least SMB1 or SMB2/3 is enabled on both (usually SMB1 is only needed for very old devices, but for troubleshooting, test with it on).
2. Command line check:
   In PowerShell (as admin), run:
   Get-WindowsFeature FS-SMB1, FS-SMB2
   And:
   Get-SmbServerConfiguration | select EnableSMB1Protocol, EnableSMB2Protocol

B. Confirm Required Services​

• Double-check these are Running (Start > run services.msc):
  • Function Discovery Provider Host
  • Function Discovery Resource Publication
  • Server
  • Workstation
  • TCP/IP NetBIOS Helper
  • SSDP Discovery
  • UPnP Device Host

C. Execute "net view" / Diagnostics​

• On both PCs, open Command Prompt (as admin) and type:
  net view \\OtherPCName
  and
  net view \\IP_of_OtherPC
• Report the exact error/code you see.
• Also try:
  net share
  to see what shares are indeed published.

D. Temporary Test: Enable Guest on One Share​

• For TEST ONLY, share a folder and set its permissions for "Everyone" (full control) and enable access without password.
• Try accessing specifically:
  \\PCName\ShareName
  in File Explorer.

E. Review And/Or Remove Any WSL or Samba​

• In Windows Features, uncheck "Windows Subsystem for Linux."

F. Review Your Screenshots/Attachments​

Answers to Your Other Questions​

Are you a real person using AI to provide some of the responses?

Click to expand...

Next Steps​

• Try the SMB and services steps above.
• Run and report results of net view \\OtherPCName.
• Let me know if you find anything odd in “Windows Features” or services list.
• I’ll review your attached screenshots and supplement any missed points shortly.

Key Findings & Next-Level Troubleshooting​

• This means your Windows 10 PC publishes shares/services on the network, but W11 is unable to enumerate them. This is not a pure firewall or credential issue; it points toward a service, protocol, or advanced permission/policy problem on the W10 box.

• That rules out basic protocol support (as long as the services are running).

• You’ve checked vital file sharing and discovery services; so unless they’re failing to start, that’s not the issue.

• Confirms the underlying TCP/IP stack and routing is solid.

• Nothing exotic interfering.

• Windows is not even able to “see” the file-sharing stack on W10 from W11—which is unusual.

Three Advanced Diagnostics & Fixes​

A. Check for Broken Shares or Permissions​

• On Windows 10, open a Command Prompt and type:
  net share
  • List the shares and see if anything unusual stands out; try removing and recreating one with generic Everyone permissions for a new test share.

B. Reset Windows 10’s Networking Stack Completely​

1. Open CMD as Administrator and enter:
   
   Code:

   netsh int ip reset
   netsh winsock reset

2. Reboot.
3. Also try in PowerShell:
   
   Code:

   Remove-WindowsFeature FS-SMB1
   Add-WindowsFeature FS-SMB1

   (Ignore any errors if the commands don’t work verbatim—optional for SMB1.

C. Remove All Saved Credentials and Network Drives​

• On W10, go to Control Panel > Credential Manager and remove any Windows Credentials relating to the target computers.
• Unmap all shared drives or “remembered” network connections (File Explorer > This PC > right-click network locations > Disconnect).

Policy/Registry-Level Fix (sometimes needed after years of OS use/misconfig):​

1. Run the following on W10:​

• Open regedit and navigate to:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
  and
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
• Make sure no odd policies exist; if entries like RequireSecuritySignature or SMB1 are present, set them to 0.

2. Also check for:​

• Ensure values like restrictanonymous are 0.
• If you see a forceguest DWORD, set it to 0 as well.

3. Check Local Security Policy (secpol.msc):​

• Local Policies > Security Options
  • “Network access: Let Everyone permissions apply to anonymous users” = Enabled
  • “Network security: LAN Manager authentication level” = “Send LM & NTLM responses”
  • “Network security: Minimum session security for NTLM SSP” = Not enabled for both clients and servers

If You’re Still Stuck… Consider Network Reset Before Reinstall​

General Reminder​

• The command you want to run is net share, not netshare—just enter it in a Command Prompt (cmd.exe), not in PowerShell or the new Windows Terminal, and you don’t need “Google” involved at all.
• If you get a security prompt (“run as administrator”), let it run—this is normal and not a risk if you're on your own system.
• Avoid “FORTECT” or similar “repair” tools—they’re often unnecessary and may cause more issues than they solve.

1. Open plain “Command Prompt” (cmd.exe), right-click > “Run as administrator.”
2. Type:
   net share
3. Paste the results here or let me know what shares it lists and if any errors appear.

Key Insights from Your Screenshots​

1. Security Policy & Registry:
   • “Let Everyone permissions apply to anonymous users” is now enabled, which is helpful.
   • “LAN Manager authentication level” is correctly set to “Send LM & NTLM responses”.
   • Registry settings like forceguest and restrictanonymous are set to 0 (good; this is permissive for file sharing).
   • RequireSecuritySignature is 0 for both LanmanWorkstation and LanmanServer, which is correct for allowing less strict SMB connections.
2. Network Devices:
   • The “Linux” device is actually your networked shared storage. It’s not relevant to the PC-to-PC issue but helpful to know it is separate from Windows file sharing.
3. Credentials:
   • No Windows credentials are saved, so credential caching or corruption is not interfering.
4. Terminal/Command Issues:
   • You cannot run CMD or PowerShell as Administrator—this is a critical problem. Most network resets and repairs require administrative rights.
   • Commands such as netsh int ip reset and netsh winsock reset failed for lack of elevation ("requested operation requires elevation"). Many fixes won't work unless you gain Administrator access.
   • The PowerShell commands for SMB1 are not recognized—these are valid only on Windows Server, not regular Windows 10.

Major Next Step: Fix Admin Rights Issue​

1. Try Enabling Admin Prompt (UAC)​

• Right-click on the Start button > Windows Terminal (Admin) or Command Prompt (Admin) or PowerShell (Admin)
• If this does not show up, your user account might not have admin rights.

2. Check User Account Type​

• Go to Settings > Accounts > Your info.
  • Does it say "Administrator" under your account name?
  • If it says "Standard user," you must log in as (or enable) an account with administrator rights.

3. If All Else Fails: Enable Hidden Administrator​

• If you can get a Command Prompt (even non-admin), try:
  net user administrator /active:yes
  • Log off and switch to the built-in “Administrator” account, then try your network commands and sharing tasks there.

4. If UAC/permissions are broken system-wide​

• Consider doing a Repair Install of Windows 10. Download the Win10 ISO from Microsoft, run Setup.exe from within Windows and choose “keep your files and apps.” This can repair low-level admin and networking issues without wiping your data.

Why Your Shares Still Aren’t Working​

• Until you can run commands and tools as Administrator, many fixes simply won’t “stick”—especially for file sharing and networking.
• Chances are, the underlying problem is a corrupted or misconfigured Windows security policy, possibly from an old misapplied setting or failed software install.

Extra: Lost Pinned Items​

• If your Windows Explorer pins disappeared, it could be temporary corruption—restart may help. If not, you can manually “pin” folders back by right-clicking and choosing Pin to Quick Access.

Bottom Line​

When you’re ready:​

• Confirm if you can open a Command Prompt or Powershell window “As Administrator.”
• Let me know if your account type says “Administrator.”
• If not, try enabling the built-in Administrator account.

• The PCs are talking over SMB.
• Authentication is taking place, but not being accepted (there’s a permissions, username/password, or share security issue).

Immediate Steps To Diagnose and Fix​

1. Use Matching Account Credentials​

• The username/password you enter must match exactly (W11 PC's local username and password) or an authorized Microsoft account login, depending on how you sign into W11.
  - Hint: If your W11 device uses a PIN or a Microsoft Account, you should enter the full Microsoft email address and the corresponding password.
• If you have a local account on W11 (not a Microsoft account), make sure the local account is enabled and has permission on the shared folder.

2. Check Permissions on the Shared Folder (W11)​

• Right-click the shared folder on W11 → Properties > Sharing > Advanced Sharing > Permissions:
  • Add “Everyone” with “Read” or “Full Control” as a test.
• Go to Security tab:
  • Ensure “Everyone” or your W10 login user has Read at a minimum.

3. Password-Protected Sharing Setting​

• On W11:
  • Control Panel > Network and Sharing Center > Change advanced sharing settings
  • Under “All Networks,” temporarily set “Turn off password protected sharing”.
  • Click Save Changes.

4. Try Accessing with IP Address​

• From W10:
  \\<W11_IP_Address>\<ShareName>
• If you get a credentials popup, enter W11_PC_NAME\username and the correct password.
  • For example: MY-WIN11-PC\john

5. Double-Check Windows Credentials​

• On the W10 PC:
  • Go to Control Panel > Credential Manager > Windows Credentials
  • If any entries for the W11 PC exist, remove them and, if needed, re-add new credentials with the correct username/password.

6. What Is the Exact Error Message?​

• Note the exact error code or text when you enter credentials, e.g.:
  • “Access is denied”
  • “The user name or password is incorrect”
  • “You might not have permission to use this network resource”
• This helps pinpoint if it’s a permissions, authentication, or trust issue.

Next step:​

1. Workgroup and System Name Consistency​

• Double-check both PCs are on the same Workgroup name (not just network name).
• The screenshots show system names and user names are different—this alone shouldn't block network sharing, but consistent naming can avoid confusion.
• On both PCs:
  Right-click This PC > Properties > Advanced system settings > Computer Name tab > Click Change
  Make sure the Workgroup name is identical (commonly "WORKGROUP").

2. Networking Profile and Discovery​

• Confirm Private Network profile is active on both machines.
• On Windows 11, recent updates changed the way network profiles and discovery behave, so:
  • Check Settings > Network & internet > Ethernet/Wi-Fi > Network Profile is set to Private.
  • Enable Network discovery and File and printer sharing under Advanced Sharing Settings in Control Panel.

3. Windows Firewall and Third-Party Security​

• Temporarily disable Windows Firewall on both PCs to test connectivity.
• If you have third-party antivirus/firewall, disable it temporarily as these often block SMB sharing.

4. SMB and File Sharing Features Enabled​

• Windows 11 sometimes has SMB 1.0 disabled by default.
• On both PCs, Control Panel > Programs and Features > Turn Windows features on or off
  Ensure SMB 1.0/CIFS File Sharing Support is enabled (for testing, but prefer SMB2/3).
• Also verify File and Printer Sharing for Microsoft Networks is enabled on the network adapter:
  • Go to Network Connections > right-click your adapter > Properties > look for that item and ensure it's checked.

5. Share Permissions and NTFS Permissions​

• On W11 PC, verify the shared folders permissions:
  • Right-click shared folder > Properties > Sharing > Advanced Sharing > Permissions:
  • Add “Everyone” group with read/write permissions for testing.
  • Under the Security tab, check NTFS Permissions and add “Everyone” with appropriate access (read or modify).
• Try accessing shares explicitly via IP address, e.g. \\192.168.x.x\Sharename.

6. User Credentials for Access​

• If your Windows 11 user account is a Microsoft account login (email address), sometimes Windows requires credentials in the full format including the computer name or domain.
• When prompted for credentials from W10, try entering:
  Windows11PCName\YourUsername
  with the password.
• Alternatively, create a new local user on Windows 11 with a simple username/password and give that user access to shares for test purposes.

7. Why Windows 11 Does Not See Windows 10​

• This could be caused by Network Discovery issues on Windows 11 or Firewall rules specifically blocking inbound SMB from your W10 PC.
• On Windows 11, enable:
  • Function Discovery Provider Host and Function Discovery Resource Publication services are running.
  • Make sure Windows Defender Firewall allows File and Printer Sharing (SMB-In) rules enabled for Private profiles.

8. Double Check Network Reset​

• If you are comfortable, on both PCs perform a Network Reset:
  • Settings > Network & Internet > Status > Network Reset
  • Reboot both systems afterward and re-validate sharing settings.

Summary​

• Harmonize workgroup names on both systems.
• Confirm Private network profile and enable network discovery & file sharing.
• Validate all sharing and NTFS permissions on the W11 PC.
• Confirm firewall and antivirus allow sharing traffic.
• Explicitly access shares with IP and correct credentials.
• Restart File Sharing and Discovery services on Windows 11.
• Consider using local user accounts for testing credentials.

Streamlined “Last Resort” Sharing Setup​

Step 1: BOTH PCs — Set to Private Network​

• Settings > Network & Internet > Ethernet/Wi-Fi > Network Profile: Set as Private.

Step 2: BOTH PCs — Enable Discovery and Sharing​

• Control Panel > Network and Sharing Center > Advanced sharing settings:
  • Network discovery ON
  • File and printer sharing ON
  • Turn OFF password protected sharing (for testing)

Step 3: W11 — Create a Simple Test Share​

1. On Windows 11, right-click Documents or create a new folder on your desktop.
2. Click Properties > Sharing > Advanced Sharing.
3. Tick Share this folder. Click Permissions.
4. Add “Everyone” with Full Control (for test only).
5. Go to Security tab. Add “Everyone” with at least Read permission.

Step 4: W10 — Access by IP (Not by Name)​

• Open File Explorer and in the address bar type:
  \\W11IPAddress\ShareName
  E.g. \\192.168.1.15\TestFolder

Step 5: If Prompted for Credentials​

• Try:
  W11ComputerName\Username
  and your W11 user’s password.
• As a further test, create a new LOCAL user on W11 with a simple password and try credentials for that user.

Step 6: Firewalls​

• Temporarily turn off Windows Defender Firewall on both PCs (Settings > Update & Security > Windows Security > Firewall & network protection).

• It almost always means (1) the Firewall is blocking it, (2) SMB/CIFS is disabled, or (3) some group policy or network service is not running.
• At that exact point, either a remote connection walkthrough or hands-on help may become appropriate because one critical piece is unexpectedly “non-default” even after rebuild.

Don’t Let Windows Networking Get You Down​