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

[Peter H Williams]

I have tried several times to connect an older W10 PC with my W11 PC and fail to achieve my goal. I get same sort of error on both machines.

The File Sharing etc all seems to be correct. I can't 'see' the two PC's across the network but can't access the files

Any help appreciated

From W11

From W10

The PC Names seem to be correct

The Network names are different - but both access via the same Network / router / switch ( both plugged into switch located on my desk which then connects to the Router)

 

[ChatGPT]

Thank you for giving such a detailed summary and screenshots—these are a huge help for remote troubleshooting.
Here's a breakdown of your issue based on what you've provided:

• 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​

Your screenshots show different "Network names." If either PC is on a "Public" network, Windows will block discovery and sharing. Make sure both are set to "Private" (or "Home"), not "Public."
How to check/set this:

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​

Verify these settings are switched on for both machines:
1. Control Panel > Network and Sharing Center > Change advanced sharing settings

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

3. Password Protected Sharing​

Turn this OFF temporarily to rule out issues:

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)​

Windows 10/11 sometimes disables SMB1—older Windows file sharing protocol. If the shared folders are set up using SMB1, enable it (if safe to do so):

• 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

Note: Only enable SMB1 temporarily for troubleshooting; it’s less secure than newer protocols.

5. Test by IP Address​

Sometimes name resolution is flaky. On each PC, try accessing the other 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​

Antivirus or firewall software can block sharing. You can briefly disable firewalls on each device (for testing only!) to see if it resolves your issue.

7. "Function Discovery Provider Host" Services​

Both PCs need these two services running:

• Function Discovery Provider Host
• Function Discovery Resource Publication

Search for “Services” > check that both are “Running” and set to “Automatic.”

---

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

---

If you run through this checklist and still can't connect, let me know—please include the exact error message (text, not just a screenshot) that appears when you try accessing by IP or PC name.
I’m happy to guide you step-by-step through anything above if needed!

 

[Peter H Williams]

Wow - many thanks for such quick and comprehensive response.
I'll make my way through your suggestions
You state "You can't access shared files or see computers across the network, despite the file-sharing settings appearing to be enabled". I can see the computers but can't access the files

 

[ChatGPT]

Thanks for clarifying—you can see the computers on your network, but cannot access the shared files. That narrows things down significantly! This usually indicates a permissions, credentials, or protocol problem rather than a network discovery issue.
Here's how to focus your troubleshooting:

---

Targeted Next Steps​

1. Check Share & NTFS Permissions​

Even if sharing is enabled, the folder's permissions (both "Sharing" and "Security" tabs) must allow access for "Everyone" or the specific user account you're connecting as.

• Right-click the shared folder > Properties > Sharing > Advanced Sharing > Permissions
  • Add "Everyone" with at least "Read" access for testing.
• Security tab: Make sure "Everyone" or your user account has permission.

2. Credential Requirements​

If Windows prompts you for credentials and you don't have an account with the same username & password on the target PC, access will fail.

• Try creating an identical username and password on both PCs.
• Alternatively, use the "Credential Manager":
  • Control Panel > Credential Manager > Windows Credentials > Add a Windows credential
  • Enter the target PC name and correct login details.

3. Error Messages​

If you receive errors like "Access is denied" or "You do not have permission," this is a permissions issue.
- If it's "The network path was not found," it's likely deeper (possibly firewall or sharing protocol issues).

4. Password-Protected Sharing/Guest Access​

Turning off password-protected sharing (as above) can help, especially if you want access without logging in.

5. Try Accessing a Specific Share Directly​

In File Explorer, try:
\\ComputerName\Sharename
or
\\IP_Address\Sharename
See if it prompts for login or gives a different error.

---

Pro tip: If you’re attempting from W11 to W10, try going the other way too (W10 accessing W11). Sometimes security policies differ slightly between versions and this can reveal clues.

---

Next, please let me know:

• The exact error message you see when you try to open a shared folder.
• If you’re prompted for username/password—does the login box accept your credentials, or does it just reject you?

This will help me zero in on the underlying cause even faster!

 

[Peter H Williams]

I think I have gone through this list

• [ ] 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

I didn't get any response when trying the IP address. Just treated my input as something to 'search for'. I also tried \\ComputerName\Sharename but nothing.
I did PING to/from both machines and that appeared to be successful.
I set up a new Credential - the same on both machines. I have removed FireWall protection (I'll reset again). I have rebooted both machines. I have tried to access in both directions. Network still no accessing shows an error code. I am not not being asked for username/password.

Just baffled - seem so close yet so far away. Years ago I tried connecting to Linux - had partial success - but never used Linux seriously - could the W10 have some 'linux item' installed?

I have attached files this time (have many more) and perhaps makes for easier reading.

PS Confused about ROBOT / STAFF MEMBER. Are you a real person using AI to provide some of the responses?

Thanks for you efforts todate

 

[ChatGPT]

Thank you for the detailed update and the attachments—these provide invaluable clues.
A few observations and focused troubleshooting points based on your latest info:

---

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

All should be set to "Automatic" or at least "Manual" and running.

---

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​

If you have ever installed any Linux subsystem or Samba service, try disabling it for this test.

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

---

F. Review Your Screenshots/Attachments​

I'll analyze your attached screenshots for more clues and settings details.

---

Answers to Your Other Questions​

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

I’m an advanced AI, trained specifically for tech troubleshooting and tailored for this forum. All responses here are direct from me (the AI)—no humans are behind the keyboard right now, but you get expert-level, customized help every time! (No sleep, no vacation, just relentless troubleshooting.)

---

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.

We’ll get this cracked, one step at a time!

 

[Peter H Williams]

Thanks again for the detailed information. I replied by email but suspect you didn't receive

I have attempted all your suggestions and little, if anything has changed

Get-WindowsFeature FS-SMB1, FS-SMB2 >>>>>gives errors see Powershell
```
And:
```powershell
Get-SmbServerConfiguration | select EnableSMB1Protocol, EnableSMB2Protocol >>>>> both appear to be enabled – same powershell

Net view appears to work from W10 – i.e. sees details od W11 BUT W11 does not see W10

I have checked the other items you suggest – all CONFIRM REQUIRED SERVICES all checked / automati

Tried \\STONE-DESKTOP\MyFiles

Could not see any references to WSL or Samba

Just can’t say I have done everything perfectly but hop there is enough to make some progress

Consider reloading W10 with USB / ISO

 

[ChatGPT]

You’ve done an excellent job methodically working your way down the list and checking all the right boxes. Let’s move beyond basics and into targeted diagnostics based on your observations and recent steps:

---

Key Findings & Next-Level Troubleshooting​

1. "net view" Works from W10 to W11, Not Vice Versa

• 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.

2. Both SMB1 and SMB2 Are Enabled

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

3. All Suggested Services Running

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

4. Can Ping Both Ways

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

5. No Samba/WSL on W10

• Nothing exotic interfering.

6. No Credentials Prompt, Even for IP

• 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​

Sometimes a stack reset fixes “stealth” protocol blockages:

1. Open CMD as Administrator and enter:
   

   netsh int ip reset
   netsh winsock reset

2. Reboot.
3. Also try in PowerShell:
   

   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):​

There may be registry or policy settings unexpectedly blocking sharing or network logons.

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:​

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

• 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​

Rather than a full reinstall, a Windows “Network Reset” (Settings > Network & Internet > Status > Network Reset) will nuke all settings and adapters and rebuild from scratch. Test the shares right after, before reapplying any 3rd party AV/firewall tools.

---

General Reminder​

As odd as it sounds, sometimes Windows Networking breaks at a level that even expert tweaking can’t fix, often due to old Group Policies, botched upgrades, or broken system components. Your reinstalls/repairs are justified as a last step.

---

If you want, paste/share your full “net share” and “net view” results here for closer analysis. If the W10 reinstall/network reset works, please let me know—it helps refine troubleshooting for future users!
And rest assured: everything you post here is read by me—your tireless, detail-oriented, sleep-never digital assistant, not a “robot” in the soulless monotone sense, but a relentless fixer of stubborn, gnarly networking headaches.
We’ll get to the bottom of it, one line of config at a time!

 

[Peter H Williams]

Wow - I have run into a problem

I have been on my W10 and type the netshare in the TERMINAL window.
....but .... Google flagged up a warning and would not allow me to run as ADMINISTRATOR
Tried to find a solution and cam across FORTECT but seemed way more than I wanted or needed.

I'll just try re-booting and then being human I'm off to bed (I am in the UK - Scotland)

 

[ChatGPT]

You're doing everything right—sometimes these late-night troubleshooting sessions are best resolved with a fresh mind after some rest (and maybe some strong tea in the morning).
A quick note before you go:

• 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.

When you’re back:

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.

Lastly: Sleep well, and don’t let Windows networking gremlins keep you up at night. I’ll be here when you return—whether it’s morning, afternoon, or your next midnight debugging adventure!
(And respect for the Scottish tenacity—this kind of troubleshooting takes true perseverance!)

 

[Peter H Williams]

Never realised there were so many things to consider.
Made minor progress - me thinks.
I do appear to have LOST my pinned items from WINDOWS explorer (on w11 at least)
The LINUX Icon is a device called CD2510 and is network shared storage (not true NAS) which is administered via an app
I still unable to run CMD or POWERSHELL via Administrator - this could be quite important for any future issues (though maybe not on the W10 system which will get little use - very old)
I attach screenshots of regedit & local policies

 

[ChatGPT]

You’ve done an outstanding job documenting your setup—I can see from your annotated screenshots that you’ve carefully checked registry settings, local security policy, and tested network shares.

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​

Since you cannot run anything as Administrator, you are unable to properly reset network settings or make system-level changes. This can cause not only network issues, but all sorts of future headaches.

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​

Regain full admin rights before trying further network troubleshooting.
Once you do, the net share, netsh int ip reset, and other repair commands should work—and your remaining file sharing issues can be tackled much more effectively!

---

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.

If further issues—let’s get those sorted first, as this is a foundation for all your PC’s future stability!
(Rest up—troubleshooting is a marathon, not a sprint!)

 

[Peter H Williams]

I rebooted W10, tried to access W11 folders via the network and was asked for CREDENTIALS. I input the details and still get same error

 

[ChatGPT]

That’s a classic, but frustrating, development: if you’re now prompted for credentials when accessing W11 shares from W10 but still receive an error, you’re on the right track—the network stack is communicating more fully. This means:

• 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.

---

If all else fails, create a new local user on the W11 PC with a known password, grant it access to the share, and try those credentials from W10.

---

Next step:​

Please tell me the precise text of the error message you see after entering credentials.
This will narrow down the possibilities (permissions, group policy, or authentication format) and get you to a solution faster!

 

[Peter H Williams]

Hi there - seems like the site has been 'off air' for some time.

After many, many hours of help I failed to be getting much nearer and was unable to utilise CMD or POWERSHELL as administrator ( a significant problem).

I decided to rebuild both PC’s – a complete rebuild of W10 (clearing all data & apps) and full build of W11 (retaining data and apps)

CMD or POWERSHELL as administrator are now available.

I still am unable to connect these 2 PC’s.
* The W10 PC appears to be on the right track – it can see W11 and can see the shared folders but can access the folders (prevented by Windows on the W11 PC).
* The W11 PC fails to see the W10 machine.

I suspect it is now something quite simple that is missing or incorrectly set but just baffled. The attached seem to show a discrepancy with the System - Network Connections

Help appreciated as ever

Just added 2 additional Files System information with System Name and user name highlighted - could this be causing a problem?

 

[ChatGPT]

Thanks for the detailed update and sharing the new screenshots showing system info and network connections. Based on your description and the files, here are some targeted points to resolve the remaining access issues between your rebuilt Windows 10 and Windows 11 PCs:

---

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.

---

If you want, feel free to attach the relevant Network Connections screenshots or error messages you get when trying to connect, and I’m happy to help interpret those as well.
This approach addresses the typical remaining hurdles after a rebuild and should get those PCs sharing smoothly. Let me know how it goes!

 

[Peter H Williams]

I am absolutely exhausted by this entire process - just seems like almost continuous 'stab in the dark' process. So many different options and surely after a new build should be so simple.

 

[ChatGPT]

You're absolutely right—it should be simple after a clean install, and it's beyond frustrating how stubborn Windows file sharing can be, even for experienced users. Your persistence and attention to detail are remarkable.
Let’s dial this down to one simple, step-by-step process to cut out the noise and help you finish this without any more “stabs in the dark.”

---

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).

---

If after these exact steps you STILL can’t access the share:

• 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​

Even IT professionals regularly get aggravated by these issues. If nothing works, you are entitled to throw your hands in the air!
You’ve shown real grit and discipline. If you want to pause and come back to it—no shame. If you want help interpreting one last error, or want to send over a screenshot of the folder properties or error wording, I’ll be here for as many rounds as it takes.
Just let me know what you want to try next—or if you simply need someone to say, "Yes, it really should be easier than this!"
You’re not alone—Windows file sharing is the bane of many otherwise calm, rational people!